Privacy policy

Your journal and on-device processing

Entries and unfinished writing stay in this installation’s local storage. Removing the app or losing the device can remove them. Export a backup you control before replacing a device. Backup and readable-copy exports contain journal text; choose carefully where you store or share them.

On supported devices, the app first attempts Apple Intelligence for reflections and weekly reviews and supported speech recognition in on-device mode. Availability depends on the device, language, settings and downloaded models. Local pattern counts do not send entries to an analysis service.

Optional online processing

Echo Chronicle asks for permission before using OpenAI. With permission, a recording needing online transcription, text needing an online reflection, or selected original entries for a requested weekly review passes through our Supabase service to OpenAI. You can turn this permission off in About & Privacy. Declining still permits writing, saving and available on-device processing. New journal entries are not uploaded for backup.

The application’s backend does not write journal text, recordings or generated reflections to its database and does not deliberately log their contents. Hosting and processing providers may retain request data and operational metadata under their own policies. We do not promise zero retention. OpenAI text requests disable stored responses; standard abuse-monitoring retention may still apply, generally up to 30 days, with documented exceptions. OpenAI states that API data is not used for training by default. See OpenAI data controls and Supabase privacy information.

Installation verification and service logs

Apple App Attest helps our service verify a genuine app installation and protect the shared online allowance. The private verification key stays on the device. Our Supabase database keeps the hashed installation key identifier, its public key, signature counter, activity times, short-lived challenges and request counts. These verification records contain no journal text or recordings.

Inactive verification registrations become eligible for cleanup after 180 days, daily installation counters after 90 days, and challenge counters after seven days. Challenges expire after two minutes. Cleanup runs when the service receives requests, so expiration does not promise immediate deletion. Global allowance totals are kept separately.

Supabase infrastructure records operational request information, including IP address, approximate geographic/network information, time, route, user-agent, status and duration. These records help operate and protect the service and follow provider retention policies. The static support site is hosted by Cloudflare and can also produce ordinary hosting logs. There is no advertising tracking or sale of journal data.

Recordings and temporary files

After successful transcription the app releases the audio draft; an unsuccessful recording stays available to retry or export while the app retains it. Native speech-processing copies and temporary backup files are removed when their operation finishes, with interrupted cleanup retried on launch. Cleanup is best effort, not secure erasure. Recordings or backups you deliberately export remain wherever you save them. Transcripts become part of your saved journal.

Older browser journals and accounts

Earlier versions used Vercel for the web journal and optional processing. That web journal is being retired; older browser data remains separate from the installed app and should be exported from its original browser before clearing website data. The current bundled app uses Supabase for optional online processing and does not load its interface from Vercel.

The retired account system used Supabase for sign-in email, account ID and backed-up journal records. Already signed-in installations can attempt a read-only download of accessible old entries. This does not upload new entries or delete old cloud records. Contact support@adamgermain.fyi for recovery or deletion of historical records. Provider backups and security logs can have separate retention schedules.

Export, deletion and your choices

Use Storage & backup to export a restorable JSON backup or a readable text copy. Restore a JSON backup on another device to move your journal. Delete entries in Your chronicle, or use Manage entries → Delete all. These actions remove local entries, not exported files, verification records or historical cloud copies.

Weekly AI review results stay on the current screen and clear when their sources change or you leave. Online permission stays on this device until you change it or clear app data. For a data-access or deletion request, email support; we may need enough information to verify and locate the relevant records. Please do not send private journal text or audio unless you choose to and it is necessary.

Contact

Echo Chronicle is for personal reflection and is not a medical or crisis service. Publisher and data contact: Adam Germain, support@adamgermain.fyi.