Plain-language draft
Privacy
Last updated 25 October 2026
Dry is being built to keep cycle records and optional journal entries on your iPhone, whether cycle tracking is enabled or you use the journal on its own. The current development build has no account, advertising, analytics, or external data service.
Information Dry stores
If you choose to enter it, Dry stores profile labels, period dates, cycle preferences, optional fertility observations, private journal entries, links between entries and profiles, and app settings. A profile can represent you or another adult. Its label is optional and does not need to be a real name.
A Moment, Tried, or Note entry may be linked to more than one profile or left unassigned. Fertility observations are stored as records you entered; Dry does not treat them as proof or a prediction of fertility. The separate experimental-insights noticeexplains potential inputs, provenance, confidence, and missing-data behavior.
Where records live
Records are stored in the app’s protected local container. Dry’s record store is excluded from device backup and is not configured for CloudKit or another server.
You can create a password-encrypted backup and choose where to save it. Dry does not store or recover that password, and it does not upload the backup automatically.
Permissions and app lock
Dry does not request Contacts, Health, location, camera, or microphone access in the current development build. A future experimental build may request narrowly scoped HealthKit permission to read BBT only after a separate explanation and choice. If you enable App Lock, you can use Face ID, Touch ID, or the device passcode through iOS, or set a separate six-digit app passcode stored device-only in Keychain. Dry does not receive biometric data.
Deletion
“Delete all Dry data” removes profiles, period records, journal entries, and local preferences from the installation. Removing the app also removes its local container.
Website
This informational website does not offer an account or accept cycle or journal records. The production deployment must be checked for ordinary infrastructure logs and reflected in the final policy before launch.
Before public release
This page describes the current development build and is not final legal advice. The operator identity, support contact, and final policy will be published and reviewed before Dry is offered publicly.