tells · sub-processors
Every third party that touches tells data. What they do. Whether they see content. Where their data-protection terms live.
Active sub-processors
| Sub-processor | Function | Region | Data category | Terms |
|---|---|---|---|---|
| tells AI v1.0 inference infrastructure | AI analysis processing — receives the system prompt + cultural framing + your submitted text, returns the structured analysis. | US / EU regions | CONTENT | Enterprise data-processing terms · available to B2B reviewers under NDA |
| Paddle | Payment processing — Merchant of Record for all paid plans. Handles billing, taxes / VAT, chargebacks, customer-facing invoicing portal. | UK / EU / US | NO CONTENT | Paddle privacy · Paddle DPA |
| Plausible Analytics | Page-view-level analytics on the marketing site only. No cookies, no personal identifiers, no content. Never on application surfaces. | EU (Germany) | NO CONTENT | Plausible data policy · Plausible DPA |
| vøiddo-mailer (self-hosted SMTP) | Transactional email — verification, password reset, billing receipts, lifecycle drips. Operated by vøiddo on the same VPS family; no third-party sender. | EU (Israel · Eilat) | NO CONTENT | Operated by vøiddo — see tells Privacy Policy §7 |
| Sentry | Error tracking. PII scrubbing on (send_default_pii=False). Receives stack traces and error metadata only — request bodies are not forwarded. |
US | NO CONTENT | Sentry privacy · Sentry DPA |
Notes on each
tells AI v1.0 inference infrastructure
The only sub-processor that sees the text you submit for analysis. tells AI v1.0 runs under enterprise data terms: customer content is not used to train, fine-tune, or evaluate the engine, and is not retained beyond the request lifecycle for cross-tenant purposes. Per-user rate limiting prevents enumeration. The exact prompt family that ships with each request is maintained by vøiddo and versioned internally for B2B review.
Paddle
Paddle is the Merchant of Record. They receive your email and billing address. They never receive the content of your analyses. They are also our refund / chargeback / VAT counterparty under their global tax compliance.
Plausible Analytics
Page-view counters and referrer hostnames on the marketing site (tells.voiddo.com/, the landing page only). No cookies. No fingerprints. No content from analyses. Plausible is not loaded on authenticated application pages.
vøiddo-mailer (self-hosted SMTP)
Transactional and lifecycle email runs on a self-hosted SMTP service operated by vøiddo on the same VPS family as the tells application. We do not use Postmark, SendGrid, Resend, Mailgun, or any third-party mail relay for tells. This keeps the email subject lines + bodies (which can contain plan / billing context) inside our own infrastructure.
Sentry
Sentry receives Python and JavaScript exception stack traces with PII scrubbing turned on. Request bodies, query strings, and authenticated user IDs are stripped before send. Sentry is used only to catch and alert on application errors; it does not see analysis content.
What is NOT in our sub-processor stack
For symmetry with the list above:
- No CDN that terminates TLS (no Cloudflare in front of the application).
- No analytics pipeline beyond Plausible page-views.
- No CRM / marketing automation (no HubSpot, Mailchimp, ActiveCampaign, Iterable, Customer.io).
- No session-replay vendor (no FullStory, Hotjar, LogRocket, Microsoft Clarity).
- No customer-support SaaS that holds analysis content (support runs through support@voiddo.com; ticket bodies stay in vøiddo-mailer).
- No ad networks. No retargeting pixels.
- No third-party SMS provider — tells does not send SMS.
Updates to this list
We commit to updating this page within 14 days of any change to the sub-processor stack — adding, removing, or replacing a vendor. Material additions (any vendor that would receive CONTENT) are also notified by email to all active accounts at least 30 days before they go live, so you can object or terminate without penalty.
For audit / due-diligence purposes, the canonical machine-readable version of this list is also pinned in the tells-encryption-spec repo as SUB_PROCESSORS.md with a versioned diff history.