Data processing agreement
This data processing agreement ("DPA") is part of the terms of service between you (the customer, the controller) and [legal entity name], [street and number], [postcode] [city], Belgium, company number [BE 0xxx.xxx.xxx] (Flowhawk, the processor). It applies to personal data in the telemetry and other content your workspace sends to or stores in Flowhawk. It meets Article 28 of the GDPR. You accept it by accepting the terms; if you need a signed copy, email hello@flowhawk.dev.
1. What we process
| Subject matter | Running the Flowhawk service for your workspace |
|---|---|
| Duration | As long as the agreement runs, plus the deletion periods in section 8 |
| Purpose | Storing, searching and showing telemetry; alerting and paging; AI investigations and answers you ask for |
| Types of data | Whatever your systems put in telemetry: often user ids, email addresses, IP addresses, browser and device details, URLs, and session replays where you turn them on |
| Data subjects | Your end users, staff and anyone else whose data is in your telemetry |
2. Our duties
- We process the data only on your documented instructions: these terms, your settings and what you ask in the app. If we think an instruction breaks the law, we tell you.
- Everyone at Flowhawk who can reach the data is bound to confidentiality.
- We help you answer requests from data subjects (search, export and delete in the app), and with impact assessments and consultations where needed.
- We give you the information you need to show compliance, and allow audits by you or an auditor you choose, with reasonable notice, at most once a year unless there was a breach.
3. Security
- Data at rest in Germany on servers we run, in a private network; administrative access only by SSH key, from allowed addresses.
- TLS for all traffic to the app and the ingest endpoints.
- Workspaces are isolated by row-level security in Postgres and row policies in ClickHouse.
- Secrets and common personal fields in telemetry are redacted by default before storage; you can add rules.
- Passwords are hashed; two-step sign-in and SSO are available; sensitive actions are recorded in the audit log.
- Nightly encrypted backups, kept 14 days, with tested restores.
4. Breaches
We tell you without undue delay, and within 48 hours of finding out, about a personal data breach affecting your data, with what we know and what we are doing about it.
5. Subprocessors
You allow us to use the subprocessors below. Each is bound by a contract with data protection duties at least as strict as this DPA. We announce a new subprocessor at least 30 days before it starts, on this page and by email to account owners. If you object on reasonable grounds and we can't solve it, you can stop and we refund the unused balance.
| Subprocessor | What it does | Where |
|---|---|---|
| Hetzner Online GmbH | Servers, databases and backups that hold all customer data | Germany (Falkenstein, Nuremberg) |
| Stripe Payments Europe Ltd. | Payments, invoices and tax | Ireland, United States |
| Resend, Inc. | Sending email: sign-in links, invitations, pages, alerts and billing notices | EU (Ireland) sending region, company in the United States |
| Cloudflare, Inc. | DNS and receiving email sent to flowhawk.dev addresses | Global network, company in the United States |
| Anthropic, PBC | The AI model behind investigations, questions, generated pages and suggestions. Receives only the excerpts a feature needs, does not train on them | United States |
| Twilio Inc. | SMS and phone pages, only for workspaces that turn them on | United States |
Integrations you connect yourself (Slack, GitHub, Jira, Linear, Notion, PagerDuty, Opsgenie, Microsoft Teams, Discord, webhooks, your own model or ClickHouse) receive data on your instruction. They are your providers, not our subprocessors.
6. Transfers
Where a subprocessor processes data outside the European Economic Area, the transfer relies on an adequacy decision (such as the EU-US Data Privacy Framework for certified providers) or on the European Commission's standard contractual clauses (module 3, processor to processor), with additional measures where needed.
7. Your duties
You make sure you have a legal basis to send the data, tell your users as the law requires, and use the redaction settings to keep out data Flowhawk doesn't need.
8. Deletion and return
Telemetry is deleted when its retention ends. When you delete your workspace, we delete its data from the live service within 30 days and from backups within 14 days after that. Before deleting, you can export your data from Settings > Workspace.
Contact
Questions about this DPA or a signed copy: hello@flowhawk.dev.