Privacy, in plain language.

Updated 22 September 2026. This is the privacy notice for the My Midlife Story app for iPhone and iPad, and for this website. The operator is James Gray, acting personally. It is written in plain language by the operator and is not a substitute for independent legal advice.

This website

There is no account, waitlist, health-data form, advertising pixel or analytics SDK in this website’s source. The blank worksheets can be printed; they do not ask you to submit anything. No health content is put in URLs or sent by a form.

Rork hosts this website. Delivering a web page exposes connection information such as your IP address, requested address, time and browser details to hosting infrastructure. Hosting-level logging, retention and cookies have not been fully audited; access controls also require review. We do not claim that visiting creates no server logs.

An inspection of the delivered site also found hosting-injected diagnostic code that opens a console-log connection to the host. In an embedded editor preview, additional tools can report runtime errors and selected page elements to the preview editor. These are separate from the app’s local record store. Their retention and operational settings still require confirmation; do not enter private health information into this public site or its developer console.

The app

The app’s personal records, questions, user-entered treatment details and preferences are stored on-device. No account, advertising or automatic remote health-record storage is implemented. On-device photo text recognition is optional. App lock and device file protection are available; they are not an absolute security guarantee.

No watch transfer in this version

Version 1.0.0 has no paired watch companion. The app opens no WatchConnectivity session and sends nothing to a watch. If an optional companion is added in a later update, it will be off until you authorize it, will transfer only the shortcut labels and explicitly selected treatment occurrences you choose, and will be described in this notice before it can receive anything.

Exports and recovery

You deliberately choose whether to create a PDF, readable export or encrypted backup. PDF and readable export files are not password-protected. A destination such as a cloud folder or email provider controls its own copy. Support has no copy of your local archive passphrase. Deleting app data cannot erase exported copies.

Support email

If you email simpletonfacts@gmail.com, your email provider and the receiving email provider handle the message and its delivery details. Send only the minimum needed for help. The app does not automatically attach your records. You may contact the same address about a support message you have sent.

Optional Apple Health and widget

The app can request read-only sleep access when you choose it. Sleep intervals are held in memory for the current view, not copied to a server, Story records or exports. No data available is not treated as proof you denied access. A neutral widget opens the app to its unlock gate; it displays no health records and does not save in the background.

Subscription billing

Apple processes App Store checkout. The app uses RevenueCat for subscriptions and access verification, with a generated pseudonymous billing identifier rather than a required app account. RevenueCat receives purchase and entitlement history and technical connection/device information needed for billing. Health records, HealthKit samples, notes, treatments, visit content, exports, source identifiers and private task selections are not passed to billing. Optional SDK diagnostics and automatic attribution identifier collection are disabled; no advertising identifier or subscriber attribute is supplied by the app.

Deleting local health data does not cancel an Apple subscription or erase records held by Apple or RevenueCat. Manage Apple subscriptions separately. Contact the support address for billing privacy requests without attaching health records. The owner has confirmed that no optional RevenueCat integrations are enabled. App Store privacy disclosures are published for linked billing identifiers and purchase history used for app functionality. RevenueCat’s retention and security practices are described in RevenueCat’s privacy notice; we do not claim that billing creates no server records.

Changes and contact

Any future paid services, Health connections or companion integrations will receive their own disclosures before release; no such feature is silently enabled. The operator is James Gray, acting personally. Public contact is the support address above. You can ask for access to, correction of or deletion of billing-related records held about you by writing to that address; local health records are already under your control in the app.