Sub-processors
Linqyou · last updated 2026-08-28
This is the current, complete list of third parties who process personal data on Linqyou’s behalf in order to provide the service. We update this page when the list changes and, for organization and agency customers under our Data Processing Agreement, notify you in advance of any new sub-processor as required by that agreement.
| Sub-processor | Purpose | Location | Data involved |
|---|---|---|---|
| Supabase | Database, authentication | EU (Frankfurt) | All account data |
| Cloudflare (R2) | Object storage for uploaded exports | EU (jurisdiction-restricted) | Uploaded-export files |
| Stripe | Payment processing, invoicing, tax calculation | EU/US (Stripe Inc., SCCs apply) | Billing contact details, payment metadata. Card numbers are never seen by us — Stripe handles them directly |
| AI inference provider (final vendor TBD) | Writing plain-language interpretation of your metrics and the text of your own posts | EU only — a candidate that cannot meet this is not used | Pre-computed metric summaries and the text of your own posts, for interpretation — never raw uploaded files, connection lists, messages, or contact details |
Not yet in use
The following are configured in our infrastructure for planned features but do not process any customer data today: an email-delivery provider (for magic-link sign-in and upload notifications), an error-monitoring service, and a hosting/CDN provider for the deployed application. This page will be updated with their names before they go live, in line with the advance-notice commitment above.
What never leaves our infrastructure
Raw LinkedIn export files are stored encrypted in our primary database region and are never forwarded to any sub-processor in raw form. Connection lists, messages and contact details are never sent to the AI inference provider under any circumstance — see AI transparency for exactly what is and isn’t sent.