Skip to Content
Lumi
Security and data

Data and privacy

Where a Lumi installation keeps data, which copies leave it, and how export, retention and deletion treat each one.

This document lists where a Lumi installation keeps data, which copies leave it, and how export, retention and deletion treat each one. It is written for operators of a self-hosted installation and of isolated managed installations, which run the same containers. It is a guide to configuring and operating Lumi, not a compliance certification: whether your use meets your legal obligations depends on your business, your notices and your providers.

The procedures are in Operations.

Where data lives

An installation keeps its data in these durable stores. Your own backups must cover them: Lumi ships no backup tooling.

StoreWhere (Compose installation)What it holds
PostgreSQL, public schemapostgres-data volume, or your PostgreSQL serverBusiness configuration, knowledge, the search index, conversations, enquiries, usage, admin accounts, API keys and MCP sign-in state; see the database
PostgreSQL, langgraph schemapostgres-data volume, or your PostgreSQL serverConversation checkpoints: the full message history and state of each conversation, which the chat resumes from
PostgreSQL, drizzle schemapostgres-data volume, or your PostgreSQL serverThe schema migrations applied, which tell which release the database is at
Media storagestorage-data volume, or your S3-compatible bucketImages admins upload: team member photos, client and experience logos, project images and uploaded logos in the business and resume settings. Optional
Settings filedeploy/.env on the hostThe installation's credentials: database password, internal API key, session and MCP token secrets, OpenAI key, SMTP, storage, Google and Langfuse credentials
Certificatescaddy-data volumeTLS certificates and their private keys. Reissued automatically if lost
Container logsDocker's log files on the hostOperational events and errors; see Logs

Nothing else on the host is durable: the containers keep no state of their own. The web app keeps rendered pages in memory for up to an hour, and the backend services cache the business settings for a few seconds.

The database

DataTablesPersonal data
Business configurationbusiness_settings, handoff_settings, resume_settings, knowledge_settings, appointment_settingsBusiness contact details. Enquiry email recipients and the booking calendar's email
Structured knowledgecompany, team_members, experience, capabilities, clients, projects, job_openings, their links (team_member_capabilities, project_capabilities, project_team_members) and their *_translations; uploadsTeam members' names, bios, education and work history, published or not
Website knowledgewebsites, website_pages, website_crawlsWhatever the crawled pages say. website_crawls records the email of the admin who started each crawl
Search indexwebsite_page_vectors: page passages and their embeddingsAs the pages
Conversationsthreads: topic, summary, the visitor's name, email and phone when they gave them, the page they started on, and costYes
Enquiriesenquiries: contact fields, qualification answers, message; enquiry_deliveries: each delivery channel's state and latest errorYes
Usagethread_usage: tokens and cost of each model call, per conversation; admin_usage: the same for the admin's AI features, per adminAdmin emails in admin_usage
Admins and accessadmin_accounts (password hashes), admin_sign_in_failures (hashed), api_keys (secret hashes), oauth_* (hashed MCP codes and tokens), mcp_audit_events, mcp_idempotency_keys, mcp_rate_limitsAdmin emails and names. Rate-limit buckets are hashed and hold no addresses

The chat also keeps the visitor's conversation id in their browser's local storage, so a returning visitor continues the conversation. It holds no message content.

Copies outside the installation

Some data leaves the installation while Lumi works. Deleting it in Lumi doesn't delete these copies: each provider keeps them under its own retention, which you configure in your account with that provider.

DestinationWhenWhat it receives
OpenAIAlwaysPrompts with the conversation so far and the knowledge found for it; page and search text for embeddings; text admins translate or improve
Enquiry email recipients, SMTPWith email deliveryEach enquiry: contact fields, qualification answers, topic, message and a link to the conversation
Webhook receiversWith webhook deliveryEach enquiry, as JSON; see Handoff
Google CalendarWith calendar bookingAvailability queries, and the meeting with the visitor's name and email as a guest; the hosts are also emailed
Google WorkspaceWith Workspace sign-inAdmins' identity and group membership checks
LangfuseWith Langfuse keys setTraces of conversations and admin AI calls, including message content
Crawled websites, visitors' pagesWhen crawling, or reading a visitor's pageRequests from LumiBot/1.0. Nothing about visitors is sent
Your backupsWhen you take themWhatever the stores above held at the time

Review providers' terms and data settings for your own accounts. Don't assume they share the same retention or processing.

The diagram summarises both tables. Inside the installation, Lumi's services keep data in PostgreSQL and in media storage, and the host keeps deploy/.env, the certificates and the container logs; the visitor's browser keeps only the conversation id. OpenAI always receives prompts, knowledge found and text to embed or translate. Only once you configure them do the others receive data: enquiries and meeting emails go out through your SMTP server or Amazon SES to your team's mailboxes, enquiries go to webhook receivers, meetings go to Google Calendar, admins' identity and group membership checks go to Google Workspace, and traces with message content go to Langfuse. Crawled websites and visitors' pages only receive requests from LumiBot/1.0.

Export

export writes the business's setup to a file, to move it to another installation; see Moving to another installation. The file holds:

  • every business, handoff, resume, knowledge and appointment setting;
  • every structured record in every language, published or not, with its translations and drafts;
  • the websites to crawl (address, sitemap, exclusions), but not their crawled pages or search index, which the new installation rebuilds by crawling;
  • the uploaded images that records and settings use, unless you leave them out with --without-media.

It holds no visitor data: no conversations, checkpoints, enquiries, deliveries or usage. It holds no admin accounts, password hashes, API keys, MCP sign-ins or audit records: you create admins again on the new installation.

Webhook signing secrets are left out unless you pass --include-secrets. The import then skips those webhook channels and names them, so you add them again with your receiver's secret. Email recipients, the booking calendar's address and the business's contact details are configuration and always included. Keep an export as private as the admin interface: it holds unpublished records and team members' personal details, and with --include-secrets a credential.

Retention

Out of the box, Lumi keeps everything until someone deletes it, with one exception: the worker's weekly checkpoint cleanup deletes old checkpoint history that the chat no longer needs. It keeps each conversation's latest state, so it doesn't shorten how long conversations are kept.

To keep conversations for a limited time, set CONVERSATION_RETENTION_DAYS in deploy/.env. The worker then deletes every conversation whose last activity is older than that many days, once a day at 02:30 UTC, with its checkpoints, enquiries, deliveries and usage; see Retention. It is off by default because deleting conversations also removes them from the admin's conversation list and their cost from the dashboard.

Other data has no automatic retention:

DataHow long it is kept
Knowledge, settings, imagesUntil an admin deletes them
Crawled pages and their indexUntil a crawl finds them gone or excluded, or an admin clears or deletes the website
Website crawl history, admin usageIndefinitely
MCP codes and tokensExpire after use; their rows stay until the installation is deleted
Container logsUp to 50 MB per service in the Compose installation, rotated by Docker
Copies outside the installationAs each provider and your backups keep them

Deletion

To deleteHowAlso deleted
One conversationConversations in the admin, or delete-conversations --thread <id> --applyIts checkpoints, enquiries, enquiry deliveries and usage
A visitor's conversationsdelete-conversations --email <address> --apply; see Deleting a visitor's dataAs above, for every conversation where they gave that email
Conversations older than a datedelete-conversations --older-than <days> --apply, or CONVERSATION_RETENTION_DAYSAs above
A recordDelete it in the adminIts translations, links to other records and its images in media storage
A website's knowledgeClear pages or delete the website in Knowledge → Websites; for single pages, an exclusion and Update pagesIts pages and their passages in the search index
The whole installationRetiring an installationEverything in the stores above

Deletion takes effect at once in the chat, the MCP server and the GraphQL API: they read the database on every request. Two limits apply:

  • Old conversations remember what they were told. A conversation that quoted a record or page before it was deleted keeps that text in its own history until the conversation is deleted.
  • Copies outside the installation stay. Deleting a conversation doesn't delete the enquiry emails your team received, the webhook receiver's copy, the calendar invitation, Langfuse traces or what OpenAI retains under your account's settings. Delete those where they live.

Backups

Deleting data in a running installation doesn't erase it from backups taken before. Lumi can't reach your backups, or a managed service's, so it can't delete from them. Data deleted from the live installation stays in each backup until that backup expires or you delete it. If you restore a backup, the data deleted since it was taken comes back: delete it again before reopening the installation. Keep backups only as long as your retention policy allows, and protect them like the database itself.

Operator responsibilities

Tell visitors who operates the assistant, what you collect, why, how long you keep it and how to contact you. Avoid collecting sensitive information the enquiry doesn't need, and set CONVERSATION_RETENTION_DAYS to match your policy.

When you receive an access or deletion request, account for the installation, the copies outside it and your backups, as described above. Deleting in one place doesn't establish deletion in the others.

Restrict public knowledge to material you are authorized to publish. Check visibility through the public interfaces before you turn on a new source. Keep private production material out of bug reports and demonstrations.

Trust boundaries, limits and the operator checklist are in Security. Report suspected exposure privately, as SECURITY.md describes.

On this page