This policy explains how Bevios handles data in its notes, tasks, meetings and calendar features. Bevios operates this service. For privacy questions, a copy of your account data or account deletion, email [email protected] from your account address. We verify the request before sharing or removing data.
What we handle
We handle your email, display name, sign-in and security information, and preferences. Your workspace can include notes, tasks, meeting transcripts and summaries, attachments, and calendars you connect. We process meeting audio to create transcripts. We also track usage so we can apply account limits and operate the service.
When you start taking meeting notes, Bevios processes sound from your microphone and computer to create a transcript. Bevios does not save an audio file. Your notes, tasks, transcripts and uploaded attachments are saved to your account so they can sync between devices.
Connections are encrypted in transit. Bevios can access content in your account when needed to operate the service or provide support. This means your account content is not end-to-end encrypted.
You can lock sensitive notes with Touch ID or your Mac password. Locked note contents are excluded from AI tools, content search and previews. A note lock controls access in the app; it does not prevent Bevios from accessing the account copy for service operation or support. Files added while a note is locked stay on that Mac. Locking a note does not remove files that were already uploaded.
Bevios does not notify other participants when you take meeting notes. Tell participants that you are capturing audio and obtain any permission needed before taking notes. System audio can include sound from other apps.
Google accounts and calendars
Connecting Google is optional. Google sign-in and calendar permissions are separate choices. What you can do with a calendar depends on the permissions you grant and your access to that calendar. You choose which calendars sync in Connections.
Google data we access
- Account information. Your Google account identifier, name, email address and profile information let you sign in or link the correct Google account to Bevios.
- Calendars and events. Calendar names, identifiers, colors, time zones and access roles; event identifiers, titles, descriptions, dates and times, locations, organizers, attendee names and email addresses, attendance responses, meeting links, conference details, recurrence and changes.
- Connection and change information. We keep the permissions and credentials needed to maintain your connection, along with information that keeps your calendars up to date. This can include event drafts, edits you request and the results of those changes.
Event descriptions can contain personal information. Bevios may read them to find meeting links and retain them with event-editing data. Only calendars you enable are synchronized; Google’s read permission can cover all calendars your account can access.
How we use Google data and permissions
Bevios uses Google data to show your schedule, open meeting links, associate preparation and notes with the correct meeting, and carry out calendar actions you request. Calendar linking initially asks for read-only access. Read-only linking does not create, edit or delete Google events.
If you enable event management, Bevios asks separately for permission to manage events. On eligible calendars, you can create, edit, move or cancel events and supported recurring occurrences or series, update your attendance response, send invitations or updates to guests, and request a Google Meet link. Bevios sends the event details needed for your action to Google. Guest notifications are reviewed in the action you submit; opening an event does not send an invitation. Google calendar roles and organization policies can limit these actions.
Optional task-session blocks use event-management permission on the calendar you select. Their default exported title is “Busy”; using your task title is a separate choice. Dedicated task-calendar sync uses permission to create a secondary Bevios calendar and maintain task events there, including task titles and scheduled dates. Neither feature automatically adds private task notes, meeting preparation or transcripts to Google events.
The Google permissions used for these features are basic sign-in, calendar read access, event management and access to calendars created by Bevios. These features do not request access to your Gmail messages, Gmail drafts, contacts or Meet audio and transcripts.
Who receives Google data
Your enabled calendar data passes through the Bevios server to your signed-in devices. Hosting and network services, including Cloudflare, process it to store and deliver the service. When you submit an event change, its details go to Google; guests and other people with access to that calendar may see those details or receive the notifications you request, under Google’s sharing rules.
When you use a meeting or writing AI feature, relevant calendar information, such as a meeting title, may be sent with your request to the AI services listed below. The transcription service processes audio when you choose to take meeting notes. Connecting Google alone does not send all calendar events to an AI provider. The service-provider section explains the other services involved.
We do not sell Google user data, share it with advertisers or data brokers, or use it for advertising, credit or lending decisions. Google user data, including data obtained through Google Workspace APIs, is not used to develop, improve or train generalized or non-personalized AI or machine-learning models. This restriction also applies to our AI providers.
Human access to Google user data is limited to your affirmative permission to view specific data, necessary security investigations or legal requirements. Our use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements.
Where Google data is stored and protected
Credentials used to keep your Google connection working are encrypted on our servers. Calendar details and change history are saved to your account, with local copies and pending changes on your Mac. Connections between your devices, Bevios and Google are encrypted in transit. Account controls restrict access to the signed-in account. Bevios can access the account copy, subject to the human-access limits above.
Retention, disconnecting and deletion
Bevios retains linked-account information, synced calendar data and change history while they remain in your account. This data has no fixed automatic expiry. The credentials that keep your connection working are removed from active storage when you disconnect or delete your account. Turning a calendar off stops its sync; it does not erase previously stored data.
You can connect the same Google Calendar account separately in more than one Bevios account. Each Bevios account keeps its own connection credentials, calendar choices and synced copies. Changes made to a Google calendar can still appear in other accounts with access to that calendar.
Disconnect Google in Connections to stop future syncing and calendar changes for that Bevios account and remove its connection credentials. This does not revoke Google’s authorization for Bevios or disconnect other Bevios accounts. You can remove that authorization through your Google account’s third-party connections; doing so can stop Google access for every Bevios account connected to that Google account. If Google is your only sign-in method, set a Bevios password before disconnecting.
Disconnecting does not delete your Bevios notes, tasks, linked-account information, synced calendar details or device caches. To request deletion of retained Google data, or deletion of your whole Bevios account, email [email protected]. Account deletion removes active server account data, including the Google connection and synced calendar data. Offline devices, exports, backups and provider copies have the limits described under retention.
Disconnecting or deleting a Bevios account does not itself cancel Google events or remove a Google calendar. Manage those in Google Calendar. Copies already shared with guests remain subject to Google’s and the recipients’ own retention.
How AI uses your content
Neither Bevios nor our AI providers use your content to train AI models. This includes meeting audio, notes, transcripts, prompts and generated content. We turn off model training for transcription and use AI providers that do not train on your content.
AI transcribes meeting audio, drafts summaries and action items, and responds to writing and meeting questions. These features send audio, transcripts or the relevant document content to our providers. Locked notes are excluded from the app’s AI actions. AI output can be wrong, so review it before relying on it.
Training and retention are separate. Providers may retain data for processing or safety purposes under their policies. See the service providers and retention details below.
Service providers
- Deepgram receives meeting audio and vocabulary hints to create transcripts.
- OpenRouter and the selected model provider receive the content needed to generate meeting notes or answer the AI request you make.
- Resend handles account verification, password recovery and other transactional email.
- Cloudflare helps deliver the website, downloads and service, send live meeting audio for transcription, and store uploaded attachments.
- PostHog receives usage totals, performance information, crash reports and errors with sensitive details removed. Reports use random identifiers rather than your name or email address. We use its US service.
These services may process data outside your country. Bevios does not offer a choice of processing region. Providers may have their own retention periods, separate from Bevios.
Optional error reporting uses Sentry. Before sending a backend error report, Bevios removes request contents, user identity, interaction history and exception text. Service logs may still include account identifiers and information needed to investigate problems.
App analytics and crash reports exclude notes, titles, task text, audio, transcripts, prompts, AI answers, search queries and complete URLs. We do not use session replay or automatically capture screen contents. Analytics services still receive basic network information.
You can turn off app analytics and diagnostics in Settings. This stops new reports from that device; a report already being sent may still arrive. Reports waiting to be sent may be sent if you turn sharing back on. The choice stays in place when you sign out. Security and service-operation information is handled separately.
Website analytics
We use PostHog's US service to measure website visits, referral domains, campaign tags, browser and device types, and clicks on Download. A download click does not tell us whether you installed Bevios. We do not use website analytics for advertising profiles or connect your website browser identifier to your app account.
Cloudflare uses your connection's approximate country to select our analytics policy before analytics starts. For connections classified as United States, analytics is on unless you turn it off. For other or unknown locations, we ask you to allow analytics first. An existing choice takes priority over this default. This country check does not send your IP address or country to PostHog. Analytics services still receive basic network information when analytics is on.
When analytics is on, we save a random browser identifier in local storage to recognize visits and measure which pages lead to clicks. We also save any analytics preference you choose. We do not use analytics cookies, session replay, automatic capture of other clicks, form contents or screen contents. Page addresses are reduced to known page paths, and referral addresses to their domains. Selected campaign tags may be sent, but other query parameters, URL fragments and advertising click identifiers are excluded.
Choose Analytics preferences in the footer to turn analytics off or on. Turning it off stops future analytics and removes the stored analytics identifier; reports already sent remain with PostHog. Do Not Track and Global Privacy Control signals keep website analytics off in every region. If we cannot save browser preferences, analytics stays off. The website choice is separate from the app's analytics setting. Fonts and website scripts are served by Bevios.
What stays, and for how long
- Recent meeting audio may be held temporarily for up to two minutes to help with brief connection problems. It is discarded automatically or when you close the app. Bevios does not save it as an audio file. Longer interruptions can leave gaps in the transcript.
- Notes in Recently Deleted are eligible for permanent removal after 30 days. Notes, tasks, transcripts and uploaded attachments otherwise stay until you delete them or close your account. Removing an attachment from a note does not by itself remove the stored upload.
- Account deletion removes active account data and hosted uploads. Copies on offline Macs, exports, backups, storage versions and provider systems need separate handling. Support will explain the applicable backup expiry and provider steps when confirming your request.
Get a copy, leave, or ask for help
You can export notes as Markdown or plain text from Settings. For an account export that includes tasks, transcripts and hosted attachments, or to delete your account, contact [email protected]. An account export can include locked notes. We agree on a private way to deliver it.
Before deleting your account, let pending changes sync and export anything you want to keep. Sign out on each Mac to remove its local account copy. Deletion cannot remotely erase an offline Mac or files you exported yourself.
We use workspace content to provide the requested service, not to sell it or create advertising profiles. This statement does not replace the separate terms of the providers involved. We will publish material changes here and communicate them to users.
See the terms and support guide.