Let's Love

Let's Love

by JAMSAQ STUDIO

Policy center

Data Safety Summary

Public data-safety overview

This page summarizes how Let's Love handles data so the public policy and Play Console Data safety form stay aligned.

Last updated May 18, 2026

Important actions

DS

Data controls

Review privacy details, request deletion, or contact support.

Policy library

Selected policy

DS
May 18, 2026

Data Safety Summary

A public summary aligned with Play Console data safety disclosures.

1

Data Types Collected

Personal info

Name, email address, profile photo, user ID, birthday, anniversary, and profile message. Used for account, profile, pairing, and personalization features.

Messages, photos, audio, and user content

Messages, memories, captions, comments, reactions, goals, todos, date ideas, quotes, audio messages, and uploaded media. Used to provide shared couple features.

Location

Precise or approximate location may be collected only when permission is granted for partner distance features.

App activity and diagnostics

Feature activity, notification tokens, crash logs, performance data, and app/device diagnostics. Used for notifications, reliability, security, and troubleshooting.

Purchase information

If subscriptions are enabled, purchase and subscription status may be processed through Google Play Billing and RevenueCat to unlock paid features.

2

Purposes

  • App functionality, account management, authentication, pairing, chat, memories, and shared couple features.
  • Notifications and reminders requested by the user or triggered by couple activity.
  • Analytics, crash diagnostics, performance monitoring, security, fraud prevention, and abuse prevention.
  • Optional location, camera, microphone, media, and app lock features based on user permission choices.
3

Sharing

  • Shared couple content is visible to the paired partner as part of the app experience.
  • Firebase and Google Cloud process data for authentication, database, storage, push messaging, cloud functions, crash reporting, and performance monitoring.
  • RevenueCat and Google Play may process subscription data if paid features are enabled.
  • Information may be disclosed when required by law, for user safety, or to investigate abuse or security incidents.
4

Security Practices

  • Data is encrypted in transit using HTTPS/TLS.
  • Firebase Authentication, Firestore rules, Storage rules, and server-side checks protect user and couple data.
  • Users can request account and associated data deletion.
  • Biometric data stays with the device operating system and is not sent to Let's Love servers.

Play Console Reminder

The Play Console Data safety form must match the real production app, SDKs, backend behavior, and privacy policy at submission time.