Subprocessors
The providers we use to run Scout, as listed in section 6 of our Privacy Policy.
| Provider | Purpose | Location |
|---|---|---|
| Fly.io | Application hosting and networking | United States (Virginia) |
| Fly.io Managed Postgres | Database storage and backups | Same region as the application |
| Clerk | Authentication: sign-in with Google and with email and password, email verification codes, and the account records that go with them | United States |
| Resend | Transactional email: invitations, account and billing notices, and digests | United States |
| PostHog | Product analytics, error tracking, and storage of the Service's application logs | United States (us.i.posthog.com) |
| Stripe | Payment processing and invoicing | United States and global |
| Slack | Notifications and digests, only when the Customer connects it | United States |
| GitHub, Bitbucket, Linear and Jira | Integrations, only when the Customer connects them; we read metadata from them and they receive our requests | Per provider |
We give at least 30 days' notice before adding a subprocessor that will process Customer Data, by updating that page and emailing the organization's Admins. If you reasonably object on data protection grounds within that period, we will work with you in good faith to find an alternative; if we cannot, you may terminate the affected part of the Service and we will refund prepaid fees for the unused period.