Cookie Policy
This policy describes what we store on your device, and what we read from it, when you use our website (beliq.eu) or the dashboard (dashboard.beliq.eu). It complements our Privacy Policy. This is a translation of the German Cookie-Richtlinie, which is the original.
1. Short version
Simply visiting our website stores nothing on your device. We set no advertising cookies, no cross-site tracking cookies, and no third-party analytics cookies. There is no consent banner because there is nothing to consent to. Something is stored only once you actively use a feature, and then only what that feature needs.
2. Legal framework
Under Section 25(1) TDDDG, information may be stored on or read from your device only with your consent. No consent is required under Section 25(2) no. 2 TDDDG where the storage is strictly necessary for us to provide a service you have explicitly requested.
That is a separate question from the subsequent processing of any personal data obtained. Processing needs its own legal basis under Art. 6 GDPR. Both levels are stated separately below.
3. Strictly necessary cookies in the dashboard
The dashboard sets these once you sign in. Without them, signing in is not technically possible.
| Cookie | Purpose | Duration |
|---|---|---|
authjs.session-token /__Secure-authjs.session-token | Stores your authenticated session as a signed token. | 7 days |
authjs.csrf-token | Protects the sign-in flow against cross-site request forgery. | Session |
authjs.callback-url | Remembers the destination during the sign-in flow. | Session |
Access to your device: Section 25(2) no. 2 TDDDG.
Subsequent processing: Art. 6(1)(b) GDPR.
4. Support chat
The support chat runs on Chatwoot, which we host on our own server in the European Union. It loads only when you click it, not on page view. Once you have opened it, it stores a conversation identifier in your browser (a cookie and local storage) so your conversation stays connected while you talk to us. If you never open the chat, nothing is stored.
Access to your device: Section 25(2) no. 2 TDDDG. The chat is an additional service you explicitly requested, and the identifier is strictly necessary to run it.
Subsequent processing: Art. 6(1)(b) or (f) GDPR, see Section 9 of the Privacy Policy.
5. Cookieless analytics
For usage measurement we run Umami on our own server in the European Union. Umami sets no cookies and stores no identifier on your device. It reads only what your browser sends with the request anyway, such as the referring page, browser type and screen size; no device fingerprint is derived from this, and no recognition across websites or visits takes place.
Access to your device: nothing is stored, and what is read does not serve recognition, so no consent under Section 25(1) TDDDG is required.
Subsequent processing: Art. 6(1)(f) GDPR, see Section 11 of the Privacy Policy.
6. Cookieless error tracking
On the free invoice generator and the API playground we report errors that occur in your browser to an installation we run ourselves, so we can fix them. No cookies are set, no identifier is stored on your device, and no session is tracked. The content you type into the form is stripped before the report is sent.
Access to your device: nothing stored, nothing read for recognition, so no consent required.
Subsequent processing: Art. 6(1)(f) GDPR, see Section 10 of the Privacy Policy.
7. Newsletter
Signing up for the newsletter sets no cookies. Your consent is recorded at our email processor, not stored in your browser.
8. Pages hosted by our payment provider
When you start a subscription or open the billing customer portal, we redirect you to pages operated by Armitage Labs OÜ (Creem). On those pages Creem may set its own cookies and similar technologies under its own privacy notice (creem.io/privacy). We have no influence over those cookies.
9. Managing cookies
You can inspect cookies in your browser, delete them individually or entirely, and restrict how they are stored. If you block the strictly necessary cookies in Section 3, signing in to the dashboard will no longer be possible. Instructions are in your browser's help pages:
10. Changes to this policy
We update this policy when the technologies we use or the legal requirements change. The date at the top of this page shows when it was last revised.
11. Contact
Questions about this policy: hello@beliq.eu.