LEGAL & SAFETY
Privacy Policy
This Privacy Policy explains how we process your personal information when you use the Service. Please read this Policy before using the Service. If you do not agree, do not register for or use the Service.
The processing described here reflects the system as built. The disclosures here must be kept consistent with the Google Play Data safety form.
1. Information We Process
Depending on the features you use, we may process the following information:
| Category of information | Information that may be included | Primary purpose |
|---|---|---|
| Sign-in and account information | Sign in with Google requests only the standard openid, email, and profile scopes — no contacts, calendar, or Drive access. Of what Google returns we store only your Google account identifier and your email address. The name and picture Google provides are neither used nor stored: you choose your own display name, and profile pictures are chosen from a preset set. We also store the date of birth you enter. | To create and manage accounts, confirm that users are at least 18, and protect account security |
| Text content you submit | Text profile information, posts, activity information, direct messages, activity-group messages, and report descriptions | To provide social, activity, and communication features; process reports; and maintain community safety |
| Activity and interaction information | Published activities, requests to join, confirmed participation, completed-activity count, blocking records, and report records | To provide activity features, display positive completed-activity counts, and maintain community order |
| Device and service logs | A SHA-256 hash of the Android SSAID, computed on your device so the raw identifier never leaves it; crash diagnostics collected by Firebase Crashlytics (stack traces, device model, OS version), configured not to identify users; and connection metadata such as IP address and timestamps handled by our infrastructure providers. We do not collect advertising identifiers, IMEI, or MAC addresses, and the app contains no analytics or behavioural-tracking SDK. | To operate and secure the Service, prevent misuse, and troubleshoot faults |
| Customer-support contact information | Email address, questions, and attachments that you provide when emailing us | To answer enquiries and process deletion requests or safety matters |
Profile pictures are chosen from a fixed set of twelve preset avatar illustrations provided by the platform. The Service does not support photo or video uploads, camera functionality, or a photo picker, and we do not collect camera data or photo/video content.
2. How We Use Information
We use the above information only to the extent necessary to provide and maintain the Service, including to:
- enable Google Sign-In and account creation and use;
- provide text posts, activities, direct messages, and activity-group features, and display relevant information according to the applicable screen rules;
- calculate and display positive completed-activity counts;
- receive, investigate, and process reports, and prevent fraud, harassment, illegal conduct, and other misuse;
- maintain Service security, troubleshoot faults, comply with legal obligations, and respond to lawful requests; and
- respond to enquiries, deletion requests, and other service requests.
3. Content Visibility
Text content that you publish publicly may be viewed by other users of the Service. Do not publish private or sensitive information.
Before an activity is joined, other users may view its public information. Once participation is confirmed, participants may view the activity’s members, the creator’s identity, and activity details. The display of the activity location is governed by the on-screen notice at the relevant stage.
Direct messages are visible only to the two participants in the conversation. Activity-group messages are visible only to members of the relevant activity group. Please note that a recipient may independently save, forward, or disclose information visible to that recipient.
Blocking is mutual and takes effect at the messaging-service level rather than in the interface: neither user can send the other direct messages, and each other’s activities, posts, and comments are filtered out of your respective feeds. Each of you sees an unavailable page in place of the other’s profile. Blocking does not change what is visible inside an activity group you both belong to, and it does not alter what other users can see.
5. Information Sharing
We do not sell your personal information. We share information only to the extent necessary to provide the Service, protect safety, or comply with legal requirements:
- With other users: information that you actively publish, or that becomes visible because you participate in an activity, as described in Section 3 of this Policy and the relevant screen notices;
- With service providers acting on our behalf: the processors listed below;
- With competent authorities: where necessary to comply with legal requirements or legal process, or to protect the lawful rights and interests of users, the public, or the Platform; and
- In a corporate transaction: where required by law, in connection with a reorganisation, merger, acquisition, or transfer of assets.
| Processor | What it processes | Where |
|---|---|---|
| Supabase Inc. | Database and sign-in authentication: accounts, profiles, activities, posts, and comments | United States (East US, N. Virginia) |
| Google LLC | Sign in with Google; app distribution through Google Play; crash diagnostics through Firebase Crashlytics | United States |
| NetEase Yunxin | Transmission and storage of chat messages. Direct messages and group messages are stored only with this provider and are not held on our own servers | Singapore, with a retention period of up to one year |
| Vercel Inc. | Hosting for this website, and the technical logs that hosting produces, such as request logs, IP addresses, and timestamps. It does not process your account or activity data | United States |
Fonts and other assets are bundled into the app, so no resources are fetched from a content delivery network at runtime.
Cross-border transfers
Your information crosses borders in the following ways. We set this out so you can see where your data goes, not only who handles it.
- Storage in the United States. Accounts, profiles, activities, posts, and comments are stored by Supabase in the United States. Sign-in, app distribution, and crash diagnostics are handled by Google in the United States.
- Access from Hong Kong. Social Element Limited operates from the Hong Kong Special Administrative Region, and its personnel access the systems above from there for operations, safety, and support. Your information is therefore accessed outside the country where it is stored, and outside the country where you may live.
- Chat messages. Direct and group messages are held by NetEase Yunxin rather than on our servers. Where that provider stores them, and for how long, is Singapore, with a retention period of up to one year.
Where information is transferred across borders, we rely on contractual terms with each processor requiring it to protect the information and to process it only on our instructions. We do not transfer your information to any party for its own independent purposes.
6. Information Security
We use administrative and technical measures appropriate to the risks:
- Encryption in transit: TLS across the whole path.
- Encryption at rest: provided by our cloud platforms.
- Access control: row-level security on the database with least-privilege grants. Tables are granted explicitly by role, every write goes through an authenticated server-side interface rather than direct client access, and each interface verifies the caller independently.
- Key management: server keys are kept out of the code repository, in separate key storage.
- Data minimisation: direct-message content is never stored on our servers; sensitive identifiers are stored only as irreversible hashes; there are no user-uploaded images.
- Report handling: when a report is investigated we retain only a message identifier, never message content, and clear the identifier once the matter is closed.
However, no online service can guarantee absolute security. Please keep your account secure and exercise caution when publishing information.
7. Data Retention and Deletion
We retain information only for as long as necessary to achieve the purposes described in this Policy, meet legal obligations, or address safety or dispute matters.
You may initiate account deletion in the App or submit a deletion request to olyoo2026@outlook.com in accordance with Section 8 of the Terms of Service. After the request is submitted, there is a seven-day restoration period. Logging in during that period cancels the deletion request. Once the restoration period ends, we will complete deletion of the account and associated data. See Delete Account for step-by-step instructions.
When deletion completes, your profile, posts, and comments are cleared, and your direct messages are removed from your side of each conversation by our chat provider. A copy already delivered to the other person remains on their device and in their account, because the chat provider gives us no way to reach it. Group-chat history likewise remains visible to the other members of that group, because it is a shared record rather than yours alone.
Specific retention periods:
- Denylist hashes — kept for as long as the purpose lasts. To keep people under 18 off an adults-only service, we store irreversible SHA-256 hashes of the Google account identifier and the device identifier behind a registration we have blocked. We store the hash and nothing else: no plain-text identifier is kept, the hash cannot be reversed to recover the original value, and it is used for this one check and no other purpose. We keep it for as long as that purpose lasts, which in practice is indefinitely — the whole point is to stop the same person or device registering again, and a record that expired would let exactly that happen. We consider this the least information capable of achieving it; if a narrower method becomes available, we will move to it and say so here.
- Report evidence identifiers — cleared once resolved, except where the law requires otherwise. Where a report concerns child sexual abuse material and we report it to NCMEC, United States federal law requires the related records to be preserved for a defined period after that report, which is longer than our ordinary retention. Those records are kept for as long as the law requires, and we may preserve them longer where the law permits it and safety requires it.
- Everything else — cleared when the account is deleted, following the seven-day restoration period.
Beyond this, if permitted or required by law we may retain limited information for safety, anti-fraud, dispute-resolution, or compliance purposes, to the extent applicable law permits.
8. Your Rights and Choices
To the extent provided by applicable law, you may have the right to request access to, correction of, deletion of, or restriction of processing of your personal information, withdraw consent, or obtain a copy of your personal information. Please contact us at olyoo2026@outlook.com; we may need to verify your identity.
United States state privacy rights
We do not sell your personal information, and we do not share it for cross-context behavioural advertising purposes. Depending on the privacy law of the state in which you live — for example the California CCPA/CPRA or the Virginia VCDPA, each of which applies only above its own statutory thresholds — you may have the right to know about, access, correct, and delete your personal information, to obtain a copy of it, and not to be treated in a discriminatory way for exercising those rights. You may exercise these rights by contacting olyoo2026@outlook.com, and you may appoint an authorised agent to make a request on your behalf to the extent applicable law permits.
9. Minors
The Service is intended only for persons aged 18 and over. We do not offer the Service to minors or permit minors to register for or use it. If we discover, or reasonably believe, that an account belongs to a minor, we may directly restrict, suspend, or ban the account. Please see the Minor and Child Safety Policy.
10. Policy Updates and Contact Information
We may update this Policy and will update the effective date on the official website and in the App. Where required by law, we will notify you or obtain necessary consent through an appropriate method.
For questions about this Policy or the processing of personal information, contact olyoo2026@outlook.com.