Privacy Policy

App: everQUIN Effective date: _to be set on first public release_ Last updated: 2026-04-25

⚠️ Draft. This document is a starting point written by the engineering team to reflect what the app actually does. Have a privacy lawyer review before publishing, especially if you operate in or serve users in the EU (GDPR), the UK (UK GDPR), California (CCPA/CPRA), or jurisdictions with health-data rules. This template aims for honest, plain-language disclosure consistent with the app's actual behavior.


Plain-language summary

If any of this changes in a future version, we'll update the policy and notify you in-app at least 14 days before the change takes effect.


1. What information the app processes

1a. Information you provide directly

When you complete onboarding and use the app, you may enter:

1b. Information automatically generated

1c. Information we do not collect


2. Where information lives and how it's protected

2a. On-device storage

All data you enter is stored locally on your phone using Hive, an encrypted local database. The encryption key is held in your phone's secure keychain (iOS Keychain / Android Keystore). If you uninstall the app, all data is deleted along with it.

2b. We do not run servers that store your personal data

The everQUIN app does not have user accounts. There is no server we maintain that stores your name, your reflections, your ring members, or any other input. Nothing you type leaves your device unless you explicitly tap "share."

2c. The bundled canon

The 307-verse everQUIN canon ships inside the app as a static read-only file. Loading the canon does not require any network connection. Your reading of any verse is not reported anywhere.


3. When information leaves your device

There are exactly three situations where information leaves your device. All three are user-initiated.

3a. Sharing a verse

When you tap "share" on a verse, your phone's standard share sheet opens. You choose what to send, who to send it to, and which app/channel to use (iMessage, WhatsApp, Mail, etc.). The verse text and the everQUIN attribution are passed to that app/channel. We never see what you shared, who you shared it with, or whether the recipient responded.

We log a local record that you shared a verse (so the Profile dashboard can show your share count). The recipient's name is recorded only if you typed it in or selected it from your ring members; if you used the system share sheet's contact picker, no recipient identifier is logged.

3b. App store reviews and crash reports

If you choose to leave a review on the App Store or Google Play, that review is governed by Apple's or Google's terms — not ours.

If you opt in (when prompted by your phone) to send anonymous crash reports to your platform vendor (Apple App Analytics or Google Play Console), those reports include only crash stack traces and device characteristics. They do not include your reflections, journal entries, or any user-entered data. You can opt out at any time in your phone's settings.

3c. In-app purchases (when shipped)

If a future version of the app offers paid features through in-app purchases, the purchase itself is processed by Apple or Google. We receive a confirmation that you have a valid subscription; we do not receive your payment details, full name, billing address, or other purchase metadata.


4. Permissions the app may request

The app asks for these permissions only when you take an action that requires them. You can decline any permission and the app will degrade gracefully — features that need a permission will explain what's needed and continue to work in a reduced form.

| Permission | When asked | What it enables | Refusable? | |---|---|---|---| | Notifications | After onboarding, when you set a daily reminder time | Lets the app deliver your daily verse / practice reminder at the time you chose | Yes — you can manually open the app daily | | Contacts (read-only) | The first time you use share-to-friend | Lets the system share sheet suggest people from your contacts list. The app itself never reads or stores your contacts. | Yes — you can type recipient names manually | | Photos library (write-only) | The first time you save a verse share card to your camera roll | Lets you save a generated share-card image | Yes — share via system share sheet instead | | Local storage | Automatic | Used for Hive encrypted database, no user prompt required on iOS/Android | N/A (required for the app to function) |

Notably absent: location, microphone, camera, motion, calendar, health data. The app does not need any of these.


5. Children

The app is not directed to children under 13. The app discusses mortality (the temporal timeline), intimate relationships, life experiences including loss, and self-knowledge work — content intended for adults. We do not knowingly collect data from children. If you believe a child under 13 has used the app, contact us and we'll help with deletion.

For users 13–17: parental guidance is recommended for the temporal-timeline and grief-related content (qMARVEL chapters on the Forge, qTENSOR § grief pause, etc.).


6. Your rights

Because all your data is on your device, your rights to access, export, correct, and delete your data are exercised directly through the app:

If you are in the EU, UK, California, or another jurisdiction granting specific privacy rights (right to erasure, right to portability, right to object to processing, etc.), you can exercise them all through the in-app actions above. We do not retain copies on any server.


7. Data retention

Your data is retained on your device until you delete it or uninstall the app. We do not have a copy.

If you opt into a future end-to-end encrypted backup feature (not in v1.0), retention will be governed by terms presented at the time you enable it.


8. AI and machine learning

Future versions of the app may include narrowly-scoped AI features (verse search, pattern recognition over your own journal, daily theme curation). When and if these ship, the following commitments apply:

As of this policy's effective date, no AI or ML features are active in the app.


9. Third-party services in the app

| Service | Purpose | Data received | |---|---|---| | Apple App Store / Google Play | Distribution + crash reports (opt-in) | Crash stack traces if you opt in; never your user-entered content | | Your phone's share sheet | Routing your "share" actions | Whatever you choose to share, to whoever you select | | Google Fonts (Cormorant Garamond, Inter) | Typography in-app | Bundled at build time; no runtime calls home |

That's the complete list. We do not use Google Analytics, Mixpanel, Segment, Amplitude, Firebase Analytics, Sentry, Bugsnag, AppsFlyer, Branch, Adjust, or any other third-party SDK that collects user behavior data.


10. International users

The app is local-first. There is no server-side processing, so there is no cross-border data transfer to disclose. Your data lives in the jurisdiction your phone is in. If you uninstall the app, your data is deleted in that same jurisdiction.


11. Changes to this policy

If we change this policy, we will:

1. Update the "Last updated" date at the top. 2. Display an in-app notice the next time you open the app (a banner you must dismiss to continue). 3. For material changes (e.g., adding any third-party data-sharing or AI feature that sends data off-device), provide at least 14 days' advance notice before the change takes effect.

The full version history of this policy will be maintained in the app's GitHub repository at https://github.com/everquin/everquin-app/blob/main/PRIVACY.md.


12. Contact

For privacy questions, data deletion help, or to report a concern:

We commit to responding to legitimate privacy inquiries within 30 days.


13. Crisis disclosure

The everQUIN framework discusses topics that can surface difficult feelings — mortality, grief, isolation, relationship loss, identity work. The app is not a substitute for professional mental-health care.

If you are in crisis or considering harming yourself, please contact a qualified provider or a crisis service:

We do not have crisis-detection or crisis-routing built into the app. The app does not collect content that would let us detect crisis. If you write something concerning in your journal, only you will see it.


14. App store privacy summaries

For app store privacy nutrition labels, the following summaries describe what we collect:

Apple Privacy Nutrition Label (App Store Connect):

Google Play Data Safety form:

If a future feature ever changes this, the labels will be updated before the feature ships.


Honest about uncertainty

This policy is written to reflect the app's actual technical behavior. We have made our best effort to be precise. If you spot something that contradicts how the app actually works, please tell us at the contact above — we will correct the policy or the app, whichever is wrong.