EpiTrailPrivacy Policy
EpiTrail works without an account, advertising, analytics, or tracking. The journal remains in a protected app directory on the device and is excluded from iCloud Backup. Backups are encrypted on the device and leave the app only when the user chooses. Desima does not receive them.
Data stored by the app
Episode entries and notes are stored locally in a protected EpiTrail directory. iOS applies complete file protection while the device is locked, and the journal directory is excluded from iCloud Backup. EpiTrail does not use CloudKit or operate a health-data server.
No collection or tracking
EpiTrail 1.0.1 does not send personal or health data to Desima, an analytics partner, or an advertiser. It contains no user accounts, advertising, analytics, or tracking tools.
Widget
The EpiTrail widget is a shortcut that opens the new-episode form. It has no access to the journal and does not display health information.
Export
Journal and statistics reports in CSV or PDF format are created temporarily only when you choose Export, using the app's current language. The previous temporary export is replaced. You decide where a copy is sent or saved using Apple's system share sheet.
Encrypted backups and Apple Shortcuts
A complete journal backup is encrypted on the device with an 8-digit PIN before it is shared. The PIN itself is not stored; a key derived from it remains in this device's protected Keychain so later backups can run. The file can be restored on another iPhone or iPad using the same PIN. EpiTrail does not upload backups or access email. If you configure an Apple Shortcuts automation, Shortcuts and your chosen email provider control the schedule, email account, recipient, and delivery.
Data deletion
You can delete individual entries or the entire local journal in EpiTrail. Delete All Episodes removes the local journal and temporary files. Removing the app deletes its local data; CSV or PDF reports and encrypted backups previously saved outside the app remain wherever you chose to store them.
Effective date
This policy is effective July 16, 2026.