Cookie Policy
What we actually use
Update is built to need very little in the way of cookies. Sign-in on the mobile app, the reader page, and the organization/platform portals is handled with a security token kept in the app or browser's local storage, not a tracking cookie — so most of what people usually mean by "cookies" (cross-site ad tracking, third-party marketing pixels) simply isn't part of how this platform works today.
| Name / type | Purpose | Duration |
|---|---|---|
| Session/auth token (browser local storage — not a cookie) | Keeps you signed in to the reader page, mobile app, or organization/platform portal | Until you sign out, or the token expires |
As of this policy's last update, our servers do not set any cookies at all — no session cookies, no analytics cookies, no advertising cookies. Sign-in relies entirely on a bearer token stored in your browser's local storage, not a cookie. If that changes — for example, if we add analytics or embedded third-party content that sets its own cookies — we'll update this page and this table before it goes live, and where required by law, ask for your consent first via a cookie banner.
Controlling cookies
Because we don't use non-essential cookies today, there's nothing to opt out of beyond normal browser controls. You can still clear your browser's local storage/cookies at any time through your browser's settings — doing so will sign you out.
Third-party channels
If you interact with Update through WhatsApp, Telegram, or by signing in with Google/Facebook, those platforms may set their own cookies under their own policies — that's between you and them, governed by their own cookie/privacy policies, not this one.