Draft version 2026-11-10-draft-2. Reviewed 10 November 2026. Effective date: [TO COMPLETE: PUBLICATION DATE AFTER REVIEW].
This notice explains browser storage and similar technologies in Grinzu. The Privacy Policy explains the associated personal information, purposes, recipients, international processing and rights. The operator and public privacy contact are identified there.
What these technologies do
Cookies are small records a website places in a browser. Local storage can keep settings on a device. Security challenges and connection services may also process browser/device signals without creating an ordinary advertising cookie. Some records are needed to provide a feature you request, while others require a separate choice under applicable law.
Sign-in and security
The current app uses Supabase's browser/server sign-in integration. Authentication/session cookies maintain sign-in, refresh access and support a sign-in redirect. Exact names may include a project-specific prefix and may be split across multiple cookies. We do not publish real session values, one-time codes or tokens in this notice. The sign-in library may also keep session information in your browser's local storage, and your theme choice (light or dark) is stored there too.
Cloudflare Turnstile processes browser and device signals to distinguish legitimate use from bots. Cloudflare's Turnstile Privacy Addendum explains that service. A clearance cookie can be involved if the deployed Cloudflare challenge/pre-clearance configuration uses one; we do not claim that every standalone Turnstile check sets such a cookie.
Other website/infrastructure providers may use strictly necessary security, load-balancing or request-routing technologies. A purpose described as security is not automatically exempt from consent or privacy duties merely because a provider gives it that label.
Appearance settings and temporary state
The app's theme component can store your light/dark preference in local storage, commonly under a theme key. It remains until changed, cleared or otherwise removed by your browser/app settings. Its legal treatment depends on whether it is necessary for a feature you request and applicable local rules.
Temporary interface and conversation state can exist in browser memory while a page is open. This does not mean that Grinzu provides a stored transcript or persistent call recording. Browser or operating-system features are outside our complete control.
Advertising and optional analytics
At launch Grinzu has no advertising or behavioral advertising feature, and no marketing-analytics integration. Server error diagnostics, where enabled, are not permission to collect unnecessary information or introduce session replay. We will assess any optional measurement separately and obtain consent where required before storing/accessing non-essential information on your device.
We will not treat continued browsing, acceptance of Terms or a pre-ticked choice as valid consent where the law requires a specific affirmative choice. If optional technologies are introduced, an appropriate choice mechanism will explain them and make withdrawal reasonably accessible.
Duration and controls
Authentication-cookie life depends on the session and cookie settings actually configured. Provider security records and browser persistence can use different periods. [TO COMPLETE BEFORE PUBLICATION: VERIFY THE PRODUCTION COOKIE/STORAGE NAMES, PROVIDERS, PURPOSES, EXPIRIES, CONSENT CLASSIFICATION AND RELEVANT FIRST/THIRD-PARTY DOMAINS.]
You can clear cookies/local storage, sign out, change your theme and manage browser settings or camera/microphone permissions. Blocking necessary authentication storage may prevent sign-in. Clearing local storage does not by itself delete server-side account or safety records; use the Privacy Policy's request process.
We do not sell personal information or share it for cross-context behavioral advertising at launch. If legally applicable browser signals or opt-out rights become relevant, we will honor them in accordance with applicable law.