Data protection policy

Who is responsible

The controller of personal data processed through unseen.guide is UNSEEN, which runs the site. For anything about your personal data, email privacy@unseen.guide.

This policy is written to meet the EU General Data Protection Regulation (GDPR), the UK GDPR and Hong Kong’s Personal Data (Privacy) Ordinance (PDPO). The privacy notice describes the same processing in plain words, and the cookie policy covers cookies and browser storage.

What we process, why, and on what legal basis

Delivering and protecting the site

Cloudflare delivers every page and request. To do that and to block attacks, Cloudflare processes ordinary connection and security data: IP address, browser details, the page requested, the time and threat signals, and it may set security cookies. Cloudflare also keeps short-lived technical logs of our server code, which can include request details such as the page address. Our own error records carry only fixed labels and counts, never an IP address, a page address, a model name or a Telegram chat id.

Legal basis: our legitimate interests in running a secure, working site (GDPR Article 6(1)(f)).

Site analytics

Cloudflare Web Analytics counts page views and loading speed in aggregate. It uses no cookies and does not follow you across sites.

Legal basis: legitimate interests in understanding how the site is used and keeping it fast (Article 6(1)(f)).

We also use Google Analytics 4 to understand how the site is used: the pages you view (the full page address, which on a profile page includes the performer’s username), the page title, the page you came from, a few actions on the site (for example the platform and placement of an outside link you follow, previews, saves, filters, and that search was used but never the search text), and browser and device details with an approximate location derived from your IP address. Google Analytics 4 does not log or store IP addresses. It sets cookies starting with _ga (see the cookie policy). Google signals, advertising features, user-ID and data sharing with Google are off.

Legal basis: in the EU, the EEA, the UK and Switzerland, your consent (GDPR Article 6(1)(a), with the prior consent the ePrivacy rules require for cookies): nothing is loaded before you choose “Accept”, and you can withdraw at any time under “Cookie settings” in the footer, without affecting processing before the withdrawal. Elsewhere, our legitimate interests in understanding how the site is used (Article 6(1)(f)); you can object and switch it off at any time under “Cookie settings”.

Outbound link clicks

External links pass through /r/ on their way to the platform. For each click we record in Cloudflare Workers Analytics Engine: the platform, the performer's name, the page and placement of the link, the page language, the country or region and the device class (phone, tablet, computer). We record no IP address, browser details, cookies or visitor identifier, so a click cannot be traced to a person.

Legal basis: legitimate interests in knowing which links are useful and checking the platforms' commission reports (Article 6(1)(f)).

Peek opens

When someone opens Peek, our server records one data point in Cloudflare Workers Analytics Engine, separately from outbound clicks: the entry point (which link on our site opened Peek, for example the header button, a profile page, the directory tabs or a shared link), the page language, the country or region and the device class (phone, tablet, computer). As someone moves through Peek, we record one more data point each time they pass 5, 10, 25, 50 or 100 rooms: only that number, never which rooms or performers were viewed. We record no IP address, browser details, cookies or visitor identifier, so these counts cannot be traced to a person.

Legal basis: legitimate interests in knowing how people find Peek and how far they scroll, so we can improve it (Article 6(1)(f)).

Settings and saved models on your device

Your entry confirmation, language, filter and display settings, saved models and recently viewed profiles are kept in your own browser; we cannot see them, except the language you picked, which your browser also sends to our server in the strictly necessary unseen_lang cookie so we keep you on that edition, and the “Blur thumbnails” setting (off by default), sent in the strictly necessary unseen_blur cookie so we send pages that match it. Without it, we read only the languages your browser sends with each request (Accept-Language) to pick an edition, and keep nothing. When you open the Saved page, the site sends those model names to our server to check who is live and available where you are. When the home and category lists are ordered for you, it sends only the category, country, language and tag ids of your saved models and your browser’s language. We use this data only to answer that request and do not keep it.

Legal basis: legitimate interests in providing the features you choose to use (Article 6(1)(f)). You can clear all of it yourself at any time (see the cookie policy).

Telegram live alerts

If you use our public Telegram bot, we store nothing until you confirm in Telegram that you are 18 or older and accept the terms. After that we keep your Telegram chat id, your language, whether alerts are paused, the models you follow (up to 50) and when you started, plus the time of each alert sent, for at most 7 days, to avoid repeats. We do not store your Telegram name, username, phone number, location or the text of your messages. The data is kept in a Cloudflare D1 database.

Legal basis: providing the service you ask for (performance of a contract, Article 6(1)(b)).

Browser live alerts

If you tap “Notify me” on a model page and allow notifications when your browser asks (we never ask on page load), your browser opens a push subscription with its push service and we store: the subscription’s endpoint (its address at the push service) and the two encryption values that come with it, your language, the models you follow (up to 50) and when you subscribed, plus the time of each alert sent, for at most 7 days, to avoid repeats. We do not store your IP address, location, user agent or any name or account. The data is kept in a Cloudflare D1 database. Each alert is plain text with a link to our profile page, encrypted end to end (RFC 8291) so the push service cannot read it.

Legal basis: your consent (Article 6(1)(a)), given by tapping “Notify me” and allowing notifications. You can withdraw it at any time without affecting earlier processing: tap “Notifications on” for a model, use “Stop all and delete” on the Saved page, or block notifications for unseen.guide in your browser.

Rate limiting the alert links

When you open the Telegram alert link or tap “Notify me” on a model page, your IP address (for IPv6, only its network part, the first 64 bits) is turned into a one-way hash. Cloudflare’s rate limiter uses that hash to count attempts over about a minute. We do not store your IP address or the hash. Separately, to refresh a region’s Chaturbate or BongaCams list we send that platform a recent visitor’s IP address (not hashed); see “Chaturbate’s regional restrictions” and “BongaCams’ regional restrictions” below. LiveJasmin, CamSoda and Swag receive no visitor IP address from us (see “LiveJasmin’s regional restrictions”, “CamSoda’s room list” and “Swag’s room list”).

Legal basis: legitimate interests in preventing abuse of the alert service (Article 6(1)(f)).

Performers listed in the directory

We list public rooms from the official data services of the platforms we link to and embed. For each performer we keep the username, country, languages, tags, links to the platform’s images (never the images themselves) and the times we saw the room live. We use this to run the directory and profile pages and to send Telegram alerts to people who follow a performer. Cloudflare, which hosts the site, tells search engines when our pages change (IndexNow, page addresses only).

Legal basis: legitimate interests in publishing an accurate directory of public rooms (Article 6(1)(f)). Removals the platform reports are applied automatically, and performers can ask us to remove their profile (see the DMCA and takedown policy).

Chaturbate’s regional restrictions

Chaturbate broadcasters can block regions from seeing them, and Chaturbate only tells us which rooms may be shown in a region when we give it an IP address from there. When our server refreshes the Chaturbate list for a region (a country, plus the state, province or UK nation in the United States, Canada and the United Kingdom), it sends Chaturbate the IP address of a recent visitor from that region. The address is held in our server’s memory only, replaced by the next visitor’s, and never stored, logged or shown. A visitor whose region we can’t tell sees no Chaturbate rooms.

Legal basis: legitimate interests in showing each visitor only the rooms broadcasters allow in their region, and in complying with those restrictions (Article 6(1)(f)).

BongaCams’ regional restrictions

BongaCams works the same way: its performers can block regions from seeing them, and BongaCams’ affiliate service (bngprm.com) only tells us which rooms may be shown in a region when we give it an IP address from there. When our server refreshes the BongaCams list for a region (the same regions as for Chaturbate), it sends BongaCams the IP address of a recent visitor from that region. The address is held in our server’s memory only, replaced by the next visitor’s, and never stored, logged or shown. A visitor whose region we can’t tell sees no BongaCams rooms.

Legal basis: the same legitimate interests as for Chaturbate (Article 6(1)(f)).

LiveJasmin’s regional restrictions

LiveJasmin’s performers can also block countries and U.S. states. LiveJasmin (through AWE, its affiliate programme) includes those restrictions in the list our server fetches, at most once every five minutes, and that request carries no visitor IP address or other visitor data. Using the country, and in the United States the state, that Cloudflare determines for your request, we hide restricted performers before any card, thumbnail, preview or profile is shown. Your location is used only for that check and is not stored. A visitor whose location we can’t tell sees no LiveJasmin performer who blocks any region.

Legal basis: legitimate interests in showing each visitor only the performers allowed in their region, and in complying with those restrictions (Article 6(1)(f)).

CamSoda’s room list

Our server fetches CamSoda’s public room list about once a minute; the request carries our affiliate id and no visitor data. The list does not say whether a performer blocks any region, so we cannot filter CamSoda rooms by region: CamSoda applies its performers’ restrictions itself when a visitor opens a room or its player.

We list Jerkmate models through CrakRevenue, refreshing about once a minute without sending visitor IP addresses. The API supplies no per-model regional restrictions; CrakRevenue may redirect offers according to location.

Legal basis: legitimate interests in publishing an accurate directory of public rooms (Article 6(1)(f)).

Swag’s room list

Our server fetches Swag’s public room list about once a minute; the request carries no visitor data. Swag rooms have no regional restrictions, so we list them in every region.

Legal basis: legitimate interests in publishing an accurate directory of public rooms (Article 6(1)(f)).

Emails you send us

If you email us, we process your address and whatever you write, to deal with your message, for example a privacy request or a takedown notice. Cloudflare forwards mail sent to our addresses to the mailbox we read.

Legal basis: legitimate interests in answering you, and our legal obligations where a notice or request requires a response (Article 6(1)(f) and (c)).

Running and monitoring the service

Automated checks watch the public site and our services. Alerts sent to us carry counts and fixed labels only, never visitor data, chat ids or model names. The platforms report affiliate results to us as daily totals (clicks, sign-ups, revenue), per link placement where the platform supports it; we receive nothing that identifies who clicked.

Legal basis: legitimate interests in keeping the service reliable and understanding which links work (Article 6(1)(f)).

Under the PDPO, we collect personal data only for the purposes above, by fair means, and use it only for those purposes or ones directly related to them.

Who receives personal data

• Cloudflare, our processor for hosting, network delivery, security, server code, databases, analytics, rate limiting and email forwarding.
• Google, our processor for Google Analytics: Google Ireland Limited (Dublin, Ireland) for visitors in the EEA, the UK and Switzerland, Google LLC (United States) elsewhere, under the Google Ads Data Processing Terms.
• Telegram, which delivers bot messages. Telegram handles your Telegram account and messages under its own privacy policy.
• Your browser’s push service, if you turn on browser alerts: Google (Firebase Cloud Messaging), Apple, Mozilla or Microsoft, depending on your browser. Only our server sends to it. It receives the encrypted alert, your subscription’s endpoint and the time, and delivers the alert to your browser under its own terms and privacy policy.
• The platforms we link to and embed receive data directly from your browser when thumbnails or the player load, or after you click through. They act on their own account under their own policies. Affiliate links carry our affiliate ID and, where the platform supports it, a placement label, never anything that identifies you.
• Chaturbate (Multi Media, LLC, United States) receives the IP address of a recent visitor from a region when we refresh that region’s Chaturbate list (see above). It acts on its own account.
• BongaCams (its operator, based in Cyprus) receives the IP address of a recent visitor from a region when we refresh that region’s BongaCams list (see above). It acts on its own account.
• Search engines receive page addresses, including profile pages, from Cloudflare through IndexNow.
• Authorities or courts, where the law requires it.

We do not sell personal data or share it for advertising.

International transfers

Cloudflare runs a global network, so your data may be processed outside your country, including in the United States. Cloudflare provides these transfers under its data processing terms, which include the European Commission’s standard contractual clauses and the UK addendum. Telegram processes data in the places its privacy policy describes, and so do the browser push services (Google, Apple, Mozilla, Microsoft), which may process alerts in the United States; the alerts are encrypted so they cannot read them. Chaturbate receives the IP addresses described above in the United States, and BongaCams’ operator, based in Cyprus, receives the ones described for BongaCams. Google Analytics data may be transferred to Google LLC in the United States, which is certified under the EU-US Data Privacy Framework (and its UK and Swiss extensions), with the European Commission’s standard contractual clauses as a fallback.

How long we keep it

• Settings and saved models on your device: until you clear them; tab settings until you close the tab.
• Telegram alert data: until you send /stop or block the bot (deleted as soon as we notice). Alert send times: 7 days. Unused alert links: 15 minutes. Follows of a performer the platform removed, or did not show for 30 days in a row: deleted automatically.
• Browser alert data: until you turn off your last followed model or use “Stop all and delete”, or, if the subscription ends in your browser, until the push service tells us it is gone (we delete it on that answer, a 404 or 410). Alert send times: 7 days. Follows of a removed performer, or one not seen for 30 days in a row: deleted automatically.
• Rate-limit counts: about a minute. IP addresses: not stored; the IP address used for a Chaturbate or BongaCams region refresh stays in memory only, at most until that region has had no visitor for about 15 minutes or the server restarts (usually the next visitor’s replaces it sooner).
• Performer records: deleted when the platform reports a removal, or after 30 days in a row without seeing the performer; observed live times at most 30 days.
• Outbound link click records: at most 3 months.
• Peek open records: at most 3 months.
• Google Analytics event data: 2 months (our Google Analytics setting); its cookies at most 13 months, deleted at once when you switch analytics off; your consent record (unseen:consent) stays on your device and is asked again after 13 months.
• Cloudflare’s request, security and server logs: the short periods Cloudflare sets.
• Emails: as long as we need to deal with the matter and any follow-up.
• Daily alert and revenue totals: kept as counts only, which identify no one.

Your rights

Depending on where you live, you can ask us to give you a copy of your personal data, correct it, delete it, restrict or object to its use, or give it to you in a portable form. Under the PDPO you can make a data access request and a data correction request.

• Telegram alerts: /list in the bot shows the models you follow, and /stop deletes everything we hold about your chat at once.
• Browser alerts: the Saved page shows how many models this browser gets alerts for, and “Stop all and delete” deletes everything we hold for it at once. Tapping “Notifications on” on a model page turns that one off.
• Data in your browser: only you can see or delete it, by clearing site data.
• Withdrawing consent or objecting to analytics: choose “Reject” under “Cookie settings” in the footer. Collection stops at once and the Google Analytics cookies are deleted; it is as easy as giving consent. Google Analytics uses a random id, so we cannot find which analytics data is yours, but you can still email us.
• Anything else: email privacy@unseen.guide. We may ask for information to confirm the request is yours. We answer within one month (PDPO requests within 40 days), and there is normally no fee.

Complaints

Please contact us first so we can try to fix it. You can also complain to a data protection authority: in the EU, the authority in the country where you live or work; in the UK, the Information Commissioner’s Office (ICO); in Hong Kong, the Office of the Privacy Commissioner for Personal Data (PCPD).

Automated decisions

We make no decisions about you by automated means that have legal or similarly significant effects. Ordering the room lists by your saved models changes only the order of the lists.

unseen:viewing-interests: Viewing preferences are on by default and can be turned off. This key keeps category and tag scores, not model names or a viewing log. Old scores expire after 30 days. Only topic filters are sent to fetch rooms; scores stay on your device. Manage learning on the saved models page. Turning it off clears scores and keeps only your off choice.

Children

unseen.guide and the Telegram bot are for adults only (18 or the age of majority where you live, whichever is higher). We do not knowingly process data about minors. If you think a minor has used the bot, email us and we will delete the data.

Security

We keep as little data as we can. The site is served over HTTPS with a strict content security policy that lets your browser connect only to the hosts listed in the cookie policy. Where we use your IP address ourselves (to rate-limit the alert link), it is hashed and never stored. The one exception is the Chaturbate and BongaCams region lists: a recent visitor’s IP address is sent to Chaturbate or BongaCams as it is, held in our server’s memory only and never stored (see “Chaturbate’s regional restrictions” and “BongaCams’ regional restrictions”). Alert links are single-use and expire after 15 minutes, and the bot accepts updates only from Telegram with a secret token. Browser alerts are encrypted end to end and signed with our own key (VAPID), and our server sends them only to the push services named above. Our admin tools sit behind a sign-in, secrets are kept out of the code, and our own error records never contain visitor data.

Data breaches

If a personal data breach happens, we will act straight away to contain it and assess the risk. Where the law requires, we will report it to the relevant authority within 72 hours of becoming aware of it and tell the people affected without undue delay, where we have a way to reach them, such as the Telegram bot or a browser alert.

Changes to this policy

We will update this page, with a new effective date at the top, when what we process changes, and point out significant changes here.

Contact

• Copyright and takedowns: dmca@unseen.guide
• Other legal questions: legal@unseen.guide
• Privacy: privacy@unseen.guide