FAQ
Where is my data stored and what is the data residency?
Revenue Proven production infrastructure runs on servers in Singapore, so your attribution data, sync records, and uploaded assets are stored in the Singapore region.
All Revenue Proven production infrastructure is hosted in Singapore. This includes the PostgreSQL database (running Citus on Tencent Cloud servers), the Redis cache, the application servers, and the self-hosted object storage for backups and uploaded assets.
What is stored in Singapore
- All attribution data: company matches, deal associations, campaign metrics
- CRM sync data pulled from HubSpot and Salesforce
- LinkedIn Ads engagement data and organization records
- Encrypted OAuth tokens for LinkedIn and CRM connections
- User accounts, workspace settings, and preferences
- Daily database backups on self-hosted RustFS storage
Implications for EU and other regions
If your organization is subject to GDPR or other regional data-protection regulations, storing data in Singapore may be relevant to your compliance assessment. Revenue Proven does not currently offer region-specific deployments or the option to choose an alternative storage region. If your compliance requirements restrict data transfer outside a specific jurisdiction, contact Revenue Proven to discuss your situation before subscribing.
Current help workflow
This answer was refreshed against the current Revenue Proven product and its exact /dashboard/settings route. It is written for the Shawn Brown demo workspace, whose pages contain real connected-system data in some areas and seeded examples in others.

Use this screenshot as the route-specific visual reference for “Where is my data stored and what is the data residency?”. Labels, plan gates, roles, asynchronous loading, permissions, and available controls can vary with the signed-in workspace.
When troubleshooting, first confirm the active workspace, selected account, connections, date range and entitlement. Treat Save, Send, Sync, Publish, Resume, Reconnect and Delete controls as state-changing actions, and consult the current route before relying on older screenshots or navigation instructions.

