Playnder Cookie Policy
Effective from: 15 October 2026
Last updated: 4 October 2026
1. Who uses these technologies
Playnder is operated by Alessandro Poggio, Calle Aaron Vidal Lopez Soldat 6, 4F, 46026, Valencia, Spain. Questions: hola@playnder.com. Our Privacy Policy explains the wider processing of personal information.
Cookies are small values stored by your browser. Similar device-storage technologies can serve the same purposes. This policy covers the technologies used to sign you in, complete authentication and remember your requested language in the beta.
2. Cookies used in the beta
| Cookie or name pattern | Responsible service | Purpose | Duration |
|---|---|---|---|
sb-<project-ref>-auth-token, sometimes divided into .0, .1 and further chunks | Playnder, using Supabase authentication | Keep your requested signed-in session available and refresh authentication | Up to 400 days from the latest write under the current SDK default; refreshed during use and normally cleared on sign-out |
sb-<project-ref>-auth-token-code-verifier, potentially chunked | Playnder, using Supabase authentication | Securely complete sign-in, email-link or account-recovery flows | Normally removed when the exchange completes; if a flow is abandoned, it can remain up to the SDK cookie limit of 400 days |
NEXT_LOCALE | Playnder's language routing | Remember the language selected for your visit | Session cookie under the current configuration; browser session-restore settings may preserve session cookies |
<project-ref> is the identifier of our authentication project, not a separate advertising provider. A cookie's storage lifetime is different from the validity of the credentials it contains: an expired or revoked credential does not remain valid merely because a cookie is still stored.
These cookies support the service you request. We do not use the initial beta to install advertising cookies, social-media tracking pixels or optional audience-analytics cookies. Necessary authentication and requested-language cookies are not used for those purposes.
When you dismiss the cookie notice, we store that preference in your browser's local storage as playnder-cookie-notice-dismissed-v1 so the notice stays hidden on later visits. This preference does not track your browsing or enable optional cookies.
3. Consent and your choices
Strictly necessary cookies do not require prior consent when used only to deliver a service you explicitly request. We explain them here so you can understand their use.
You can delete or block cookies through your browser's privacy settings. Clearing authentication cookies signs you out; blocking them can prevent sign-in, password recovery and other account features from working. You can change the site's language through the language controls or by opening the relevant language version.
If we introduce optional cookies, we will explain their providers, purposes and lifetimes, ask for consent before installing them where required, and provide a way to refuse and later withdraw consent. Continuing to browse or accepting the Terms will not count as optional-cookie consent.
4. Media, infrastructure and app storage
Viewing images or video sends requests to the providers delivering that content. For example, Mux receives technical information such as your IP address when a video stream or thumbnail is requested. A third-party request can involve personal information even if it sets no cookie; see the Privacy Policy for providers and transfers.
Where the native Playnder app is offered in the beta, it uses device storage for its authentication session and settings rather than the website's browser cookies. Signing out removes the locally stored authentication session. Your device settings can also clear app data. Clearing device storage does not itself delete your account.
5. Changes and contact
We will update this policy when the technologies used change. Contact hola@playnder.com for questions about cookies or device storage.