1.Scope and roles
This Data Processing Agreement (“DPA”) is part of the Terms of service between FixApi and the customer. It applies when FixApi processes personal data for the customer under the EU General Data Protection Regulation (“GDPR”) or the UK GDPR.
- The customer is the controller of the personal data in its code, repositories and the signals it sends.
- FixApi is the customer’s processor for that data.
- For account and billing data of the customer’s users, FixApi is a controller, and the Privacy policy applies.
If this DPA and the Terms disagree about personal data, this DPA wins.
2.Processing on instructions
FixApi processes customer personal data only on the customer’s documented instructions. The Terms, this DPA and the customer’s settings in FixApi are those instructions. If FixApi believes an instruction breaks data protection law, it will tell the customer.
If the law requires FixApi to process data in another way, FixApi will tell the customer first, unless the law forbids it.
3.Confidentiality
Everyone at FixApi who can access customer personal data is bound by confidentiality, and access is limited to those who need it to run the service. Staff access to private findings is logged.
4.Security
FixApi keeps technical and organisational measures that give a level of security suited to the risk. Annex 2 lists them. FixApi may improve them over time, but won’t lower the overall level of protection.
5.Subprocessors
The customer authorises FixApi to use the subprocessors in Annex 3. FixApi binds each one to data protection duties at least as strict as these, and remains responsible for them.
FixApi will give at least 30 days’ notice by email before adding or replacing a subprocessor. The customer may object on reasonable data protection grounds. If we can’t resolve the objection, the customer may end the affected service and receive a refund of prepaid fees for it.
6.Helping the customer
- FixApi will help the customer answer requests from people exercising their data protection rights. Owners can export and delete data in the app; FixApi will help with anything the app doesn’t cover.
- If FixApi receives such a request directly, it will pass it to the customer and not answer it alone.
- FixApi will give reasonable help with data protection impact assessments and with regulators.
7.Personal data breaches
FixApi will tell the customer without undue delay, and within 48 hours, after becoming aware of a personal data breach affecting customer personal data. The notice will describe what happened, the data and people likely affected, the likely consequences and what FixApi is doing about it, and FixApi will add details as it learns them.
8.Deletion and return
The customer can export its workspace data at any time and delete its workspace in the app. A deletion is carried out 30 days after it is requested, unless cancelled. When the agreement ends, FixApi deletes customer personal data in the same way, unless the law requires it to keep some.
9.Audits
FixApi will make available the information needed to show it meets this DPA. If that isn’t enough, the customer may audit FixApi, with at least 30 days’ notice, no more than once a year unless a regulator requires it or after a breach, and under confidentiality.
10.International transfers
FixApi is based in the US. Where customer personal data is transferred from the EU, the UK or Switzerland to a country without an adequacy decision, the European Commission’s Standard Contractual Clauses (Module 2 where the customer is a controller, Module 3 where it is a processor) apply as part of this DPA, with the UK International Data Transfer Addendum for UK data.
11.Changes to this agreement
We may change this agreement at any time. When we do, we update the date at the top and email the new version to the customer’s account owners at least 30 days before it takes effect. If the customer signs in or keeps using FixApi after that date, it accepts the new version. New subprocessors follow the notice and objection steps above.
12.Annex 1: the processing
- Subject matter: providing FixApi to the customer under the Terms.
- Duration: the term of the agreement, plus the deletion period above.
- Nature and purpose: reading the customer’s code to find code affected by API changes, alerting, writing and checking fixes, delivering them as instructions or, where the customer gives write access, as pull requests, and, if the customer uses them, receiving runtime and CI signals and confirming findings across workspaces.
- People concerned: the customer’s staff and contractors, and anyone whose personal data appears in the customer’s code, repositories or signals.
- Kinds of data: names, email addresses and usernames in code, commits and pull requests; identifiers in web addresses before they are replaced; any other personal data the customer puts in its code.
- Special categories: none intended. The customer should not put them in code or signals.
Confirming findings across workspaces
Runtime and CI signal records are compared between workspaces to confirm findings. Data-like parts of web addresses are replaced before storage, other workspaces learn only whether a match exists, and records are deleted 90 days after they were last seen. A workspace owner can stop the workspace from counting towards other workspaces’ findings in its settings.
13.Annex 2: security measures
- In transit: connections to FixApi use HTTPS.
- Secrets: passwords, sessions and email links are stored as hashes; webhook addresses are encrypted with AES-256-GCM under keys that rotate automatically.
- Sign-in: connecting or removing a sign-in method needs the password or a recent sign-in, and is emailed to the user.
- Workspace isolation: each workspace’s data is scoped to it; other workspaces never see its code, paths or messages.
- Staff access: private findings are hidden in FixApi’s internal tools unless opened on purpose, and every view is logged.
- Logging: security events in each workspace are recorded and visible to its owners.
- Code execution: fixes are checked in an isolated sandbox whose network is cut after install.
- AI providers: code is sent only to AI providers that keep no copy and don’t train on it.
- Data minimisation: source files are not kept after a scan by default, CI logs are read in memory only, and history is deleted by plan.
14.Annex 3: subprocessors
| Subprocessor | Purpose |
|---|---|
| OpenRouter and the model provider it routes to | Writing fixes from the affected code |
| Our sandbox provider | Running code to check a fix |
| GitHub | Repository access, sign-in and, with write access, pull requests |
| Resend | Sending emails |
| Slack and Discord | Delivering alerts, only where the customer adds a webhook |
| Hetzner (servers in Helsinki, Finland) | Storing and processing all service data |
Questions about this DPA go to [email protected].