Default wording matters
BaeMax's privacy policy gives one documented example for new installs: 'Open BaeMax for your update.' Existing beta users are told to check Settings, Notifications, then Hide notification details.
- Documented hidden-detail example: Open BaeMax for your update
- Detail hiding is the documented new-install default
- Turning detail hiding off may expose partner names or event types
- Android lock-screen privacy settings still apply
The trade-off
Hidden detail protects privacy by removing specific context from push text. Turning it off can make an alert easier to identify, but the privacy policy says partner names, event types, or message hints may then appear.
- Use discreet wording around shared spaces
- Use detailed wording only if the extra clarity is worth it
- Keep Android lock-screen preview settings aligned with the choice
- Mute alerts or use quiet hours when no reminder should appear
Control noise
Privacy is not only about wording. BaeMax's privacy and architecture pages document mute, detail, quiet-hour, and disable controls, but the installed settings should be checked for their current category scope.
- Mute alerts when needed
- Use quiet hours
- Keep personal scheduled reminders local
- Choose which notifications are worth having
What this does not solve
Hidden previews reduce casual exposure. They do not make a shared phone private or remove the need for Android notification settings.
- Someone with device access may still see app contents
- System notification settings still matter
- No lock-screen setup is risk-free
- Use app lock for another layer
Test every notification surface
Create a harmless local reminder and a harmless partner update, then inspect each while the phone is locked and unlocked. Check banners, grouped alerts, notification history, and any watch, vehicle display, or other device to which Android forwards notifications. A generic lock-screen line can still appear differently elsewhere. Review Android notification channels as well as the in-app detail setting, because the operating system makes the final display decision. Clear the tests and repeat after an app or Android update. If the app name itself would reveal too much, disable or mute that alert path rather than relying on wording alone.
- Use invented test content rather than a real health entry
- Inspect locked, unlocked, grouped, and historical alerts
- Check connected displays only if the phone forwards alerts to them
- Mute a category when even a discreet preview is too revealing
Separate local reminders from partner-delivered alerts
A reminder generated on the phone and a push notification sent because a partner shared something can travel through different systems. Test both. Local reminders may stay on the device, while push providers necessarily process delivery metadata and may process the notification text described in the privacy notice. Use generic wording for any alert that crosses a provider path. For details that should not appear outside the app, let the notification say only that an update is waiting and require the app lock before reading it.
- Check which categories can be disabled independently.
- Avoid putting cycle dates, symptom names, or relationship conflict in notification text.
- Review notification history after dismissing an alert.
- Use direct emergency communication rather than depending on a muted or delayed push.