Cookies and browser storage
Small preferences keep the interface in your language and your working session available.
What this site uses
The public pages use the existing language and appearance preferences. We have not added advertising pixels, marketing analytics or a tracking-consent tool. Essential authentication and requested app settings are used when you enter and use the app.
Cookies are sent to the site with matching requests. Local storage stays in your browser unless an app function reads it and submits the relevant information. Functional storage is used to provide the feature or preference you request; it is not permission for unrelated tracking.
Language and beta acknowledgement
rizicon-locale is a first-party cookie written when you choose Slovak or English. Its configured lifetime is 365 days.
rizicon-beta-acceptance is a first-party cookie written after you accept the beta notice when entering the app. It records the notice version for up to 365 days. A new notice version may ask you to acknowledge it again. This cookie is not an authentication credential and does not record consent to advertising.
Sign-in cookies
Supabase uses first-party session cookies, normally named sb-<project-ref>-auth-token (possibly split into numbered chunks), and temporary authentication cookies when required by the sign-in flow. They allow the browser and server to recognise and refresh your session.
The installed Supabase SSR library sets a maximum cookie lifetime of 400 days for stored auth cookies; refreshes can renew it. Actual session and token validity depends on the authentication configuration, and the cookie lifetime does not guarantee access for that period. Sign out to end the current app session, or remove site data in your browser.
Preferences and working data in local storage
rizicon-theme stores your appearance choice. In the app, rizicon-budget-plan and rizicon-suggestions-config store planning data or a local fallback for settings. rizicon-ai-mode and rizicon-ai-config store AI preferences and any provider keys you choose to enter.
Local-storage entries have no built-in expiration in this release. They remain until overwritten, removed in the app where a control is available, or cleared through your browser. Clear site data on shared devices when appropriate; removing local planning data can remove unsynchronised work.
Map services inside the app
Entering the map loads Mapbox services, which may use browser cache or local storage for map delivery and service-use accounting. Requests also expose ordinary network information to Mapbox. This is separate from the decorative graphics on the public pages, which do not initialise Mapbox.
The provider’s storage behavior can change with its software version. The linked Mapbox information describes its use of data and storage. Accepting the beta notice does not constitute consent to advertising or other unrelated tracking.
Your choices
Use the language and theme controls to change preferences. Your browser’s privacy settings can inspect, delete or block cookies and site data. Blocking session cookies can prevent sign-in; clearing saved settings resets the corresponding features.
If non-essential analytics or advertising is introduced later, this notice and the necessary choice controls must be updated before that processing starts. For questions about storage or personal data, use the contact form.