Cookies and browser storage

Watch uses authentication cookies to keep you signed in and protect your account session. These are required to provide the account service you request. We do not include advertising cookies, analytics trackers, session replay or social-media embeds in the application.

What the application stores

• Supabase authentication cookies (sb-…-auth-token), including chunked cookie values when needed, hold session credentials. They are HttpOnly; their expiry and refresh follow the configured authentication session.
• watch_dev is a first-party device cookie set by the website. It lasts 1 year and is SameSite=Lax, and Secure on HTTPS. It is readable by page scripts because the browser computes it. It holds a SHA-256 hash of browser characteristics (user agent, platform, language, time zone, screen size, CPU cores and memory). It is used only for account security: recognising devices in your sign-in history and triggering new-device emails. It is not used for advertising or analytics, and it is required for those security features.
• Local browser storage holds display preferences, saved alerts, watchlists, notification read status and locally entered goal, risk or commission preferences. These local values do not enforce billing or replace server-side risk controls. The standalone dashboard also stores setup-guide dismissal locally; the hosted service saves that status in your encrypted account workspace.
• Temporary browser session storage may support interface state. It is separate from your server-managed subscription and encrypted integration credentials.

Your controls

Sign out to end your account session. You can delete site cookies and storage through your browser settings; this signs you out and removes local preferences. Blocking authentication cookies prevents sign-in. Clearing browser storage does not end a prepaid plan or delete your account; contact support if you need help with your account.

Other services

Checkout opens on the active payment processor's own hosted page (Stripe, Paystack, Flutterwave, Fincra or Korapay), which may set its own cookies under its own policy. Those services, Supabase authentication, hosting infrastructure and your configured providers have their own privacy and storage practices. They are not embedded marketing widgets.

If optional tracking is added

Optional tracking must remain disabled until the applicable consent requirements and notices are implemented. This version does not load optional tracking and therefore does not show an "accept all" tracking banner.