Data Residency

Dino is built on a region-partitioned architecture. Your primary data is stored and processed in the region assigned to your workspace, and Dino does not move that primary data to another region in the normal course of running the service.

Regions

A workspace is assigned a region when it is created. Dino operates the following regions:

• European Union
• Eastern Europe
• Western North America
• Asia Pacific
• Oceania
• A global default region for workspaces that do not select a specific region

Regional selection is available on our Team and Enterprise plans.

What stays in region

For a workspace assigned to a region, the following are stored in that region:

• API definitions, environments, and configuration
• Encrypted API credentials
• Scans, scan results, and findings
• Runner records and runner assignments

Each region has its own isolated database and object storage. Scan assignment is region-bound: a scan for a workspace in a region is only ever assigned to a runner in that same region, and managed runner compute for that region is deployed in that region. A runner in one region cannot reach another region's data.

Global functions

A small set of functions are global by design, and we list them here for transparency:

• Authentication and identity are provided by Stytch, and billing is provided by Polar, as described on our Sub-processors page.
• Limited routing metadata, such as the mapping of an organization to its region, is held in a global lookup so requests reach the correct region.
• Aggregate, tenant-anonymous operational analytics carry no tenant identifier, no credential, and no target data.
• Support access to your data, when requested or required, is performed by authorized Dino personnel and logged.

AI processing

AI features call third-party model providers listed on our Sub-processors page. Where you use Dino-provided AI, prompt and completion content is processed by those providers under their terms, with secrets redacted before any content is sent. Customers who require tighter control over AI processing can use bring-your-own-key, in which AI requests run under your own model-provider account.

Self-hosted runners

If you run self-hosted runners, scan execution and the handling of decrypted credentials happen inside your own infrastructure, giving you direct control over where that processing occurs.

Cross-border transfers

Where personal data is transferred across borders, Dino relies on the European Commission Standard Contractual Clauses, and the EU-US Data Privacy Framework where applicable, as set out in our Data Processing Agreement. Regional residency is the primary way we help you minimize cross-border transfer in the first place.

Questions

Contact privacy@usedino.dev.