Skip to content
Databay
  • Docs
Network statusGet startedStart
Choose by origin

One gateway. Three network origins.

Match the route to the source network the destination requires. Targeting and session controls come next.

  • ISP / residentialPremium Residential · Residential Flex
  • Carrier networkMobile
  • Hosting networkDatacenter
Shared entry pointgw.databay.co:8888The credential selects the route.
Four proxy products

Compare targeting depth, session limits, and product fit.

Compare specifications
Premium ResidentialISP-origin · granular controlsShared rotating pool; not a static ISP allocationResidential FlexResidential · country or continentBudget shared pool with a shorter sticky-session limitMobileCarrier-network originShared rotating pool; not a device, SIM, or exclusive IPDatacenterHosting-network originShared, rotating, bandwidth-billed; not dedicated or static
Compare networksUse cases
Pricing guide

Price the complete order.

The unit rate is one term. Review the minimum, total, and traffic validity together before checkout.

$/GBUnit ratePrice per GB
×Minimum bandwidthOrderable allowance
=Payable totalDue at checkout

Traffic validity stays with every plan.

Choose a rate card

Pick the network origin first, then review its current minimum, total, and validity.

Premium ResidentialISP-origin · granular location controlsSee pricingResidential FlexResidential-origin · country or continentSee pricingMobileCarrier-network origin · country or continentSee pricingDatacenterHosting-network origin · country or continentSee pricing

Build

  • Documentation
  • API reference
  • Integration guides

Free tools

  • All free tools
  • Proxy format converter
  • Free proxy list
  • Proxy checker
  • What is my IP?

Learn

  • Proxy basics
  • Platform workflows
  • Blog
  • Research
  • FAQ

Company

  • About
  • Press
  • Discord community
Trust & safety
  • Trust center
  • Report abuse
Navigation

Explore Databay

Products

One gateway; choose the exit origin, targeting depth, and session behavior.

Premium ResidentialISP-origin · granular controlsResidential FlexResidential · country or continentMobileCarrier-network originDatacenterHosting-network origin
Compare networksUse cases
Pricing

Current minimum, payable total, and validity by network.

Premium ResidentialISP-origin · granular location controlsResidential FlexResidential-origin · country or continentMobileCarrier-network origin · country or continentDatacenterHosting-network origin · country or continent
Resources

Build

  • Documentation
  • API reference
  • Integration guides

Free tools

  • All free tools
  • Proxy format converter
  • Free proxy list
  • Proxy checker
  • What is my IP?

Learn

  • Proxy basics
  • Platform workflows
  • Blog
  • Research
  • FAQ

Company

  • About
  • Press
  • Discord community

Trust & safety

  • Trust center
  • Report abuse
Network statusCompare network pricing before ordering
Get started
All documents in release v1

Law Enforcement Guidelines

Archived release: v1. Updated: September 17, 2026.

Use your browser’s print command to print or save this complete document as a PDF.

  1. 1. Scope and Contact
  2. 2. Information Needed to Assess a Request
  3. 3. Authentication, Authority, and Scope
  4. 4. Available Records and Preservation
  5. 5. Emergencies and Mandatory Reporting
  6. 6. Customer Notice and Account Access

1. Scope and Contact

These guidelines describe the handling of government and law-enforcement requests directed to WATTENNE INTERNATIONAL LLC, a Wyoming limited liability company operating Databay. They should be read with the Privacy Policy and Terms of Use. They do not enlarge an authority's legal powers or the Company's authority to disclose information.

Authorities may use the existing abuse@databay.com contact to submit a request for review or seek intake instructions. This is an intake channel, not a designation of an agent for service of process or an agreement that email is legally sufficient service. Address process to WATTENNE INTERNATIONAL LLC and meet the service and jurisdictional requirements applicable to it. The channel does not offer a guaranteed emergency response or response deadline.

2. Information Needed to Assess a Request

A request should identify the requesting agency, jurisdiction, official's name and role, independently verifiable official contact details, case reference, and the legal basis for the request. Supply the relevant signed legal process or explain the legal basis for a request made without compulsory process.

Describe the account or incident using specific identifiers, the record categories sought, relevant dates and timezone, and any applicable deadline. Explain any requested confidentiality restriction and provide its legal basis and duration. Limit requests to information relevant to the matter. Avoid sending unnecessary sensitive information or unlawful material.

3. Authentication, Authority, and Scope

Before disclosing non-public information, we assess the requester's identity, the authenticity of the request, the applicable legal authority and service requirements, and the scope of information lawfully available for disclosure. An official-looking email or a customer's acceptance of our Terms does not by itself authorize disclosure.

We disclose records when required by valid, applicable legal process or when another applicable legal basis permits the particular disclosure. Communications-privacy restrictions, including restrictions distinguishing communications content from subscriber or other non-content records where applicable, must be respected. A general business interest or request from an authority does not override those restrictions.

Requests from outside the United States require assessment of jurisdiction, applicable privacy and international-transfer requirements, and any appropriate cross-border legal mechanism. They are neither automatically enforceable nor automatically invalid because of their origin.

Where appropriate and permitted, we may seek authentication, clarification, narrowing, or further legal review. We do not promise to challenge every request. Disclosure is limited to responsive information actually held and lawfully subject to the request or other applicable disclosure basis.

4. Available Records and Preservation

The Privacy Policy describes our records and retention commitments. Company-operated proxy systems do not inspect, log, store, or monitor customer traffic payloads. Account, authentication, billing, verification-reference, operational, or abuse-report information may differ in availability and retention. Third-party providers may hold separate records; we cannot promise access to records that we do not control.

The production gateway's request logs do not record the customer's final exit proxy IP or a per-connection mapping to it. An exit IP address and incident timestamp therefore do not guarantee that we can identify a customer or downstream user. We do not promise complete connection histories, exit-address mappings, or records not actually held.

We preserve identified existing records as required by applicable law or a valid preservation obligation, and may preserve relevant records when otherwise lawful and necessary. Preservation requests should specify the records, identifiers, time range, legal basis, and required period. Preservation is distinct from disclosure and does not itself authorize release of the preserved records. Applicable legal requirements govern the scope, duration, extensions, and release of a hold.

These guidelines do not promise to create missing records, reconstruct deleted records, monitor future traffic, or retain all customer data indefinitely. They do not limit an obligation independently imposed by applicable law.

5. Emergencies and Mandatory Reporting

For an emergency request, explain the nature and immediacy of the danger, the people at risk if known, why the requested information is necessary, and why ordinary process cannot be obtained in time. Supply a verifiable official contact for follow-up. Labeling a request an emergency does not alone establish authority to disclose.

We may make an emergency disclosure only where applicable law permits it and its conditions are met, including any required good-faith belief concerning danger of death or serious physical injury and the need for disclosure without delay. We also comply with applicable mandatory reporting and associated preservation obligations, including child-exploitation reporting where legally required. These are distinct legal grounds and are not a promise of routine voluntary disclosure.

6. Customer Notice and Account Access

We do not routinely notify customers that an official inquiry has been received. We provide notice when applicable law requires it, subject to lawful confidentiality restrictions. We also honor any prior notice or privacy commitment that continues to govern the relevant information or customer relationship; these guidelines do not retrospectively replace that commitment or create new permission to disclose historical data.

Receiving an inquiry does not automatically suspend an account and is not itself proof of misuse. Independently substantiated abuse, credible risks requiring proportionate interim restrictions, or applicable legal obligations may justify action under the Terms and Acceptable Use Policy.

From the blog

Latest from the blog

Setup guides, benchmarks, and research notes on proxies and web data collection.

Aug 23, 202615 min read

AstroProxy Alternatives: Architecture and Migration Guide

Compare AstroProxy alternatives by port architecture, targeting, rotation, pricing, compliance, and measured migration fit using dated official sources.

Databay Research Team
Read
Aug 23, 202610 min read

California Proxy: Privacy-Minimized Localization QA

Choose and verify a California proxy for authorized localization QA with a privacy-minimized protocol that separates an IP network signal from precise...

Databay Research Team
Read
Aug 23, 202612 min read

Comcast Residential Proxy: AS7922 Evidence and Test Plan

Evaluate a Comcast residential proxy with Databay's published AS7922 sample, live-supply limits, route verification, and a provider-neutral purchase test.

Databay Research Team
Read

One account. Four proxy pools.

Compare Premium Residential, Residential Flex, Mobile, and Datacenter, then review the current product-specific pricing page before ordering.

Get startedExplore proxies

Pricing, order minimums, and traffic validity vary by product.

Databay logo

Four shared proxy products across residential, mobile carrier, and datacenter network origins. Current commercial terms are published on each product-specific pricing page.

Get in Touch

hello@databay.comsupport@databay.comsales@databay.com
Legal notices: 30 N Gould St Ste N, Sheridan, WY 82801, USA

AI-readable files

  • llms.txt
  • llms-full.txt

Company

  • About
  • Trust Center
  • Editorial Standards
  • Press Area
  • Partners
  • Legal Documents
  • Report Abuse

Use Cases

  • Web Scraping
  • E-commerce
  • Travel
  • Cybersecurity
  • Market Research
  • Reviews Monitoring
  • Website Monitoring
  • Social Media
  • Ad Verification

Proxy products

  • Compare Proxy Products
  • Premium Residential Proxies
  • Residential Flex Proxies
  • Mobile Proxies
  • Datacenter Proxies
  • Proxy Reseller Program
  • Free Proxy List
  • Free Proxy Checker
  • What Is My IP?

Product pricing

  • Premium Residential Pricing
  • Residential Flex Pricing
  • Mobile Pricing
  • Datacenter Pricing

Integrations

  • Databay X Incogniton
  • View All →

Resources

  • Proxy Basics
  • Platform Workflows
  • Free Tools
  • Proxy Format Converter
  • API Documentation
  • Documentation
  • FAQ
  • Blog

© 2026 WATTENNE INTERNATIONAL LLC. All rights reserved.

MastercardVisaWire TransferWeChat PayEthereumLitecoin