Cookies & Storage

1. What cookies and similar technologies do

Cookies are small values stored by a browser and sent to a service under the browser's rules. Local and session storage keep values on the device for app features. Native apps can also keep preferences and authentication information. These technologies can support a session, remember choices or measure use.

2. Sign-in and security

Authentication cookies keep you signed in and help authorize account actions. Anti-bot protection can process browser and device signals to distinguish abuse. Blocking all storage or cookies can interfere with sign-in, verification, checkout or other requested features. These functions are distinct from optional marketing preferences.

3. Visitor analytics

Floot's built-in tracker measures page use using paths, referrers, browser information, language, timezone-derived country and a random 30-minute session identifier. It does not record URL query strings, fragments or the IP address as part of those page-view events. A page path can itself contain a record identifier.

The current default mode uses local storage for the session identifier. A future preferences control must apply the selected mode before non-essential storage where consent is required; the mockup below does not yet change that behavior. This draft does not claim that merely clicking a preview button disables tracking.

4. Other services and choices

Stripe checkout, Google Play, Cloudflare and other providers may use their own technologies when their services are requested. Their notices and controls apply to their processing. A browser setting is not guaranteed to control native app or server-side subscription records.

You can use browser storage controls and device permissions. Clearing storage may sign you out or reset preferences. Ask a privacy question through support if you need help understanding processing. This draft does not promise a Do Not Track or Global Privacy Control response that has not been implemented.