Privacy at Lovelai

Lovelai is open in approved launch markets. We collect the minimum data needed to run launch signup, verify identity, protect members from fraud, and operate chat-first AI dating for cross-cultural love.

What we collect

Launch signup data can include email, locale, relationship intent, referral and UTM source, LINE opt-in, and consent version. Member data can include profile details, prompt answers, ritual responses, profile-card feedback, relationship signals, verification state, messages, translations, reports, and safety-review metadata.

Lovelai AI processing

Lovelai features can process profile context, prompt answers, ritual responses, photo vibe feedback, bio pull feedback, interest choices, message text, and safety signals to create chat-first profile cards, AI Love Briefs, Lovelai Concierge matchmaking chat replies, daily romantic scenario mini-games and rituals, Culture Bridge notes, Guided Intro suggestions, Bridge Translation with nuance, and Scam-Shield warnings. These AI features are opt-in and should wait for Lovelai consent before profile or message analysis.

Third-party AI providers

Lovelai sends limited, delimited request data to server-side AI providers for these Lovelai features. Private chats are not used for global model training in v1. The product uses personal learning only, and Lovelai memory can be deleted without deleting the account, chats, reports, or verification state.

Verification data

Full identity and biometric checks are used for messaging unlock only when the verification provider path is configured. The trust layer is eKYC-backed where provider proof is retained, and the Japan flow is JPKI-ready while the live provider endpoint remains a launch proof gate. Raw verification artifacts should be stored separately from profile data with stricter access controls and retention.

UGC safety data

Reports, blocks, moderation appeals, and support contact requests are treated as user-generated safety records. They are used to review profiles, messages, scam pressure, impersonation, harassment, privacy concerns, and account restrictions.

Locale coverage

Localized privacy and consent copy must be reviewed before unsupported locales are made routable or indexable.