This Cookie Policy explains how Maskr uses cookies, local storage, session storage and similar technologies. It should be read with the Privacy Policy.
Version: 1.0
Effective date: 15 April 2026
Cookie contact: privacy@localhost
1. What cookies and storage technologies are
Cookies are small files placed on your device. Local storage and session storage are browser storage areas that can hold site data. Similar technologies can include pixels, tags, device identifiers and scripts that store or access information on your device.
Under the Privacy and Electronic Communications Regulations 2003, users should receive clear information about cookies and similar technologies. Consent is usually needed for non-essential storage or access, while strictly necessary technologies can be used where needed to provide a service requested by the user. Personal data collected through cookies is also handled under UK GDPR and the Data Protection Act 2018.
2. How Maskr uses cookies and storage
- To keep you logged in and manage secure sessions.
- To protect forms, accounts and messages with CSRF and security controls.
- To remember age gate, cookie consent, privacy and display preferences.
- To support rate limiting, anti-abuse, fraud prevention, upload security and moderation workflows.
- To remember local interface choices, such as chat preferences or recent UI state, where enabled.
- To measure traffic, performance and usage where analytics are enabled and consent has been obtained where required.
- To support checkout, subscriptions or payment provider redirects where billing is enabled.
- To support embedded or third-party content where such content is enabled.
3. Cookie categories
| Category | Purpose | Examples / depends on configuration | Consent position |
|---|---|---|---|
| Strictly necessary | Needed for login, sessions, routing, account access, form submission, age-gate flow and core site functions. | Session cookie, remember-login token, PHP session identifier, routing state. | Usually no consent required where essential to provide the requested service. |
| Security | Protects accounts, forms, uploads, messages, moderation tools and owner settings. | CSRF token, rate-limit state, abuse-prevention state, staff session checks. | Usually no consent required where essential for security. |
| Age gate | Stores whether an age gate or adult access step has been completed, where enabled. | Age confirmation cookie or local storage flag. | Usually treated as necessary for adult access controls where required. |
| Preferences | Remembers choices such as cookie consent, layout, privacy controls, filters, theme or chat interface options. | Cookie consent cookie, layout preference, recent emoji or local chat UI state. | May require consent if not essential. Some preference storage may be treated as requested by the user. |
| Analytics | Measures visits, performance, errors, traffic sources and feature use where analytics are enabled. | Analytics identifiers, page view IDs, performance tags. | Consent is normally required unless a narrow exemption applies. |
| Marketing | Supports advertising, campaign measurement, remarketing or promotional attribution if enabled. | Marketing pixels, campaign IDs, ad platform cookies. | Consent is normally required. |
| Payments | Supports checkout, fraud prevention, payment redirects and payment-provider security where paid plans are enabled. | Stripe, PayPal or other payment gateway cookies and tokens. | Some may be necessary for checkout. Provider-controlled cookies may have their own consent and privacy rules. |
| Third-party content | Supports embedded media, maps, widgets, verification providers, analytics tools or other integrations where enabled. | Embedded video, maps, age assurance widgets, external scripts. | Consent may be required depending on purpose and provider. |
4. Strictly necessary cookies
Some cookies and storage are required for Maskr to work. If you block them, you may not be able to log in, pass age controls, submit forms, send messages, manage privacy settings, upload photos, use billing, use staff tools or keep your account secure.
5. Security and age assurance
Security and age-related technologies may be used to protect adult-only access, prevent underage users, reduce fake accounts, detect abuse, protect uploads and support moderation. Where an external age assurance provider is used, that provider may set its own cookies or process device data under its own notice.
6. Analytics and marketing
Analytics and marketing tools are only used where enabled by the site owner. If used, they may collect page views, device information, approximate location derived from IP address, traffic source, campaign data and interaction events. Non-essential analytics or marketing cookies should be controlled by consent where required.
7. Payments and checkout
Where paid plans, subscriptions or billing are enabled, payment providers may use cookies and similar technologies for checkout, fraud prevention, security, payment completion and dispute handling. See the relevant provider notice during checkout and the site's billing area where available.
8. Local storage and chat features
The site may use local storage or session storage to remember interface state, recent chat UI choices, draft-like browser state, filters, collapsed panels, age gate state, consent choices or other preferences. Clearing browser data may reset those choices.
9. How to manage cookies
- You can block or delete cookies through your browser settings.
- You can clear local storage and session storage through browser site data controls.
- Where a cookie consent tool is enabled, use it to change optional cookie choices.
- You can also review related account settings in privacy controls.
Blocking cookies may sign you out, reset age-gate or consent choices, break checkout, stop messages or uploads working, or make security checks fail.
10. Changes and contact
We may update this Cookie Policy when cookies, storage technologies, analytics, payment providers, age assurance providers or legal requirements change. Questions can be sent to privacy@localhost or raised through support.