humanflow

Subprocessors

Last updated: 17 September 2026

These are every company that handles data on our behalf. Each is bound by a written data processing agreement to act only on our instructions, keep your data confidential, apply appropriate security, and delete or return it when the service ends. This is the canonical list — our Privacy Policy and GDPR notice point here rather than repeating it, so there is only one page to be wrong.

ProcessorWhat it doesWhat it receivesWhere
AnthropicThe language model behind the humanizerThe text you submit for rewritingUnited States
SupabaseApplication databaseAccount record, and submitted text with its resultUnited States
DigitalOceanHosting for the API and the in-house detectorAll request data in transit; detector runs hereUnited States
VercelWebsite hosting and edge deliveryRequest metadata, including IP address in transitUnited States
UpstashRate-limit and quota countersAccount ID, or IP address for signed-out visitors, held 48 hoursUnited States
PostmarkTransactional email — verification, password resetEmail address only. Never your submitted textUnited States
SentryCrash and error reportingDiagnostic data. Session replay is disabled; no submitted text is attachedUnited States
Google AnalyticsAggregate site measurementPage views with IP anonymisation on and advertising signals offLoads only if you accept analytics cookiesUnited States
PostHogAggregate product measurementPage and feature usage eventsLoads only if you accept analytics cookiesUnited States
Google AdsMeasuring which ads lead to a purchaseThat a purchase happened, its amount, and the ad click it followed. No submitted text, and no audience is built from itLoads only if you accept analytics cookiesUnited States
MetaNot live yetMeasuring which app-install ads lead to a sign-up or a purchaseIn the iOS app only: that an install, sign-up, first rewrite or purchase happened, and what a purchase cost. No submitted text, no email, no name, and no advertising ID — the app asks for no tracking permission, so Meta receives Apple's aggregated attribution rather than anything identifying youUnited States
GoogleSign in with GoogleEmail address and name, to verify the sign-inOnly if you choose that sign-in methodUnited States
AppleSign in with AppleEmail address (or relay address) and nameOnly if you choose that sign-in methodUnited States
StripePayment processing for web subscriptionsBilling details and payment method. Card numbers go to Stripe, never to usUnited States

Not in use yet

Meta is listed because the integration exists in our code, but it is not processing anyone's data today.

Where your data goes

We are established in the United States, and so is every processor in the table above.

If you are in the EEA or the UK, your data is therefore transferred out of it. The United States does hold an EU adequacy decision, but it reaches only organisations that have self-certified to the EU–US Data Privacy Framework, and we have not. So every transfer here — to a processor and to our own infrastructure alike — rests on Standard Contractual Clauses and the UK Addendum in each data processing agreement, not on adequacy. We would rather say which one it is than let the word do work it cannot do.

What is not on this list

Our detector runs on a model we trained ourselves, on our own infrastructure. Your text is not sent to any third-party detector — not to Turnitin, not to GPTZero, not to anyone. We do not use advertising networks, data brokers, or retargeting pixels, so none appear here.

Changes

We will update this page before a new processor begins handling your data, not after. If you hold a data processing agreement with us, we notify you by email at least 30 days before adding one, and you may object.

Questions

Email support@humanflow.pro. If you need a signed data processing agreement for your organisation, ask and we will send one.