This notice is information, not blanket consent. Contract acceptance, this notice acknowledgment, liveness/face-consistency consent, international AI/cloud transfer consent, and optional marketing consent are recorded separately.
01Collected 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.
- For billing and token delivery, 72 processes account-linked product and transaction identifiers, store environment/status, period dates, provider-reported usage totals, reservations, balance and usage-ledger entries, refunds and verification/reconciliation records. These support delivery, fraud prevention, disputes and accounting; the store handles full payment-card details.
02Sharing 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.
03Security 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.
04Account, legal consent, and profile data
Firebase/Auth UID, phone number, auth/session state, account creation/login state, accepted legal docs, consent package version, timestamps, and account deletion request records may be processed for account security, compliance, support, deletion, and disputes. Display/preferred name, declared gender, age/birthdate, language, country/city/region, about/bio, introduction preferences, and profile visibility state are used for profile and controlled introduction experiences.
05Photos, media, and verification data
Primary profile photo, cropped/verified photo, profile media, and media moderation state may be processed for profile display, photo consistency, and safety. Camera capture, live frames/video/signals, real-camera/anti-replay/profile photo consistency signals, and verification result/status are for risk reduction and profile consistency. They are not official KYC, legal identity verification, guaranteed gender, guaranteed age, or guaranteed location.
06Photos, media, and files permission
Photos/media/library/file permissions may be requested for profile media upload, permanent chat media selection, and user-chosen save/download/export flows where supported. 72 does not claim that chat media is automatically saved to the gallery. Users can control permissions in OS settings or use limited library controls where available.
07Security measures and encryption
72 may use authentication, backend checks, Firebase/GCP security controls, Firestore/Storage access controls, signed URLs where applicable, limited admin/human review access, audit/security logs, moderation controls, and abuse-prevention tooling. Data may be protected by in-transit or at-rest encryption provided by platform/cloud infrastructure. 72 does not claim end-to-end encryption for chat/media and does not guarantee absolute security.
08What 72 does not guarantee
72 does not guarantee legal identity/KYC, guaranteed gender, guaranteed age, guaranteed location, guaranteed safety, guaranteed compatibility, guaranteed relationship outcome, E2EE, detection of all abuse/scams/fake profiles, prevention of external media recording, notification delivery, or immediate deletion of every backup/legal/safety record.
09Camera and microphone
Camera access supports the verification and photo/video capture flows you start. Microphone access supports voice messages and supported recordings with audio. Permissions are requested for the relevant feature, not as permission to record you secretly in the background. Refusing an essential capture permission can prevent that capture feature from working. You can review device permissions in operating-system settings. Verification is a risk-reduction check, not official identity verification or a guarantee about age, gender, location or safety.
10Location, notifications and contacts
Location permission can support updating country, city and location-related profile or safety information. It does not certify another person’s real location. Notification permission lets the operating system show chat, account and service updates; delivery remains subject to device and network conditions. Where you use contact-based blocking, contact access supports that selected privacy function. You can manage device permissions and the corresponding in-app preferences. Turning off a permission does not automatically erase data previously submitted; use the privacy and deletion options for that.
11Usage data and device permissions are separate
A camera, microphone, media, contact, notification or location permission does not imply agreement to analytics or marketing. Optional usage analytics is controlled by the app’s separate choice. Essential account, security, delivery, billing and diagnostic records used to operate or protect the service are described in the Privacy Notice. Do not treat accepting this policy as permission for every device capability.