Cookie Policy
Last updated: September 20251. What Are Cookies?
Cookies are small text files stored by your browser when you visit a website. This policy explains exactly what cookies and browser storage KinkDate.eu uses — and what it does not use.
2. What KinkDate.eu Does NOT Use
We want to be explicit about what we do not do:
- We do not use Google Analytics or any Google tracking scripts.
- We do not use Meta (Facebook) Pixel or any Facebook/Instagram tracking.
- We do not use TikTok, Twitter/X, LinkedIn, or any other advertising or analytics pixels.
- We do not use
express-sessionor any server-side session cookies of our own. - We do not store authentication tokens in HTTP cookies. Authentication uses browser
localStorageinstead (see Section 4).
3. Cookies That May Be Set
3.1 Socket.io (Functional)
KinkDate.eu uses Socket.io for real-time chat. Socket.io is served from our own server (not a third-party CDN) and may set a session cookie to maintain the WebSocket connection. This cookie:
- Contains no personally identifiable information beyond a random session identifier.
- Is used solely to maintain the chat connection.
- Is a functional cookie required for the core service to operate.
- Is deleted when you close your browser session (session cookie).
3.2 PayPal (Third-Party — Payment Flow Only)
When you initiate a credit purchase, the payment is processed via PayPal. During the PayPal checkout flow, PayPal may set their own cookies for fraud prevention, session management, and their own analytics. These cookies are governed by PayPal’s Cookie Policy. We have no control over PayPal’s cookies.
PayPal cookies are only relevant when you are actively going through checkout. If you do not purchase credits, PayPal cookies are not set.
4. Browser localStorage (Not Cookies)
KinkDate.eu uses localStorage — a browser storage mechanism separate from HTTP cookies — to store the following:
- cs_token — your JSON Web Token (JWT), used to authenticate you with the server. Expires after 30 days.
- cs_user — a cached copy of your profile data (username, credits, role) used to populate the UI without an extra server round-trip.
- cs_age — a simple flag (“1”) confirming you have acknowledged the 18+ age gate. Set once on first visit.
These localStorage items are:
- Never transmitted to third parties.
- Only read by KinkDate.eu’s own JavaScript.
- Cleared when you log out or clear your browser storage.
- Not HTTP cookies and therefore not subject to standard cookie consent requirements under ePrivacy; however, we disclose them here in the spirit of full transparency.
5. How to Control Cookies and Storage
You can control cookies and localStorage through your browser settings:
- Chrome: Settings → Privacy and Security → Cookies and other site data
- Firefox: Settings → Privacy & Security → Cookies and Site Data
- Safari: Preferences → Privacy → Manage Website Data
- Edge: Settings → Cookies and site permissions
Note: clearing cs_token from localStorage will log you out. Clearing cs_age will cause the age gate to reappear on your next visit.
6. Summary Table
| Name | Type | Purpose | Expires | Third Party? |
|---|---|---|---|---|
| cs_token | localStorage | Authentication JWT | 30 days | No |
| cs_user | localStorage | Cached profile data | Until logout | No |
| cs_age | localStorage | Age gate confirmation | Persistent | No |
| io (Socket.io) | HTTP Cookie | WebSocket session | Session | No (self-hosted) |
| PayPal cookies | HTTP Cookie | Payment processing | Varies | Yes — PayPal only |
7. Changes to This Policy
We may update this Cookie Policy when our technology or third-party services change. The date at the top of this page reflects the most recent update.
8. Contact
For questions about cookies or your privacy: [LEGAL CONTACT EMAIL]