Cookie Policy
Last updated:
This policy explains the browser technologies used across CryptoVista’s application and public documentation. Cookies and local storage are different mechanisms; removing one does not necessarily remove the other.
1. Cookies and similar storage
Cookies are small values a website can send with later requests. Local storage and IndexedDB store data in the browser and are not automatically attached to every request. These mechanisms can support sign-in, preferences, saved drafts and installation of the web app.
2. Essential authentication and security
The application uses authentication cookies or session storage through Supabase to maintain your signed-in session and support secure account operations. Authentication and hosting providers can also use security-related cookies or technical identifiers. Blocking required session storage can prevent sign-in or account features from working.
3. Preferences and recovery data
The application can retain interface preferences, recent navigation, local recovery drafts and user-selected settings in browser storage. These can remain until replaced, cleared by the feature or removed using browser site-data controls. A locally saved draft is not proof that it has been saved to the server.
4. Documentation analytics
The documentation includes Vercel Web Analytics for page and visitor statistics. Vercel describes this analytics product as operating without traditional analytics cookies and without cross-site tracking. This does not mean hosting, authentication or other application features never process technical request data.
5. Google and other third-party pages
When you leave CryptoVista for Google sign-in, a payment page, an exchange or a linked site, that provider controls its own cookies and storage under its own policy. CryptoVista’s site-data controls do not clear data stored by another domain.
6. Your controls
Use your browser’s privacy and site-data settings to review, block or delete cookies and browser storage. This can sign you out, reset preferences or remove unsynchronized work. Browser notification permission is managed separately. Use available application controls or contact support about an optional processing choice; a browser setting does not itself submit an account-deletion request.