Subprocessors
In short: Gitfence runs on one server in Germany. Database backups stay in the EU and contain no customer code. A few providers handle traffic, sign-in, email and payments. Gitfence sends nothing to AI providers.
HootCodes LTD operates Gitfence. These are the third parties that process customer data for us. Our data processing agreement (section 7) explains how we add or replace them.
Always used
| Subprocessor | What it does | Customer data | Where |
|---|---|---|---|
| Contabo GmbH | The server that runs Gitfence: application, database and disk | Everything Gitfence stores: the private mirror of connected repositories, filtered views, caches, accounts, audit logs, signed documents | Germany (EU) |
| Hetzner Online GmbH | Object storage for backups, in a dedicated Gitfence project | Database backups, made daily and kept for 14 days: accounts, settings, audit logs, signature records. Signed documents (the agreements people sign), backed up daily and kept for 30 days. No customer code. The audit log keeps the start of comments that agents post, which can quote code. | Helsinki, Finland (EU) |
| Cloudflare, Inc. | DNS, TLS, proxying and attack protection | All traffic to Gitfence, in transit, including IP addresses. Nothing is cached for us. | Global, including the USA |
| GitHub, Inc. | Sign-in, and the GitHub App that reads your repositories and opens pull requests | Repository content, GitHub identities | USA |
| Postmark | Transactional email: invitations, access requests, notifications | Recipients' names and email addresses, organization and repository names, access paths, pull request titles and the text of review comments sent to a member. Never repository files. Open tracking is off. | USA |
Paid self-serve plans
| Subprocessor | What it does | Customer data | Where |
|---|---|---|---|
| Polar | Merchant of record for card payments: checkout, invoices, tax | Billing contact and payment details. We never see card numbers. | USA, EU |
Only if you connect them
| Subprocessor | What it does | Customer data | Where |
|---|---|---|---|
| Slack | Notifications and approval buttons | Event summaries (names, paths, reasons), Slack user IDs | USA |
| Linear | Checking whether a linked ticket is still open | Ticket keys and status | USA |
| Jira (Atlassian) | Checking whether a linked ticket is still open | Ticket keys and status | Your Atlassian region |
Your identity provider (for single sign-on and SCIM) and the webhook or SIEM endpoints you configure are your own choices and destinations, not our subprocessors.
Not used
- No AI providers. Gitfence calls no AI or large-language-model API. Your code is never sent to one and never used to train models.
- No advertising or third-party analytics. This website sets no cookies and loads no third-party scripts.
- UpButler (HootCodes' own uptime monitoring product, operated by HOOTCODES LTD) checks Gitfence's public URLs from outside and runs our public status page. It sees only those URLs and whether they answer, never customer personal data, so it is an internal tool, not a subprocessor.
Changes and transfers
We give at least 30 days' notice before adding or replacing a subprocessor that handles customer personal data, by updating this page and emailing account admins. You can object on reasonable data protection grounds within that period.
Where a subprocessor processes personal data outside the European Economic Area, we rely on the EU-US Data Privacy Framework where the provider is certified, otherwise on the European Commission's Standard Contractual Clauses.
Questions: [email protected].
Last updated: 2026-10-10.
Fence your first repository in minutes
Free for one repository and your own team. Add a restricted person and Pro is free for 14 days, no card.