Last updated: July 5, 2026

Privacy Policy

This policy explains data processed inside AI72 / IntroMe. AI72 / IntroMe is a controlled introduction, temporary introduction, permanent chat, messaging, media, voice, video, and AI-assisted social/dating introduction platform. It is not a public profile browsing service or swipe catalog.

1. Age and eligibility data

AI72 is only for users who are at least 18. Age, birthdate, age range, eligibility declarations, account history, and safety signals may be processed for age gating, safety review, preference limits, and introduction constraints.

• Suspected underage use may lead to review, restriction, suspension, closure, or preservation of safety records.
• These checks do not provide legal identity verification or a guaranteed age/identity outcome.

2. Account and authentication data

AI72 may process account data for account creation, sessions, security, support, and legal records.

• Firebase/Auth UID, phone number, auth provider, auth state, account creation date, login/session state, and account status.
• Push tokens, device tokens, app install/device/session identifiers, and limited device records.
• Legal consent records, accepted policy version, consent timestamp, account deletion requests, support, appeal, and recovery records.

3. Profile data

AI72 may process name, display name, preferred name, declared gender, age or birthdate, language preference, country, city, region, approximate location signals, about/bio, interests, prompts, profile photos, profile media, verified primary profile photo state, and visible profile snapshot fields.

• Introduction preferences may include age range, country/city priority, region choices, gender preference, availability, and waiting-room choices.
• Except for user-provided names, some profile labels may be displayed in the viewer language.
• Country and language labels may be localized; city localization may be limited.

3A. Beta waitlist and contact data

The beta waitlist form on the AI72 public website may collect full name, email, device preference, country, city, preferred language, declared gender, optional Instagram/WhatsApp information, a short application note, 18+ confirmation, Privacy Policy consent, and beta contact consent. This form does not create an AI72 account and does not replace mobile app registration.

Beta waitlist data may be processed to plan beta invitations, build a balanced test cohort, contact applicants with beta and product updates, reduce duplicate submissions and abuse, evaluate trusted tester candidates, and manage future beta invitation workflows. Declared gender is not a verification claim; it is used only to plan the beta pool and testing experience.

4. Location, country, and city data

Users may select country, city, or region preferences. If permission is granted or a feature uses location signals, AI72 may process approximate location, country/city signals, timezone, coarse location, and location-consistency signals. Location data does not guarantee precise location, identity, or safety. Permissions can be changed in device settings.

5. Verification, liveness, and profile consistency

AI72 may process live camera capture, verification video, verification frames, liveness challenge, real-camera, anti-replay, screen-replay risk signals, face-continuity, audio/video sync, selfie/profile photo consistency, declared name/gender/city consistency, verification metadata, verification result, and primary profile photo moderation/verification result.

• These checks are for risk reduction, profile consistency, liveness, anti-abuse, and safety signals.
• They are not official identity verification, KYC, guaranteed age/gender/location verification, or a guarantee that a user is safe.
• In some jurisdictions, face geometry or face data may be biometric or sensitive data and may be handled under applicable law, consent, and jurisdiction-specific retention/transfer rules.

6. Messages, chats, voice, video, and media

AI72 may process temporary introduction messages, permanent chat messages, sent/received photos, videos, audio, voice messages, video call metadata, timestamps, delivery/read metadata, media metadata, storage paths, moderation status, Shared Media index metadata, hidden/deleted/expired states, quarantined media states, and restricted media access records.

• Messages and media may be processed for delivery, display, translation, transcription, TTS, moderation, reports, safety, debugging, legal compliance, abuse prevention, product quality, and support.
• Video call filters or visual effects are separate from verification/profile capture pipelines.

7. Translation, transcription, and TTS

AI72 may process original text, translated text, detected language, selected display language, voice-message audio, transcripts, TTS request/output metadata, and original/translation toggle state. These features may use AI, speech, translation, cloud, or safety providers. AI outputs, translations, transcripts, and TTS may be inaccurate.

8. AI and automated processing

AI72 may use AI and automated systems to support liveness, real-camera checks, profile consistency, primary profile photo consistency, profile photo/media moderation, translation, transcription, TTS, profile text assistance, safety/risk signals, report review, moderation support, product quality, and support.

• AI72 introduces users through controlled product flows and product rules.
• AI does not guarantee compatibility, safety, identity, gender, location, intention, or relationship outcome.
• Serious enforcement may involve human review where required or appropriate.

9. Reports, blocks, moderation, and safety

AI72 may process profile reports, message reports, media reports, blocks, unblocks, moderation decisions, media quarantine/disable/remove states, safety review queue records, appeal/support communications, abuse-prevention records, fake-report detection, ban-evasion, and legal request records. The reporting user identity is generally not shared with the reported user.

10. Notification and chat action data

AI72 may process push tokens, device records, notification preview settings, message preview settings, notification delivery metadata, notification actions, chat action metadata, and privacy-first notification preferences.

11. Payment and subscriptions

AI72 may process 7-day app-level free access start/end timestamps, free access eligibility, subscription eligibility based on declared gender or account type, subscription status, entitlement state, weekly/monthly plan type, App Store / Google Play transaction identifiers, receipt metadata, renewal/cancellation/refund/status metadata, fraud/dispute/support records, and tax/accounting records. The first 7 days are not an Apple or Google subscription free trial; no card is required and no subscription starts at sign-up. Full card data is generally handled by Apple or Google and may not be directly visible to AI72.

12. Device, usage, diagnostics, and security

AI72 may process app version, platform, OS version, device model, device category, locale, language, timezone, country, crash logs, callable errors, Firebase/GCP logs, analytics events, performance diagnostics, debug/test events, non-public internal development test-profile markers, abuse/fraud/security telemetry, network state, and support diagnostics.

13. Purposes of processing

AI72 may process personal data for the following purposes.

• Account creation, authentication, login, account recovery, and session continuity.
• Eligibility, age gate, liveness, profile consistency, safety checks, fraud/replay/bot/ban-evasion prevention.
• Controlled introductions, temporary intro, permanent chat, media delivery, Shared Media, message delivery, and voice/video features.
• Translation, transcription, TTS, profile text assistance, product-rule introductions, and localization.
• Moderation, reporting, blocking, safety review, appeals, support, notifications, debugging, security, legal compliance, deletion, and product analytics.

14. Legal bases and regional rights

Legal bases may include performance of contract, legitimate interests, user consent where required, legal obligations, vital interests or safety, and explicit consent for sensitive/special category data where required. KVKK, GDPR, UK GDPR, US state privacy, and LGPD addenda may be handled under applicable law and regional processes.

15. Sharing, recipients, and providers

AI72 shows data to other users only in product-permitted contexts: temporary intro, permanent chat, visible profile fields, Shared Media, profile view, safety/report/support workflows.

• Firebase/Google Cloud, Google Maps/geocoding where used, OpenAI or related AI providers, translation/speech/TTS, moderation/safety, analytics/crash/log providers, and Apple/Google app-store/payment/push/platform-integrity providers may be used.
• Disclosure to legal authorities may occur only for legal process, safety, emergency, or rights protection.
• User content is not used for advertising or marketing without separate permission.

16. International transfers

AI72 may use global cloud, AI, analytics, support, moderation, and app-store providers. Data may be processed outside the user country. TR/KVKK, GDPR, UK GDPR, LGPD, and other transfer rules may require notices, safeguards, contracts, SCCs, transfer impact assessments, or explicit consent.

17. Data retention

Retention depends on data type, product state, legal obligations, safety needs, account status, and jurisdiction.

• Account/profile data is retained while the account is active plus any required legal/security period.
• Legal consent records may be retained for at least 5 years or the legally required period.
• Temporary intro data is short-lived operational data; metadata may be retained for safety/debug/legal/abuse-prevention.
• Permanent chats remain while the account/chat exists unless deleted, restricted, or subject to safety/legal retention.
• Beta waitlist data may be retained for the beta program, invitation planning, and a reasonable follow-up period; it may be removed on a valid deletion or privacy request subject to applicable exceptions.
• Reported content, ban/abuse records, and moderation history may be retained longer.
• Verification media may be retained for safety/review/compliance, debugging, dispute, or moderation reasons unless deleted under an applicable product, legal, or retention policy.

18. Account deletion and user rights

Users may start deletion in-app or through support. Depending on applicable law, users may have access, correction, deletion, portability, objection, restriction, consent withdrawal, automated processing challenge, or human review rights. Deletion may not immediately remove security records, reports, legal compliance records, transaction/tax records, abuse-prevention records, appeals, moderation history, or backup copies.

19. User controls

AI72 may provide controls for profile editing, privacy settings, notification previews, block/report, language/localization, location permissions, account deletion, consent withdrawal where applicable, and future Shared Media visibility controls.

20. Children and minors

AI72 is not for users under 18. Suspected underage use or content may lead to restriction, suspension, closure, preservation, review, or reporting where appropriate.

21. Security

AI72 uses reasonable technical and organizational safeguards. No system is perfectly secure. Users should protect their devices, phone numbers, accounts, verification codes, and personal information.

22. Public and other-user visibility

AI72 does not provide open public profile browsing. Data may be shown only in controlled contexts such as temporary intro, permanent chat, profile view, Shared Media, safety/report/support, and legal compliance. Some content may be blurred, limited, signed-URL gated, hidden, disabled, expired, or quarantined.

23. No absolute prevention of external recording

AI72 may restrict in-app saving, downloading, gallery export, and sharing paths. It cannot fully prevent screenshots, screen recording, another-device recording, or misuse by another user. Users should avoid sharing sensitive content.

24. Changes

AI72 should use a stable canonical route, effective date, version records, and consent gate or notice where material changes require it. Registry and hash updates will be handled in a later legal registry/version phase.

25. Linked documents

This policy should be read with the Terms of Service, Community Guidelines, Safety Center, AI and Automated Processing Disclosure, Moderation and Reporting Policy, Account and Data Deletion, Notifications and Chat Actions, and Data Safety and Permissions.