Privacy Policy

Last updated: October 2026

This policy explains what EchoChamber collects, why it collects it, and how to delete it.

Data we collect

• Account data — if you create a cloud account, your email address, user ID, display name, and avatar URL.
• Your content — the notes, messages, media, links, reminders, sketches, and tool attachments you create.
• Sync and device data — device identifiers, sync cursors, timestamps, hybrid logical clock values, and app version information used to keep your devices in sync.
• Usage and subscription data — storage, database, and bandwidth usage, plan tier, and subscription status. Google Play processes payments; we never see your card details.
• Crash and diagnostic reports — the error type, a technical stack trace, the app version, your platform and OS version, and a random identifier for your app installation. These are sent without requiring an account, so that we can fix faults on installations that have never been signed in. Your account ID is attached only when you happen to be signed in at the time. See Diagnostics below for exactly what this does and does not include.
• Feedback you choose to send — the rating, category, and description you type into the feedback dialog, plus, if you leave the option enabled, recent error messages from your device. See Diagnostics.
• Photos and files — only when you attach or share them inside the app. The camera is used for QR device pairing and for capturing images you choose to save.

Your data stays on your device

All journal entries, messages, media, and settings are stored locally on your device first. Nothing is transmitted to us or any third party unless you turn on an optional feature:

• Cloud sync — off by default; only syncs if you sign in and enable it
• LAN sync — peer-to-peer between your own devices only, never through a server
• Encrypted export — goes wherever you choose, not to us

How we use data

• To store, sync, and display your content on the devices you sign in on.
• To enforce plan limits and process subscriptions.
• To diagnose crashes and improve reliability.
• To respond to support requests.

What we do not do

• We do not sell your personal information.
• We do not use your journal content for advertising.
• We do not use third-party advertising or tracking networks.
• Firebase Analytics collection is disabled in the app.
• We do not read your notes, messages, or media. Not for analytics, not for AI features, not for support.

Who receives your data

• Supabase — authentication, database, and file storage for cloud features, and storage for crash diagnostics.
• RevenueCat and Google Play — subscription status and transaction identifiers. RevenueCat is used as the subscription manager; Google Play processes payment.
• Payment processing — purchases made from the Windows app or this website are processed by a payment provider acting as merchant of record (the provider named on your receipt).

These providers process data under their own terms and privacy policies. We do not share your journal content with them.

Diagnostics, crash reports, and feedback

This section is specific, because "diagnostics" is a word that can cover almost anything.

Crash and fault reports. If the app hits an error it cannot recover from, it records a short technical report and sends it to us. A report contains:

• the kind of error, and a stack trace — a technical list of the lines of our own code that were executing;
• your app version, build number, platform, and OS version;
• a random identifier generated by the app for this installation, used to group repeat reports together and to limit how many reports one installation can send.

What a crash report never contains: the text of your notes or messages, your note or folder names, your media, your file paths, or your account details. If the app is signed in when a report is sent, your user ID is attached so we can correlate the fault with your account; otherwise the report is anonymous.

Feedback you send. The feedback form collects a rating, a category, and your description. It also offers an optional email address — only if you want a reply. That address is stored with your feedback and used for nothing else; leave it blank and no contact information leaves the device. If you leave Include technical details enabled, the report also attaches recent error messages from the app's log on your device. That option is on by default and you can turn it off before submitting. Information messages are never included, because some of them contain note names.

How long we keep it. Crash reports are kept while we need them to fix the fault. Diagnostics are review-only: unlike your content, they are not visible in the app and cannot be read by you or by any other user.

Deleting it. Reports waiting on your device are deleted when you delete your account, and are also cleared when you uninstall. Reports already sent are tied to your installation rather than to your account, so deleting your account removes the link to your account but does not automatically delete the anonymous fault report itself — it may still be evidence of a fault affecting other people. If you would like a particular report removed, email us and we will delete it.

Turning it off. Disabling cloud sync in Settings stops your content from being sent. Crash reporting is not a toggle: an app that silently swallows crashes is an app we cannot fix, and the reports contain no content. If you would prefer no diagnostics at all on a specific installation, please email us and we will note it.

Where data is stored

Your content is stored locally on your device. If you sign in to a cloud account, a copy is stored on our Supabase project so it can sync between your devices. Local backups you create are stored on your device.

Retention and deletion

Local data stays on your device until you delete it or uninstall the app. Cloud data is retained while your account exists. You can permanently delete your cloud account and its associated data at any time using the in-app Settings → Account → Delete account flow, or by following our account deletion page.

When you request deletion we remove your RevenueCat customer record, your files in cloud storage, and your authentication account. Financial records required by law, such as purchase history held by Google Play or our payment provider, may be retained by the payment provider.

Security

Cloud data is protected in transit with TLS and at rest by our infrastructure provider. Access to your data requires a valid account session. No system is perfectly secure, so please use a unique password and do not share your account.

Children

EchoChamber is not directed at children under 13, and we do not knowingly collect personal information from children.

Your rights

• Export — export all your data at any time, encrypted, to any location
• Delete — delete individual notes or your entire journal locally
• Account deletion — if you created an account, you can delete it entirely
• Access and questions — contact us for a copy of your data or to ask questions

Changes to this policy

We will post any changes to this page and update the date above. Material changes will be announced in the app's release notes.

Contact

Questions about this policy, or requests regarding your data, email support@echochamberapp.com.