Last updated: 15 October 2026
This Privacy Policy explains how darkevilyn.com ("the Site", "we", "us") handles information when you visit. Your discretion matters to us, and we collect as little as possible.
1. Information we collect
- Information you volunteer. If you contact us or send a tribute reference, we receive whatever you choose to send (e.g. a message, a screenshot, a username).
- Technical data. Standard server logs may record IP address, browser type and pages visited, used only for security and to keep the Site running.
- Browser storage. Local storage remembers your age confirmation. The operator's Studio keeps its access token in memory, or in session storage when the operator explicitly chooses to remember it for that tab. Logging out removes that token. We do not set advertising or tracking cookies.
- Member accounts, when enabled. Signing in with Google supplies a verified email address and a Google account identifier. We do not request access to your Gmail messages or contacts. We store your chosen display name, account role, age-confirmation date and account activity. You can use a display name instead of your real name.
- Sign-in cookies. Account access uses an essential, secure HTTP-only cookie with a maximum lifetime of seven days. A separate cookie binds the Google sign-in request for up to ten minutes. Signing out revokes the session; signing out everywhere revokes all of your current sessions. We store hashed session tokens, not your Google password.
- Account activity. Balance entries, gifts and call records are kept with their amounts and dates so you can review your history. The operator can review and export call metadata: account identifiers and display names, timestamps, verified duration, rate, charge and reason for ending. This does not record video, audio or private chat content. Gift recipients see your display name and gift details.
- Public lounge. While Dark Evilyn is online, messages and display names are visible to all visitors, including guests. The latest 50 messages from the last hour are shown; going offline or moderation can remove them sooner. A guest cookie lasts up to 24 hours. Hashed network identifiers, guest credentials, message retry hashes and moderation records are retained for up to 24 hours for abuse prevention. Expired records are removed by scheduled cleanup. Model call-alert preferences are stored locally in the browser.
- In-call text chat, when calling is enabled. Messages pass through the private call room to the other participant. The site does not save their contents in account history or browser storage. Messages remain in the open page and are cleared when you leave or reload it; the other participant can retain their own copy.
- Private-session requests. When booking is available, the form sends your selected duration, displayed price, transaction hash, payment network, contact details and preferred times to our Cloudflare Worker. Payment confirmation is manual.
- The wheel. Spins run in your browser. This implementation does not send your spin results to the server. The operator manages the shared options and frequency settings.
- The slot machine. Spins run in your browser and are not sent to the server. Your spin count and recent gifts are kept in session storage for that tab only, and your sound preference in local storage.
2. Payments
Cryptocurrency tributes are sent directly to our wallet addresses on public blockchains; we never receive or store your card or bank details. Sessions booked through CamContacts are billed on their platform under their privacy policy. On-site calls use your account balance and the rate confirmed before calling.
Card top-ups are not currently available. On-site paid calls are available only to approved pilot accounts while testing continues. The free wheel and slot machine do not use your account balance. Any future on-site payment provider and its data processing will be described here before activation.
Public account crypto top-ups remain disabled. A private live test, when enabled, is limited to approved test accounts. A test invoice links the account to a coin, network, receiving address, exact amount, quoted USD credit, deadline and submitted transaction hash. If a smaller USDC payment is approved after verification, we also retain the received amount, exchange rate, credited amount and operator decision alongside the original invoice. The operator can review these records. Blockchain transfers are public; they are not anonymous simply because your site display name is private. The site never requests your wallet recovery phrase or private keys.
3. How we use information
We use submitted information to respond to you, manage bookings and keep the site secure. The service providers described below process information needed for those functions. We do not sell or rent your information, or provide your contact details to third parties for their own marketing.
4. Third-party services
Cloudflare hosts the website and stores site settings and booking records. Fonts are served by Google Fonts. On-site account video calls and private chat use an operator-run LiveKit server hosted at Kamatera. The older booking flow supports Jitsi and remains disabled. Public lounge messages are stored separately in Cloudflare D1; they are never taken from private calls. Camera or microphone access requires your browser permission. If operator notifications are enabled, booking details are also sent to the operator's Telegram bot. Following an external link, including CamContacts, takes you to a service with its own privacy policy.
When member registration is enabled, Google processes the sign-in request and Cloudflare stores account and transaction records. Google sign-in is optional; public pages can be viewed without a member account.
The crypto service is being configured with Alchemy for exchange-rate quotes and Base, Blockstream for Bitcoin, TronGrid for TRON, and MEV Blocker for Ethereum. These read-only requests send asset identifiers for quotes and transaction or block identifiers for verification, not your Google email or profile. Opening a transaction-explorer link connects your browser to that external service.
5. Data retention & your rights
New booking records expire 90 days after creation or confirmation, or 30 days after the scheduled end if that is later. Records created before this update may retain the previous 30-day expiry. Content backups expire after 90 days; booking backups follow the booking retention window. Optional Telegram notifications have a separate retention period controlled by the operator. You may request access to, or deletion of, information you have sent us by contacting the operator, subject to applicable record-keeping requirements.
Member accounts and transaction history do not currently have automatic deletion. Contact the operator for an access or deletion request; financial records may need to be retained. Expired or revoked sign-in credentials cannot be used to access an account.
Crypto invoice identifiers and reserved payment amounts are retained after expiry to prevent a delayed transfer from being assigned to another account. There is currently no automatic deletion of these accounting records.
6. Minors
This Site is strictly for adults 18 years of age or older. We do not knowingly collect information from anyone under 18. If you are not of legal age, leave now.
7. Changes & contact
We may update this policy; the "last updated" date will change. Questions? Reach us via ccMail to Dark Evilyn on CamContacts. [Operator: add a contact email if you want one shown.]