Cookies

Effective 8 October 2026 · version 1.0

Companion uses one cookie. It is required to keep you signed in, and it is the reason no cookie banner appears anywhere in the product.

The one cookie

Name	Purpose	Lifetime	Details
`cfd_session`	Keeps you signed in to the app	30 days	HttpOnly, so no script can read it. SameSite=Strict, so it is never sent from another site. Secure, so it is only sent over HTTPS.

This cookie contains a signed session token. It does not contain your password, your Telegram identity, your location, or anything else about you. Signing out or deleting your account clears it.

What is not used

No advertising cookies. There is no advertising and no ad network in the product.
No analytics cookies. Google Analytics, Plausible, Mixpanel, and similar tools are not present.
No social tracking pixels. Nothing on the site or in the app loads a third-party tracker.
No fingerprinting. The sign-in records kept to recognise a new device are stored server-side and are not used to identify you across other sites.

Why no consent banner

Consent rules require a banner when cookies are used for anything other than strictly necessary purposes. There is exactly one cookie, it is strictly necessary, and without it you cannot stay signed in. A banner with a single non-optional button would inform nobody of anything they could act on, so it is not shown. This page is the disclosure instead.

About the website

This website sets no cookies. It loads one web font from Google Fonts, which means your browser contacts Google when the page opens. We store no identifier from that request. A privacy-respecting font cannot be added without self-hosting the files, which is on the roadmap.

Push notifications

If you allow notifications, your browser stores a push subscription on your device and sends it to us. It is not a cookie and is not used for tracking. It is stored only while notifications are enabled, and is removed when you turn them off or delete your account.