How 1:2 handles user data, identity checks, payments, and launch-list collection.

1. Information we collect

• Account information, including phone number used for OTP login and verification.
• Profile information such as name, date of birth, bio, in-app captured profile photos, and profile preferences.
• Identity verification state and result data returned through Yoti.
• Location data, when permission is granted, to power scan, radar, nearby discovery, and certain safety features.
• Messages, video messages, and other communication content exchanged inside the app.
• Safety-related data including date check-ins, safety notes, and safety ratings.
• Payment and subscription event data from Google Play, RevenueCat, and connected billing systems.
• Technical and device information needed for authentication, fraud prevention, reliability, abuse prevention, and service security.
• Wishlist information submitted on 1to2.vip, including email address and related request metadata.

2. How we use information

• Create and protect user accounts.
• Authenticate access using phone OTP.
• Verify identity and age.
• Enable matching, chat, radar, and nearby discovery.
• Process payments, subscriptions, and access tiers.
• Prevent creator-farming, off-platform solicitation, fake accounts, fraud, and abuse.
• Support safety features tied to real-world dates and meetups.
• Operate the wishlist, launch queue, and invite-access flows on 1to2.vip.

3. Sensitive data handling

1:2 is a dating platform, which means some data processed through the service can be personal or sensitive. We use secured backend systems, encrypted connections, secret-managed server integrations, and database-side controls to reduce the risk of client-side tampering or unauthorized access.

4. Third-party services

• Supabase for authentication, storage, realtime, database operations, and edge functions.
• Yoti for identity and age verification.
• RevenueCat and Google Play for subscriptions, purchase events, and billing state.
• OpenAI for optional profile-writing assistance and certain moderation support.
• Connected service providers may support launch-list delivery and related service operations.

5. Camera, microphone, and media

1:2 may request camera access for in-app profile photo capture, verification flows, and video messaging. Microphone access may be requested for video message audio. Profile media is intended to be captured within the app as part of the trust and anti-abuse design.

6. Location data

If a user enables location access, 1:2 uses location data to power radar, scan, nearby user discovery, and some safety functionality. Users can disable radar visibility in the app, which is intended to stop their profile from appearing in radar and scan results.

7. Age restriction

1:2 is strictly for adults aged 18 and over. Under-18 access is not permitted. Users may be asked to confirm date of birth and complete identity verification to access the service.

8. Data retention

We retain information for as long as needed to provide the service, maintain platform safety, enforce rules, prevent fraud, resolve disputes, comply with legal obligations, and support payment, moderation, and trust operations.

9. Account deletion

Users may request account deletion. Some records may still be retained where necessary for fraud prevention, abuse investigations, payment records, legal compliance, or platform safety review.

10. Your choices

• Update profile information inside the app.
• Disable radar visibility.
• Enable or disable biometric lock on-device.
• Request account deletion.

11. Security

We use reasonable technical, organizational, and administrative safeguards. These include authenticated backend flows, restricted secret handling, database-side controls, encrypted transport, and verification-based trust systems. No platform can promise absolute security, but the service is designed to reduce unnecessary exposure and abuse.

12. Changes to this policy

We may update this Privacy Policy from time to time. When we do, we will update the last-updated date on this page.