Cookie notice.
DayBack uses three cookies. All of them are for signing in.
| Cookie | Purpose | Set by | Lasts |
|---|---|---|---|
tj.session_token | Remembers that you signed in with your emailed link, so you are not asked again on every page | DayBack | 7 days, refreshed while you use DayBack |
tj.session_data | A signed copy of your session, so pages do not look it up on every request | DayBack | 5 minutes |
tj.state | Set only when you sign in with Google. Checks that the reply from Google belongs to the sign-in you started | DayBack | 5 minutes |
They are set when you sign in, all are marked SameSite=Lax so they are not sent from other websites, and they hold nothing except your sign-in. They are essential to the service, so there is no consent banner to click.
If you sign in with Google, Google’s own sign-in pages use Google’s cookies, under Google’s policy. DayBack does not see them.
No analytics cookies. No advertising cookies. No tracking pixels. No third-party cookies.
We do measure how quickly pages load, using Vercel Speed Insights. It reports Core Web Vitals: how fast the page appeared, how soon it responded, whether it moved about while loading. It sets no cookie and does not identify you or follow you between sites.
To clear them: sign out, or clear cookies for this site in your browser settings. You will simply need to sign in again next time.
Questions: hello@dayback.app.
Last updated: 27 September 2026