Pre-launch draft · August 13, 2026
Privacy Policy
This draft explains the data boundaries built into LOVEME. The legal operator, registered address, privacy contact, applicable jurisdictions, and final retention periods must be confirmed before public launch.
1. Data we process
- the name you choose to enter during the quiz;
- relationship context, need ratings, selected themes, and your partner guess;
- an optional private description of a relationship situation;
- calculated results, Flower Score, and structural conversation progress;
- payer email, payment status, private access identifiers, cookies, and operational logs;
- limited page and funnel milestones when Google Analytics is enabled.
LOVEME does not use your microphone and does not record the couple's spoken conversation. What partners say during the guided conversation is not sent to LOVEME.
2. Why we process it
We use this data to provide paid access, calculate personal results, show the permitted shared view, save structural progress, process payments, secure the service, support users, and understand the basic product funnel.
3. What your partner can see
Your partner does not receive your raw ratings, full answers, or private situation text. Once both quizzes are complete, LOVEME shows only the limited shared result designed for the couple. Access and invitation links are private bearer links—share them only with the intended partner.
4. Service providers
LOVEME may use Vercel for hosting, Supabase for server-side data storage, Stripe for payment processing, and Google Analytics for privacy-limited measurement. Card details are entered on Stripe's hosted checkout and are not stored by LOVEME.
5. Cookies and analytics
A technical cookie protects post-payment access. Analytics receives page paths without query strings or private tokens. Names, quiz answers, scores, selected needs, relationship text, and spoken content are excluded from analytics.
6. Retention, security, and your choices
LOVEME uses high-entropy private links, hashed access tokens, server-only database access, and verified payment webhooks. Final retention periods and the verified process for access, correction, deletion, and privacy requests will be published with the confirmed operator and privacy contact before launch.