LifeOS

Privacy

Last updated: 13 August 2026

What LifeOS is

LifeOS is a personal intelligence fabric. You ask what you need to know and do; the system assembles answers from sources you connect and from web research. It is not a public social network and not a multi-tenant demo with fake inboxes.

Data residency

LifeOS runs on Atlas under Agyeman Enterprises. Application traffic is served at lifeos.agyemanenterprises.com. Auth and data plane for this app only use the dedicated instance at lifeos-db.agyemanenterprises.com (Kong). We do not use Supabase Cloud for LifeOS and we do not store LifeOS data in another product's database.

Account and authentication

Accounts use email and password plus a one-time email code. Auth email is delivered through the AE-Mailer GoTrue hook for the lifeos tenant — not a browser-side mail SDK. Session cookies stay on the LifeOS origin.

Connected sources

When you connect Gmail or Google Calendar, OAuth refresh tokens are encrypted at rest in connector_accounts. Sync and tool execution happen on the server. The language model receives tool names, arguments, and redacted results — never OAuth tokens, service-role keys, or raw database credentials.

V0 connectors are Gmail, Google Calendar, manual upload, and web research only.

Provenance and epistemic status

Facts drawn from connected sources must carry provenance (source, retrieved_at, kind, confidence). Model inferences are stored as ai_inference and are not silently promoted to user_stated_fact.

What we do not do

  • Autonomous send, pay, or schedule (V0 actions are read, research, recommend, prepare).
  • Sell your personal mailbox contents as a product feature to third parties.
  • Invent sample calendars or placeholder answers when connectors are missing — LifeOS fails closed.

Export and deletion

Signed-in users can download a minimal export of query history and connector status (without tokens) from Settings, and can request permanent account deletion. Deletion removes the auth user; related rows cascade via foreign keys on the LifeOS schema.

Inference

Orchestrated inference goes through LiteLLM (ai.agyemanenterprises.com). If LiteLLM or required connectors are unavailable, LifeOS fails closed rather than fabricating answers.

Contact

Privacy questions for LifeOS: use the support path published for Agyeman Enterprises products, or reply to an official LifeOS transactional email from AE-Mailer.