BaeMax Love keeps the primary readable record on the phone. When a user chooses partner sharing, selected updates are encrypted before leaving the sending phone. Some features, such as notifications, maps, beta email, and delivery metadata, work differently and are called out here.
| Area | What it contains | Where it goes | Control or limit |
|---|---|---|---|
| Local app record | Check-ins, period logs, symptoms, mood, tasks, notes, settings, reminders. | Readable on the user's phone. | Clear local data from the app. Export supported app state where available. |
| Partner sync | Only categories the tracker chose to share. | Encrypted before leaving the sending phone, then delivered to the paired partner. | Change sharing categories or unpair to stop future partner updates. |
| Notification text | Push alerts for partner updates, reminders, beta email flows, and related events. | Through the push provider path described in the privacy policy. | Use discreet wording, quiet hours, or disable notifications. |
| Maps and location | Location only when the user intentionally shares a location check-in or live session. | Map and location provider paths apply when those features are used. | Choose no location, stop live location, or revoke OS permission. |
| Beta email | Email address, confirmation state, cancellation-token hashes, and request metadata. | Signup and email providers described in the privacy policy. | Use the cancellation link or email support for removal. |
| Operational metadata | Server request metadata needed for delivery, abuse prevention, and service operation. | Service logs and providers as described in the privacy policy. | Kept separate from the readable local app record. |