Cookies & Storage
What Submilo remembers in your browser, and how you can control it.
Last updated: 27 October 2026Local storage
Submilo uses your browser’s local storage for saved profile display details, display settings, cached exchange rates, and Supabase authentication session tokens. Account subscription records and their reminder preferences are stored in Supabase. Older browser-only records may remain locally. Local storage is different from a cookie: it remains in your browser and is not automatically sent with each page request.
Cookies and tracking
The current application does not set advertising or analytics cookies and does not include an advertising or analytics integration. Google and email sign-in use Supabase Auth, with session tokens stored in local storage by the browser client. This version does not use authentication cookies. This page should be reviewed when hosting, authentication, analytics, or other integrations change.
External requests
Google sign-in communicates with Google and Supabase. Email/password sign-in and account subscription reads and writes communicate with Supabase. Public currency rates are requested from ExchangeRate-API. Custom website logos are requested from Google’s favicon service. These providers receive normal connection information, and Google receives the domain whose icon you request. Their handling of those requests is governed by their own policies.
Managing storage
You can remove this site’s stored data in your browser’s site settings. Export your records first from Settings → Data & privacy if you want to keep them. Clearing browser storage removes the local sign-in session, preferences, and any older browser-only records. Account subscriptions remain in Supabase. Blocking local storage can prevent Submilo from keeping you signed in.