Sub-processors
Last updated: [Last Updated Date]
[Company Legal Name] uses the third parties below to process customer personal data and account holder data. Each is bound by a written contract with data protection terms. We tell customers at least [Sub-processor Notice Days] days before we add or replace one, as the Data processing agreement says. To get these notices, write to privacy@[domain].
An entry marked [to be confirmed] is planned but not yet chosen, and no data goes to it until it is.
| Sub-processor | Purpose | Data | Location |
|---|---|---|---|
| Vercel | Hosts the customer web app and the admin console | Account holder data, lead and message data as it passes through the app, and the sealed (encrypted) session block that the web tier cannot open | [Vercel Region] |
| Amazon Web Services | Hosts the worker that carries out campaigns, with secret storage and logs | All customer personal data the worker handles, including the decrypted LinkedIn session while an action runs | [AWS Region] |
| Neon | The database that stores the product's data | Account holder data, leads, conversations and messages, action records and the sealed session blocks | [Neon Region] |
| Stripe | Payments and the customer portal | Billing contact, plan, seat count and payment status. Card details go directly to Stripe and are not stored by us | [Stripe Region] |
| Resend | Sends the product's emails | Email address and name of the recipient, and the link or six digit code in the email. Notices about replies hold no message text | [Resend Region] |
| Slack | Receives operator alerts from the worker and the admin console | Alert names, counts and the name of the affected area. Never message text, cookies or tokens | [Slack Region] |
| Dead man's switch service [to be confirmed] | Receives a regular signal from the worker so that we are told when it stops | The time of each signal only, no customer data | [Heartbeat Region] |
| Error tracker [to be confirmed] | Collects error reports so we can fix faults | Error details after cookies, tokens and message text are scrubbed out | [Error Tracker Region] |
| IP proxy provider [to be confirmed] | Supplies the fixed IP address each account uses to reach LinkedIn | The traffic between our worker and LinkedIn for each account is routed through the provider. It is encrypted in transit, and the provider sees the IP addresses and the volume | [IP Provider Region] |
Not sub-processors
- LinkedIn is the network the customer chooses to use. It is not our processor.
- Google (Chrome Web Store) distributes our extension. It does not process customer personal data for us.
Changes
We list every change below with its date. [Change log entries are added here when a sub-processor is added or replaced.]