1. Who we are
Fwozen is a service operated by Wavicon. These terms are governed by the laws of the state in the United States where Wavicon has its principal place of business, and the courts there have exclusive jurisdiction. If you need the entity details, the registered address, a DPA, or an MSA for a procurement file, mail [email protected] and we will send them.
2. What the service does
Fwozen is a GitHub App, web application, Slack app, and REST API that blocks merges and deploys by writing check runs to your repositories, on your instruction or on a schedule you configure. It reads repository, branch, and pull request metadata, and GitHub’s branch rules. It does not read your source code.
3. Your account and your organisation
- You need a GitHub account and the right to install an app on the organisation.
- You are responsible for who you invite and what they do. Fwozen records every action with an actor, which is what makes that responsibility auditable rather than theoretical.
- API tokens are yours to protect. Revoke them in the app the moment you suspect a leak.
4. Acceptable use
Don’t use Fwozen to break the law, don’t attack the service, and don’t resell it as your own. We rate-limit the API to keep it available for everyone; the current limits are published in the docs.
5. Availability, and what happens when we are down
A freeze writes an explicit failing fwozen check to each open pull request in scope, and GitHub stores that result. An outage on our side does not clear it, so pull requests already blocked by a live freeze stay blocked while we are unreachable.
An outage does affect new work. A pull request opened during one, or a new commit pushed to an existing pull request, needs a check written to a head commit we have not seen, and while we are down nothing writes it. Fwozen does not rely on a missing check to block a merge, so those pull requests can merge until our reconciler catches up and re-asserts the freeze. This is the behaviour you are agreeing to, and it is described in full on the security page.
No plan carries an uptime commitment or a service credit, and we are not going to write one we have no operating history to stand behind. What exists instead is a public status page at status.fwozen.com, and support with a stated response target: email within two business days on Team, priority within one business day on Business. Where our responsibility ends is worth stating plainly too — GitHub’s own availability is not something we can promise on, and a freeze already written to a pull request is enforced by GitHub, not by us.
6. Payment
- Plans and prices are on the pricing page and are per organisation, never per user.
- Monthly plans renew monthly; annual plans renew annually. Both cancel at period end.
- If a payment fails, we show you a banner and keep freezing. We do not disable a safety control over billing.
- Taxes are calculated at checkout. Every plan is card, self-serve, in the app.
7. Cancellation
You can cancel in the app, in two clicks, without emailing anyone. You keep access until the end of the period you paid for, then drop to Free. Freezing keeps working on Free.
8. Your data
You own it. We store the minimum needed to operate the freeze engine, listed exactly on the security page. Delete your organisation and the data goes; private data is purged within 30 days of cancellation.
9. Liability
Fwozen is a control you configure, not a guarantee about your engineering process. We will tell you when a freeze is not enforced — that is the whole product — but we cannot be liable for a merge that happened because the check was never required, a bypass actor was configured, or someone with admin rights chose to override it. Our aggregate liability is capped at the fees you paid us in the twelve months before the claim, which is the ordinary shape for a service at this price. Nothing here limits liability that cannot be limited by law.
10. Changes
Material changes get an email and 30 days’ notice before they take effect, and the effective date at the top of this page changes with them.
11. Contact
[email protected] for anything commercial, [email protected] for anything security-related.