Privacy Policy

Everything below is stored only so the product can function for you. Your account holds:

• Your reflections — the text you write, the mode you chose, and the AI response, plus derived signals such as an estimated mood score, emotions, and topics.
• Derived intelligence — memories, insights, daily summaries, next-day briefs, weekly summaries, threads, ideas, and open loops that Averomi generates from your reflections.
• Things you add — people, important dates, reminders, and check-in preferences.
• Account details — your email address, preferred name, language and companion settings, timezone, and a securely hashed password (we never store your password in readable form).
• Push subscriptions — if you enable notifications, the browser push endpoint and keys needed to deliver them.
• Product analytics— a small set of event names and timestamps (for example, “reflection created”) with short enumerated properties. Analytics never include the content of your reflections; a payload sanitizer drops any content-like fields before they are written.

When an AI provider (OpenAI) is configured on this installation, the text of the reflection you submit — together with the specific context Averomi selects for that reply (relevant memories, insights, recent entries, people, and dates) — is sent to that provider to generate a response. If no provider is configured, or a request fails, Averomi falls back to a local, on-server response and no data leaves this installation for that reflection.

The AI provider processes this data to return a response and under its own terms. Averomi does not use your content to train models.

Weather context is off by default. If you turn it on, your browser asks for your location and Averomi sends only your coordinates to Open-Meteo to fetch a local forecast. No account identity is sent to Open-Meteo. You can disable weather at any time, which stops the requests and removes the stored location.

You can mark any reflection as sensitive. A sensitive reflection still receives an immediate AI reply, but it creates zero derived artifacts: no memory, embedding, idea, reminder, open loop, insight, or check-in candidate is created from it, and it is excluded from digests, briefs, summaries, and the context used for future replies. This is enforced in the data-flow code, not merely hidden in the interface.

Separately, if you tell Averomito forget a specific reflection (the “don’t remember this” control), it immediately archives every memory derived from that reflection, deletes those memories’ embeddings, and marks the reflection sensitive so it is excluded going forward.

Your data is kept until you delete it. You can delete individual items in the app, and you can delete your entire account at any time. Deleting your account permanently removes all of your data — reflections, derived intelligence, people, dates, reminders, push subscriptions, analytics events, and billing records — through a database cascade. This is not reversible.

You can export your data at any time. A full account export returns a single JSON file containing your profile and preferences, reflections, memories, ideas, reminders, open loops, threads, people, important dates, summaries, briefs, insights, check-ins, feedback, activity logs, push endpoints, and analytics events. Password material, session tokens, and raw embedding vectors are excluded for security; embeddings are represented by a count and model name.

Averomi does not sell your personal data and does not share it with advertisers or data brokers. Data is shared only with the service providers needed to run the product: the AI provider (when configured), Open-Meteo (only if you enable weather), your browser push service (only if you enable notifications), and the payment provider identified at checkout (Dodo Payments, only if billing is enabled on this installation).

Averomi uses a single session cookie to keep you signed in. It is an opaque, httpOnly token; only its hash is stored on the server. There are no third-party advertising or tracking cookies.

Passwords are hashed with bcrypt and session tokens are stored only as hashes. Averomi relies on encryption in transit and at the database and hosting layers. This version does not add application-level encryption of your reflection content on top of that; see the product documentation for the security roadmap.

Questions about privacy or a data request can be directed to the service operator who provided your account access. The operator is responsible for supplying its current support channel.