Terms of service

Version 2026-09-06. This is the version recorded against your account when you signed up.

These terms are between you — or the company you represent — and Uladzislau Hreben, operating as HREBEN, a sole trader established in Poland and entered in the CEIDG register, NIP 5273097952, REGON 527715202, reachable at hello@daybook.team. They are written to be read, not to be survived.

The service

Daybook is project management with an assistant connector. You get access to it as it exists, including whatever it becomes. Features may change; anything removed that you were relying on will be announced rather than discovered.

Your account

Keep your credentials to yourself and tell us if they are compromised. You are responsible for what happens under your account and for what the people you invite do in your workspace. API keys and assistant connectors act with your authority — treat them like passwords, because that is what they are.

Your content stays yours

Everything you put into Daybook remains yours. Hosting it grants only what running the service requires: storing it, backing it up, and showing it to the people you have given access. It is not used to train models, not sold, and not shared beyond the subprocessors listed in the privacy policy.

Trial and payment

When a trial or subscription ends

The workspace becomes read-only. Nothing is deleted, nothing is hidden, and everything can still be read and exported. Paying again restores writing immediately.

This is a deliberate choice. Locking people out of their own planning to encourage payment is a thing some products do; it is not done here.

Refunds

If Daybook has not been what you expected, write to hello@daybook.team within 30 days of a payment and it will be refunded. No form, no reason required. The trial exists so this should rarely be needed.

Acceptable use

Do not use Daybook to break the law, to store other people's data you have no right to hold, or to attack the service or its other users. Automated access through the API and the connector is expected and encouraged; hammering it until it falls over is not.

Availability

Daybook does not currently offer a contractual uptime guarantee, and does not want to promise one it has not measured. Outages are worked on promptly, backups are taken on a schedule, and restoring from them is tested rather than assumed. If a formal availability commitment matters for your use, ask before you buy rather than after.

Ending it

You can stop at any time by cancelling and, if you want, asking for your data to be deleted. Daybook may end an account for a serious or repeated breach of the acceptable-use section, or for non-payment — with notice and an opportunity to export, except where the law requires otherwise.

Liability

Daybook is provided as it is. To the extent the law allows, liability is limited to what you paid in the twelve months before the claim. Nothing here limits liability that cannot legally be limited.

Changes

These terms carry a version. Material changes are announced before they take effect, and continuing to use the service after that is acceptance. If you do not accept a change, cancel and ask for a refund of the unused period.

Law

Polish law applies and the Polish courts have jurisdiction, this being where Daybook is established. Your data is stored in Finland, which is a fact about where the servers are rather than about which law governs this agreement. If you are a consumer, the protections of your own country's law are not affected by any of that, and you may still bring a claim where you live.

Questions about any of this: hello@daybook.team. A term you find unreasonable is worth raising — several of the clauses above exist because they were the ones that felt unfair when read from the other side.