Terms of service

Agreement

These terms are an agreement between HootCodes LTD, a company registered in Bulgaria, European Union (registered office: Aleksandar Stamboliyski Blvd 55, fl. 4, 1000 Sofia, Bulgaria; UIC 208188022; VAT BG208188022), and the organization or person using Gitfence ("you"). "We" and "us" mean HootCodes LTD. By creating an account or using the service, you accept them. If you use Gitfence for an organization, you confirm you're allowed to accept these terms for it. Enterprise customers may have a separate written agreement, which takes precedence.

The service

Gitfence sits between GitHub and the people and AI agents you choose. It gives each of them a filtered view of your repositories, validates what they push, and turns their work into pull requests on GitHub. It also offers Fenced CI, an MCP server for agents, invitations with document signing, access requests, temporary and ticket-scoped access, integrations, exposure reports and audit export, as described on this website.

Your account

• You sign in with GitHub. Keep access to your GitHub account and your Gitfence tokens secure; anyone holding a token can act as its owner within that token's access.
• Each AI agent token belongs to a person and never gets more access than that person.
• Tell us promptly at [email protected] if you think an account or token has been compromised.

Your responsibilities

• You decide who gets access. Gitfence enforces the access you configure. You're responsible for whom you invite, the levels you grant, the exceptions you approve and the integrations you connect. Use Preview as to check what someone will receive before you invite them.
• You must have the right to connect each repository and to share its contents with the people you grant access to.
• Documents you require (NDAs, policies) are agreements between you and your members. Gitfence records signatures and blocks access until they're signed, but isn't a party to those documents and doesn't give legal advice. Whether a typed-name signature is enforceable depends on your jurisdiction and the document.
• GitHub settings stay yours. Branch protection, Actions settings, forks and secrets on GitHub are under your control. If you choose to let GitHub run CI on restricted people's work, that workflow can read your full source; the settings screen explains this before you choose.

What Gitfence can't do

We describe the security model, what we test and its limits on the security page. In particular:

• Fencing applies from the moment you set it. Gitfence can't recall code someone already cloned, saw or copied before you restricted it.
• Redaction and leak checks are best effort. Fenced CI removes hidden source from test output, and the Gitfence pull request check looks for hidden code in proposed changes. Both catch verbatim and near-verbatim copies, not every transformation (for example, encoded output).
• Some information can still be inferred, such as test pass/fail results and timing, and the messages of commits that changed both hidden and visible files.

These limits are part of the service as described; they aren't failures of it.

Plans and billing

• Free: 1 repository, you and your full-access team, with no limit on your AI agents. No restricted people.
• Pro: $29 per restricted person per month, or $24 per month billed yearly. A restricted person is anyone whose access to a repository is less than everything; each counts once across your repositories. Full-access teammates and admins are free. AI agents act for a person and are not counted or limited; an account with no person behind it that you restrict counts as a restricted person.
• Free trial: the first time an organization adds or invites a restricted person, it gets Pro free for 14 days, with no card. One trial per organization and per owner GitHub account. If you don't subscribe by the end, you can't add or invite restricted people; the ones you have keep their access for 5 more days, after which it is paused until you subscribe. If a paid subscription lapses, restricted people keep their access for 14 days, after which it is paused until you renew. Full-access teammates are never affected.
• One-person minimum: Pro is billed for at least one restricted person, even if you have none.
• Seat changes: when you add or remove restricted people, the subscription quantity updates automatically and the difference is prorated by our payment provider.
• Payment: Polar is the merchant of record and processes payments, tax and invoices under its own terms.
• Late payment or cancellation: you keep Pro allowances for 14 days. After that you can't add restricted people or repositories, but existing members, tokens, clones and pushes keep working.
• Enterprise: pricing, dedicated infrastructure and any service levels are set in a separate agreement.
• Price changes: we'll give at least 30 days' notice before a price change applies to your next billing period.

Fair use

Don't use Gitfence to:

• break the law or infringe others' rights;
• attack, probe or overload the service, or get around its limits or security (report vulnerabilities to [email protected] instead; see the security page);
• run workloads in Fenced CI other than your project's tests (for example, mining or bulk computing);
• scrape the service or resell it without our agreement.

We may rate-limit, suspend or end access that puts the service or other customers at risk. Where we reasonably can, we'll warn you first.

Your content

You own your code and data. You give us permission to store, process and transmit it only as needed to run Gitfence for you, including the mirror, filtered views, caches and backups. We don't use your code to train AI models or send it to AI providers; the privacy policy explains what we store.

For your repository content and your members' personal data, you are the controller and we are your processor. Our data processing agreement (GDPR Article 28) applies to that processing and forms part of these terms.

Third-party services

Gitfence depends on GitHub and, if you connect them, on Slack, Linear, Jira and your webhook endpoints. Your use of those services is governed by their own terms, and their outages or changes can affect Gitfence.

Availability and changes

We work to keep Gitfence available and secure, but the service is provided "as is" and "as available", without warranties of any kind, except where the law doesn't allow that to be excluded. We may change or improve features; if we remove something material to a paid plan, we'll tell you in advance.

Liability

Limitation of liability and indemnity to be written with legal counsel.

Ending the service

You can stop using Gitfence and cancel at any time from the billing portal. We can end these terms if you materially break them and don't fix it after notice, or immediately for serious abuse. After an account ends, we delete its data as described in the privacy policy. Export anything you need first.

Changes to these terms

We'll post changes here and update the date below. For material changes, we'll email account admins at least 30 days before they take effect.

Governing law

These terms are governed by the laws of Bulgaria, and the courts of Sofia, Bulgaria have exclusive jurisdiction. If you are a consumer resident elsewhere in the EU, this does not deprive you of the protection of mandatory consumer laws in your own country, and you may also bring proceedings there.

Contact

Questions about these terms and other legal matters: [email protected]. Support: [email protected]. Privacy matters are covered by our privacy policy and go to [email protected]. Company details are on our legal page.

Last updated: 2026-10-10 (draft).