Cookies & Local Storage Policy
Effective date: November 4, 2026
We use browser storage only as described below. A "cookie" is not the only technology covered by European rules: localStorage and similar technologies can also require consent depending on their purpose.
Technologies planned for the free beta
Authentication/security
- Examples
- Session cookie, anti-CSRF and security tokens
- Proposed treatment
- Necessary for an explicitly requested sign-in/security function; no marketing use
Functional preferences
- Examples
- Language, basic UI or accessibility preferences
- Proposed treatment
- Evaluate necessity; keep use minimal and explain it
Temporary editing state
- Examples
- Local unsaved draft state
- Proposed treatment
- Use only to deliver the editor requested by the user; document lifetime
Persistent visitor memory
- Examples
- Seen notifications, opened apps, completed narrative steps across visits
- Proposed treatment
- Optional; obtain consent where required; add reset/disable controls
Audience measurement (Minilytics, run by the publisher)
- Examples
ml_vid(random visitor identifier, 1 year),ml_sid(current visit, 30 minutes)- Proposed treatment
- Anonymous statistics for the publisher only, never shared or used to follow you elsewhere; exempt from consent (CNIL); you can refuse it
Embedded third-party media
- Examples
- Music/video players, social embeds
- Proposed treatment
- May set third-party trackers; load only after appropriate user action/consent where necessary
Your choices
- Essential storage: cannot be switched off in the service without affecting security or requested operation.
- Optional memory: visitors can choose "Remember my visits" / "Not now"; they can later turn it off and clear the stored exploration history.
- Audience measurement and embeds: the anonymous audience measurement can be refused at any time in Settings → Legal & Privacy, or by opening https://unlokmi.me/?ml_ignore=true (https://unlokmi.me/?ml_ignore=false counts you again). Third-party embeds, if introduced and legally required, will ask a genuine accept/reject choice first, which can be changed later.
If only strictly necessary storage is used, a cookie-consent banner may not be needed, but users must still receive clear information. Merely accepting Terms is not valid consent to optional tracking.
Retention
Session storage expires with the session or applicable cookie expiry. Persistent memory remains until cleared or until the period set by the implemented feature; today, no exploration memory is kept between visits: a visit is forgotten when the page is closed. The sign-in cookie lasts 30 days at most, the language cookie 1 year, the audience measurement cookies 1 year (ml_vid) and 30 minutes (ml_sid). The technical cookie table (name, provider, purpose, expiry) must be filled from browser DevTools after implementation and before publication.
Contact
Questions or consent withdrawals: naimtahouri@gmail.com.