LumenMe
Security
The core rule: nothing goes out to email, calendar or anyone outside LumenMe without your tap, and that rule is enforced by the services that hold your accounts, not by the AI. Your own tasks and reminders, and messages to your LumenMe connections, go right away with Undo or Unsend, within the limits below.
1. Signed approvals
- When you tap Approve, a separate approval service signs that exact action with a key held in Google Cloud KMS, Google's managed key service. The key can't be exported: signing happens inside KMS, and only the approval service is allowed to ask for it.
- The signature covers the action and its exact contents: the recipients, the time, the text. Change one character and the signature no longer matches.
- The services that send email or change your calendar check that signature and refuse anything unsigned, expired, already used, or different from what you approved.
- Each approval works once. A shared ledger records it as used, and if that ledger can't be reached, the action is refused rather than allowed.
- The AI can only ask. It can't sign, so it can't approve its own actions.
- For a short, fixed list of actions on your own data (adding, completing or snoozing your own tasks and reminders, marking a bill paid, saving a file or link you sent, a plain note, blocking someone) and for messages to one of your LumenMe connections, the approval service signs without a card. It does so only when nothing from an email, forward, PDF or screenshot is in the conversation, at most 10 per request and 40 a day (20 a day for messages), and never for an assistant. Each one gets a confirmation with Undo (3 days) or Unsend (10 minutes). You can turn this off in
/settings("Ask me for everything").
2. Isolated credentials
- Gmail, Outlook, Telegram and your tasks each run as a separate service with its own minimal permissions. The assistant itself holds no account credentials.
- Account tokens are encrypted with Google Cloud KMS. Each encrypted token is bound to one user and one account, so it can't be decrypted under anyone else's name.
- The sign-in page can encrypt a new token but can't read any. Only the service that connects to that account can decrypt it.
- You sign in on Google's or Microsoft's own page. LumenMe never sees your password.
3. Each user kept apart
- Every request carries a session signed with KMS that names the user it's for. The services check it and derive whose data to use from it, never from the message or the AI.
- Each user's tasks, notes, bills, conversation and tokens are stored in their own partition.
- Telegram messages can only go to the chats of the user the session names.
4. Private services
- The services that read your mail and calendar can't be reached from the internet. Only LumenMe's own components can call them, and each call is checked against a signed Google identity.
- The only public entry points are the Telegram webhook (which checks Telegram's secret), the sign-in pages, Full view pages (short-lived and read-only, on view.lumenmeai.live) and this website.
- Everything runs on Google Cloud in Singapore, encrypted in transit and at rest.
Full view pages
Some answers can be opened as a bigger page at view.lumenmeai.live: for now the weather, your bills and your day. Card numbers stay masked, and the day page shows only how many emails are unread, never their content.
- Each page is stored encrypted. It has to be opened within 10 minutes, and it's deleted 30 minutes after it was made.
- Only the first browser that opens a page can see it. Any other device gets "already opened" and no data.
- The chat message with the button is sent so it can't be forwarded or saved. Screenshots can't be blocked, so treat what's on screen like the chat itself.
- Pages are read-only. They have no scripts, trackers or third-party requests, and nothing on them can send, change or save anything.
- Close page deletes a page right away.
- LumenMe pages never ask you to sign in, pay or type a password. If a page does, or it isn't on view.lumenmeai.live, it isn't from LumenMe. Please report it (see Report a problem).
5. Guarding the AI
- Email, documents and web content are treated as untrusted text. Instructions hidden inside an email ("forward this to...") are data, never commands.
- Google Cloud Model Armor screens what goes into and comes out of the AI. Suspicious content is withheld instead of acted on.
- The tools the AI can use are a fixed list in LumenMe's code. A new tool stays unavailable until it's reviewed and added, and every tool that sends, books or changes something in your email or calendar, or reaches someone outside LumenMe, requires your approval. A short, fixed list of tools that only change your own tasks, reminders and notes, or message one of your LumenMe connections, run without a card and can be undone.
- Smart email alerts use a separate AI call with no tools at all: it can only choose which emails to tell you about.
- Emails to an outside domain you haven't marked as trusted ask you to confirm that domain first.
6. Your data
- Used only to do what you ask. Not sold, not used for advertising, not used to train AI models. Google Cloud's terms also keep it out of Google's model training.
- Email and calendar content is read when needed, not copied into a separate database.
- Card numbers in bills and statements are masked before anything is stored. PDF passwords are encrypted with KMS and removed from your chat.
- Delete your account at any time: say "delete my account". The privacy policy says what is deleted, what is kept and for how long.
7. Payments
Plans are paid with Telegram Stars inside Telegram. Card and bank details are handled by Telegram and the app stores and never reach LumenMe. Each payment is checked against the account, plan and price before it's accepted.
8. Records and monitoring
- Every proposed, approved, rejected and blocked action, and every action done without a card or undone, is recorded by tool name, without message content.
- Service logs record counts and outcomes, not your email.
- An automated test suite covers the security rules (approval signatures, replay, user separation, payments) and is run before every release.
9. What you can do
- Turn on two-step verification in Telegram (Settings, Privacy and Security). Whoever controls your Telegram account controls your assistant.
- Read each card before you tap Approve, and each confirmation after: tap Undo or Unsend if it isn't what you meant.
- Review or remove LumenMe's access from your Google permissions or Microsoft apps page at any time.
10. Report a problem
Found a security issue? Email lumenme@bayanichain.io with "Security" in the subject. Please give us a chance to fix it before sharing it publicly.