Lantern & Loch demonstration
Privacy policy
Updated 24 October 2026
This fictional venue demo is operated by Luke Molony. For privacy questions or account/data deletion, email luke@offline.company.
What we collect and why
Google sign-in supplies your verified email and account identifier, and may supply your name and profile photo. We keep those supplied fields, sign-in times and the collection-notice version in a restricted visitor directory to identify your workspace, understand who uses the demo and handle requests. Signing in does not imply marketing consent. We do not request Gmail, Calendar or Drive access, or store Google provider tokens as profile data.
We store your offsite brief, preferences, shared agent messages, proposals, fictional holds and your access/approval decisions to run the demonstration. We also keep usage, quota and operational records to control costs, prevent abuse and recover interrupted work.
What is shared
Your workspace shows the messages your personal agent sends to the venue and the venue agent’s replies. It does not collect your private terminal-agent conversation, local vault passphrase or agent credentials. Share only the offsite details needed for the task; avoid real confidential or sensitive personal information.
Google provides sign-in; Supabase provides authentication and database storage; Vercel hosts the website; and OpenAI processes the relevant brief and shared conversation to run the venue agent. Those providers also process data under their own terms and policies. Your personal-agent provider handles its own private conversation separately. Operator access to visitor records is restricted; the visitor directory is separate from the shared workspace.
Retention, reset and deletion
Demo data is kept indefinitely by default. The operator can instead configure demo inactivity expiry after 24 hours or 7 days. The visitor directory and usage/quota records are separate from that policy.
Reset starts an empty demo run and cancels the old run’s access, approvals and work. It does not delete your visitor record or restore spent quota. Revoking agent access is also separate from deleting your account.
To request account/data deletion, email luke@offline.company with the email you used to sign in. We verify ownership before acting. Deletion includes separate application, authentication and remote-agent cleanup steps; limited security, usage and revocation records may remain. Backups and service-provider retention can outlast removal from the active demo. Do not send passwords, vault passphrases or tokens with your request.