Privacy Policy

VeriDates
Effective date: July 13, 2026
Operator: Guillermo Perez-A operating as VeriDates
Privacy contact: contact@veridatesapp.com

1. Information we collect

• Account and sign-in data: email address returned by your Google account, phone number, display name, date of birth, authentication identifiers and session tokens. The current release uses Google Sign-In; phone verification uses a one-time code.
• Profile and preference data: your name, age, city or region you provide, gender and discovery preferences, bio, interests, prompts, profile status, primary profile photo, likes, passes, matches, blocks and reports.
• Messages: the text you send to a match, message timestamps and sender/recipient identifiers. Messages are not end-to-end encrypted.
• Face-verification data: your primary profile photo, face-liveness capture submitted when you choose Face Verify, verification result, timestamps, confidence values, attempt and fraud-prevention records. We do not store a reusable face template in our own database.
• Safety and technical data: report details, limited message-safety signals, app/device version, IP-derived abuse controls, device/app-integrity signals and general app-usage analytics.
• Purchase data: Google Play purchase tokens, order references and entitlement status if you buy a digital product. We do not receive your full payment-card number.

2. Data we do not collect in the current version

VeriDates does not request your precise GPS location, contacts, SMS messages, call logs, or background location. The current version does not use advertising SDKs, Firebase Authentication, Firebase Cloud Messaging, or Crashlytics. Government-ID verification is not enabled in the current release.

3. How we use data

• Create, authenticate and secure accounts, including Google Sign-In and phone verification.
• Build profiles, apply discovery preferences, create mutual matches and enable matched users to exchange messages.
• Confirm that a live face matches the account's primary profile photo and display a Face Verified status when that check succeeds.
• Prevent spam, impersonation, fraud, underage use and other misuse; process blocks and reports; and respond to legal or safety requests.
• Measure basic app performance and usage, protect the app with integrity checks, and provide purchase entitlements.

4. Service providers and disclosures

We do not sell personal information. We use providers that process data only to operate the Service:

• Supabase: account authentication, PostgreSQL database and backend functions.
• Cloudflare R2: private storage of the primary profile photo. Other users receive a limited, short-lived link only when the app needs to show the photo to them.
• Amazon Web Services: AWS Rekognition Face Liveness and face comparison process the verification capture and primary photo to return a verification result.
• Twilio Verify: delivery and validation of phone-verification codes. VeriDates does not store the code itself.
• Google: Google Sign-In if you choose it, Google Play billing, Play Integrity through Firebase App Check, and Firebase Analytics.

Other users can see the profile information you choose to show them, including your profile photo and verification status. Matches can see messages you send them. We may disclose information when legally required or to investigate safety, fraud or abuse.

5. Camera and microphone

The camera is used only after you take an action that needs it, such as taking a primary profile photo or starting Face Verify. Face Verify sends the necessary capture to AWS Rekognition through a secure verification session. The app may request microphone access only when you choose a call or live surface; live peer communications are not active in the current release. You can deny or revoke permissions in Android settings, but features that need them will not work.

6. Retention and deletion

We keep account, profile, match and message data while an account is active. We delete or anonymize it after a verified deletion request, generally within 30 days, except for limited records we must retain for fraud prevention, safety investigations, payment disputes or legal obligations. Primary photos are replaced when you change them. Certain limited safety event records are scheduled to expire after 30 days. Backups may take longer to age out.

See Delete your VeriDates account for the in-app and web deletion paths.

7. Security

We use encrypted network connections, authentication controls, restricted backend access and short-lived media links. No system can guarantee absolute security.

8. Your choices and rights

• Update information you can edit in the app and control Android permissions in device settings.
• Block or report users in the app.
• Request access, correction or deletion by emailing contact@veridatesapp.com. Rights may vary by where you live.

9. Children

VeriDates is not for anyone under 18. If you believe a minor is using the Service, contact us immediately. Read our Child Safety Standards.

10. Changes and contact

We will post material updates here with a revised effective date. Privacy questions or requests: contact@veridatesapp.com.

Legal home · Terms of Service · Refund Policy · Delete account