Data Safety Summary
A readable summary for Apple App Privacy, Google Data Safety, permissions, and SDK review.
Last updated: September 1, 2026
The binding disclosure is the current store form plus the Privacy Notice. This summary reflects the current discovery-catalog build and must be rechecked against the final shipping archive and backend before release.
Collected or processed categories
Account identifiers, phone authentication, profile and verified photos, age, gender/profile attributes, language, country/city and approximate location, device/install identifiers, App Check, notification tokens, product interactions, analytics, offers, chats, media, voice, reports, support, and purchase/entitlement records may be processed.
- Camera, microphone, photo library, location, contacts, and notification access are requested only for their described feature.
- Sensitive verification and user content are not used for advertising tracking or general-purpose model training.
Sharing and service providers
Data is disclosed to processors only as needed for hosting, authentication, push, billing, maps, verification, moderation, transcription, translation, analytics, security, and support.
- No sale of personal data is intended.
- No ATT/IDFA cross-app tracking path is part of the current declared build; this must be reconfirmed from the final archive and every included SDK.
Security and deletion
App Check, authentication, server authorization, minimal catalog projections, short-lived media access, transport security, blocking, reporting, and account deletion reduce risk.
- No system is risk-free.
- Account deletion is available in the app and the public deletion page.
- Store forms must include data collected by every SDK and server transfer, not only fields visible in the UI.