Cookie Policy
Last updated July 27, 2026
We set three cookies, all of them for signing you in, and none of them for watching you. This page lists every one, plus the handful of values the app keeps in your browser's local storage.
1. The short version
We do measure how the product is used, and it is worth being clear that this does not change the answer above: our analytics is first-party, runs on our own servers, and identifies anonymous visitors by a daily-rotating hash computed from the request itself. It stores nothing on your device — no cookie, no local storage entry, no identifier of any kind. There is no script from a vendor, so there is also nothing for a blocker to block. The privacy policy explains exactly what that measurement records.
If a cookie banner ever appears on this site, it will be because we started setting something that needs one, and this page will say what it is first.
2. The cookies we set
All of these are first-party, set by our authentication layer, and marked HttpOnly and SameSite=Lax — meaning your browser will not hand them to JavaScript, and will not send them along with requests originating from other sites. On our production domain they also carry the Secure flag and a __Secure- name prefix.
| Cookie | Purpose and lifetime |
|---|---|
| better-auth.session_token | Identifies your signed-in session. Without it every page load would ask you to sign in again. Expires with the session — 7 days by default, or when you sign out. |
| better-auth.dont_remember | Records that you chose not to stay signed in, so the session ends when you close the browser. Only set when you make that choice. |
| better-auth.state | A short-lived random value used during Google or GitHub sign-in to prove the response coming back is the one we asked for. Lives about five minutes and only exists during that flow. |
None of these carry a tracking identifier, and none of them are read by anyone but us. We do not set a cookie on the marketing pages at all — you can read the homepage, pricing, and the blog without one.
3. Local storage
Separately from cookies, the app keeps three small values in your browser’s local storage. These never leave your device — they are not sent to our servers with requests the way a cookie is.
| Key | What it holds |
|---|---|
| viberss.sign-in.remembered-email | The email address you last signed in with, so the field is pre-filled. Only written if you ask to be remembered. |
| verify-email:lastSentAt:… | When a verification email was last sent, so the resend button can enforce its cooldown without a server round trip. |
Clearing site data in your browser removes both, at the cost of re-entering your email at sign-in.
4. What is not here
Things a page like this usually has to disclose, which we can simply say we do not use:
- No analytics cookies and no third-party analytics at all — no Google Analytics, Plausible, PostHog, Mixpanel, or anything comparable. Our own measurement is cookieless, as described above.
- No advertising or retargeting cookies, and no relationship with an ad network.
- No social-media tracking pixels.
- No session-recording or heatmap tools.
- No third-party fonts or scripts — our typeface is served from our own domain, so no CDN sees your request either.
Our privacy policy covers the data we do collect, which is a different question from the one this page answers.
5. Turning them off
Every browser lets you block or delete cookies, usually under Settings → Privacy. Because the only cookies we set are the ones that carry your session, blocking them means you can still read the public pages but cannot stay signed in to the reader.
Do Not Track
We honour Do Not Track by default, in the sense that there is nothing to switch off. Our own measurement cannot follow you between days or between sites whether the header is set or not, and no third party receives anything to honour it with.
6. Changes
If we add or remove a cookie, this page changes and the date at the top moves. If we ever add a category that requires consent, we will ask for it before setting anything. Questions go to hello@feedpik.com.
Questions about this page? Write to hello@feedpik.com.