TrialCutActive today
| Provider | Purpose | What it receives | Where | Status |
|---|---|---|---|---|
| Google LLC Google Ireland Ltd for EEA/UK users |
Sign-in, and access to your mailbox at your instruction | Your Google account, the searches we run against your mailbox, and the cancellation emails you send. Google already holds your mail — this is us reading and sending through it, not sending anything to them. | Global | Active |
| Render Services, Inc. | Application hosting and the managed database | Everything TrialCut stores: your account, your trials, your cancellations and the 600-character confirmation excerpts, plus server logs containing your IP address. | Oregon, USA | Active |
| Apple Inc. | App distribution, payment, and push notification delivery | Your device's push token, and the text of each alert — which contains the merchant's name and the exact amount. Separately, as a controller in its own right, Apple handles your subscription payment; we never see your payment details. | Global | Active |
| RevenueCat, Inc. | Managing subscription state across devices | An internal account identifier and your subscription status. No email address, no mail content, no merchant data. | United States | Active |
| Formspree, Inc. | Receiving the waitlist form on the marketing website — the website only, never the app | The email address a visitor types into the waitlist box, which of the two boxes they used, and the IP address and time of the submission. Not an account, not a mailbox, nothing from the app. | United States | Active |
| Meta Platforms, Inc. Meta Platforms Ireland Ltd for EEA/UK visitors |
Measuring which adverts bring people to our marketing website — the website only, never the app | From consenting visitors to trialcut.app: IP address, browser user-agent, the page URL, and a random browser identifier. Not your email address, not your account, and nothing whatsoever from your mailbox. | United States and Ireland | Active |
Named but not active
These are listed in advance, honestly labelled, because naming a sub-processor before it starts processing is the right order to do it in. None of these currently receives any data of yours. When one starts, its row moves to the table above and the change log below records the date.
| Provider | Intended purpose | Would receive | Where | Status |
|---|---|---|---|---|
| OpenAI, L.L.C. | Reading the minority of trial emails that ordinary pattern matching cannot parse | The subject line and up to 4,000 characters of that single message. Not your email address, not the sender, not any identifier. | United States | Not active |
The model-assisted path is disabled in our production configuration and the server refuses to call it rather than failing quietly. It will not be switched on until we hold a contractual no-training term, a zero-data-retention endpoint and a no-human-review commitment — and this page and the Privacy Policy will be updated first. Nothing we learn from your mail is ever used to train, fine-tune or improve any model, under any configuration.
Who is not on this list
There is no analytics provider, no crash reporter, no email marketing platform, no customer-support tool holding your data, and no data broker. The waitlist on the website is a plain form received by Formspree, named above; it is not a mailing-list tool and the addresses on it are used for one launch message only. In the app there is no analytics, advertising or crash-reporting SDK of any kind, and its only third-party library is RevenueCat's, which is listed above. The one advertising company we deal with at all is Meta, and only on the marketing website, only for visitors who consent, and never with anything that came from your mailbox or your account — it is named above rather than omitted. If anything else ever changes, the provider appears above before it receives anything.
Notice of changes
Before we add a sub-processor that would receive personal data, we will update this page and the change log below. Where a change is material — a new category of data, or a provider receiving mail content for the first time — we will also tell you in the app before it takes effect, and ask for your consent again where the law requires it.
If you would like to be notified of changes to this list directly, write to [email protected] and we will add you.
Change log
| Date | Version | Change |
|---|---|---|
| 8 September 2026 | 1.5 | Meta Platforms moved to Active: the consent-gated pixel on the marketing website now has an advertising account behind it and runs for visitors who click Allow. Website visitors only; nothing from the app, and nothing a visitor types into the waitlist form. |
| 8 September 2026 | 1.4 | Formspree moved to Active: the waitlist form on the marketing website is now connected to a Formspree form and receives what a visitor types into it. Website visitors only; nothing from the app. |
| 8 September 2026 | 1.3 | Formspree named as a sub-processor, not active: the marketing website gained a waitlist form that will post to Formspree once a form is created there. Until then the page shows an email link instead. Website visitors only; nothing from the app. |
| 7 September 2026 | 1.2 | Meta Platforms named as a sub-processor, not active: a consent-gated advertising pixel now ships on the marketing website and will begin processing once an advertising account exists. It covers website visitors only and receives nothing from the app. RevenueCat moved into the active table, where it belonged. |
| 7 September 2026 | 1.1 | RevenueCat moved to active: the subscription SDK now ships in the iOS app and receives an internal account identifier. OpenAI remains not active. |
| 5 September 2026 | 1.0 | First published. Google, Render and Apple active. OpenAI and RevenueCat named as not active. |