How Envisianote uses your Google data
Last updated 14 October 2026
Envisianote connects the decisions, work and knowledge behind software development. To do that for your own work, it reads the meetings, documents and calendar you choose to connect. This page explains exactly what each permission covers, and what it never touches.
Google Calendar
Read-only. Envisianote shows your schedule, so the day’s meetings sit alongside your work. It is what lets a document attached to an invite reach us at all without you picking it. And it reads the attendee list of a meeting you record, so the transcript can label who actually said what instead of “Speaker A” and “Speaker B”. We also match documents and open items we already hold against an upcoming meeting; no screen in the product renders the result today, and we say so here because the processing uses your calendar data.
We only read events. We never create, change or delete anything in your calendar.
Google Docs
Read-only. Design docs, RFCs and specs are where engineering decisions actually get written down. Envisianote reads the documents that reach it so it can surface the open questions, decisions and action items inside them — and quote them back when you ask a question.
A document reaches Envisianote in one of four ways, and in no other way:
- you choose it in Google’s own file picker when you connect Google Docs;
- it is attached to, or linked from, an event on your calendar — the agenda or design doc on a meeting invite, read without you having to pick it a second time;
- its link is mentioned in a meeting you recorded, or posted in a Slack channel you connected;
- you paste its link into Envisianote yourself.
The documents we follow are listed on your profile page, under Connectors, and you can remove any of them. A removed document stays removed — even if it is still attached to a meeting on your calendar or is linked again — until you add it back yourself. Removing it stops further reading; what was already read stays in your workspace until it ages out, so an answer or a card may still cite it. The read-only Docs permission is what lets us open a document you did not pick in the file picker: a doc attached to your meeting invite was never handed to us through the picker, so the per-file Drive permission alone cannot read it. We request the read-only permission only. We cannot modify a document you wrote.
Google Drive
We cannot see the rest of your Drive. Envisianote does not search, list, or index your Google Drive, and has no technical ability to do so: we hold no permission that can enumerate Drive, and no production code path calls files.list. The Drive permission we hold — drive.file — grants access to the documents you pick in Google’s own file picker and the documents we create, and nothing else.
What that means in practice:
- We open a document only when it has reached us by one of the four routes above. A file that was never picked, attached, linked or pasted is never opened — even if you own it, even if it is in the same folder as one you did pick.
- Google Docs only. Never Sheets, Slides, PDFs, images, or any other file type.
- You can add or remove documents at any time from your profile page, under Connectors. Removing one ends our access to it.
- We never write to, move, or delete a file you created, and never download binary file content.
Exporting a meeting to Google Docs
If you switch on “Export each meeting to a new Google Doc” under Connectors, Envisianote creates a new Google Doc in your Drive containing that meeting’s summary and action items. It is off by default, and no meeting is exported automatically unless you switch it on. This permission is limited to files Envisianote itself creates — it does not let us open, change or delete anything that was already in your Drive.
What we never do
- We do not sell your data, or share it with data brokers.
- We do not use it for advertising.
- We do not use it to train generalized AI models.
- No one at Envisianote reads your Google data, except where you have explicitly asked us to for support, where the law requires it, or in aggregated and anonymized form for operations such as debugging a failure you reported.
Staying in control
You can disconnect a Google integration at any time from your profile page, under Connectors. Disconnecting revokes our stored tokens and stops all further access. Deleting your account removes the content we derived from your Google data.
Envisianote’s use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Full detail on storage, retention and deletion is in our Privacy Policy.