1. Scope and who is responsible
This policy describes personal-information handling on HELLOSAO at hellosao.com, including its account, verification and restricted live features. Forgotten Quarry LLC, a Wyoming limited liability company, is the operator and the organization deciding why and how personal information is used for the service. Contact rjohnson@forgottenquarry.com for privacy questions and requests, or use the mailing address in section 18.
This notice covers HELLOSAO’s handling of information. It does not govern another participant’s independent use of information you share or a separate website you choose to visit. Naming a provider below does not transfer responsibility for HELLOSAO’s own decisions to that provider.
Back to top2. Information collected and why
Information is obtained from you, from your use of the service, from service providers that deliver it, and from people who submit a report about an account. Only provide information needed for the feature or issue. In particular, avoid putting birthdates, identity numbers, financial details or sensitive personal history into public profiles or chat.
Required registration and eligibility information is necessary to create an account or use protected features. Declining creator ID/selfie review prevents broadcasting; declining required viewer age screening prevents live participation. An optional introduction, chat message or gift is not necessary to create an account. Camera and microphone access are required only for the features that use them, and you can still read public information without enabling them.
| Information | Main purposes |
|---|---|
| Email, password submitted for authentication, account identifier, email-confirmation and sign-in records | Create and secure an account, authenticate access, send requested account messages and investigate misuse. Password handling is performed through the authentication service; passwords are not public profile fields. |
| Display name, participation type, country of residence, reading language and optional introduction | Maintain your profile, apply participation requirements and display the identity and preferences relevant to a feature. |
| Approximate connection country and, for U.S. viewers, state; match result, source and time | Compare declared residence with network-derived location during registration and preserve the basis of an eligibility decision. |
| Birthdate submitted for a viewer age check; resulting age threshold, jurisdiction, status and policy version | Determine age eligibility and prevent immediate retries intended to bypass an underage rejection. The typed birthdate is evaluated but is not retained as a separate birthdate field in the application’s age record. |
| Creator invitation use, application introduction and room topic, admission decisions | Control creator intake and review access to the creator program. |
| Government photo ID, fresh selfie, capture challenge and submission time | Manually assess creator identity, age, document readability and expiration, apparent facial match and inconsistencies. |
| Verification decisions, checklist results, age threshold, document-expiration information, reviewer, reason, timestamps and viewing logs | Record and audit verification, determine whether it remains valid, resolve concerns and manage deletion of document images. |
| Room and connection identifiers, live audio/video while transmitted, chat and language settings, participant events and technical session information | Deliver and control a live session, display messages, reconnect when possible and investigate technical failures or misuse. |
| Test-token transactions, gifts and recipients, room removals, blocks, complaints, report subjects and reporters | Deliver test features, keep transaction records consistent, investigate reports and enforce safety rules. |
| Account-notice acknowledgments, broadcasting consent, policy versions, administrative actions and support correspondence | Record the choices actually made, handle requests and maintain accountability for administrative decisions. |
3. Network information and location
Cloudflare processes connection information, including an IP address, to deliver and protect the website and derive approximate location. HELLOSAO’s registration record stores coarse country and relevant U.S. state information and a timestamp; it does not store the raw IP address in that registration record or request GPS coordinates for this check.
This registration check is not continuous GPS tracking and is not proof of a person’s physical location or residence. A VPN, mobile network or provider error may affect the result. Incorrect residence or location results may be raised with the team without changing information to evade a restriction.
Hosting, authentication and media providers may separately process IP addresses, browser or device information, request times, security signals and service logs. WebRTC media delivery also requires technical connection and network information. The narrower registration-record practice should not be read as a claim that no infrastructure provider ever processes an IP address.
Back to top4. Viewer age screening
Viewer registration uses the birthdate you enter to test the applicable minimum age. HELLOSAO keeps the resulting eligibility information and policy context instead of a separate full-birthdate field. A failed age check can result in a temporary retry restriction tied to the registration attempt. The application does not place your typed birthdate in a public profile or ordinary application log.
“Age self-declared” means you declared an eligible age; it does not mean your identity was verified. ID or selfie collection is not the default viewer flow. Stronger verification may be required for a jurisdiction or an account under review. No external age-verification provider is currently connected, and access remains blocked where its successful completion is required.
The service is for people at least 18 or the higher applicable age. We do not invite children to use it. Use the age-concern report if you believe an account is underage. Credible information is reviewed and may lead to restriction, rejection and appropriate handling of the associated information. A legal duty to protect a child or preserve evidence may affect deletion.
Back to top5. Creator ID photos and selfies
Creator verification requires a government-issued photo ID and a newly captured selfie following a time-limited challenge. The image itself may contain a full name, photograph, birthdate, document number, nationality and other printed details, even though those details are not all extracted into separate database fields. Do not submit another person’s documents or unnecessary additional documents.
Images are resized in your browser before upload. The selfie flow requests camera access; its capture does not require microphone access. You review and submit the images through the verification form. Unsubmitted previews remain in that browser session; submitting sends the images for private storage and review.
Authorized administrators compare the images manually. HELLOSAO does not currently create facial-recognition templates or use an automated face-matching or liveness vendor for this review. Human comparison is still identity-related processing; this description is not a claim that photographs are exempt from sensitive-data rules.
Document images are encrypted in private storage with restricted access. Opening them requires an authorized administrator and a recorded reason. Temporary viewing links expire after 60 seconds, and document reads are audited. The system keeps document data out of ordinary application logs and does not send the images by email. Authorized viewing necessarily decrypts an image for the reviewer; no security measure can guarantee absolute protection.
Uncertain cases may be marked for external verification. No provider is currently connected and escalation does not automatically transmit the documents. Before any outside flow begins, the provider, information involved, purpose and applicable choices must be explained. Payout onboarding, if later introduced, is a separate process.
Back to top6. What other people can see
When a feature displays your account, participants may see your display name and the profile or room details you choose to publish. In an authorized room they can see or hear the live content you transmit, read chat, and see displayed gift acknowledgments. Consider what your background, spoken conversation and screen may reveal.
Email, typed birthdates, private verification images and internal review notes are not public profile fields. Administrators can access account information and review records within their assigned permissions. Creator room controls may show participant identifiers needed for moderation, but they do not grant creators general access to other users’ identity documents.
Reports identify the subject and reporter to authorized reviewers. We limit access to report information, but cannot promise absolute reporter anonymity: context, a necessary investigation or a legal obligation can require disclosure. We do not publicly display an unreviewed report as an established finding.
Back to top7. Activity tracking and safety monitoring
HELLOSAO records operational and safety activity, including account events, room connections, chat metadata, test gifts, blocks, room removals, complaints and administrative actions. Automated eligibility and access controls use account and policy information. Authorized staff can review relevant records to investigate abuse, age concerns, suspected fraud, security incidents and violations of the room rules. This is operational and safety monitoring, not a promise that every action is observed by a person as it happens.
When enabled, live audio and video travel through Cloudflare’s real-time media service to authorized room participants. HELLOSAO does not currently offer media recording, replay, download, clips or a stream archive. Transport and processing involve transient media handling; the service should not be treated as an end-to-end encrypted private messenger.
People receiving a stream may independently record or capture it despite the site’s rules. Room restrictions reduce the permitted audience but do not make a disclosure confidential or prevent copying by a recipient. Only share content you are prepared for the intended audience to receive.
Chat text and available translations are short-lived; message metadata such as identifiers, sender, room and timestamps can remain after text is cleared. The current test translation feature uses fixed phrase examples and does not send your message to an external AI translation provider. Audio translation is not enabled. Any future provider or materially different use must be disclosed before it is introduced.
Where staff live-room review is enabled, authorized safety staff may review public, private, invitation-only or paid rooms without an ordinary arrival notice or a purchase. Access must be limited to an authorized purpose, time-limited and recorded in an audit trail. A restricted room is not exempt from safety review. The current pilot does not promise continuous human monitoring or offer every future room-review feature. A report can separately preserve information supplied in it after the ordinary chat copy expires.
Back to top8. Purposes and legal grounds
HELLOSAO uses information to provide requested account and live features, check age and admission requirements, secure the service, prevent abuse, resolve reports, maintain reliable test transactions, answer requests and meet applicable legal obligations. It does not use creator verification documents for public promotion or advertising.
Where a law requires a legal basis, the basis must match the particular processing. Providing a requested service may rely on contractual necessity; a specific legal duty may require compliance processing; proportionate security and abuse prevention may involve legitimate interests after considering the impact on people. Optional processing may require consent that can be withdrawn. Mandatory local rules take precedence over a general description of these bases.
Acknowledging this policy, accepting terms, using the website or ticking a general account notice is not consent to every purpose. Government IDs, age information and identity-related images can require additional legal conditions, notices or consent in some countries. Where those conditions apply, the relevant processing must satisfy them separately. An acknowledgment records the document version and review time; it does not grant age eligibility or permission to broadcast.
Server rules automatically check eligibility and access conditions; creator document decisions are made by authorized reviewers. If an inaccurate automated age or location result affects you, you may request review and correction. Rights relating to automated decisions depend on applicable law.
Back to top9. Providers and other disclosures
HELLOSAO uses providers to perform defined service functions. They receive information needed for those functions, subject to the applicable service arrangements. Current operational providers include the following; their own notices explain processing they perform in their separate roles.
| Recipient / service | Function and information involved |
|---|---|
| Cloudflare | Website hosting, delivery, security, approximate network location and live-media transport when enabled. Processes requests and connection information, and the media necessary for an authorized live session. |
| Supabase | Account authentication, database services and private verification storage. Processes account information, stored application records and verification information. The current application database is configured in Seoul, South Korea; this does not mean all provider support or infrastructure processing is confined there. |
| Authorized administrators and reviewers | Account administration, creator admission, identity and age review, safety reports and technical operations within their permitted responsibilities. |
| Authorized participants | The profile, room, chat, gift acknowledgment and live content displayed to them when you use the relevant feature. |
| Authorities, professional advisers or parties involved in a legal claim | Information necessary for a valid legal obligation, serious safety issue, protection of rights or a properly assessed legal claim. Requests are considered in light of applicable law. |
10. Advertising, future providers and business changes
The current application has no advertising network, cross-site advertising pixel or real-money payment integration. This policy does not authorize selling personal information or sharing it for cross-context behavioral advertising. Operational service-provider processing still occurs as described above. Definitions of sale and sharing vary by jurisdiction; you may contact us about how an applicable privacy right relates to your information.
No external identity-verification, payout or AI translation provider has been selected by this policy. If one is introduced, the notice and relevant collection flow must first identify the new processing, recipient and choices, and obtain consent where required. New payment information should be collected only through the approved payment or payout process.
If ownership or operation of the service changes, personal information may be involved in a properly protected transaction or transfer. Applicable obligations, purpose limits and notification requirements continue to apply; a business transfer is not permission to disregard previous privacy commitments.
Back to top11. International processing
HELLOSAO is intended for a limited set of viewer and creator countries, while its providers and authorized personnel may process information elsewhere. The current application database is in South Korea and Cloudflare operates international infrastructure. Your information may therefore cross borders, including to places with different privacy laws.
Contact our privacy address for information about the recipients, processing locations and applicable safeguards for your information. Available mechanisms and conditions depend on the transfer and the law that applies; they can include an applicable adequacy decision, approved contractual safeguards or another permitted basis. This notice does not claim a transfer certification or local regulatory approval.
Where local rules require additional transfer information or specific consent, it must be provided or obtained separately. Reading this policy is not a substitute for that consent. We will explain a material change in processing locations or recipients where required before introducing it.
Back to top12. Retention and deletion
Retention depends on the type of information and its purpose. The following describes the current implementation. An administrator’s “Past 30 days” activity view is only a display window; it does not delete older account, transaction or moderation records.
| Information | Current handling |
|---|---|
| Creator ID and selfie images | Default pending-review retention is 30 days from submission. A review decision normally sets a new deadline of up to 30 days from that decision, capped at 90 days from submission. Escalation preserves the existing deadline. The submission screen states the configured periods. Administrators may shorten retention; increasing the settings alone does not extend existing deadlines. |
| Image deletion | Automatic cleanup is scheduled every 15 minutes. It removes the stored image ciphertext, associated keys and viewing grants from active storage when due. Cleanup timing can be affected by an operational failure; the system restricts new collection if cleanup is stale. |
| Minimum verification record | Review status, reviewer, timestamps, reasons, checklist and eligibility/expiration information remain after image deletion for accountability and age-access decisions. A blanket automatic deletion deadline is not currently configured for these review records. |
| Viewer birthdate and retry controls | The typed birthdate is evaluated without a separate retained DOB field. Underage-rejection controls use a protected hash of the email, a 24-hour retry restriction and an attempt record that expires after seven days. Short-lived signup tickets are cleaned up after expiry. Eligibility status and policy context remain with the account. |
| Live audio and video | No HELLOSAO recording or replay archive is created by the current live implementation. Technical transport and provider processing still occur while a session is delivered. |
| Chat and translation text | Ordinary live-chat text expires after about 60 minutes: cleanup clears message bodies and deletes cached translations. Message identifiers, sender/room references and timestamps remain. Text deliberately included in a complaint can remain as part of that separate complaint record. |
| Live quality diagnostics | Limited connection-quality counters, timing and route information are kept for technical troubleshooting and expire 30 days after their last update. Room, session and cleanup-coordination records have no general automatic deletion deadline. |
| Accounts, consent history, invitations, test transactions, room events, complaints and administrative logs | Retained during the pilot for the relevant account, transaction, safety or audit purpose. These records do not currently have a universal automatic purge deadline. Requests and periodic retention decisions require review of necessity and applicable obligations. |
| Provider logs and backups | Handled under the configured provider arrangements and backup lifecycle. Deletion from active application storage does not promise immediate deletion of all backup or infrastructure copies. |
13. Security measures
Controls include encrypted connections, server-checked access permissions, private verification storage, encrypted document images, temporary document views and audit records. Authentication uses secure, HttpOnly cookies in production. Verification images are not exposed as public files, and staff access is restricted to authorized functions.
No website, storage system or transmission method is completely secure. Keep your password private, sign out on shared devices and report suspected unauthorized access. Do not send passwords, identity images or full payment credentials through ordinary email or chat. If an incident requires notice under applicable law, the responsible operator must provide it through the appropriate process.
Back to top15. Your choices and privacy requests
Depending on your location and the applicable law, you may have rights to learn how information is used, access or receive a copy, correct inaccuracies, request deletion, restrict or object to processing, receive certain data in a portable form, withdraw consent, or request review of certain automated decisions. Some laws also allow an authorized representative or an appeal of a denied request. These rights have conditions and exceptions.
You can edit the profile fields made available in My account and control browser permissions. Residence, participation and age evidence may need an administrator’s review rather than an unrestricted edit. HELLOSAO does not currently provide a self-service account-deletion or data-export button.
Send privacy requests to rjohnson@forgottenquarry.com. Identify the account, your country or state where relevant, and the desired action without sending an ID image or password by ordinary email. Reasonable identity or authority checks may be needed, limited to what is proportionate. A person should not be required to create an account merely to make a request where the law does not allow that requirement.
Requests must be answered within the period required by the applicable law, with any permitted extension explained. If a request cannot be fully granted, the reason and available review or complaint route should be provided. Valid privacy requests should not result in unlawful discrimination. Withdrawing consent does not undo prior lawful processing and may make a consent-dependent feature unavailable.
You may contact the competent privacy regulator where the law gives you that right. An unresolved request does not remove the right to complain to a regulator or seek another legally available remedy.
Back to top16. Regional considerations
The account registration regions are the United States, Canada, Australia, the United Kingdom, Germany, Japan, South Korea and Taiwan for viewers, and Thailand, the Philippines, Vietnam, Colombia and Argentina for creators. Different duties can apply to an operator, a consumer service and sensitive identity or age information in each place.
- EEA and United Kingdom: applicable rights can include access, correction, erasure, restriction, portability, objection, consent withdrawal and protections relating to certain automated decisions. You may contact us or the competent supervisory authority. Where processing relies on legitimate interests, the interests include account security, abuse prevention and investigation of complaints, balanced against your rights.
- United States: state privacy, sensitive-data and age-assurance requirements vary and may depend on thresholds or activities. Where an opt-out right for sale, targeted advertising or qualifying profiling applies, it must be honored, including a recognized browser signal when required. The current pilot does not conduct the advertising or sale activities described above.
- Canada, Australia, Japan, South Korea and Taiwan: depending on the applicable law, you may request access to or correction of your personal information, withdraw consent, or raise a complaint about its handling. Contact us for details of overseas processing and service providers relevant to your information. Mandatory local notice and consent requirements continue to apply.
- Creator countries: government ID, age, selfie and cross-border processing can trigger additional requirements. Rights and consent conditions differ in Thailand, the Philippines, Vietnam, Colombia and Argentina. Contact us to request access, correction, deletion or another right available under the law that applies to you. Local response deadlines apply to those requests.
17. Changes to this notice
This page identifies its version and effective date. We will update the notice to reflect changes in processing and communicate material new uses before they occur where required. A revised notice alone does not supply consent or a legal basis for an incompatible new use.
New accounts acknowledge reviewing the Terms and Privacy Policy separately. We retain the acknowledged versions and time. A future material change may require a new notice, acknowledgment or consent depending on the change and applicable law.
Back to top18. Privacy contact
Contact Forgotten Quarry LLC using the email or mailing address below for privacy requests or questions. Any required privacy officer or local representative will be separately identified. Do not send sensitive identity documents or passwords by email. The signed-in age-concern reporting feature is also available for reports about a possibly underage account.
- Operator
- Forgotten Quarry LLC
- Business mailing address
- 207 W A ST UNIT 1001 RAINIER OR 97048 United States
- Support and privacy email
- rjohnson@forgottenquarry.com
Document version: 2026-09-11.1 · Effective September 11, 2026