AcriorityPrivacy Policy
1. Who we are
Acriority is operated by an individual based in Israel ("we"). For anything in this policy, contact support@acriority.com.
This policy describes what the Acriority app and service actually do with your data. We wrote it to match the implementation, not the other way around.
2. What we collect
Account data: your email address, password (stored only as a one-way Argon2id hash — we cannot read your password), an optional display name, your device's timezone (used to compute which day an activity belongs to), email-verification status, and the versions of the Terms and this policy you accepted and when.
Content you create: your life areas ("Domains" and "Areas"), goals, quests, and any reflections you choose to write. Reflections and the names/titles you write are treated as the most sensitive tier of data: they are stored in our primary database, synced to your own devices, and shown back to you. They are never included in analytics and never shared with third parties.
Progression history: an append-only log of your quest events (created, completed, "didn't manage", edited, archived, reflections) with two timestamps per record — when the activity belongs to and when you reported it — and the XP ledger derived from it. This is the source of truth for your levels, attributes, radar and journey.
Device and security records: for each device you sign in on — platform (Android/iOS), app version, and last-seen time; security tokens (stored only as hashes); and a security audit log of account-level actions (sign-ins, password changes, consent changes, legal acceptance) that records your user agent and a truncated IP address (the last part is removed before it is written).
Product analytics (optional — see section 4): small behavioral events such as "a quest was created", "onboarding was completed" or "the radar was viewed", carrying only coarse values — counts, buckets like "short/medium/long", and yes/no flags. Analytics events never contain text you wrote: no quest titles, no goal names, no reflections. The analytics pipeline has no field that could carry your content. Timestamps on analytics are set by our server, and events are stored in our own database.
What we do not collect: no precise location, no contacts, no advertising identifiers, no tracking across other apps or websites, no payment data (the Service is currently free).
3. How we use your data
- To provide the Service: store and sync your content between your devices, compute your progression, and show your history back to you.
- To secure accounts: verify emails, reset passwords, detect token misuse, and keep the audit log.
- To measure whether the product works, using the analytics described in section 4 — aggregate product measurement, never advertising.
We do not sell your data. We do not show ads. We do not use your data to train AI models.
4. Analytics and your choice
Analytics collection is on by default for a new account. This is disclosed during onboarding, where you can turn it off immediately, and you can change your choice at any time in Settings. Your choice is enforced on our server: turning analytics off silences the analytics stream at its single collection point — including any future mirror (section 5). Each change of your choice is recorded in the security audit log; the analytics record notes only that a change occurred, with no other detail.
Your analytics choice never affects your account, your progression, or any feature.
5. Where your data lives, and who else processes it
Your data is stored in our database hosted on Render (cloud infrastructure provider), which processes it on our behalf as a hosting provider.
PostHog (EU Cloud, hosted in Frankfurt) — an analytics mirror, active from this version of the policy. It receives only the analytics events described in section 2, identified by a random pseudonymous ID; your email, your account ID, and anything you wrote are never sent to PostHog, and IP addresses are discarded. Nothing is mirrored unless analytics is on and you have accepted this version of the policy.
Resend — a transactional email provider, active from this version of the policy. It processes your email address and the content of our account emails (verification and password-reset messages) solely to deliver them.
We send only transactional email (verification, password reset). We do not send marketing email.
No other third parties receive your personal data, except if we are legally required to disclose it.
6. Data on your device
The app keeps a local copy of your data on your device so it works offline. This local copy is protected by your device's own protections (screen lock, device encryption); the app does not add a separate encryption layer to its local database. Signing out removes your data from that device.
7. How long we keep data
- Your content and progression history: for as long as your account exists.
- Raw analytics events: up to 24 months, after which they are aggregated and the raw events deleted.
- Security audit log: 12 months.
- Sign-in (refresh) tokens: up to 60 days.
- Deleted accounts: deletion requests enter a 30-day grace period (account disabled), after which all your data — content, progression history, analytics and account records — is permanently erased. Residual copies in encrypted database backups expire within the backup retention window of 35 days after erasure.
8. Your rights and choices
- Access and correction: almost everything we hold about you is visible and editable in the app itself.
- Analytics choice: Settings, at any time (section 4).
- Deletion: you can request deletion of your account and all your data by emailing support@acriority.com from your account's address. Deletion follows the schedule in section 7 and is real — including your event history. An in-app deletion flow is planned.
- A copy of your data: you can request an export of your data (your entities, events, reflections and XP ledger) by emailing support@acriority.com. An in-app export is planned.
We will also honour rights granted to you by the privacy law that applies to you, including Israel's Privacy Protection Law.
9. Security
Passwords are stored only as Argon2id hashes; all traffic between the app and our servers is encrypted in transit (TLS); security tokens are stored only as hashes; database backups are encrypted at rest by our hosting provider; access to production data is restricted to authorised operators.
10. Changes to this policy
We may update this policy by publishing a new version. Material changes require your renewed acceptance in the app before continuing normal use. The version you accepted, and when, is recorded.
11. Contact
Privacy questions and requests: support@acriority.com.