COOKIE & CLIENT STORAGE POLICY
Status: Active 2026 • Real-time Storage Inspection
1. What Are Cookies and Client-Side Storage?
Cookies and HTML5 Web Storage (`localStorage` and `sessionStorage`) are small text markers or state objects placed on your device by websites you visit. They are used to make web applications function efficiently, preserve user interaction states, and provide minimal diagnostic telemetry to site operators.
2. Detailed Table of Client-Side Storage Tokens
Findermediastsh operates on an ultra-lean data storage profile. Below is the exhaustive audit of every token, key, and cookie generated across our application:
| Identifier / Key | Classification | Provider | Retention | Technical Purpose |
|---|---|---|---|---|
| findermediastsh_cookie_consent | Essential / Functional | findermediastsh.online (Local) | Persistent (365 Days) | Stores the user's explicit consent decision to prevent re-displaying the cookie consent banner on subsequent page navigations. |
| __cf_bm / cf_clearance | Strictly Necessary / Security | Cloudflare (CDN Edge) | 30 Minutes to 24 Hours | Distinguishes authentic human users from malicious automated bot traffic and mitigates Layer 7 DDoS threats across the edge network. |
| fms_directory_filter_state | User Preference | findermediastsh.online (Session) | Session Only | Remembers your active city filter selection (e.g., Berlin vs. Tbilisi) during active browsing sessions. |
3. Browser Opt-Out & Local Storage Purge Instructions
You possess full control over stored cookies and local keys. You can configure your browser to block, alert, or delete all client-side tokens at any time:
- Google Chrome: Settings → Privacy and Security → Site Settings → Cookies and data.
- Mozilla Firefox: Settings → Privacy & Security → Cookies and Site Data → Clear Data.
- Apple Safari: Preferences → Privacy → Manage Website Data → Remove All.
- Brave / Edge: Settings → Cookies and Site Permissions → Manage and delete cookies.
Note: Clearing your local storage will reset your cookie consent status, causing our consent dialog to re-render upon your next visit.