Privacy Policy — review draft
Email supportUnder-16 users & parental authorization — planned, not available
Planned product rule: users who meet the applicable local minimum age but are under 16 must link a parent or legal guardian account and obtain authorization. At 16, this product rule no longer requires the link, but any higher local minimum age or additional guardianship requirements still apply. Parental consent cannot bypass an applicable minimum age. Account linking, guardian verification, permission controls and withdrawal of authorization are not implemented or enabled yet. This website is describing a planned rule, not providing a working consent or age-verification process. Do not send a child’s or guardian’s identity documents to support to try to activate it.
Scope & contact
This draft describes YoluChat and its website. YoluChat is operated by an individual in Malaysia. Operator identification, a correspondence address and the final effective date are pending. Contact support@yoluchat.com for privacy questions. This document is an incomplete draft, not a statement that all legal or app-store requirements have been met.
Accounts & communication
Account features use an email address, authentication credentials, username, display name and avatar. Authentication requests use Supabase Auth. Messages and media you choose to upload, group/channel memberships and roles, and contact relationships are used to provide communication and permission-controlled access. Sharing a YoluChat contact card is different from uploading your phone’s address book; no automatic address-book upload is asserted here.
YoluVibe, audiences & Story
Social features process the text and media you publish, audience choices, comments, reactions, saves and social relationships. Eligible viewers may retain copies of content they receive. Story visibility expires after the selected 1, 6, 12 or 24 hours; this does not establish that every record, media file or backup is physically erased at that time. Backend cleanup and backup periods still need confirmation.
Permissions, service providers & international processing
Camera, microphone, media and location features request relevant permissions when used. Supabase provides the authentication, database, file-storage and API infrastructure; project metadata confirms its primary region as Singapore (ap-southeast-1). Vercel hosts this website, and Zoho hosts support email. Firebase Cloud Messaging is configured in the deployed server code, and the public health check reports push enabled. LiveKit calling integration is present, but its actual activation and processing region are not yet confirmed. The primary database region does not establish that all provider logs, email, network delivery or backups stay in Singapore. A complete processor, SDK, contract-protection and international-transfer review remains outstanding.
Website & support correspondence
Website product demos run locally in your browser and do not send demo conversations to the YoluChat API. Hosting and email providers may process technical delivery records; exact log fields and retention need verification. If you contact support, your email address, message and any attachments you provide are used to handle your request. Do not send unnecessary sensitive information.
Security, retention & your requests
The current test version does not offer end-to-end encryption. We do not promise absolute security or that received copies can be recalled. Account data, uploaded files, messages, technical logs, support emails and backups each need a confirmed retention/deletion schedule. Access, correction and deletion questions can be sent to support. The complete account-deletion process, verification method, exceptions and completion time remain to be implemented or verified; no automatic or fixed-time deletion is promised.
Children, advertising & future changes
There are currently no advertising or charging plans. The minimum age, parental-consent process and rules for each intended market are not finalized. The operator’s product requirement is use only by people aged 12 and above. This is not a verified eligibility rule for all markets or an app-store age rating; any higher applicable local minimum must take precedence, and the required controls remain pending. The final notice, effective date and material-change notification process will be completed after the outstanding facts are confirmed.
File access and Story retention
The avatar, chat-file and social-media storage buckets were verified as non-public. Access is governed by application authorization, not by a promise of end-to-end encryption. The live database rules stop other viewers accessing an expired Story and allow an owner archive view. Expiry removes visibility; it is not proof that the database record, uploaded media or backup copy has been permanently erased. Recipient copies cannot be assumed to disappear.
Push data and delivery expiry
Deployed Firebase messaging code sends an app-instance push token, notification title/body and identifiers for the user, room and message. The payload therefore may include a notification preview, not only anonymous statistics. It sets a one-hour delivery TTL; that is a delivery expiry, not a one-hour chat-history, provider-log or backup deletion promise. Device-level delivery, settings-specific previews and provider retention still require verification.
Retention periods still requiring confirmation
Final retention periods for accounts/profiles, messages, uploaded media, moderation records, technical logs and support emails have not been established in this draft. The verified Story display periods and push delivery TTL must not be used as substitutes. No 30-day or 90-day deletion deadline is claimed. Retention reasons, exceptions, consent-withdrawal handling and request completion times must be settled and matched to an executable deletion process before store submission.
Database backups are not media-file backups
Supabase documents that database backups do not include the actual files stored through its Storage API, only their database metadata. YoluChat has not yet verified a complete recoverable database-and-media backup set or performed a recovery acceptance test. The Pro plan was verified as active on 27 October 2026. The dashboard lists seven daily database restore points dated 20–26 October 2026 (UTC). A recovery drill has not been completed, so a fixed recovery time is not promised. Independent media backups and their retention remain pending.
Reference requirements
Infrastructure references
Supabase database backups and Storage objects
Supabase regions
YoluChat