1. Information We Collect
Account information — email address, display name, and profile photos you provide when creating or updating your account.
Device information — device manufacturer, model, operating system version, screen resolution, RAM, and app version. This helps us diagnose issues and enforce our policies.
Network information — IP address, ISP, ASN, and approximate geolocation derived from your IP address. This is used for safety enforcement and abuse prevention.
Usage logs — app actions, page views, errors, and crash reports. These help us monitor performance and fix problems.
Sign-in identities — if you link multiple sign-in methods (Google, Apple, Email) to your account, we store the associated provider identifiers (such as email addresses and Apple identifiers) in an identity map alongside your account to enable multi-provider sign-in.
Voice chat data — connection metadata only (e.g., join/leave times, connection quality). We do not record audio.
Age verification data — your date of birth (entered at sign-up) and, if you choose to access 18+ features (private messages, gacha), a temporary copy of a government-issued ID (passport, driver's licence, or national ID card). The ID image is reviewed by a human admin and is permanently deleted as soon as a decision is recorded — we do not retain the image after review. Only the verification status, decision timestamp, and ID type (e.g. "passport") are kept on your account afterwards.
2. How We Use Your Information
- Provide, maintain, and improve our services
- Enforce community standards and our policies
- Device and network banning for user safety
- Error monitoring and debugging
- Resolve your identity across multiple sign-in providers
- Prevent multi-account abuse
- Verify that users of 18+ gated features (private messages, gacha) are 18 or older, in line with Apple App Store content guidelines and UK Online Safety Act requirements
3. Data Storage & Retention
- Live logs: stored in Firestore with configurable retention (default 48 hours)
- Archived logs: stored in R2 with 90-day retention
- User data: stored in Firestore, backed up to R2 with 7-day backup retention
- Images and media: stored on Cloudflare R2 CDN
- Age verification ID images: stored on Cloudflare R2 CDN ONLY until an admin records a decision (approve, reject, or DOB modify). The image is deleted as part of the same admin action. Worst-case retention is bounded by the admin queue review time, typically minutes to a few hours. Only the verification status, ID type, and decision timestamp persist after deletion.
4. Device & Network Banning
We may ban specific devices or network addresses to enforce our policies and protect our community. Bans may be temporary or permanent, and may be applied automatically when an account is suspended.
5. Data Sharing
We do not sell your data. We share data only with the following service providers to operate ShyTalk:
- ip-api.com — IP geolocation enrichment (free tier; no personally identifiable information is shared beyond the IP address)
- Firebase (Google) — authentication and database services
- Cloudflare — CDN, storage, and page hosting
- LiveKit (self-hosted) — voice chat connections processed through our servers on Oracle Cloud infrastructure in Singapore and London, United Kingdom. Connection metadata (IP address, join/leave times, connection quality) transits through these servers during voice chat sessions.
6. Your Rights
You have the right to:
- Request an export of your data
- Request deletion of your account and associated data
To exercise these rights, contact us at shytalk.help@gmail.com.
7. Changes to This Policy
We may update this privacy policy from time to time. Continued use of ShyTalk after changes are posted constitutes your acceptance of the revised policy.
8. Data Controller
The data controller responsible for your personal data is Shyden Ltd (Company No. 17110487), registered at 71-75 Shelton Street, Covent Garden, London, WC2H 9JQ, United Kingdom.
For data protection enquiries, contact us at shytalk.help@gmail.com.
9. Contact
If you have questions about this privacy policy, contact us at shytalk.help@gmail.com.
10. Age Verification
Why we collect this. ShyTalk's private messages and gacha features are 18+. Apple App Store guideline 1.1.4 and the UK Online Safety Act both require us to make a reasonable effort to confirm a user is 18 or older before granting access to those features.
How verification works. The 18+ features are gated behind a server-side flag on your account. To unlock them, you upload one government-issued ID image (passport, driver's licence, or national ID card) to a private review queue. An admin compares the date of birth on the ID against the date of birth on your account, then records a decision: approve, reject, or modify the date of birth on file.
Image lifetime. Your ID image is uploaded directly to encrypted storage (Cloudflare R2) using a short-lived signed URL — the upload bypasses our backend so the image never touches our application servers. The image is permanently deleted as part of the same admin action that records the decision; we do not retain copies, backups, or thumbnails. The only persistent record afterwards is the verification status, ID type (e.g. "passport"), decision timestamp, and an audit-log entry naming the admin who decided.
Sub-18 users. If your account's date of birth indicates you are under 18, you cannot enter the verification flow. The 18+ features remain disabled and you cannot override this by submitting an ID. If you believe the date of birth on your account is wrong, please contact support — we will not accept ID submissions to override the date of birth on file. Once you turn 18, the verification flow becomes available automatically.
Reverting verification. If an admin reviewing your ID determines that the date of birth on file is wrong AND that you are under 18, your verification status is reverted, the 18+ features are disabled, and any existing private-message threads on your account are locked until you reach 18. The admin records a written reason for this decision in the audit log, and you receive a system message explaining the change.
Legal basis (UK GDPR / EU GDPR). We process this data on the basis of legal obligation (Apple guideline 1.1.4, UK Online Safety Act) and legitimate interest (preventing minors from accessing 18+ features). You have all the rights described in section 6 above, including the right to request deletion of your verification records.
Non-prod environments. ShyTalk operates a development environment for internal testing. In that environment the verification flow runs end-to-end but the ID image is treated as test data — please do NOT submit a real government-issued ID in the dev environment. Upload any non-sensitive image (a screenshot, a photo of a book, etc.) to exercise the flow.
11. Account Cohorts (UK Online Safety Act)
Why we separate accounts by age. The UK Online Safety Act requires services with under-18 users to take proportionate steps to keep minors and adults from interacting with each other on social features. To meet this duty we group every ShyTalk account into one of two cohorts — minor (under 18) or adult (18 and over) — and limit cross-cohort visibility and interaction across the app.
How your cohort is decided. Your cohort is derived automatically from the date of birth on your account. It is recalculated at every sign-in, so an account that has crossed its 18th birthday moves to the adult cohort on the next sign-in without any action from you.
What the cohort affects. Discovery, search, follow lists, leaderboards, gift-walls, voice rooms, 1:1 conversations, group conversations, gift sending, peer-to-peer coin transfers, and push notifications are all filtered so that accounts in different cohorts do not see or interact with each other. Profiles and rooms outside your cohort are presented as "unavailable" rather than naming the reason — this is deliberate, so that no user can infer another user's age from the app's behaviour.
Existing connections. When this policy was first applied we ran a one-off migration: cross-cohort follow links were removed, cross-cohort 1:1 conversation threads were hidden, and mixed-cohort group conversations were frozen (preserved as read-only, with no new members or messages permitted). Affected users received a system message explaining what changed. We could not preserve any cross-cohort interaction state and these changes cannot be reversed from within the app.
Cohort overrides. A small number of staff and partner accounts (clearly identified internally) may have their cohort manually set by an administrator. Every override writes an entry to our internal audit log naming the administrator, the target account, the previous and new cohort, and the written reason supplied at the time. Overrides do not apply to ordinary user accounts.
Your rights. Your cohort is derived from data you provided (date of birth) and is processed under the same legal bases as the rest of your account information (section 6 above). You can request the current cohort value on your account and the audit-log history of any cohort changes by contacting support. If you believe your date of birth is wrong on the account, see section 10 ("Age Verification") — correcting the date of birth automatically corrects the cohort on the next sign-in.