The register
Checked against the code and the running configuration on the date above. Rows marked optional only apply if you or a merchant switches that feature on.
| Service | What it does for Torva | What it can see |
|---|---|---|
| Supabase | The database, authentication and file storage behind the whole platform. | Everything Torva stores: merchant accounts, store records, products, customers, orders, uploaded images and documents. |
| Netlify | Hosts and serves the application: torvaos.com, the Desk and every merchant storefront. | Every request to the site, including the IP address it arrives from, in its own server logs. |
| Cloudflare | DNS for merchant custom domains. | Domain names and DNS queries. No store or customer data. |
| Whop | Subscription billing and checkout for Torva plans. | The merchant’s name, email and payment details, and the subscription’s status. Card numbers go to Whop and never to Torva. |
| Resend | Sends email: Torva’s own account email, and a merchant’s store and campaign email. | The recipient address, subject and content of each email sent, and its delivery result. |
| Railway | Runs the site-scan worker that reads a public website when a merchant asks for a rebuilt preview. | The public pages of the website being read. No merchant account or customer data. |
| Anthropic | The AI features in the Desk, the Ask Torva assistant, and the assistant on public torvaos.com pages. | The text of the request sent to it, which can include store content the feature is working on, and the questions a visitor types into the public assistant. |
| OpenAI | Generates product photo concepts and relabelled product images. Optional. | The prompt sent to it and the merchant’s product photo or logo the image is made from. |
| Google Analytics 4 and the Google Ads tag on public torvaos.com pages; Google sign-in for storefront customer accounts and address autocomplete, both optional. | Public page visits and the cookies GA sets. Where sign-in is on, the customer’s Google identity. Where autocomplete is on, the partial address being typed. | |
| Meta | Advertising measurement on the Torva homepage and /start builder. | Permitted public page URLs and referrers, browser/network information, advertising cookie identifiers and event names. No email address, store content or account/payment details are added to events. |
| Microsoft | Clarity heatmaps and session replay on public torvaos.com pages. | Interaction with public marketing pages: clicks, scrolling and movement. Input fields are masked. |
| Apple | Apple sign-in for storefront customer accounts. Optional. | The customer’s Apple identity, as the customer chooses to share it. |
| Stripe | Card processing, when a merchant connects their own Stripe account through Torva. Optional. | The merchant’s Stripe account and the payment data for the orders it processes. The merchant’s agreement is with Stripe directly. |
| EasyPost | Buys shipping labels and returns tracking, through the merchant’s own EasyPost account. Optional. | The recipient name, address and parcel details on an order being shipped. |
| Mapbox | Address autocomplete at checkout, where it is the configured provider. Optional. | The partial address a customer is typing. |
| Entri | Lets a merchant’s DNS provider write the domain records itself, if the merchant chooses that route. Optional. | The domain and the DNS records being written. |
| Telegram | Delivers merchant notifications to a chat the merchant connects. Optional. | The content of the notifications sent, and the chat identifier. |
| Sentry | Server error reporting. | A stack-trace fingerprint and nothing else. Request data, error messages and user fields are stripped before a report leaves Torva. |
| Zoho | Torva’s own mailboxes, hello@ and support@. | Email you send to Torva, and our replies. |
Where the data is
Torva’s database, authentication and file storage run on managed infrastructure in the United States. The application is served from a global edge network, so a request is handled near you and the data behind it stays in the United States.
The services above are predominantly United States companies processing data in the United States. If you or your customers are outside the US, using Torva means data is transferred there. Where a transfer mechanism is required, we rely on the standard contractual clauses in each provider’s data processing terms.
Changes to this list
We keep this page current rather than accurate-as-of-signup. When we add a subprocessor that can see merchant or customer data, we update this page and the date at the top, and we email account owners before it starts.
To be told about changes in advance, or to ask about a specific provider, email hello@torvaos.com.
- Terms — The agreement between Torva and a merchant: plans, responsibilities, suspension and what happens when it ends.
- Privacy — What torvaos.com collects, what Torva holds, what it processes for a merchant’s customers, and how to make a request.
- Acceptable use — What may and may not be sold or done on Torva: research use only, no health claims, no controlled substances, a mandatory 21+ gate.
- Refunds — The 30-day money-back guarantee on the first subscription payment, and what it does not cover.
- Notice & takedown — How to report copyright or trademark infringement on a store hosted by Torva.
- Security — Tenant isolation, credentials, accounts, error handling, and what Torva does not claim yet.
- Accessibility — What Torva aims for on accessibility, what is not independently checked yet, and how to report a barrier.
Written to be read, not to impress. This is not legal advice, and it does not tell you what the law requires of your business.