Answers questions about the inbox
Out loud, hands free. How many unread, who from, what a particular message says. Reading is free and unrestricted; nothing about a read changes the mailbox.
Jarvis
An assistant thatstays on the desk.
A private assistant that runs on its owner's own machine and connects to their own Google account. This page describes what it does, which Google permissions it needs, and why — the same account of the software the privacy policy is written from.
Runs onOne person's Windows machine, not our servers
UsersSingle owner — no accounts, no sign-up
Policylabsobsidian.co/privacy
What it does
Mail and calendar, by voice and from the desktop
Drafts replies in the owner's voice
Learned from their own sent mail. Every send is either a card the owner taps to approve, or a message they typed themselves in the desktop app and pressed send on.
Keeps four calendars in step
One account is the calendar of record. The write surface refuses any event that is not the assistant's own mirror, so a human-made event can never be edited or removed by a sync.
Files and tidies, reversibly
Cleanup moves mail to Trash, where it can be recovered. Permanent deletion is impossible by construction: the scope that would allow it is never requested.
Google permissions
What it asks for, and why it needs it
- gmail.modifyRestricted
- Read and search the owner's mail so the assistant can answer questions about it out loud, summarise what arrived, file messages into the account's own labels, move things to Trash, mark them read, and send replies the owner has approved. Modify is the narrowest scope that covers both reading and those changes.
- calendar.eventsSensitive
- Read the day's agenda from each connected account's primary calendar, and keep one calendar of record in step with the others by creating and updating only events the assistant itself made.
- userinfo.emailBasic
- Learn which address has just been connected, so the grant is labelled correctly in the assistant's own settings. Nothing else is read from the profile.
The shape of it
Where the data actually lives
- It runs on one person's own Windows machine, not on a server we operate.
- It is single-owner software. There are no accounts, no sign-up, and no other person's mailbox is connected to it.
- Google refresh tokens rest encrypted with Windows DPAPI, readable only by that Windows user.
- It never downloads Gmail attachments, and only ever reads each account's primary calendar.
- It uses OpenAI's models for voice, summaries and drafting — so mail and calendar content does reach OpenAI, and the privacy policy says exactly which fields and why.
The full account — every field that leaves the machine, how long anything is kept, and how to revoke access — is in the privacy policy. Questions go to hello@labsobsidian.co.