Will-e · Crypto RadarBeta version
← Back to sign in

Cookie policy

PILOT · NO CHARGES

Cookies and browser storage

Last updated: 3 October 2026. This page describes storage installed by the Will-e application. It is not a substitute for the separate privacy information required for account data.

Sign-in cookie: radar_session

First-party authentication cookie containing an opaque session token, not your password. Without “Remember me”, the login cookie is a browser-session cookie and the server session lasts up to 12 hours. Browsers with session restoration may retain session cookies after reopening. When you select “Remember me on this computer”, both cookie and session last up to 30 days. Account creation currently creates a 12-hour cookie. Signing out revokes the current session and removes its cookie. Public HTTPS access uses Secure, HttpOnly and SameSite=Strict protections.

Tab/session preferences

sessionStorage keys: crypto_radar_risk_ack records acknowledgement of the risk notice; crypto_radar_opportunity_sound stores your sound-alert choice; will_e_cookie_notice remembers dismissal of this information notice. They normally last for the browser tab/session and contain no password. Dismissing the notice is not consent to advertising or analytics.

Analytics, advertising and social networks

The current application does not include analytics, advertising trackers or embedded social-media widgets. Instagram and Telegram icons are not connected and make no requests to those services. If optional tracking is introduced, it must remain blocked until the appropriate consent is collected, with equally accessible accept and reject choices and a way to withdraw consent.

Your controls

You can sign out, leave “Remember me” unchecked, or remove this site's cookies and storage in your browser settings. Blocking authentication cookies prevents sign-in. Other public market links open third-party sites, which have their own storage and privacy policies.

This inventory covers the application code. Hosting-layer storage and the site's controller/contact details must be checked and completed before public launch.