A voice OS that has access to your calendar, inbox, files, and the ability to take action on your behalf is powerful and dangerous in equal measure. The permissions model is the system that controls what the AI can read and what it can do. It has three parts: OAuth scopes that define what data the AI can access, per-tool consent that controls which actions the AI can take, and confirmation flows that put the user in the loop for irreversible operations. Without a clear permissions model, voice AI becomes a security liability.
WHAT TO LOOK FOR
OAuth scope minimization
Each external integration uses the smallest OAuth scope sufficient for the feature. Calendar read and calendar write are separate; Gmail read and Gmail send are separate. Users can grant calendar read without granting calendar write.
Per-tool consent
Tools like send_email, create_calendar_event, and pay_invoice each have their own consent state. Granting voice access to one does not implicitly grant access to all. Consent state is durable and revocable at any time from the user dashboard.
Confirmation for irreversible actions
Sending an email, creating a payment, or deleting a record requires explicit voice confirmation: 'Should I send that?' Reversible or low-risk actions like reading data or creating a draft do not require confirmation, which keeps the conversation flowing.
TLDR:Lucy OS1 uses Google OAuth with the minimum scopes required for each feature. Calendar access is read-only by default; calendar write is a separate scope the user explicitly grants. Email read is one scope; email send is another, and Lucy always confirms a draft out loud before sending. Memories can be edited or deleted by the user at any time. The permissions model is opt-in per capability, not all-or-nothing, so users can grant Lucy access to exactly what they want and no more.
Each external integration uses the smallest OAuth scope sufficient for the feature. Calendar read and calendar write are separate; Gmail read and Gmail send are separate. Users can grant calendar read without granting calendar write.
Tools like send_email, create_calendar_event, and pay_invoice each have their own consent state. Granting voice access to one does not implicitly grant access to all. Consent state is durable and revocable at any time from the user dashboard.
Sending an email, creating a payment, or deleting a record requires explicit voice confirmation: 'Should I send that?' Reversible or low-risk actions like reading data or creating a draft do not require confirmation, which keeps the conversation flowing.
Users see every memory in a dashboard and can edit or delete each one. Memories can be marked private, which excludes them from prompt injection. There is no opaque memory layer that the user cannot inspect.
Users can delete individual conversations or wipe their entire history. Deletion is irreversible and removes the conversation from active databases within a defined window. Backups follow the same retention policy.
Every tool call the AI made on behalf of the user is logged with timestamp, parameters, and result. The user can review this trail to see what Lucy did and when. This is essential for trust in any AI that takes actions.
QUICK COMPARISON
| Capability | Lucy OS1 | Most AI tools |
|---|---|---|
| Memory across sessions | ✓ Permanent, never resets | ✗ Resets after every session |
| Voice quality | ✓ Lucy OS1 Natural Voice (best-in-class) | ✗ Basic STT, struggles with noise |
| Calendar awareness | ✓ Reads Google Calendar in real time | ✗ No calendar access |
| Available 24/7 | Always on, any device | Available but stateless each time |
| Gets personal over time | ✓ Builds your context continuously | ✗ Starts from zero every session |
Voice-first AI with memory and calendar integration. Free to try.
Start TalkingFree tier available. No credit card required.
GET STARTED
Create your free account
No credit card required. Sign in with your Google account and you're inside in under a minute.
Connect your Google Calendar
Lucy reads your upcoming events before every conversation, so it already knows your day before you say a word.
Start talking about voice os permissions model
Speak naturally. Lucy listens, responds by voice, and begins building context from your very first exchange. The more you use it, the better it gets.
Welcome