← Back to signup

Privacy Policy

Last updated: 27 October 2026

This Privacy Policy explains how Trivo Technologies collects, uses, and protects personal information when you use the Trivo platform (the “Service”) as a merchant, and how we handle the data of your customers on your behalf.

1. Information we collect

Account details (name, email, phone, store URL, country/region), billing information processed by our payment provider, and operational data you enter (products, orders, customers). We also collect technical data such as IP address and usage logs to operate and secure the Service.

2. How we use it

To provide and improve the Service, process your plan billing, send transactional and service messages, prevent abuse, and comply with legal obligations.

3. Your customers’ data

Data about your storefront’s customers is processed on your behalf. You are the data controller for that data; we act as a processor and use it only to provide the Service to you.

4. Sub-processors

We share personal data only with the service providers we need to run the Service, each under a written contract that limits them to processing it on our instructions and keeps it confidential. We do not sell personal information. Our sub-processors are:

  • Amazon Web Services (AWS) — hosting of the application, database and uploaded files, in the US East (Ohio) region (us-east-2).
  • OVHcloud — our mail server, in London, UK, which sends store and platform email and hosts Trivo Mail mailboxes.
  • Cloudflare — DNS, content delivery and protection against attacks; it sees visitors’ IP addresses and requests in transit.
  • Stripe and DNA Payments — payment processing for plan billing and for storefront checkouts. Card details are entered with them directly and never stored by us.
  • Anthropic — AI features (for example drafting product descriptions, emails and chatbot replies). Only the text needed for the request is sent, and it is not used to train their models.
  • Google — “Continue with Google” sign-in, address look-up at checkout, and the optional Search Console and Analytics integration described in section 9.
  • Twilio — SMS and WhatsApp notifications, where they are switched on.
  • Expo — push notifications to the Trivo mobile apps.

Integrations a merchant chooses to connect (for example a delivery carrier, a marketplace or an advertising platform) receive only the data needed for that integration, on that merchant’s instructions.

5. International transfers

Our main hosting (AWS, us-east-2) and our AI provider (Anthropic) are in the United States, so personal data from the UK and the European Economic Area is transferred there. Where the recipient is certified under the EU–US Data Privacy Framework and its UK Extension we rely on that certification; otherwise we rely on the UK International Data Transfer Addendum (IDTA) and the EU Standard Contractual Clauses (SCCs), with the supplementary measures they require. Our mail server stays in the UK.

6. How long we keep it

  • Account and store data — for as long as the account is open, then deleted, except where the law requires us to keep records (for example tax and accounting records).
  • Email content — the body of each email we send is kept for 90 days, so a merchant can see what was sent and investigate a delivery problem, then deleted.
  • Email delivery logs (recipient, subject, time and delivery result) — 13 months.
  • Mail-server logs — 30 days.
  • Unsubscribe and do-not-email list — kept indefinitely, so that an opt-out is honoured for good. After an erasure request we keep only a keyed hash of the address (not the address itself), which is enough to recognise it and nothing more.
  • Backups — overwritten on a rolling basis, so deleted data drops out of them as older backups are replaced.

7. Marketing email

Stores on Trivo can send marketing email only to customers who opted in, and every marketing email carries a one-click unsubscribe link. Marketing emails contain a small tracking image and tracked links, so the sending store can see whether and when an email was opened and which links were clicked, per recipient. This is used only to measure how campaigns perform. Turning off images in your email app stops open tracking.

8. Your rights, and security

Depending on where you live, you have the right to access the personal data we hold about you, to have it corrected or deleted, to receive a copy in a portable format, to restrict or object to how we use it, and to withdraw consent at any time. Account-level data export and deletion tools are available in your settings, or you can contact us (section 10). We respond within one month; if a request is complex we may extend that by up to two further months and will tell you why within the first month. If you are not satisfied, you can complain to the UK Information Commissioner’s Office (ico.org.uk) or your local data protection authority.

Data about a store’s customers is controlled by that store: a shopper exercising these rights should contact the store, and we help the store respond.

We use industry-standard measures including encryption in transit and access controls. No method of transmission or storage is completely secure, so we cannot guarantee absolute security.

9. Google user data

Trivo offers an optional integration that connects your own Google account to your Trivo store, so that Search Console and Google Analytics figures appear in your dashboard and you can submit your sitemap without leaving it. This section describes that integration specifically and applies in addition to the rest of this policy. The integration is off until you start it yourself, and nothing here applies if you never connect an account.

What we ask for, and why

When you start the connection we ask Google for the following, and for nothing else. Each is used only for the dashboard feature named beside it:

  • Your name and email address (openid, email) — so the dashboard can show you which Google account is connected and let you confirm you are disconnecting the right one.
  • Google Search Console (webmasters) — to read your search performance (clicks, impressions, click-through rate and average position), to read the index status of individual pages, and to submit or re-submit your sitemap. Submitting a sitemap is a write, which is why this is not the read-only scope; we make no other change to your Search Console property.
  • Google Analytics (analytics.readonly) — read-only traffic figures shown alongside the search data. This one is optional: if you decline it, the Search Console features still work.

How we store it

We store the refresh token Google issues, against your store record, so the dashboard can keep showing your figures without asking you to sign in again. Access tokens are requested from Google as needed and are never written to our database. We do not copy your Search Console or Analytics data into our own storage for any purpose other than displaying and caching the report you asked for.

Limited Use

Trivo’s use and transfer of information received from Google APIs to any other app adheres to the Google API Services User Data Policy, including its Limited Use requirements. In particular we do not sell this data, do not transfer it to advertising platforms, data brokers or resellers, do not use it to serve advertising, and do not use it to train generalised artificial-intelligence or machine-learning models. No Trivo employee reads it except with your explicit permission (for example when you ask us to investigate a support issue), where it is necessary for security purposes, or where we are required to by law.

Disconnecting

You can disconnect at any time from the Google panel in your dashboard under Settings → SEO, which deletes the stored refresh token. You can also revoke Trivo’s access directly from your Google Account permissions page. Revoking access stops all further reads immediately.

10. Contact

Privacy questions, and any request to exercise the rights in section 8, can be sent to privacy@trivotechnologies.com or through the contact form at trivotechnologies.com/contact. Trivo Technologies is the data controller for the account data described in this policy.