Source
Google Drive, read where it already is
Drive is where the memo, the model and the signed copy usually end up, and where the sharing decisions were made one file at a time. Nemosyne reads the files and carries those decisions through into everything it derives from them.
What it captures.
- Documents in the drives and folders you connect — Docs, Sheets, Slides, PDFs and uploaded files.
- Google-native formats, exported and read rather than skipped.
How it behaves.
- Authentication
- OAuth, against your Google Workspace.
- Permissions
- Per file — see below.
- Scope
- What you grant. The connector enumerates what it can see and reads that.
- A document
- One file.
- Sync
- Continuous; only what changed is re-read. A failed pass backs off rather than restarting.
- Writes
- None. Nothing is written back into Drive.
What this means for permissions.
Drive's per-file sharing carries through: a file shared with three people yields facts only those three can see, and a fact drawn from two files is visible only to people who can open both. An answer is built only from files the person asking could already open.
What we enforce, and the limits we publish →Questions this raises.
- What do you do with our Drive data?
- It is read to build your memory and for nothing else. Our privacy page names, field by field, what is held and what each scope is used for.
- Does a link-shared file become public inside the memory?
- It is as visible as Drive makes it, and no more.
- Can we connect a single folder?
- Yes, and on a first run that is usually the right move: one folder, one decision worth improving, and a memory you can check before you widen it.
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 · Salesforce · Slack · Gmail · HubSpot