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 upcoming meetings in your daily briefing, with relevant context prepared for each;
• 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 an agenda or design doc attached to a meeting can be used as preparation context for it.

Google Docs and Drive: drive.readonly, documents.readonly

Your existing 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 drive.readonly to list your Google Docs and documents.readonly to read the text of the ones that matter, so that we can:

• show you a list of your documents during onboarding and let you choose which ones Envisianote should follow;
• read the documents you selected, plus your recently modified documents, to extract the decisions, open questions, and action items that appear in your briefing;
• answer your questions with quotes and references from your own documents.

Why a narrower scope will not do. The drive.file scope grants access only to files our application itself created, or that you picked through the Google File Picker. Every document these features depend on already existed in your Drive before you installed Envisianote, so drive.file returns nothing for them.

How we minimise what we touch. Our Drive query is restricted server-side to items whose type is Google Docs and which you own or can edit. We do not read Sheets, Slides, PDFs, images, or documents that were merely shared with you for viewing. On connect we read at most the 25 most recently modified qualifying documents from the previous 30 days. We never download binary file contents.

Exporting to Google Docs: drive.file

This is our only write scope, and it is used for one action, and only when you trigger it: exporting a meeting summary to a new Google Doc. 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

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:

• Anthropic and OpenAI — transcription, summarisation, and question answering. 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.
• 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.

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 — in Settings. 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.