Subprocessors and data recipients
This page lists every outside organisation that receives personal data when TerrAlert runs, what each one does, where it is, and on what terms. It is the list referred to in our Privacy Policy and our Data Processing Agreement.
1 How this list works
TerrAlert, Inc., United States ("TerrAlert") operates the service at terralert.io. Privacy contact: [email protected].
We sort each organisation by the role it plays:
- Processor acts only on TerrAlert's instructions, under its data processing terms. When TerrAlert processes personal data for a business customer (for example, the email addresses of its team members), these are subprocessors under our Data Processing Agreement.
- Independent recipient is a service your browser contacts directly to draw a map, search for a place or sign you in. It decides for itself how it uses what it receives, under its own privacy policy, which we link below.
- No personal data is a data source TerrAlert's servers query for satellite imagery or land signals. These requests carry map coordinates only.
2 Where TerrAlert runs
The TerrAlert application, its database (PostgreSQL with PostGIS), its job queue (Redis), its map tile server and the imagery it processes all run on servers we operate at DigitalOcean, in a single region in the United States. These components are not separate providers: no other company hosts the database.
If you are in the European Economic Area, the United Kingdom or Switzerland, this means your personal data is stored in the United States. The safeguards for that are described for each provider below and in section 9 of our Data Processing Agreement.
3 Subprocessors
| Provider | What it does for TerrAlert | Data involved | Location | Transfer safeguard | Role |
|---|---|---|---|---|---|
| DigitalOcean, LLC | Server hosting for the application, database, job queue, processed imagery and the database backups kept on the server. | Everything TerrAlert stores: account and profile data, areas and detections, alert history, support tickets, contact enquiries, logs. | United States (single region) | EU Standard Contractual Clauses (2021/914) and UK Addendum, in DigitalOcean's data processing terms | Processor |
| Backblaze, Inc. | Off-site storage of encrypted database backups (Backblaze B2), so the database can be restored if the server is lost. | Encrypted copies of the whole database, which contains everything TerrAlert stores. Each backup is encrypted on our server with age before it is uploaded, and Backblaze does not hold the key, so it cannot read the contents. Copies are removed about 35 days after upload by the bucket's retention rule. | United States (US East region) | EU Standard Contractual Clauses and UK Addendum, in Backblaze's data processing addendum | Processor |
| Cloudflare, Inc. | DNS, TLS encryption at the edge and protection against denial-of-service attacks for terralert.io. | IP address and the content of every request to terralert.io, including the API at terralert.io/api, as it passes through. Cloudflare does not store the application's data. | United States company; global edge network | EU Standard Contractual Clauses and UK Addendum, in Cloudflare's data processing terms | Processor |
| Supabase, Inc. | Authentication only: sign-up, sign-in, password reset, two-factor authentication, and the confirmation and password-reset emails. TerrAlert's own database is not hosted at Supabase. | Email address, password (stored by Supabase in hashed form, never by TerrAlert), name, organisation and time zone given at sign-up, two-factor settings, sign-in IP address and session tokens. Name and email from Google if you use Sign in with Google. | United States company. The region of TerrAlert's Supabase project is available on request. | EU Standard Contractual Clauses and UK Addendum, in Supabase's data processing agreement | Processor |
| Stripe, Inc. | Payments and subscriptions: checkout, card processing, invoices, the billing portal and, where enabled, tax calculation. | Name, email address, organisation name, billing address, tax ID if you give one, card details (entered on Stripe's page and never seen by TerrAlert), payment history. | United States | EU Standard Contractual Clauses and UK Addendum, in Stripe's data processing agreement | Processor. Stripe is also an independent controller for its own fraud prevention and legal duties, under Stripe's privacy policy. |
| Resend (Plus Five Five, Inc.) | Delivery of the emails TerrAlert sends: change alerts, the weekly digest, team invitations and support replies. TerrAlert hands each message to Resend over SMTP. | Recipient email address and the content of the message, which can include an area's name and details of a detection. | United States | EU Standard Contractual Clauses and UK Addendum, in Resend's data processing agreement | Processor |
| Sentry (Functional Software, Inc.) | Error reporting for the API server, the background worker and the web app, and performance timing for a 10% sample of server requests and background tasks. The web app sends error reports only: no session replay and no performance tracing in the browser. | The error message, its stack trace and technical context (request path or page, browser and operating system). Our servers are configured not to attach request bodies, cookies or user details to a report. A report from the web app reaches Sentry from your browser, so Sentry sees the IP address it comes from. | United States | EU Standard Contractual Clauses and UK Addendum, in Sentry's data processing addendum | Processor |
| Mailbox provider for TerrAlert's @terralert.io addresses | Hosts the mailboxes that receive support, sales and privacy email, including copies of support tickets and of contact-form and sales enquiries. Copies are deleted from these mailboxes on the same schedule as the originals (see the Privacy Policy), or sooner on request. | Name, email address and the content of the message. | To be confirmed | To be confirmed | Processor |
4 Services your browser contacts directly
When you use the map or sign in, your browser fetches some things straight from these services. TerrAlert does not send them your account data, but like any website they receive your IP address and the ordinary details your browser sends with a request (such as its type and language).
| Service | Why your browser contacts it | Data involved | Location | Terms | Role |
|---|---|---|---|---|---|
| OpenFreeMap | The background map: its style, labels and vector tiles. | IP address and the map tiles being viewed. | Operated by the OpenFreeMap project on its own servers | Your browser connects directly. openfreemap.org | Independent recipient |
| Nominatim (OpenStreetMap Foundation) | Place search on the map, and the outline of a place you pick as an area. Used only when you run a search. | IP address and the text you search for. | United Kingdom (OpenStreetMap Foundation) | Your browser connects directly. OSMF privacy policy | Independent recipient |
| Google (Google LLC, or Google Ireland Limited for Google accounts in the EEA and Switzerland) | Sign in with Google, only if you choose it. | Your Google account name and email address, which Google passes to our authentication provider with your permission. | United States / Ireland | You sign in with Google directly. Google privacy policy | Independent recipient |
5 Data sources that receive no personal data
TerrAlert's servers query these public data services for satellite imagery and land-change signals. Each request comes from our server, not your browser, and carries only map coordinates (a bounding box, an area outline or tile numbers) and TerrAlert's own access key. No name, email address or other account data is sent.
| Source | What TerrAlert gets from it | What it receives | Role |
|---|---|---|---|
| Copernicus Data Space Ecosystem (European Commission and ESA) | Sentinel-2 imagery | Area coordinates and dates | No personal data |
| NASA FIRMS (LANCE) | Active-fire detections | Bounding box of an area | No personal data |
| NASA GIBS | Flood extent tiles | Tile numbers or a bounding box | No personal data |
| Global Forest Watch (World Resources Institute) | GLAD and RADD deforestation alerts | Area outline and a start date | No personal data |
| IndexNow | Tells search engines that a public page on terralert.io changed | Public page addresses only | No personal data |
6 Destinations you choose
If you add a webhook endpoint, including a Slack or Microsoft Teams incoming webhook, TerrAlert sends alerts to the address you give it. If you invite team members, TerrAlert emails them an invitation. These are recipients you choose, not TerrAlert's subprocessors, and the data sent to them is covered by your own arrangements with them.
7 Changes to this list
Before a new subprocessor starts processing personal data, we update this page and email the owners of business accounts at least 30 days ahead, as our Data Processing Agreement requires. A customer may object to the change as the Agreement describes. Questions about this list go to [email protected].