1. Defaults
Unless otherwise agreed in your order form, the following defaults apply to production deployments of Verus:
| Data category | Primary region | In transit via | At rest in |
|---|---|---|---|
| Customer deal documents & uploads | UK (London) | Cloudflare edge (global PoPs, TLS 1.3) | AWS EBS eu-west-2; encrypted S3 backups in the same region |
| Valuation outputs & run metadata | UK (London) | Cloudflare edge | AWS EBS (SQLite) eu-west-2 |
| Account & authentication data | UK (London) | Cloudflare edge | AWS EBS (SQLite) eu-west-2 |
| Marketing-site lead data (CRM) | Global edge / US control plane | Cloudflare | Cloudflare D1 (global with EU primary) + R2 |
| Transactional email | Global (Google data centres) | Google Workspace (SMTP relay / Gmail API) | Sent copies in the markst.com Workspace mailbox |
| AI inference (when enabled) | United States (Anthropic API), UK/EU (Amazon Bedrock) or customer network (locally hosted private LLM) | HTTPS / in-region / in-cluster | Transient — zero retention on Anthropic Enterprise API |
| Error telemetry | UK (London) | None — no third-party telemetry vendor | Verus application log, AWS EBS eu-west-2 |
2. Alternative regions
For customers with stricter residency requirements, the Verus back-end supports two additional primary regions selected at contract time:
- EU — AWS
eu-central-1(Frankfurt). All customer data and run metadata stays within the EEA. Cloudflare edge routing is configured to prefer EU PoPs. - US — AWS
us-east-1(N. Virginia). For US-domiciled counterparties or joint ventures whose data-residency policies demand US-only processing.
Region selection is one-way per tenant — once data is established in a region it is not migrated silently. A re-home exercise is a separate engagement documented in the service agreement.
3. Transfer mechanisms
Where personal data leaves the UK/EEA (for example to reach Anthropic for optional AI features, or Google Workspace for transactional email), transfers rely on:
- EU Standard Contractual Clauses (2021/914), modules 2 and 3 as applicable.
- The UK International Data Transfer Addendum (IDTA) executed with each US sub-processor.
- Supplementary technical measures: TLS 1.3 in transit, AES-256 at rest, access logging, opt-out of AI features for tenants requiring it.
A Transfer Impact Assessment is available on request.
4. Backup & failover residency
Backups of UK-hosted data are encrypted and stored in a second AZ within the same region. Cross-region replication (e.g. UK → EU for disaster recovery) is available under a specific contractual arrangement and does not happen by default — a UK customer's data does not leave UK boundaries absent instruction.
5. Data exit
On termination or request, markst will return your data in a structured export (SQL dump + object-store manifest) and then destroy it in line with the Privacy Notice §6 retention schedule. A written destruction certificate is provided on request.
6. Contact
Questions on residency, or requests for a specific regional deployment: legal@markst.com.