Last updated: 2026-11-04
MenoLog is a private journal for tracking menopause and perimenopause symptoms. Journal processing takes place on your device without a developer-operated health-record upload service. This policy also describes Apple services, device backups, and the exports or support messages you choose to send.
No developer-operated journal upload. MenoLog has no journal account system or behavioral analytics. Apple purchases, user-directed exports, website requests and support email are separate as described below.
When you use MenoLog, the following is stored in its local app container:
Journal records use Apple SwiftData. Preferences, Health access-request status, a cached Pro entitlement, and review-request history use local UserDefaults separately. MenoLog does not upload these to developer-operated servers. App data may be included in Apple device backups according to your system settings; that is Apple's backup system, not ours.
Medication and weekly-review form drafts and the optional PDF patient name remain in view memory until saved or used for an export; they are not restart-restorable drafts. Onboarding symptom choices are saved when Finish succeeds. Enabling a reminder during onboarding can already save its preference and schedule a notification before Finish; abandoning onboarding does not necessarily undo that setting. The reminder's general prompt can appear on the lock screen according to system settings. MenoLog does not include your journal notes or treatment names in that reminder.
The upcoming health-permission update requests read-only access only to sleep analysis and step count, the types used by the treatment-change context. Results are queried locally and summarized into daily totals and before/after averages. The update merges overlapping asleep intervals so the same time is counted once, excludes awake and in-bed-only samples, and clips intervals to the requested period. Sleep is grouped by the end of each merged interval in the device's current time zone; an end before 4 a.m. belongs to the preceding calendar day. This summary can differ from Apple Health's display and is context, not medical advice or proof of treatment effect. MenoLog never writes to HealthKit or uploads these results to a developer-operated service.
Earlier installed versions may also request active energy permission, although the current treatment-change display does not query that type. Earlier sleep summaries may add overlapping samples more than once. Installing the update does not revoke permissions already granted: review or turn off individual types in Apple Health under your profile, Privacy, Apps, MenoLog. Apple does not disclose to MenoLog which individual read permissions you allowed; missing results can mean no accessible samples or denied access.
The updated MenoLog purchase page offers an Annual Pro subscription and a Lifetime one-time purchase through Apple's StoreKit. Previously purchased Monthly subscriptions remain recognized while entitled and can be restored. Apple handles billing, subscription management and purchase restoration. We do not receive your payment information or Apple ID; the app processes verified transactions and caches entitlement status locally to unlock Pro. Restore Purchases restores access, not journal data.
MenoLog does not use any third-party SDKs except Apple's StoreKit for in-app purchases and Apple's HealthKit for the optional health integration. We do not integrate with analytics platforms, advertising networks, or crash reporting services.
MenoLog provides an Appointment Pack (PDF) and CSV exports. They are generated on your device and are only shared when you explicitly use iOS's share sheet to send them somewhere (email, message, AirDrop, etc.). You decide where they go and who sees them.
The updated Appointment Pack includes all recorded treatment changes in the selected date range, all medications on record (including stopped medications), the latest weekly reflection in range, summary statistics, top symptoms and triggers, and a response summary for the latest qualifying change. That comparison can use logged days around the change outside the selected range. The PDF is a summary, not every daily note or every reflection. An optional patient name is included if you enter it. Earlier versions limited the displayed treatment changes and medications.
Daily-log CSV contains dated mood, period status, triggers, symptom names/severity and notes. Treatment Journey CSV contains treatment-event details and weekly-review scores, adherence, concerns and questions. These are readable reference files, not encrypted backup archives, and have no matching import feature. Generated files are written to the app's temporary directory before sharing. They are not immediately erased when the share sheet closes; iOS may reclaim temporary files later. Copies you save or send are managed separately.
MenoLog is intended for adults managing their own menopause or perimenopause experience. It is not directed to children under 13 and we do not knowingly collect information from them.
MenoLog is a personal journal, not a medical device. It does not diagnose, treat, or prevent any condition, and it does not provide medical advice. Always consult a qualified healthcare provider for medical decisions.
These pages are hosted by Vercel, which receives ordinary request information such as IP address, browser information and requested URL for delivery and security; see Vercel’s Privacy Notice. If you email support, we receive the message, address and attachments you choose. We retain support correspondence as long as reasonably needed to resolve requests, keep relevant support records or meet legal obligations. You can request deletion by email. Providers may retain limited technical or backup records under their policies. Do not send unnecessary health records.
If we update this policy, the "Last updated" date above will change. Material changes will be described with the updated policy and additional notice where required.
Daily logs, symptoms, medication records, treatment-change events and weekly reviews remain locally until you change or delete supported records or remove the App. There is no automatic age-based purge or developer-held journal to retrieve. Turning off a symptom removes that entry from the current daily log after a successful save; hiding a symptom type does not delete its history. Deleting a medication checks deletion of the medication and its matching treatment events in one save; failure keeps their original records for retry. Independent daily logs and weekly reviews remain. The current App has no single control that erases every journal record, preference and independent copy, and no Recently Deleted recovery.
The upcoming health-permission update queries only sleep and step summaries from Apple Health; MenoLog does not write or delete the original Health records. Earlier versions may also request active energy permission without displaying that data. The update does not revoke earlier permissions. Revoke access or manage those records in Apple Health and system settings. Updated sleep summaries count overlapping asleep intervals once, exclude awake and in-bed-only records, and use the end of each merged interval as its local wake day (before 4 a.m. belongs to the previous calendar day). They may differ from Apple Health and must not be used as a diagnosis or treatment recommendation. Daily-log edits are automatically saved after a short delay and flushed when leaving the view; they are not a separate restart-restorable draft. A failed save is not a backup. Reminder, App Lock, onboarding and authorization-request preferences are separate from journal records.
Removing the App normally removes its local container. Offloading retains App data and is different from deleting it. CSV and Appointment Pack PDFs are readable reference exports, not complete restorable database backups; there is no corresponding archive import. Files saved or shared outside the App, recipient copies and previous device backups remain until managed separately. Recovery from Apple device backup requires a completed usable backup and successful system restoration; the developer cannot guarantee it or restore a remote journal copy.
The updated App pauses the normal record interface if its persistent database cannot be opened and only a temporary in-memory store is available. New recording and editing through that interface are blocked. The App keeps the existing database and attachment files rather than treating the temporary empty store as your archive. Database-dependent startup work in that interface is paused; previously scheduled reminders, widget snapshots or independent copies may remain.
Check available device storage, close and reopen the App, and contact support before deleting or reinstalling it. This recovery screen is not a backup, a repair guarantee or an automatic restoration of missing records. Older installed versions may behave differently until updated.
The updated App keeps the existing 500-millisecond debounced daily-log saving and attempts a flush when leaving Today. A failed write leaves the latest in-memory mood, symptoms, severity, triggers, notes and tags available for retry, shows a visible warning and offers Retry saving changes on Today. It does not roll back unrelated pending edits or count a failed write as a successful review milestone. These unsaved edits are not restart-proof drafts and can be lost when the process ends; previously stored database records remain separate. If today’s record cannot be read or created, the App shows an error and Retry opening today’s record rather than treating the failure as a new empty journal. Existing symptom-selection switches remain live, while onboarding selection is checked before completion. Medication edits and their treatment-event additions or corrections are checked together; medication deletion checks the medication and matching treatment events together. Failed writes preserve their original stored data and open form values. Independent daily symptom logs and weekly reviews remain after medication deletion. Older-medication history preparation checks reads and saves and avoids inserting a duplicate partial migration after failure. Library preparation and open forms are local; none of these checks adds a health-data upload, automatic medical recommendation, backup archive or guaranteed recovery.
Contact & Support — questions about this policy can be sent to captainlongevity@gmail.com.