Data Residency & Processing Locations
Understand exactly where your data flows, how it's processed, and the controls you have over its residency.
Our Data Philosophy
Local-First, Minimal Retention
Tork is designed with a local-first architecture. The content you send to our API for evaluation is processed entirely in memory and is never written to disk or persistent storage.
This means your sensitive data—the actual text, code, or content being evaluated—is not written anywhere. What is stored for audit purposes is a record of the call: timestamp, decision, PII types and counts (never the values), SHA-256 hashes of the input and output, and caller identity. See the retention table below.
API request content is never stored. It is processed in memory by the serverless function that handles the request and is not written to disk or a database.
All data in transit uses TLS. Persistent data is encrypted at rest by Supabase on AWS. API keys are validated only against SHA-256 hashes.
Governed-call records are retained per plan (7 days to 7 years). Account and personal-data deletion is available on request with a 30-day grace period.
Processing Regions
Only the Supabase row is a measured region (Supabase Management API, 2026-09-14). The other rows describe how each provider places data. The certification tags are each provider's own published attestations; Tork has not audited them and holds no certification of its own — see the Trust Center.
Data Residency by Product
The table above covers tork.network itself. Tork runs several products, each on its own Supabase project — which region your data lives in depends on which product you use.
Infrastructure spans 6 regions today across 10 Supabase projects. Enterprise customers with a residency requirement not covered above should contact hello@tork.network.
Data Flow
API Request Received
Your request hits our edge network (Vercel) and is routed to the nearest processing region. TLS 1.3 encryption protects data in transit.
In-Memory Processing
Content is evaluated in memory inside the edge function that handles the request. Policy rules are applied, PII is detected, and decisions are made. No content is written to disk or a database.
Call Record Written
A record of the call — timestamp, decision, PII types and counts, SHA-256 hashes of input and output, caller IP and SDK identity, agent/session identifiers, and the signed receipt — is written to our database in AWS ap-southeast-1 (Singapore, Singapore). Every governed call is recorded; the content itself is never logged.
Response Returned
The evaluation result (ALLOW/BLOCK/REDACT + signed receipt) is returned to you. The request content is not retained after the response is sent.
Regional Compliance
European Union
DPA + SCCs available- Standard Contractual Clauses (SCCs) available — see /legal/sccs
- Data Processing Agreement (DPA) available — see /legal/dpa
- EU representative: appointment in progress (see Privacy Policy)
- Deletion requests: 30-day grace period, then purged
United States
BAA available- CCPA/CPRA consumer rights handled per our Privacy Policy
- HIPAA Business Associate Agreement available — see /legal/baa
- State privacy law rights (e.g. Virginia VCDPA, Colorado CPA) handled per our Privacy Policy
- No Tork database is in a US region; see the Processing Regions table for sub-processor placement
Australia
Home jurisdiction- JCorp Australia Pty Ltd, trading as Tork, is the controller named in our Privacy Policy
- Privacy Policy written against the Australian Privacy Principles (APPs)
- Cross-border transfers disclosed per region on this page
- Complaints may be lodged with the OAIC
United Kingdom
DPA available- International Data Transfer Agreement (IDTA) available on request
- UK GDPR rights handled per our Privacy Policy
- Complaints may be lodged with the ICO (ico.org.uk)
- Subject access requests honoured
Data Retention Policies
API Request Content
Not retainedProcessed in memory for the duration of the request. Not written to the database or any persistent storage.
Governed-Call Records
Set by planPer-call records (timestamp, decision, PII types and counts, content hashes, caller identity) are retained for at least the retention period of your plan — from 7 days on Free to 7 years on Enterprise. Not user-configurable today.
Account Data
Account lifetime + 30 daysEmail, name, company. Purged 30 days after a deletion request; audit entries are anonymised rather than deleted.
API Keys
Until revokedValidated only against a SHA-256 hash. Revocation disables the key immediately; the hashed record is retained for audit.
Usage Metrics
Per-call records per plan; daily aggregates retainedAPI call counts for billing are derived from the per-call records above and rolled up into daily aggregate metrics.
Session Data
Token lifetimeAuthentication is managed by Supabase Auth with short-lived access tokens and rotating refresh tokens. Sessions expire automatically.
Enterprise Options
For organizations with specific data residency requirements, we offer advanced deployment options.
Dedicated Tenancy
Enterprise plan — scoped per engagementIsolated database and compute resources for your organization
- Dedicated Supabase project in a region you choose
- Separate Vercel deployment
- Custom domain and SSL
- Priority support included
Regional Deployment
Enterprise planTork infrastructure already spans multiple regions
- 6 regions live today across 10 projects, including APAC and the UK
- Additional database regions available on request
- Request processing runs on the Vercel edge network; the database region is what is pinned
Bring Your Own Key (BYOK)
Roadmap — not yet availableUse your own encryption keys for data at rest
- AWS KMS integration
- Customer-managed keys
- Key rotation support
- Audit trail for key usage
On-Premise Deployment
Enterprise plan — scoped per engagementRun Tork governance within your infrastructure
- Docker image published from this codebase
- Kubernetes and air-gapped operation scoped per engagement
- Your data stays in your environment
- Self-managed updates