Subprocessors
Draft list taken from the integrations in the code base. The owner must confirm each row and the transfer mechanism before this page is published.
We will announce a new subprocessor in the changelog before it starts processing your data, so you have time to object.
| Name | Purpose | Data | Location | Transfer mechanism |
|---|---|---|---|---|
| Lemon Squeezy | Merchant of record: checkout, tax calculation and collection, invoices, payment processing | Name, email, billing address, payment details (held by Lemon Squeezy, not by us), subscription status | To be confirmed by the owner | To be confirmed by the owner |
| Sign-in and the source of your Search Console, GA4 and AdSense data, read with the permissions you grant | Account identifier and email; the reports you connect | Operated by Google; chosen by Google | You grant access directly to Google; see the Google API Services User Data Policy | |
| Sentry | Error monitoring, with request bodies, cookies, headers and query strings switched off | Error traces and a request identifier | To be confirmed by the owner (hosted or self-hosted) | To be confirmed by the owner |
| Email delivery provider | Transactional email such as invitations, billing notices and report delivery | Recipient address and message content | To be confirmed by the owner (the code supports more than one provider) | To be confirmed by the owner |
| Language-model provider you choose | Drafting and summaries when you use hosted calls or bring your own key | The text of the request, with personal data scrubbed before sending | Depends on the provider | To be confirmed by the owner; with your own key the contract is between you and your provider |