Subprocessors
Who processes data for CreatorSense.
Every service provider that handles personal data when we run Trace and CreatorSense, with what it does, where it runs and the data involved.
At a glance
Short list, checked against the code.
Hosting
Railway in the United States runs the app, database and marking engine.
Storage
Cloudflare R2 holds media and evidence files.
Payments and email
Stripe for billing, Resend for email.
No AI training
We do not use your content or your fans' details to train AI models.
In full
The full list, with locations.
1. Subprocessors
These are the service providers that process personal data for CreatorSense, a business name of Matt Orchard (sole trader), ABN 65 815 285 275, Sydney NSW, Australia when we provide CreatorSense. Each was checked against the services our code and configuration actually use. They may only use the data to provide their service to us.
| Provider | What it does for us | Where | Data involved |
|---|---|---|---|
| Railway | Hosting of the CreatorSense app, API, background workers and the Trace marking engine; the main Postgres database and Redis cache | United States | All account data, fan records, delivery records, Vault IP addresses and browsers, cases, logs. Media passes through while being marked. |
| Cloudflare (R2 storage) | Storage of uploaded originals, marked copies, leak copies and evidence files | Cloudflare network (bucket location chosen by Cloudflare) | Media files and evidence packs. Files may show the creator or others. |
| Cloudflare (Workers) | Edge playback of per-viewer marked streams, where streaming is used | Cloudflare global network | Signed playback tokens, viewer IP address as part of the request, stream segments |
| Cloudflare (Turnstile) | Bot check on the login and sign-up forms | Cloudflare global network | Browser and device signals, IP address |
| Google Cloud (Cloud Run, Secret Manager) | Standby host for the Trace marking engine if the main host is down; storage of service keys | United States (us-central1) | Media and delivery data only while the standby is in use; service credentials |
| Google Cloud (BigQuery) | Aggregate usage metrics, marking quality metrics and analytics for the older tools | United States | Account ids, usage counts, marking quality metrics, and daily revenue snapshots from connected platforms (older tools). No fan handles. |
| Stripe | Payments, subscriptions, invoices and tax calculation | United States and Ireland | Name, email, billing address, card details (held by Stripe), invoices |
| Resend | Sending email: sign-in, receipts, usage alerts, leak scan results | United States | Email address, name, message content |
| Sentry | Error monitoring for the app and API | United States | Technical error details, browser and device type, account id where relevant. Configured not to send default personal data. |
| Google (Analytics) | Website and app analytics, only with cookie consent; cookieless signals before a choice is made | United States | Pages viewed, actions, truncated IP, browser and device type |
| Google (Sign-In) | Sign in with Google, if you choose it | United States | Name, email, Google account id |
2. Used only when switched on or needed
| Provider | What it does | Where | Data involved |
|---|---|---|---|
| RFC 3161 timestamp authority | Signs the time of evidence records, when configured. The authority used is named in each evidence pack. | Depends on the authority | A hash of the record only |
| Arweave | Public, permanent record of evidence hashes, when switched on | Public decentralised network | Hashes, internal reference ids, event type and time. No content, handles, names, emails or IP addresses. Cannot be deleted. |
| PayPal, Wise | Paying referral commission | Depends on the provider | Payout email and amount |
3. Integrations you choose to connect
These are not our subprocessors: you connect them with your own account and they act under their own terms. We list them so you know where data goes when you use them.
| Service | Used for | Data involved |
|---|---|---|
| OnlyFansAPI | Mark-on-unlock and fan import for creators who connect it with their own API key | Buyer handles or ids and unlock events the service sends; the creator's key (encrypted) |
| Fanvue | Mark-on-unlock and fan import for creators who connect their Fanvue account | Buyer handles or ids and purchase events; access tokens (encrypted) |
| Your AI tool (MCP) | Answers your questions about your own account through the MCP connector | What the MCP tools return to it |
4. Changes and objections
We update this page before a new subprocessor starts processing personal data for Trace customers. Customers under the Data Processing Addendum also get at least 30 days' notice by email to the account owner and can object on reasonable data protection grounds by emailing info@creatorsenseai.com. If we cannot address the objection, the customer may cancel the affected service and receive a pro-rata refund of prepaid fees for it.
Other legal documents: Privacy Policy · Terms of Service · Acceptable Use Policy · Refund Policy · Referral Programme Terms · Data Processing Addendum · Cookie Policy · Security · Copyright Policy.
Questions
Ask us anything about a provider.
info@creatorsenseai.com · CreatorSense · Sydney NSW, Australia. We answer by email; there are no calls to book.