1.Who we are
FixApi watches the third-party APIs your code depends on, finds the code a change affects and delivers verified fixes, as instructions or as pull requests. In this policy, “FixApi”, “we” and “us” mean the company that runs the FixApi website and app.
For questions about this policy or your data, email [email protected].
2.What this policy covers
This policy covers personal data we decide how to use: your account, your workspace membership, our website and our emails to you. For this data we are the controller.
When your company uses FixApi on its code and its apps, any personal data inside that material (for example a name in a code comment or an email address in a web address your app reports) is processed for your company, on its instructions. For that data your company is the controller and we are its processor, and our Data Processing Agreement applies.
3.What we collect
When you create an account
- Account details: your email address, your name and a password. We store the password only as a one-way hash.
- Company details: your company name, company size and job role, which we ask for during setup.
- Sign-in methods: if you sign in with Google or GitHub, the account identifier that service gives us and the email address it confirms.
- Agreement record: the date you accepted the Terms of Service and which version you accepted.
When you use a workspace
- Members: who belongs to each workspace and their role, and the email addresses of people you invite.
- Plan: your workspace’s plan and any plan you request.
- Alerts: which member receives alert emails, and the Slack or Discord webhooks you add. We encrypt webhook addresses when we store them.
- Security log: security events in your workspace, such as sign-in method changes, member and role changes, invitations and deletion requests, with the time, the IP address and the browser that made the change.
When you connect GitHub
- You choose read or write access and install the matching FixApi GitHub App:
- With read access, the App reads repository contents, metadata, pull requests and commit statuses. It cannot change anything.
- With write access, the App also writes contents (to open fix branches) and pull requests.
- With either, only if you turn on the CI log scan, it reads Actions logs.
- When you switch, you approve the other App on GitHub, and we remove the old one.
- We store repository names, commit identifiers, the pull requests we open, the fixes we send you and the GitHub account the App is installed on.
- By default we don’t keep copies of your source files after a scan. We keep what we need to show you a finding or a fix: short code snippets, diffs, the code before and after a fix, and the evidence for a finding.
When you send runtime or CI signals
These features are optional. If you use them:
- For runtime reports we keep the API host, method, a path template, status, error code, a hash of the response shape and any Deprecation or Sunset value. Before anything is stored, we replace parts of the path that look like data (IDs, email addresses, usernames) with a placeholder.
- For the CI log scan we read logs in memory and never store them. We keep a fingerprint of each warning after removing values from it.
When you visit our website
- Analytics, only if you accept them: page views, page performance, errors, and whether you signed up or finished setup. We hide record IDs in web addresses, and we never send your name or email address to the analytics provider. See the Cookie policy.
- If you write to us: what you send us.
4.How we use it and why
We use personal data only for these purposes, each with its legal basis under the GDPR:
| Purpose | Legal basis |
|---|---|
| Running your account and workspace, scanning, alerting and opening fixes | Contract |
| Sending account emails such as sign-in alerts, invitations and deletion notices | Contract |
| Keeping the service secure, the security log and preventing abuse | Legitimate interests |
| Confirming findings across workspaces (see below) | Legitimate interests |
| Understanding how the website is used | Consent |
| Keeping records the law requires | Legal obligation |
We don’t sell personal data, and we don’t use your code to train AI models.
5.Confirming findings across workspaces
A runtime or CI finding starts as “suspected”. It becomes “confirmed” when at least three workspaces see the same thing within seven days. To check this, we compare the stored values listed above (host, method, path template, status and similar, or a warning fingerprint) between workspaces.
- Other workspaces never see your paths, messages or code. They learn only that a match exists.
- A match changes only the reporting workspace’s own finding.
- A workspace owner can stop their workspace from counting towards other workspaces’ findings in the workspace settings. Their own findings keep working.
6.AI used for fixes
To write a fix, we send the affected code to an AI model through OpenRouter: the whole file when it has 240 lines or fewer, otherwise the 100 lines on each side of the change.
- We route these requests only to providers that keep no copy of the request and don’t train on it.
- If no such provider is available, we fall back to a rule-based fix and the code goes to no other provider.
- Each fix is run and checked in an isolated sandbox before we send it to you or open a pull request.
7.Who receives your data
We share personal data only with service providers that help us run FixApi:
| Provider | What it receives |
|---|---|
| OpenRouter and the model provider it routes to | Code sent for fixes |
| Our sandbox provider | Code run to verify a fix |
| GitHub | Repository access, sign-in and, with write access, pull requests |
| Sign-in, if you use it | |
| Resend | Emails we send you |
| Databuddy | Website analytics, only after you accept |
| Slack and Discord | Alerts, only if you add a webhook |
| Hetzner (servers in Helsinki, Finland) | All data we store |
We may also disclose data when the law requires it, or to protect the rights and safety of our users or FixApi. If FixApi is sold or merged, data would pass to the new owner under this policy.
8.International transfers
We store your data on servers in Helsinki, Finland, in the EU. Some of our providers are in the US. When personal data from the EU, the UK or Switzerland is transferred to a country without an adequacy decision, we use the European Commission’s Standard Contractual Clauses and their UK equivalent.
9.How long we keep it
| Data | Kept for |
|---|---|
| Your account | Until you delete it |
| Workspace history (resolved findings, merged fixes, past scans) | Free 30 days, Starter 90 days, Team 365 days, Enterprise as agreed. Open work and each repository's latest scan are always kept |
| Runtime and CI signal records | 90 days after they were last seen |
| Data exports | 7 days, then deleted |
| Sign-in sessions | 30 days |
| Security log (sign-in method, password, member, invitation, deletion and export events) | 13 months. The IP address and browser on each event are removed after 90 days |
| Records that a deletion happened | 3 years, with the person identified only by a pseudonym |
Deleting your data
You can delete your account, a workspace or a repository in Settings. Deletion happens 30 days after you ask, and we email you with a button to cancel it. Signing in during those 30 days cancels an account deletion. At the end we delete the data, including code snippets, diffs, evidence and signal records, and email you to confirm.
After an account is deleted, we keep its security log events and the record of the deletion for the periods above, with the email address, sign-in logins and account ids replaced by a pseudonym: a code made with a secret key, from which the address cannot be read back. We use these records only to keep the service secure and prevent abuse, never to restore the account, and then delete them. Invitations still waiting for the deleted address are cancelled.
10.Your rights
Depending on where you live, you can:
- Access and portability: get a copy of your data. A workspace owner can request an export in Settings; we email a link when it’s ready, with the data as a JSON file and a PDF summary.
- Correction: fix your details in Settings, or ask us.
- Deletion: delete your account, a workspace or a repository in Settings.
- Objection: object to uses based on legitimate interests, including confirming findings across workspaces.
- Restriction: ask us to pause using your data while a request is checked.
- Withdrawing consent: change your analytics choice at any time from Cookie settings in the site footer.
Email [email protected] for anything you can’t do in the app. We reply within one month. You can also complain to your data protection authority.
If your company’s data is in FixApi and you are not our customer, please contact your company first, since it decides how that data is used. We will help it answer you.
11.How we protect it
- Passwords, sign-in sessions and email links are stored only as hashes.
- Webhook addresses are encrypted, and the keys rotate automatically.
- Connecting or removing a sign-in method needs your password or a recent sign-in, and we email you about it.
- FixApi staff can’t read your private findings in our tools unless they open one on purpose, and each time is logged.
- Code that a fix runs is checked in an isolated sandbox with its network cut after install.
12.Children
FixApi is a service for businesses and is not meant for anyone under 16. We don’t knowingly collect their data.
13.Changes to this policy
We may change this policy at any time. When we do, we update the date at the top and email the new policy to everyone with a FixApi account before it takes effect. If you sign in or keep using FixApi after that, you accept the updated policy.