Privacy Policy

Who we are

Envisianote, Corp. (“Envisianote”, “we”, “us”), a Delaware corporation, provides a work-context assistant, available as a web application at envisianote.com and as a macOS desktop application. This policy covers both. It applies to people who sign up for and use Envisianote (“you”). Envisianote, Corp. is the controller of the personal data described here.

If you have questions about anything here, write to privacy@envisianote.com.

What we collect

Account information

When you sign in with Google we receive your name, email address, and profile picture from your Google account. We use these to create your account, to identify you in the app, and to contact you about the service.

Meetings you record

When you record a meeting, we receive the audio, and we generate a transcript, a summary, and action items from it. If you record system audio as well as your microphone, both tracks are included. We do not record anything unless you start a recording.

Content from services you connect

Envisianote is only useful if it can see your work, so it reads from the services you choose to connect. Nothing is connected by default — each one requires you to complete that service’s own authorisation flow, and you can disconnect any of them at any time.

• Google — your calendar events and your Google Docs. Detailed in the next section.
• Slack — messages in the specific channels you select.
• GitHub — pull requests, reviews, and issues in the specific repositories you select.
• Linear — issues and their status in your workspace.

Usage and diagnostic data

We record which features you use and when, so we can understand what is working, and we collect error reports when something fails. We do not use this data for advertising.

Google user data

This section describes, scope by scope, the Google data Envisianote requests and what it does with it. These are the only Google scopes we request.

Sign-in: openid, email, profile

Used to authenticate you and create your account. We store your Google account ID, email address, name, and profile picture URL.

Google Calendar: calendar.readonly

We read your calendar events — never create, modify, or delete them — in order to:

• show your schedule, so the day’s meetings sit alongside your work;
• match documents and open items we already hold against an upcoming meeting — we do not currently show the result of that matching anywhere in the product, and we disclose it because the processing uses your calendar data;
• read the attendee list of a meeting you are recording, so that speakers in the transcript can be matched to the real people present instead of anonymous “Speaker A” labels;
• detect Google Docs attached to an invitation, so that if you have also connected Google Docs, an agenda or design doc attached to a meeting is read and the decisions, questions and action items inside it are extracted.

Google Docs: drive.file, documents.readonly

Your design docs, RFCs, and specs are the written record of your work, and they are what makes your briefing useful on the first day rather than the tenth. We use documents.readonly to read the text of a Google Doc, so that we can:

• extract the decisions, open questions, and action items that appear in your briefing;
• answer your questions with quotes and references from your own documents.

Which documents we read. 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 the calendar you have shared with us — an agenda or design doc attached to a meeting, 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 at any time. Removing one stops us reading it, and it stays removed — even if it is still attached to a meeting on your calendar or is linked again — until you add it back yourself. What we had already read from it stays in your workspace until it ages out, so a briefing card or an answer may still cite the document after you remove it; write to us if you want that cleared immediately. documents.readonly is the permission that lets us open a document you did not pick in the file picker — a document attached to your meeting invite was never handed to us through the picker, so the narrower per-file permission alone cannot read it. Google classifies documents.readonly as sensitive, and it is the only sensitive document permission we hold.

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. We open a document only when it has reached us by one of the four routes above. drive.file grants us access to the documents you pick and the documents we create, and nothing else.

What we do not touch. We read Google Docs only — never Sheets, Slides, PDFs, images, or any other file type, and we never download binary file contents. Our access is read-only; the single exception is described below.

Exporting to Google Docs: drive.file

This is our only write scope, and it is used for one action: exporting a meeting’s summary and outcomes to a new Google Doc, for accounts that have that export switched on. Nothing is exported otherwise. drive.file confines our write access to the documents Envisianote itself creates, so we never hold broad write permission over your Drive. We do not modify, move, or delete documents you created — we cannot; the scope does not permit it.

Limited Use

How we protect it

Google user data is protected by the same mechanisms as the rest of your content, stated here explicitly because it is Google data:

• In transit. Every request between your device, Envisianote and Google is encrypted with TLS. We never accept Google data over an unencrypted connection.
• At rest. Our PostgreSQL database and the Amazon S3 bucket holding recorded audio are both encrypted at rest by the infrastructure providers.
• At the application layer, on top of that. The OAuth access and refresh tokens that let us reach your Google account are encrypted with AES-256-GCM before they are written to the database, using a key held outside it. So are your transcripts, summaries, and the name and email on your account. A copy of the database alone does not yield your Google tokens or your content.
• Access control. Every database query is scoped to the owning user’s account, and the vector index that makes your content searchable is a per-user namespace rather than a shared one. Your Google data is never pooled with another customer’s.
• Least privilege. We request read-only scopes for reading (calendar.readonly, documents.readonly) and the per-file drive.file scope for writing, which reaches only documents you pick or that we create. We hold no scope that can enumerate, modify or delete your Drive at large, and no Google scope classified as restricted.
• Deletion. Deleting your account removes your Google data from our database, deletes the stored tokens, and purges the derived vectors from the search index. Disconnecting Google alone deletes the tokens and stops all further access.

Revoking our access

You can disconnect Google from Envisianote’s settings at any time, which deletes the access tokens we hold. You can also revoke access directly from your Google account permissions page. Either stops all further access immediately.

How we use what we collect

We use your content solely to produce the features you signed up for:

• Today — a daily briefing of what needs your attention, drawn from your meetings, documents, and connected tools.
• Ask — answers to questions about your own work, grounded in your own meetings and documents.
• Notes — transcripts, summaries, and action items for the meetings you record.

Your content is used to generate output for you, and is never shown to another Envisianote user. We do not use your content to train our own models, and we do not sell it.

Who we share it with

We do not sell your data or share it for advertising. We share it only with the service providers that make the product work, each of which processes it on our instructions and for no other purpose:

• AssemblyAI — speech-to-text. Your meeting audio is sent to AssemblyAI, which produces the transcript and separates the speakers. They operate under API terms that prohibit training their models on content we submit.
• Anthropic and OpenAI — summarisation, extraction, and question answering, over the transcript and your connected documents. Both operate under API terms that prohibit training their models on content we submit.
• Amazon Web Services — audio storage and audio processing.
• Neon — our application database.
• Agentset — the search index that makes your documents and meetings retrievable when you ask a question.
• Vercel — application hosting.
• Inngest — the background job service that processes webhook events from GitHub and Slack after they arrive, so that a pull request or a message you have connected becomes part of your briefing.
• Upstash — the rate-limiting and usage-accounting store. It holds counters keyed to your account; it does not hold your content.
• Stripe — payment processing. Card details go to Stripe directly; we never see or store them.
• PostHog (product analytics), Sentry (error monitoring), and Resend (transactional email).

We may also disclose information where we are legally required to, or to protect the rights and safety of our users, and we would transfer data as part of a merger or acquisition — in which case this policy continues to apply until you are given notice of a new one.

How we protect it

The mechanisms — what is encrypted and with what, how your content is kept apart from other customers’, and what deletion actually removes — are described in full on our Security page.

Where it is stored, and for how long

Your account data, transcripts, summaries, and extracted items are stored in our PostgreSQL database, hosted in the United States. Recorded audio is stored in Amazon S3. Everything is encrypted in transit using TLS and encrypted at rest by our infrastructure providers. Sensitive account fields are additionally encrypted at the application layer, and every database query is scoped to the owning user’s account.

Retention. We keep your content for as long as your account exists, so that your notes and briefings remain available to you. Recorded audio is retained alongside its note rather than discarded after transcription, because features such as speaker identification re-read the original audio. Deleting a note deletes its audio and transcript. Deleting your account deletes your notes, transcripts, extracted items, and stored audio, and revokes the integration tokens we hold. Backups and log entries may persist for a short period after deletion before being overwritten on their normal cycle.

Your choices

• Disconnect an integration — on your profile page, under Connectors. This deletes the stored tokens and stops further access.
• Delete a note — removes its transcript, summary, and audio.
• Delete your account — removes your content as described above. Write to privacy@envisianote.com and we will action it.
• Access or correct your data — depending on where you live you may have rights to access, correct, export, or object to our processing of your personal data. Write to us and we will respond.

Children

Envisianote is a workplace tool and is not directed at children. We do not knowingly collect personal data from anyone under 16. If you believe a child has provided us data, contact us and we will delete it.

Changes to this policy

We may update this policy. When we make a material change we will update the date at the top of this page and post a notice in the application. Continuing to use Envisianote after a change means you accept the updated policy.

Contact

Questions, requests, or complaints: privacy@envisianote.com. Our Terms of Service are at envisianote.com/terms.