Privacy claims
Plain claims, proof, and limits.
Use this page to quote BaeMax Love privacy statements without stretching them past what the product and policy support.
| Claim | Public wording | Evidence | Limit |
|---|---|---|---|
| Local primary record | Primary readable records live on the phone. | Privacy policy, privacy architecture, product facts JSON. | Partner sync, notifications, maps, beta email, and operational metadata have separate paths. |
| Encrypted partner sharing | Chosen partner updates are encrypted before leaving the sending phone. | Privacy policy and privacy architecture. | Do not describe every provider path as encrypted local storage. |
| No ads | BaeMax Love states that it does not run ads. | Privacy policy and product facts JSON. | Future monetization must be reviewed before store copy changes. |
| No sale of personal data | BaeMax Love states that it does not sell personal data. | Privacy policy and product facts JSON. | Do not turn this into a broad anonymous or zero-risk claim. |
| No contacts upload | BaeMax Love does not request contacts or upload an address book. | Privacy policy and product facts JSON. | Pairing uses explicit links, QR codes, or codes instead. |
| No chat analysis | BaeMax Love does not analyze chat screenshots, text threads, or dating messages. | Facts page, FAQ, not-a-chat-analyzer page. | Optional chat is experimental and off by default. |
| No medical claims | BaeMax Love is not a medical device, diagnosis tool, contraceptive method, emergency monitor, or crisis service. | Terms, FAQ, facts page. | Cycle predictions are estimates with ranges and confidence labels. |
| AI processing boundary | Sensitive cycle and supporter summaries are generated by product logic, not sent to a third-party generative model. | Product source of truth and facts pages. | Do not market BaeMax Love as AI-powered. |
Owner: BaeMax Love. Last updated July 9, 2026.