Evidence register · Public record

Claims should leave a trail

"Ethically sourced", "verified every 5 minutes", and "99.9%+ uptime" are useful only when they can be checked. Follow the evidence from residential consent to research data, network health, and published policy.

Opt-in Paid, consent-based residential supply
1,000 IPs in the public reputation study
8,000+ Customers served since 2022
99.9%+ Public uptime target
Sourcing ethics

IP Sourcing Ethics & Consent Model

Databay states that its residential supply is provided through opt-in partner applications: participants are shown a consent flow describing bandwidth sharing before traffic is enabled. This page is Databay's current sourcing disclosure, not an independent certification of every endpoint. Prospective customers with contractual sourcing requirements should request the applicable diligence materials and terms before purchasing.

  • Opt-in partner appsIPs enter the pool through partner applications that show a consent screen before any traffic is routed.
  • Plain-language consentSharing is explained in one screen, not buried in a EULA.
  • Paid participationParticipants are compensated for the bandwidth they share: suppliers, not products.
  • Revocable anytimeClosing or uninstalling the app removes the device from the pool, with no penalty.

We accept residential supply only from partners that represent it is gathered through applications with a visible consent step, never from malware, rootkits, or hidden installers. Because consent is revocable, pool membership fluctuates naturally. That churn is the cost of doing this honestly.

The demand side is policed too. This page is the long-form explanation behind every "ethically sourced" claim elsewhere on the site; these are the enforcement points behind it:

  • EnforcedCustomers agree to the Acceptable Use Policy before they can place an order; it explicitly bars credential stuffing, fraud, piracy, CSAM and a long tail of other abuse patterns.
  • EnforcedDatabay states that abuse reports are reviewed through its Trust & Safety contact.
  • EnforcedAccounts that route abusive traffic through volunteers' connections are terminated.
Published measurements

First-Party Research

We publish original measurements, not aggregated marketing claims. The centerpiece is our residential IP reputation study: we took 1,000 residential IPs across 25 of the world's largest residential ASNs and ran every one of them through six free IP-reputation databases, plus a Cloudflare-Free cross-verification origin.

1,000 Residential IPs tested
25 Residential ASNs
6 Reputation databases
0 Cloudflare threat score, all captures

The malice-focused feeds (Tor exit list, Spamhaus DROP, ASN-drop) flagged none of the sample; Spamhaus ZEN listings were dominated by PBL policy codes: the "this is a residential line" designation, not a malice verdict. The same open-methodology standard applies to the free proxy list: every entry is re-probed every 5 minutes, and stale entries are dropped rather than left to inflate counts.

Verify our numbers yourself:

Editorial standard

Who writes this site

Every guide, benchmark and dataset note on this site ships under one collective byline: the Databay Research Team. The engineers behind that byline work with the network they write about - the same probe pipelines, reputation scans and free-proxy dataset that customers query - and every published number links back to the method that produced it. No individual personas, no borrowed credentials: the byline is the team, and the proof is the published methodology.

Databay Research Team

Engineering & Research

The same group that runs the probe pipelines and the free proxy list dataset researches, writes, and maintains every guide on this site. Where a page states a number, the harness that produced it is documented on this page or linked from the article itself.

The working output is public: the technical guides, the IP-reputation study, and the probe-pipeline methodology. Corrections and factual disputes go to hello@databay.com. We update the article and its modified date rather than quietly editing a number.

Editorial standards

The standard published pages are held to

What must be executed for real before it ships, how dates behave, and what happens when we get something wrong.

  • Evidence policyA how-to claim ships with executed output: pinned tool versions, recorded transcripts, runnable scripts. Where a transcript is constructed rather than captured, the article says so in place.
  • Numbers keep their methodPublished measurements link the methodology and, where possible, the raw dataset behind them. A number whose method we cannot publish does not go on the site.
  • Honest datesPublished and updated dates change only with substantive edits, each recorded in a change summary. "Last tested" marks when a procedure was actually re-executed, never a cosmetic refresh.
  • Cadence over volumeArticles publish when the work behind them is done, not to fill a calendar: no bulk same-day drops, and a refreshed article states what changed.
  • Hard linesNo fabricated measurements, testimonials, credentials, or review scores, and no self-serving review markup anywhere on the site. Build checks enforce image alt text and flag duplicated boilerplate across pages.

Corrections: factual disputes go to hello@databay.com. When a report holds up, we correct the article and update its modified date rather than quietly editing a number.

Operational health

Network Status

We publish real-time network health at status.databay.com: uptime, incident history and per-service availability. The network targets 99.9%+ uptime; the status page is where that figure is continuously kept honest.

99.9%+ Uptime target, measured continuously
24/7 Incident history & per-service availability
status.databay.comLive uptime, incidents and per-service health. No login, no gate.
Third-party record

Independent Signals

Don't take our word for any of this: the third-party surfaces are linked directly, unfiltered.

Verify us, then try us

Read the policies, download the dataset, and check live status before putting the network itself to the test.

Every register entry above links to its primary source.