1. Subprocessors we use
These providers process personal data for every customer. Operators are bound by written data-protection terms.
| Provider | Purpose | Data |
|---|---|---|
| Google Cloud / Firebase | Hosting, database (Firestore), file storage, authentication | Account, workspace and scan data |
| Redis hosting provider | Job queue and rate-limit counters | Short-lived job and request metadata |
| Resend | Transactional e-mail | Recipient e-mail address and message content |
| Dodo Payments | Payments, invoicing, tax (merchant of record) | Billing contact, plan and payment data |
| Google, GitHub | Sign-in with Google or GitHub, when you choose it | Name, e-mail and account identifier |
2. Only if you connect them
These receive data only when you turn the integration on, and under your own agreement with them.
| Provider | Purpose | Data |
|---|---|---|
| GitHub, Atlassian (Jira), Linear, Slack | Integrations you connect | Only what you ask to send, such as a check result, a ticket or a notification |
3. Changes
We give workspace owners at least 30 days' notice by e-mail before adding a subprocessor, as set out in the Data Processing Addendum. Questions: privacy@webcompsuite.com.