Ephira is a focused local tracker
Ephira is best understood as a private menstrual calendar with customizable entries. It is useful when someone wants to track flow, symptoms, moods, birth control, medications, and personal categories without creating an account or syncing a cloud record.
- Good fit: local-only tracking is the priority.
- Good fit: open-source code matters.
- Weak fit: partner support is required.
Open source improves inspectability, not magic
Public code lets people inspect how the app is built, but it does not automatically prove every build is safe, maintained, or configured correctly. It is still worth checking updates, backups, exports, and device security.
- Inspectability is useful.
- Maintenance still matters.
- Device access still matters.
BaeMax changes the exposure
Once a partner receives context, the privacy model is no longer only about the tracker’s device. It also includes the receiving device, notifications, relationship changes, and whether access can be stopped later. If the need is “I want a private cycle record,” Ephira is the clearer fit. If the need is “I want my partner to know how to support me today,” BaeMax is the clearer fit.
- Use Ephira when solo privacy is enough.
- Use BaeMax when sharing solves a real support problem.
- Avoid sending full logs when a summary would do.
- Keep the private record minimal.
- Choose what a partner can see by category.
- Review notification privacy before sharing.
When a local-only tracker is the better fit
Ephira is most compelling when local-only tracking is the primary need. BaeMax adds a partner-support feature, which is useful only if the user wants selected sharing and care actions.
- Stay with a local-only tracker if no sharing is wanted.
- Use BaeMax when one trusted partner should get limited context.
- Check backup and export before moving history.
Build the calendar around fields you will review
Ephira supports flow, symptoms, moods, medications, birth control, notes and custom entries. That flexibility can become a long form nobody completes. Start with period dates and the two or three observations that affect care or appointments. Add a custom field only when its wording and scale will remain consistent. Ephira says predictions begin after two complete cycles and can be turned off, so early dates should be treated as a baseline rather than an immediate forecast. Review the calendar legend after a month and remove fields that have not answered a real question.
- Start with a small repeatable field set.
- Treat the first two complete cycles as setup data.
Plan export and device replacement before relying on local-only storage
Ephira says records stay in an encrypted SQLite database on the device and can be protected with biometrics or a passcode. It also lists a PDF export of the full health history. Before replacing another tracker, create test entries, export the PDF and inspect whether it contains the dates and categories you need. A readable PDF must be protected outside the app. Because there is no account or cloud record, verify the current device-to-device migration route and keep the old tracker until the new record survives a restore or replacement test.
- Inspect an export before moving history.
- Protect readable reports outside the app lock.
Use inspectability to ask better operational questions
Ephira's official page identifies a local encrypted SQLite database, optional biometric or passcode protection, customizable tracking and public MIT-licensed source code. Those are meaningful facts, but the practical decision still depends on the installed release. Confirm that the store developer matches the official project, updates are current on the intended phone and the lock behaves after restart. Review the public issue tracker for unresolved export or migration problems without assuming every report affects the current version. Then test the exact categories needed: flow, symptoms, mood, birth control, medication or custom entries. Choose Ephira when a solo, local, inspectable record is more important than account recovery or partner sharing. Choose BaeMax when selected context should reach one partner. If both are used, leave detailed medication and cycle history in Ephira and send only the temporary support request through BaeMax; two health histories create correction and deletion work without adding clarity.
- Verify the installed release and lock behavior on the actual phone.
- Keep detailed health history in one authoritative record.