Privacy Notice

Privacy contact

Contact support@yol.chat for privacy questions or requests. You can also reach us at contact@ingenxmedia.com.

Information we use

• Account email address, authentication identifiers and credentials handled by Supabase; your screen name and optional bio, status and profile picture.
• Room messages and private messages, their participants, timestamps, formatting and read status; buddy lists, blocks, room memberships and recent online activity.
• Reports, bans and information you send when contacting support.
• Your successful 18+ self-declaration, its timestamp and accepted rules version. The entered birthday is submitted to the server to calculate eligibility but is not saved in your member profile or age-declaration record. We do not request ID documents or selfies for this check.
• Technical information used by hosting and delivery providers, such as IP addresses, request information and operational logs.

Why we use it

We use account and messaging information to provide the service you request, including sign-in, room chat, private messages, profiles and buddies. Our basis for this is performance of our service agreement. We use security, moderation, reports and age-eligibility information for our legitimate interests in operating an adults-only community, preventing abuse and protecting users. We may process information where necessary to meet a legal obligation. Optional profile information is not required to use basic chat.

What other people can see

Members can see your screen name, published profile information, online status and room contributions. Your account email and age-declaration record are not shown in your member profile. Uploaded profile photos have public image links: anyone who has that link can view the image.

Private IMs are restricted in the application to their participants. They are not end-to-end encrypted. Authorised operators with database access can access stored data for service operation, security, support or legal reasons. Ordinary room moderators do not gain access to private IMs through the moderation panel. Recipients may copy or screenshot messages.

YOL Hosts and private host IMs

When enabled by the site administrator, automated YOL Hosts may welcome members, answer questions and post occasional public-room conversations. Host screen names are shown in red, and their profiles disclose that they are automated, not human members or moderators. They do not count toward real-member online counts. Public host-to-host conversations and room-entry welcomes use prepared messages; when a real member asks a question, the host service may use a prepared reply or send that message and a limited amount of recent conversation context to Cloudflare Workers AI for a generated response.

Members can also send private instant messages to YOL Hosts. These host IMs are stored separately in Supabase, and are accessible to the signed-in member and the privileged service running the host feature. A host IM sent by a member, and a limited amount of earlier context from that host conversation, may be sent to Cloudflare Workers AI when a prepared answer is not suitable. This is distinct from ordinary private messages exchanged between real members, which are not sent to the YOL Host AI model. New members may receive a one-time prepared welcome IM from ChatHost. Never share passwords, financial details or other sensitive information with automated hosts. AI-generated replies may be inaccurate, and hosts are not human moderation or emergency assistance. The administrator can switch off the hosts. See Cloudflare's privacy information.

YOL News and RSS sources

YOL News displays attributed headlines supplied by external RSS/Atom publishers. Its server-side news reader retrieves those headlines without passing your YOL CHAT account information to news publishers. Clicking an original source link takes you to that publisher’s website, where its own privacy and cookie terms apply. Administrators can save private draft YOL TV bulletins in Supabase; these are not public until deliberately published through a separate process.

YOL TV and external video

When you open YOL TV or select a video or channel, the selected provider (such as YouTube or Vimeo), or the host of a direct video file, receives connection information including your IP address and may process playback data or use cookies under its own policy. Video files are hosted externally. Channel thumbnails may be loaded from the video provider or the cover-image host when the channel guide opens. The selected player loads automatically, but playback waits until you press Play. YouTube uses its privacy-enhanced embed domain; this does not eliminate all provider processing. See Google privacy information and Vimeo privacy information.

Service providers and disclosures

We use Cloudflare for website delivery and aggregate website analytics, Supabase for authentication, databases and profile-picture storage, and Resend for account emails and optional unread-IM notifications. Support correspondence is handled by our email providers. These providers process information needed for their services. Information may also be disclosed when necessary to comply with law or address abuse.

Provider infrastructure can involve processing outside the UK. For current hosting locations and applicable transfer arrangements, contact us. Provider privacy information is available from Cloudflare, Supabase and Resend.

Unread IM email notifications

When enabled in Chat Options, we may email your registered address to let you know that new unread IMs are waiting while you are offline. These service reminders contain your screen name and a link to YOL CHAT, but no message contents, sender names or attachments. You can turn them off in Chat Options; the in-site unread notice and sound remain available. We store your notification preference, scheduling and delivery timestamps, and temporary delivery details to prevent repeat emails. These records are removed when your account is deleted. Resend processes your destination address and the reminder email to deliver it. Notifications normally wait at least five minutes and are limited to one per member in 24 hours.

Website analytics

We use Cloudflare Web Analytics to understand website visits and improve site performance. The reports show aggregate statistics such as page views, referring websites, country, browser, operating system, device type and page-loading performance. These statistics are not linked to your screen name, account email or chat messages.

Cloudflare states that Web Analytics does not use analytics cookies or browser storage, fingerprint visitors, or track individuals across websites. Individual visitor IP addresses are not shown in our Web Analytics reports. See Cloudflare Web Analytics information for details. Website-delivery and security processing are separate from these aggregate analytics.

Member activity statistics

To understand participation and improve the service, we record the most recent UK calendar day on which each member connected to chat. This record is linked to the member account and is kept while its profile exists; it is removed when the profile is deleted. Our basis is our legitimate interest in understanding and improving community participation. Administrators can see aggregate counts of accounts, active members, online members and stored room messages and private IMs. This statistics dashboard does not show message contents, account emails, individual browsing histories or IP addresses. The activity record is separate from Cloudflare website analytics.

Browser storage

The website uses browser storage to keep your authentication session and preferences such as sounds, automatic IM opening and message styles. Signing off clears the local login session; some preferences remain until you clear browser storage. We do not use advertising trackers. Infrastructure providers may use security mechanisms needed to deliver the service.

How long information is kept

Messages currently have no automatic expiry and remain available as saved conversation history. Deleting a member-created room deletes its room-message history. Removing a room message hides it from the room display. Its database record retains a removal marker, sender and timestamp. Account records, age declarations, lists and profiles remain while the account exists. Contact us to request account or message deletion.

Support and moderation records are kept for as long as needed to resolve the matter and address related abuse, disputes or legal requirements. Provider logs and backups follow their applicable retention settings and may remain after removal from the live application. Ask us for details relevant to your request.

Your rights

Depending on the circumstances, you may request access, correction, deletion, restriction, portability or object to processing based on legitimate interests. Contact us using the addresses above, preferably from your account email. We may need proportionate information to confirm your identity. You can complain to the Information Commissioner's Office (ICO).

Age eligibility and choices

YOL CHAT is intended for people aged 18 or over. Account access requires a self-declared birthday indicating 18+ and acceptance of the Community Rules. The eligibility calculation is automatic; contact support if you believe access was wrongly refused. If we learn an account belongs to someone under 18, we will restrict access and review appropriate deletion. Do not enter a false birthday.

Changes

We will update this notice when the service or our data use changes and draw attention to material changes through the site.

Screen-name changes

Members can change their screen name once every 30 days. We keep the time of the latest change to enforce this limit. Your account ID stays the same, so messages, buddy connections, blocks and moderation records remain attached to your account. Existing messages display your current screen name.

Private IM attachments

Members may send supported images, audio files and documents in private instant messages. Files are stored in a private Supabase Storage bucket and access is limited to the conversation participants, subject to account and block restrictions. A trusted backend uses storage credentials to upload and delete files. Files become unavailable after 30 days; a scheduled cleanup runs every 15 minutes to remove expired files. A failed cleanup may delay physical deletion until a later successful run.

Senders may delete their files earlier. Attachment filenames and message records can remain in the conversation after the file expires or is deleted. The limits are 10 MB per file and 50 MB of stored attachments per sender across all conversations. Downloaded copies on a recipient’s device cannot be withdrawn.