Data Safety and Permissions
This document explains AI72 / IntroMe data categories, device permissions, why data is used, and how the disclosure aligns with store data safety review. Final Google Play Data Safety or Apple privacy answers must be generated separately from the current build, SDKs, permissions, and product flows.
1. Purpose and product context
AI72 is not a public browsing or swipe catalog. It is a social/dating introduction platform with controlled introduction, temporary intro, permanent chat, profile media, voice, video where available, translation, transcription, TTS, verification/liveness/profile consistency, moderation/reporting, notifications, and account deletion. This document does not replace the Privacy Policy.
2. Data safety summary
AI72 may process phone/auth data for accounts; profile and preference data for controlled introductions; camera/microphone data for verification, media, voice/video, and chat; country/city/location, language, timezone, and device signals for localization, preferences, safety, and introduction eligibility; message, media, voice, translation, transcript, and TTS data for communication, delivery, report/moderation, and support; and push tokens and notification settings for notifications. Account deletion is available, but some records may be retained under safety/legal exceptions.
3. Data categories
Categories include account/auth data, legal consent records, profile data, profile photos/media, verification/liveness/profile consistency data, temporary intro and permanent chat messages, voice/audio/transcription/TTS data, media and Shared Media data, selected country/city or device location where granted, device/notification data, reports/blocks/moderation data, diagnostics/log/security data, 7-day free access eligibility, subscription status, entitlement state, weekly/monthly plan type, and platform transaction/receipt metadata.
4. Account, 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.
5. Photos, media, and verification data
Primary profile photo, cropped/verified photo, blurred derivative where used, profile media, and media moderation state may be processed for profile display, controlled reveal, 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.
6. Messages, voice, media, and Shared Media
Temporary intro messages, permanent chat messages, timestamps, delivery/read metadata, reactions, delete/report/block metadata, voice messages, audio files, transcripts, translated text, TTS output metadata, sent/received images/videos, thumbnails/previews, media metadata, and Shared Media references may be processed for communication, delivery, display, translation/transcription/TTS, report/block/moderation, safety, and support. Shared Media does not grant download or redistribution rights.
7. Location, device, notification, and analytics data
Selected country/city, approximate location if permission is granted, region/preference data, location consistency signals, timezone, and locale may be used for localization, preferences, safety, and introduction constraints. Push token, install ID, device model, OS, app version, notification settings, preview settings, and notification action metadata may be processed for push delivery, device state, debugging, analytics, and security. Firebase Analytics may log app open, login, startup, lifecycle, screen, and event data.
8. Reports, moderation, diagnostics, and future payments/subscriptions
Profile/message/media reports, block/unblock records, moderation decisions, appeal/support records, abuse/fraud/safety records, crash/callable/backend/debug/security/admin/audit logs may be processed for platform safety, evidence, enforcement, support, analytics, and legal compliance. 7-day app-level free access, subscription status, entitlement state, weekly/monthly plan type, Apple/Google transaction metadata, and refund/cancellation status may be processed for post-paywall subscription access, billing, tax, refund, fraud, and support workflows.
9. Data sharing
Data may be shown to other users only in product-permitted contexts: temporary intro, permanent chat, visible profile fields, Shared Media where allowed, and report/support situations where necessary. Service providers may include Firebase/Google Cloud, Google Maps/geocoding where used, OpenAI or AI providers, moderation/safety providers, speech/transcription/TTS/translation providers, analytics/log providers, Apple/Google platform services, future payment providers, and support/legal providers. Valid legal requests, child safety, threats, fraud, abuse, or legal compliance may require disclosure to authorities.
10. Camera permission
Camera may be requested for liveness/profile consistency, primary profile photo capture, profile media capture, permanent chat/video/media where available, and video call where available. It is used when the user starts verification, photo/media capture, or camera/video features. It is not for secret background recording. Camera/face data may be sensitive or biometric in some jurisdictions.
11. Microphone permission
Microphone may be requested for voice messages, video call where available, live verification spoken prompts if used, and audio/transcription/TTS features. It is used when the user records voice or starts supported audio/video features. It is not for secret background recording. Transcription, translation, and TTS may be inaccurate.
12. Photos, 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. AI72 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.
13. Location permission
Location may be requested for country/city/nearby preference, localization, safety/profile consistency signals, and location sharing where available. It is used if the user grants permission or starts a current-location feature. Location is not official location verification and does not guarantee where a user is. City localization may be limited.
14. Notifications and contacts permissions
Notification permission is used for push notifications, permanent chat/intro/account/safety/system updates, and notification actions. Delivery, timing, and preview behavior are not guaranteed. Contacts permission is used only if the user starts the contacts/blocking flow to block people they do not want to meet; it should not be described as public discovery.
15. Network, audio settings, and tracking note
Internet/network/audio settings permissions may support cloud-backed app features, WebRTC/audio routing, notifications, media, and chat. Reviewed app manifests did not show an explicit advertising ID/app tracking permission; the merged manifest and active SDK list must be checked again before store submission. Bluetooth or background location should not be described as active unless enabled later.
16. AI and automated processing data safety
AI/automation may support liveness/profile consistency, primary photo consistency, media moderation, translation, transcription, TTS, profile text assistance, product-rule introductions, safety/report/moderation support, and admin/human review support. Home AI chat, 72-hour relationship analysis, relationship summary, memory extraction, AI candidate ranking/scoring, or all-chat AI moderation should not be described as active user-facing features.
17. Security measures and encryption
AI72 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. AI72 does not claim end-to-end encryption for chat/media and does not guarantee absolute security.
18. User controls, deletion, and retention
Users may control profile editing, language/country/city preferences, notification preview/settings, OS permissions, pass/leave/reject/block/report, delete for me/delete for everyone where available, account deletion, support/privacy requests, and appeal where applicable. Some data may be deleted, disabled, or anonymized; some records may be retained for safety, legal, moderation, abuse prevention, audit, dispute, backup, or compliance reasons. App uninstall is not account deletion.
19. Store disclosure alignment
Final Google Play / Apple privacy disclosures may need to evaluate phone number, user content, photos/videos/audio, profile content, reports/support messages, age/declared gender, verification/camera data depending on jurisdiction, selected country/city/device location where used, Firebase/Auth UID, install ID, push token, SDK identifiers, usage data, diagnostics, and purchases/subscriptions such as free access eligibility, subscription status, entitlement, plan type, and platform transaction metadata. This list is not the final store form; final answers must match the current build, active SDKs, merged Android manifest, iOS privacy manifests/Info.plist, backend providers, product flags, payment status, billing implementation, and current data flows.
20. What AI72 does not guarantee
AI72 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.
21. Linked documents
This document should be read with the Privacy Policy, Terms of Service, Account and Data Deletion, Community Guidelines, Safety Center, AI and Automated Processing Disclosure, Moderation and Reporting Policy, Notifications and Chat Actions, and Support documents.