What this notice covers
“Cookies” includes HTTP cookies and, where relevant, browser local storage used by MaiLens web clients. Server cookies and local storage behave differently; HTTP-only cookies cannot be read by ordinary page JavaScript, while local storage is accessible to the web client.
Necessary session & security state
Authenticated MaiLens services use session state so signed-in browsers can access account-bound features. Security/challenge state and server-side rate-limit mechanisms can also be used to protect registration, verification, password recovery and other abuse-sensitive operations.
Functional preferences
MaiLens web clients can store functional preferences such as appearance, interface locale/language and other local UI choices. Removing these preferences can reset the interface to default behavior.
Attribution and anonymous engagement
Across the wider MaiLens web authority, purpose-specific signed first-party receipts can support referral attribution or anonymous public-social engagement where those features are offered. Those receipts are not registered accounts and do not grant access to private content.
What is not established
The current shared authority does not establish a third-party advertising-cookie system or named third-party analytics-cookie category. MaiLens.Studio should not publish or request consent for categories that are not actually deployed.
Third-party cookies
If you leave MaiLens.Studio for an enabled third-party checkout or federated identity flow, that provider may set its own cookies or state under its own domain and policy. Examples supported by the shared MaiLens authority include Stripe and optional Google/Apple federated sign-in.
Your controls
You can use browser controls to remove cookies and local storage. This can sign you out, reset preferences, or remove browser-held attribution/continuity state. Clearing browser data does not automatically delete server-side account, project, commercial, support or audit records.