US and EU Data Residency for Static IP Proxy Traffic

Some customers cannot allow traffic or logs to leave specific jurisdictions. Compliance frameworks, government contracts, and enterprise security policies often require that all network traffic and metadata stay inside defined regions.

QuotaGuard offers US and EU Data Residency so your static IP proxy traffic stays entirely within your chosen region.

Who this is for

• Teams under US or EU government or enterprise contracts that prohibit cross-border routing
• Companies with SOC 2, HIPAA, GDPR, or internal data localization requirements
• Vendors handling PII, financial, or healthcare data that must remain domestic or in region
• Customers whose firewalls, DLP rules, or vendor agreements explicitly require US-only or EU-only egress IPs

What you get

• Region-locked routing. All proxy traffic stays inside either US-based or EU-based infrastructure, per your choice.
• Regional static IPs. Static outbound IPs are allocated per region, with no cross-region routing or failover.
• Log residency. Connection logs remain in-region according to your configured retention settings.
• No app changes. Keep using your existing QuotaGuard Static or Shield configuration. We adjust routing, not your code.
• Proven platform. Same infrastructure used by thousands of Heroku, AWS, and other cloud customers, now with regional boundaries.

US Data Residency

Select the US region to keep all proxy traffic, static IPs, and logs inside US-based infrastructure.

Typical use cases

• US government or public sector contracts that require domestic routing
• US‑headquartered companies whose policies prohibit non‑US routing
• Applications subject to HIPAA, PCI DSS, or SOC 2 where US‑only egress simplifies audits

EU Data Residency

Post-Schrems II concerns about EU–US data transfers mean some teams prefer routing that never leaves the EU. Our EU Data Residency option keeps egress and logs inside EU infrastructure, which simplifies conversations with DPOs and privacy counsel.

Select the EU region to keep all proxy traffic, static IPs, and logs inside EU-based infrastructure.

Typical use cases

• Organizations subject to GDPR and EU data localization guidance
• Customers who must keep traffic inside EU-based data centers due to Schrems II-style concerns
• Vendors with contracts that mandate EU-only endpoints or EU-only processing locations

How it works

• You choose a region (US or EU) for your QuotaGuard Static or Shield subscription.
• QuotaGuard assigns regional static IPs and backs them with infrastructure deployed only in that region.
• All proxy traffic for that subscription flows through in‑region infrastructure. There is no cross‑region routing or automatic failover to other geographies.
• Application payloads are proxied only, not stored at rest. Logs and metadata are stored in region and retained according to your log retention settings.

Plans and pricing

The Data Residency option is available as an add‑on to any existing QuotaGuard Static or Shield plan.

• Dedicated regional infrastructure and static IPs per region
• Add‑on pricing starts at $899 per month, plus your existing plan usage tiers

For current plan details, see the pricing page or contact us for a quote aligned to your traffic profile.

For engineers and security teams

If your job is to justify this to security, compliance, or another engineer, here is the concrete version.

• QuotaGuard is a proxy. We route traffic through our infrastructure on AWS. We do not store or log request or response bodies. Only encrypted packets pass through our servers, as documented in our Privacy, Security, and GDPR FAQ.
• For HTTP and SOCKS traffic, we log connection metadata only. Time of request, account identifier, source IP, destination URL or IP, HTTP method, status code, and byte counts. No payload content. Logs follow our documented retention policy. One month visible in the dashboard, up to one year in long-term storage before deletion.
• For customers on the Data Residency add‑on, proxy infrastructure and logs for that subscription are kept only in the selected region (US or EU). There is no cross‑region routing or automatic failover to other geographies.
• Using US or EU Data Residency does not by itself make you HIPAA or GDPR compliant. It gives you a small, regional egress surface with known IPs and documented behavior, which makes your own compliance story simpler to explain to auditors, DPOs, and privacy counsel.

Getting started

To enable US or EU Data Residency on your account, contact QuotaGuard Support or Sales with your preferred region and existing plan details.

We will provision region-specific static IPs, update your account configuration, and confirm the routing and logging behavior in writing for your security and compliance teams.

‍