How we handle data and access.
The synthetic population is separate from account information and saved research. Here is how those different kinds of data are used and protected.
Privacy and data-use information
Account records include your email, optional display name and access settings. We also store saved conversations, research results and service usage records needed to operate the product and account for its use.
| data | where · why |
|---|---|
| email + name | your account record, sign-in and seat management |
| contact requests | email, category, message and request reference, reviewed by authorized administrators |
| Team invitations | when enabled, invited email addresses, membership roles and invitation status support owner-managed seats; invitation links are not emailed automatically |
| saved research | conversations, query results and simulation records associated with your account |
| usage and diagnostics | request activity, model usage and cost records, browser/device information and error reports used to operate and troubleshoot the service |
| request context | request time, category and status support review and follow-up |
| payments | checkout is handled by Stripe; review the price and payment terms presented there before completing a purchase. |
Service providers and browser storage
Google Firebase and Google Cloud support authentication, account storage and hosting. AI requests and relevant tool results are sent to the configured model provider, which can include OpenAI, Anthropic or Google depending on the selected model and enabled provider. Stripe supports checkout. Map requests can contact configured mapping or imagery providers. These are service operations, not a claim that information never leaves our servers.
Sign-in uses browser storage to keep your session available across visits. The app also stores interface preferences and uses operational diagnostics. Only submit information you are authorized to use with the service.
Requests and retention
Saved conversations have account-level controls, but deleting a conversation is not the same as deleting all related simulation artifacts, service logs or backups. Use our contact-request form for privacy, deletion, billing, account or security requests. Our Privacy Notice identifies Submission Bridge LLC and explains processing, providers, retention criteria and your choices.
The population is synthetic, by design, not by policy
Business records draw on public filings, registers and company descriptions. Resident agents are synthetic statistical representations built from census and survey inputs. Their modeled activities are not observations about identifiable real people. This is separate from the account information and research you save.
How the service is secured
SOC 2 is a future objective, not a current attestation. No security certification is claimed.
- Sign-in runs on Firebase Authentication, Google sign-in or email + password. We never see or store passwords.
- Everything is served over TLS with HSTS; a strict Content-Security-Policy limits what the pages may load and where they may connect.
- Account data and saved simulations use account-scoped access checks. Additional controls are being reviewed as the beta evolves.
- Private API and billing credentials are handled on the server; browser configuration is separate from those secrets.
- The data pipeline runs on public and government sources; business facts trace to records anyone can verify.
Beta service information
Economic Twin is a research and simulation product. Source observations, modeled estimates and synthetic activity are different kinds of information. Outputs are not guarantees of business performance, verified customer relationships or a complete accounting of the economy. Inspect their assumptions and scope.
Access and usage limits depend on the service offered. Review any checkout price, included usage and renewal terms before purchasing. Business Data exports retain source-specific rights and do not establish permission for every downstream use. Keep credentials private and do not bypass another account’s access controls.
Paid plans renew monthly. Included exploration credits reset each billing period; purchased top-up credits do not expire. Our Terms of Service describe renewal, cancellation, refunds, credits, limitations and dispute provisions. Signup requires agreement to the Terms and acknowledgment of the Privacy Notice.
Found something?
Choose Security in our contact-request form to report a concern. Do not include passwords, private API keys, payment-card details or exploit data about another user. Send an initial description so we can arrange an appropriate follow-up.