Privacy
Draft updated 28 September 2026
Who is responsible
If you self-host Leothos, you or the organisation operating that deployment controls the data. For the future Leothos-hosted service, the legal operator, contact address, and applicable jurisdiction must be inserted here before accepting production customers.
Data Leothos can hold
Depending on what you enter or connect, Leothos can hold account and workspace membership details, invitations, contacts, relationship notes, events, tasks, private reflections, message content and metadata, Pocket transcripts and summaries, integration settings, limited MCP audit metadata, and hosted subscription identifiers and seat quantity. Payment card details are collected and held by Stripe, not Leothos.
How data is used
Data is used to provide the features you request: organising relationship context, showing history, planning follow-ups, reflecting, syncing configured messages, processing configured Pocket recordings, and responding to authorised MCP requests. This template does not authorise advertising, data brokerage, or model training.
Services and data flows
A deployment can use Supabase for authentication and database hosting, a hosting provider for the web app, Stripe for hosted subscription billing, Pocket for recordings, an AI model provider for optional transcript extraction or summaries, and an MCP client you configure. iMessage sync runs through a worker on your Mac. Each provider receives data according to the feature you enable and its own terms.
Retention and deletion
Records remain until an authorised member deletes them or the workspace. Account settings provides a personal JSON export; owners and admins can export the active workspace. Password-reauthenticated account deletion removes the member's personal workspace and credentials but preserves shared team memory. A team owner must transfer ownership first. Metadata-only security records may remain without a user identifier. A deployment operator must still publish its backup deletion window and support channel.
Security
Leothos uses application authentication and database access controls, but no system can promise absolute security. Self-hosters are responsible for secrets, updates, backups, network security, and provider configuration. This page does not claim a security certification or regulatory compliance.
Your choices
You can avoid optional integrations, revoke MCP connections, remove individual records, export your account, delete a password-based account in Account settings, and stop a local worker. Social-login-only accounts currently require operator-assisted reauthentication and deletion. Operator contact details must be published before hosted launch.