Security
Sub-processors
The third parties that process customer data on Costfluent's behalf: what each one does, the customer data it sees and where it processes it.
| Provider | What it does for Costfluent | Customer data it sees | Where |
|---|---|---|---|
| Hetzner Online | Hosts every application server and datastore | All customer data | Falkenstein, Germany |
| Scaleway | Stores the encrypted off-site backups | All customer data, encrypted before upload | Amsterdam, Netherlands |
| Cloudflare | DNS, the proxy in front of the public hostnames, and access control for the operator consoles | Traffic passing the proxy: IP addresses, request metadata and content | Global edge network |
| Resend | Sends every product email: sign-in, invitations, alerts, reports, invoices | Recipient email addresses and the message content | Ireland |
| Google Cloud | Runs the GCP connector: one service account per organization and the BigQuery jobs that read the billing export a customer shares with it | The customer's GCP billing export rows | The location of the customer's BigQuery dataset |
| Amazon Web Services | Holds the identity the AWS connector uses to assume each customer's read-only role, and the connector's setup template | The customer's AWS account id and the events of the setup stack; billing data is read from the customer's own bucket | Northern Virginia, United States |
| GitHub | Sign-in with GitHub, at the user's choice | The email address of a user who signs in with GitHub | United States and other countries |
| Sign-in with Google, at the user's choice | The email address of a user who signs in with Google | Global |
A cloud connector that reads your own account with access you grant is not a sub-processor for that account: the data goes from your account to Costfluent, and no third party processes it on our behalf. Providers that process customer data only at a user's choice, such as social sign-in, are marked so.
Questions about a provider or the processing behind it: Contact