ricursor / privacy
Cookies & browser storage
Last updated 2026-10-19 · Current application practices
01Necessary authentication storage
Browser storage maintains your signed-in session and sign-in return path. Session cookies may also be used by the authentication or hosting layer. Signing out removes the app session; expiry and refresh behavior are controlled by the authentication provider. Blocking this storage can prevent sign-in.
02Recovery and privacy choices
Session storage records an observed password-recovery session and sign-in return path for the current tab. The local-storage entry ricursor-privacy-choice records a versioned necessary-only choice until you clear it or the notice version changes. A shared sidebar control can save an open/closed preference in the ricursor-sidebar-state cookie. These serve security or interface preferences, not tracking.
03No optional tracking
No optional analytics or advertising trackers are enabled in the application. Token analytics displays reported project usage, not website tracking. Fonts are served by Ricursor rather than requested from Google Fonts. Hosting infrastructure may still process necessary request logs; its retention and cookies require operator verification.
04Managing storage
Reopen Privacy & storage from the footer or account settings. Necessary storage stays active without consent; there is no optional consent to withdraw at present. You can clear site data in your browser, which signs you out and clears the saved privacy choice.