Source
Gmail, for the commitment nobody wrote down
The condition that was agreed, the deadline that moved, the correction that never reached the file — in most firms these exist once, in an email thread, and are lost the moment the person who sent them is busy. Nemosyne reads the thread and keeps what it established.
What it captures.
- Threads in the connected mailbox.
- Senders and recipients, so a statement has an author.
- Attachments, read the way any other document is read.
How it behaves.
- Authentication
- OAuth, against your Google Workspace.
- Scopes
- gmail.readonly, and nothing else. There is no scope that would let it send, delete or modify anything.
- Permissions
- Per mailbox — see below.
- A document
- A thread. A long exchange is one unit of reading.
- Sync
- Continuous; only what changed is re-read.
What this means for permissions.
A mailbox is one of the most sensitive things a firm can connect. Its contents stay bounded to the person whose mailbox it is, and a fact drawn from it and from something else is visible only to people who can see both. Our privacy page names what is held from Google sources, field by field, and what each scope is used for.
What we enforce, and the limits we publish →Questions this raises.
- Does it read everyone's mail?
- It reads the mailboxes you connect. Connecting one is a decision about one person's mail, and that is deliberately not a one-click firm-wide switch.
- Can it send or delete anything?
- No. It holds a read-only scope, so the ability is absent rather than merely unused.
- Is our mail used to train a model?
- No. Documents are read to build your memory and for nothing else; model calls run under enterprise terms that exclude training.
Connect it to what you already use.
Free for three people and about a hundred documents. No card, no expiry.
Start free →See also SharePoint · Google Drive · Salesforce · Slack · HubSpot