RandomHello privacy and safety notice

Effective 30 October 2026 • Version 0.4.8

Operator: fzdyzx. Privacy, account deletion, appeals and child-safety contact: fzdyzxjianliu@gmail.com.

RandomHello is an adults-only random text chat service. The first hour starts at matching and continues while either person is offline. Paid extensions require the app, server and Google Play to enable purchases; see the payment notice below.

Data and purpose

We process your email to verify access through Tencent Cloud email delivery. Account records include your account ID, name, gender, private date of birth, selected built-in avatar and login sessions. Current partners may see your name, gender, computed age and avatar, but not your email or birth date. Google Play distributes the app and processes optional purchases; we do not receive identity documents, selfies or card details. An email code alone does not verify legal identity or age.

Content filtering runs on your device using a limited phrase list. Matching outgoing messages are not sent; matching incoming messages are hidden. It can miss harmful content or hide harmless text and does not replace reporting. The server enforces the same limited phrase rules before forwarding. Rejected text that reaches the server is encrypted for 24 hours, marked as blocked and not delivered. Suspected child-safety or serious-threat matches create an unverified automated review case with available evidence retained for 90 days; a phrase match alone is not confirmation of misconduct and does not automatically permanently ban an account. No third-party moderation service receives chat text. Only built-in cartoon avatars are available. Previously uploaded profile photos are replaced in active profiles; pre-existing preserved evidence follows its original retention period.

Chat text received for valid active-chat send attempts is encrypted at rest on the server for 24 hours from receipt. Encrypted account references include the participants’ account IDs, emails and names for safety investigation. Message metadata includes sender, recipient, match, server time, expiry and delivery status. Client receipt is not proof that a human read the message. Messages rejected while the partner is offline are not queued for later delivery.

At expiry, messages are no longer available for evidence capture. Automated cleanup runs at least once per minute while the server is operating. Match associations remain during the match and for 24 hours after it ends. This is not a chat-history recovery service. Server-held messages are excluded from ordinary account-database backups. Operators must not create disk snapshots or independent copies that defeat these limits.

Reports and preservation

You can report and block during a chat or report through Account settings → Recent conversations & reports within 24 hours after the chat ends. A report preserves the still-available conversation, account references and relevant profile details, including a selected built-in avatar, in a separate encrypted case for 90 days from reporting. Older messages may already be gone. Reporting ends an active match and blocks the other person. You receive a case ID and can check your submitted reports.

Only authorised safety personnel may access evidence for investigation and appropriate action. A documented, verified legal preservation requirement may extend retention to its recorded deadline. Case access, export, resolution, hold and deletion actions are logged for 180 days without message bodies. Normal chat retention and ordinary report retention are product limits, not claims that every jurisdiction imposes the same period. Preservation does not automatically authorise disclosure to another party.

Age-check results are held for up to 24 hours per session; age-safety audit events for up to 30 days. Email rate-limit records last one hour, verification codes up to 10 minutes, and login sessions up to 30 days unless revoked earlier. Block relationships remain until account deletion. Purchase processing, when enabled, is described in the payment notice below.

RandomHello account deletion

Operator: fzdyzx. You can request deletion without installing or signing in to RandomHello.

1. Send an email from your registered email address to fzdyzxjianliu@gmail.com, with the subject “RandomHello account deletion”.
2. State that you want your RandomHello account and associated data deleted. If you cannot access the registered email, explain this so we can help verify ownership.
3. We verify ownership before acting and reply to confirm the outcome. Do not send passwords or login verification codes.

Deletion removes your live profile (email, name, gender, birth date and avatar selection), revokes login sessions and ends your active match. For safety investigation, already accepted messages keep their original 24-hour expiry; match associations expire 24 hours after the match ends, connection records after 30 days, and reported evidence after 90 days from reporting. Safety audit logs are retained for 180 days. Verified legal preservation may extend evidence retention to a documented deadline. Deleting the account does not restart these periods. Details of other short-lived security records and recovery copies appear elsewhere on this page.

Delete your account in Account settings. This ends an active match, revokes access and removes the live account profile and avatar. Already accepted messages and short-lived match references retain their existing 24-hour deadlines. Reported or legally preserved evidence is not erased early by account deletion. Contact the email above for deletion without access to the app, correction requests, access requests or an appeal. We verify the request before action; applicable legal rights and preservation exceptions must be assessed.

Name, gender and birth date cannot be edited directly after registration. Contact support for a genuine correction; the inability to edit in the app does not remove applicable correction rights. The device stores a login token and language preferences and holds up to 300 messages in page memory, cleared on reload. Other participants may copy or screenshot what you send.

Security, providers and disclosures

We use HTTPS/TLS in transit and AES-256-GCM for stored messages and case evidence. This is not end-to-end encryption: authorised server-side safety processing can decrypt case evidence. The service uses overseas Tencent Cloud infrastructure; email delivery uses Tencent Cloud and adult/app checks use Google. Your matched partner receives your chat and permitted profile fields. Data is not used for advertising in this build. A valid lawful request may require disclosure after authority, scope and applicable cross-border rules are reviewed. No automatic reporting or disclosure to law enforcement is implemented by the app.

Successful chat connections record account ID, connection IP, server time, a hashed session reference and the client-reported app version. These records are encrypted for 30 days for abuse investigation, with repeated equivalent connections deduplicated within 15 minutes. A case may preserve the latest available relevant connection records separately under its case deadline. IP addresses may represent a proxy or shared network and do not establish legal identity. The client-reported version is not a verified device identity. The updated in-app privacy notice must be acknowledged before new chat connections. We do not collect identity documents or add persistent device fingerprints.

There are up to three local encrypted recovery copies of cases and connection records, refreshed approximately every 15 minutes. Ordinary chat messages are excluded. Each copy expires within one hour and is also cleaned against each record’s original deadline; releasing a legal hold updates the copies. Restoring a missing record never starts a new retention period. These copies protect against some accidental loss on the same server, not loss of the server, disk or encryption key. There is no offsite backup. Audit entries have keyed integrity checks; this is not immutable storage and cannot defeat a privileged attacker with the encryption key or an entire-store rollback. No system can promise perfect security or recovery after loss. If a material privacy practice changes, update the notice and provide notice in the app before collecting under the changed practice.

Community and child-safety standards

The service prohibits minors, sexual content, child sexual abuse or exploitation, sexual grooming or enticement, trafficking, threats, harassment, scams, impersonation, and disclosure of others’ private information. These prohibitions apply to chat, account names and avatars. Never request, send or redistribute child sexual abuse material. Report concerning accounts or content in the app; contact the safety email for urgent concerns, a report outside the in-app time window, or an appeal. If anyone is in immediate danger, contact the appropriate local emergency service.

We review reports and may restrict chat access, remove content, suspend accounts or preserve relevant evidence. Applicable child-safety reporting obligations, including reporting confirmed material or facts to the competent authority where required, must be handled by the operator after reviewing jurisdiction and obligations. Paying does not override safety restrictions or a partner’s decision to leave. This service is not an emergency service and does not promise round-the-clock human response.

Adult access policy (30 October 2026): We check that the date of birth registered to your account indicates age 18 or above. You continue to sign in using an email verification code. This is a self-declared age check, not independent identity or age verification. Accounts known to be underage, restricted or banned remain blocked. Date of birth remains private account data and cannot be changed by registering again with the same email; contact support to correct an error. A session access decision expires within 24 hours and may be renewed while the login session remains valid and the registered birth date is eligible. Access events are kept for 30 days. Account deletion removes these age records. No separate IP-country declaration is collected for this policy. This policy is not a claim of worldwide legal compliance.