Terms of service
These terms govern your use of Chronik. They are short on purpose: the service is free, and most of what follows is about being honest with you regarding what that means.
What Chronik does
Chronik watches releases in the GitHub repositories you connect and turns them into messages in the destinations you configure — chat workspaces, webhook endpoints, and public changelog pages. It reads; it does not write to your repositories.
The service is free of charge
There is no fee, and there is no bill. Chronik costs nothing to use, and we do not intend to change that for the features described here. Two things follow, and we would rather state them plainly than let you discover them:
There is no availability commitment. No uptime figure, no response time, no guarantee that a release announcement arrives, or arrives promptly. We run the service carefully and we watch it, but a free service comes with no service level, and you should not build anything that must not fail on top of one.
We may change or discontinue it. Features can change, and the service can end. If we discontinue it we will give you reasonable notice and a way to export what you have, but we are not promising to keep it running forever.
Where the law allows it, our liability is limited to intent and gross negligence. Nothing here limits liability for injury to life, body or health, or under the Product Liability Act.
You decide who receives what — and that is a real responsibility
Every destination is your choice, and so is its audience. Connecting a chat workspace, naming a webhook endpoint, or switching a changelog page to public sends release content to people we neither know nor control. Chronik does exactly what you configured; it cannot tell whether the recipients were the ones you meant.
This matters most in three cases, and each of them has surprised somebody before:
- A private repository whose changelog you make public. Release notes from a private repository can name unreleased features, customers, or internal reasoning. Publishing the page publishes those notes.
- A repository that becomes private later. Making a repository private on GitHub does not retract what was already announced or already published.
- A webhook endpoint you no longer control. A URL that has changed hands keeps receiving everything sent to it.
Check the destination before you connect it, and check it again when your repository changes hands or changes visibility. We provide the switches and make the current state visible; the decision about who may read your release notes is yours and stays yours.
Your account
You are responsible for your account and for what happens through it. Tell us at [email protected] if you believe someone else has access.
You may only connect repositories you are entitled to connect. Whether a GitHub permission is enough to make that decision inside your organization is a question about your organization, not about Chronik.
Acceptable use
Do not use Chronik to distribute unlawful content, to attack the service or the systems it talks to, or to send volumes plainly beyond ordinary use. We may suspend an account that does, and we will say why.
Ending it
You can delete your account at any time; it takes effect immediately. We may close an account that breaches these terms, and outside that case we will give you reasonable notice.
Changes to these terms
We publish a version number with every change. A change that materially affects the bargain is put to you before it applies, rather than taking effect quietly.
Applicable law
German law applies. If you are a consumer, this does not deprive you of the protection of the law of your country of residence.