--- title: "Data locations · Frazer" description: "Where Frazer stores each kind of data. The region us-virginia1 in Vint Hill, Virginia, servers you bring, encrypted copies off-site and a recovery standby, all in the United States." url: https://frazer.ai/legal/data-locations index: https://frazer.ai/llms.txt tokens: 1369 --- > For agents: every page on frazer.ai is indexed at https://frazer.ai/llms.txt. # Data locations · Frazer Legal · Data locations Version 1.0 · Oct 15, 2026 # Data locations Where your data is stored. Frazer runs in one region, us-virginia1, in Vint Hill, Virginia. Workloads on servers you bring stay where those servers are. Version 1.0 Effective October 15, 2026 Applies to Data in the Frazer platform and on this website Region us-virginia1, Vint Hill, Virginia Provider Frazer AI LLC, a Florida limited liability company Address 1221 Brickell Ave, Ste 900, Miami, FL 33131 Text [Markdown](https://frazer.ai/legal/data-locations.md) · [History](#history) In short A reading aid, not the text ## The main points, in plain words. - Frazer’s own records (accounts, projects, audit logs, billing, metrics and logs) are stored in **us-virginia1**, in the United States. - Workloads and data on **servers you bring** stay on those servers. - Backups are encrypted and copied off the primary site; a second site in the United States is ready to take over if the first is lost. - We add a region where customers need their data, and this page changes with 30 days’ notice. 01 · Where it lives Fig. 1 ## Your servers, one region, and copies off-site. **Fig. 1** Where each kind of data is stored region: us-virginia1 02 · By kind of data ## Each kind of data, and where it is kept. Data locations | Data | Where it is stored | | --- | --- | | This website and its forms | Served by our website host from the United States; what you send through a form is delivered by email to our team. See [sub-processors](https://frazer.ai/legal/subprocessors). | | Workloads and data on servers you bring | Where your servers are: your own site or your provider account. | | Workloads and data on Frazer servers | us-virginia1: Vint Hill, Virginia, United States. | | Accounts, sign-in and your organization | us-virginia1, in Frazer’s global layer. | | Projects: resources, plans, audit log and secrets | The control plane in us-virginia1 (cell us-virginia1-c1), kept apart per project. | | Metrics and logs from your clusters | The monitoring cell in us-virginia1, one tenant per project. Kept 30 days by default; known token formats are dropped before storage. | | Billing records | us-virginia1. Card details stay with our payment processor and never reach Frazer’s systems. | | Backups of the control plane | Encrypted and copied off the primary site, continuously and every hour, in the United States. A restore test runs every night. | | Disaster-recovery standby | A second site in the United States, where Frazer is restored if the Vint Hill site is lost. | | Email Frazer sends you | Sent from Frazer’s own mail servers in the United States. Bodies are kept only until delivered; delivery records for 30 days. | 03 · Residency ## One region, in the United States. - ### Frazer’s records Accounts, projects, audit logs, billing, metrics and logs are stored in us-virginia1, in the United States. - ### Your servers Workloads and data on servers you bring stay where those servers are. Metrics and logs from them go to the monitoring cell in us-virginia1. - ### Another region Regions are added where customers need their data. Tell us where yours must stay. History 1 version ## Every version, and what changed. Before a change that matters to you takes effect, we email owners and billing contacts 30 days ahead and list it on [the legal page](https://frazer.ai/legal). Earlier versions stay online. Data locations · versions | Version | Effective | What changed | | --- | --- | --- | | 1.0 | Oct 15, 2026 | First versioned page. Adds the website and its forms, and describes backup and recovery sites by place, not by provider. | ## How to reach us - Privacy and data protection [privacy@frazer.ai](mailto:privacy@frazer.ai) - Security and vulnerabilities [security@frazer.ai](mailto:security@frazer.ai) ## Documents - [**Legal** Every document, its version and history](https://frazer.ai/legal) - [**Terms of Service** The agreement for using Frazer](https://frazer.ai/legal/terms) - [**AI Terms** Agents, models, outputs, and no training](https://frazer.ai/legal/ai) - [**Service Level Agreement** Uptime, and credits without a claim](https://frazer.ai/legal/sla) - [**Data Processing Addendum** Signed in the console; no sales call](https://frazer.ai/legal/dpa) - [**Privacy Policy** No cookies, no third-party trackers](https://frazer.ai/legal/privacy) - [**Acceptable Use Policy** What may and may not run on Frazer](https://frazer.ai/legal/acceptable-use) - [**Community Guidelines** Public repositories, models and discussions](https://frazer.ai/legal/community) - [**Copyright and DMCA** Takedown notices and counter notices](https://frazer.ai/legal/copyright) - [**Law enforcement** How we answer requests for user data](https://frazer.ai/legal/law-enforcement) - [**Vulnerability disclosure** Scope, safe harbor and response times](https://frazer.ai/legal/vulnerability-disclosure) - [**Sub-processors** Every company that processes your data, why, and where](https://frazer.ai/legal/subprocessors) - [**Data locations** Where each product stores data, per region](https://frazer.ai/legal/data-locations) - [**Email senders** The only addresses Frazer mails from, against phishing](https://frazer.ai/legal/email-senders) - [**Security notices** Vulnerability notices by email and RSS](https://frazer.ai/security/notices)