This describes what Anantaa actually does with your data today — not a generic template. If a practice described here ever changes, this page is updated to match, not the other way around.
Account & sign-in
If you sign in with email/password or Google/GitHub, your session is a signed cookie (NextAuth), and your account record (email, name, role) lives in our Postgres database. Passwords are bcrypt-hashed — we never store or can recover your plaintext password.
Saved items, Spaces, and audit logs
Notes you save and shared Spaces you create are stored in Postgres, scoped to your account, and deletable by you at any time — a delete is a real, permanent removal of that content. Every create/update/delete is separately logged with structural metadata only (e.g. "a note was created," never the note's actual text) — this audit trail exists for accountability and never contains your content.
Location & trail history
If you opt in to "track my location trail," it's recorded only in this browser's local storage (IndexedDB) — it never reaches our servers, in raw or derived form, unless you separately opt in to sharing derived place names with search suggestions. You can clear it at any time from Preferences → Privacy.
Search history
Recent searches are stored in this browser's local storage by default, not on our servers. If you opt in to sharing them, they're used only to power a "next search" suggestion and are never stored server-side beyond that one request.
Gmail, Google Calendar, and Outlook connectors
Connecting Gmail, Google Calendar, or Outlook under Settings → Connectors is entirely opt-in and separate from signing in. Each grant is scoped to exactly what the corresponding Workflow step actually does, never broader than needed:
- Gmail (the gmail.modify scope) — reads inbox metadata to organize/summarize messages, and moves messages to trash only after you explicitly approve a specific deletion (e.g. the spam-cleanup workflow's human-approval step). We never read message content for any purpose other than the workflow you ran, and never send email on your behalf without your approval.
- Google Calendar (the calendar.events scope) — creates calendar events only when a workflow step you configured asks it to (e.g. "create a calendar event" step). We don't read your existing calendar beyond what's needed to avoid duplicate events.
- Outlook (Mail.ReadWrite, Calendars.ReadWrite) — mirrors the Gmail/Calendar behavior above for Outlook accounts, same scoping, same approval-gated actions.
None of this data is sold, shared with advertisers, or used to train any model. You can disconnect any connector at any time from Settings → Connectors, which immediately revokes our access; workflow steps that depend on it will ask you to reconnect rather than silently failing.
Payments
Ad billing and any real payment flow runs through Stripe — we never see or store your raw card details. Stock orders placed through the agentic order flow are simulation-only against a sandbox trading API; no real money or real shares are ever involved.
Third-party services
Map/place lookups use OpenStreetMap's Nominatim/Overpass and the OSRM routing project; weather uses Open-Meteo — all free, open-data services with no API key tied to your identity. Search results may come from a self-hosted SearXNG instance we run, not a third party.
Your controls
You can delete saved items, clear your local search/location history, leave Spaces, and delete your account at any time. Contact us (see Business profile) for anything this page doesn't cover.