Privacy, in plain language.
Understand what is processed in the cloud, what can stay on your device and which controls you have.
Updated 20 November 2026. This policy describes Aivo on iPhone, iPad and Mac and the services used to provide it. Contact team@aivolabs.eu with privacy questions or requests.
1. What Aivo processes
Voice and writing
Aivo uses OpenAI for cloud transcription. When you submit dictation, Aivo sends your recorded audio and selected dictation languages through its server to OpenAI over encrypted connections. When available, Aivo also sends relevant words you added to your personal dictionary and words learned from your corrections as vocabulary hints. OpenAI uses these inputs to return a transcript.
On Mac and older app versions that offer cloud writing modes or Norwegian text normalization, those features may also send dictated text, relevant vocabulary and applicable writing instructions through Aivo’s server to OpenAI to produce a revised draft. Review important text before using or sending it.
Permission for AI processing
In the iPhone and iPad update 2.2.14, Aivo explains this data sharing before sending any dictation to OpenAI. Choose Allow sharing with OpenAI to permit it or Don’t share to decline. You can decline and still browse Aivo and manage your dictionary and snippets. Microphone permission, keyboard Full Access, signing in and paying for a subscription are separate from this choice. The choice is saved for each account or guest on that device and does not sync to other devices.
On iPhone and iPad, open Settings → AI processing in Aivo to review your choice or select Stop sharing. On Mac, open Settings and find AI processing with OpenAI under Privacy to review or withdraw permission. Withdrawal stops new sharing for AI processing and cancels pending local work. It cannot recall data already sent. Your saved history, word totals, saved tools and subscriptions remain available.
These iPhone and iPad controls require the 2.2.14 update. Check the App Store for availability. Older installed iPhone and iPad versions do not receive the controls from this policy update. Aivo for Mac has included explicit permission controls since version 1.0.15.
Meeting recording and Notetaker
Checked 20 November 2026. Public Mac version 1.0.25 (build 36) supports Notetaker recording and transcription on macOS 15 or later. Public iPhone version 2.2.14, released on 11 November, is verified for dictation. A public iPhone Notetaker release has not been confirmed.
Personal Mac recordings and their transcripts are saved with the recording and managed separately from ordinary dictation history. Recording in a personal workspace alone does not upload the audio. When you choose transcription and acknowledge the sharing, the saved audio and selected language are sent through Aivo to OpenAI for transcription.
Enabled company pilots are a separate workflow. Depending on the enabled configuration, company audio, transcripts and documents can be stored in protected company storage under the record’s access, expiry and deletion rules. Speaker-labelled transcription sends audio to ElevenLabs Scribe only after a separate pilot acknowledgement. Summary generation separately sends transcript text to OpenAI. Source review, approval and Word/PDF document export require the enabled company pilot; a paid seat or ordinary Teams trial does not enable it by itself.
Dictation-history switches do not delete Notetaker recordings or exported files. Deleting an Aivo record cannot recall exports or override provider, backup or legally required retention. Read the processing and storage information in the app, the company Notetaker pilot notice and the data-handling guide before a workplace evaluation. Processing is global; this section does not establish EU-only processing or universal zero retention.
Recent history and local-content choices
These controls concern ordinary dictation content; Notetaker recordings follow the separate workflow above.
The updated apps bind new recent history and pending results to the current Aivo account on that device. Mac’s Don’t save new history stops new recent history and the last-result buffer. The iPhone update’s Limit saved dictation content also stops automatic correction learning and prevents correction/undo text carrying into the next keyboard session. Both controls are off by default. Temporary audio/results are cleaned in normal app flows; interrupted or crashed flows and operating-system backups have separate limits.
These switches do not erase existing history, earlier recovery archives, dictionary entries or snippets, and do not stop cloud processing or usage accounting. Earlier content without reliable account ownership is preserved separately instead of automatically assigned to the next account. Review/export requires supported device-owner authentication, and restoring entries is deliberate. Recovery does not add words again to lifetime totals. Check app availability, exact controls and recovery steps.
Saved vocabulary and preferences
Personal dictionary entries, snippets, custom writing instructions and learned corrections can be stored on the device and synced to your account where the relevant sync feature is available. These can contain personal information you choose to save. Account-scoped storage keeps different signed-in accounts separate.
Account and usage
We process your account identifier, Apple sign-in identifier, email address or Apple relay address, subscription status, preferences and usage counters to provide access, enforce plan limits and synchronize supported features. Signed-in usage is associated with your account; it is not all anonymous. Limited guest access uses a guest identifier and abuse-prevention controls.
Optional company sign-in
Microsoft Entra sign-in requires an explicitly configured team, an updated SSO-capable app and administrator-assisted setup with Aivo. External-tenant consent and publisher verification remain part of the broader rollout. Existing Apple sign-in and subscriptions remain available; company sign-in is optional. See the Teams setup and linking guide.
When this optional flow is used, Microsoft authenticates the work identity and returns identity tokens to Aivo’s server. Aivo validates the sign-in and links the immutable Microsoft tenant ID and object ID to an existing Aivo account and team. Linking requires the member to use their existing Aivo account first and confirm the link. Aivo does not automatically merge accounts by matching email addresses, create accounts or grant paid seats merely because someone belongs to a directory.
Aivo stores the identity link and access-session records. Sign-in flows expire after 10 minutes and Aivo company sessions last up to eight hours; expiration is an access limit, not a guarantee that every related record is deleted immediately. The flow requests only openid profile, with no Microsoft Graph, mail, document or directory-management permissions. Aivo does not send dictation audio, dictated text or saved vocabulary to Microsoft as part of company authentication. Microsoft also processes authentication and normal browser/network data under its own policies.
This first phase does not provide enforced SSO, automatic provisioning or SCIM directory synchronization. Microsoft directory changes are not a verified immediate revocation mechanism for every Aivo session. Provider retention, account settings and contractual arrangements remain subject to separate verification. Read the identity data flow and limitations.
Teams, usage and service costs
For company subscriptions, we process team membership, invitations, seat counts and billing records. The team owner can see membership and company billing information. The team console does not display employees’ dictated text.
We also record technical usage and cost information, such as the operation and model used, request and retry status, provider request identifiers, billable audio duration, input and output token counts, and estimated processing cost. These records can be associated with your account or guest identifier and your active company membership. They help us operate the service, understand costs and investigate reliability or abuse. The new usage and cost records do not contain audio recordings, transcripts or prompts.
Company roles and security events
Access to company records is role-based. Owners and administrators can view the company roster and invitations; owners and billing managers can view company billing; owners, administrators and auditors can read and export company audit events. Ordinary members see their own access status. These permissions do not reveal members’ dictated content, personal saved tools or device-local history in the Teams console.
Company security records include event times and types, company and actor account identifiers and limited operation metadata such as roles, target IDs and counts. Customer-facing views and exports exclude dictated content, prompts, email addresses, invitation secrets and credentials. Application access cannot edit or delete audit records, and exports are logged. No fixed automatic deletion deadline is published for this security history; the 90-day detailed AI cost-record cleanup is separate. Security and billing records may remain after account closure. Contact support about access, retention or deletion requests. See company separation and audit access and export limits.
Typing and keyboard permissions
Aivo does not upload a continuous stream of everything you type. Audio you submit, text you ask to process, saved vocabulary and correction information can be used for the corresponding features. The iPhone keyboard needs Full Access for communication with the app and network-dependent dictation. Mac needs microphone and Accessibility permissions to capture dictation and insert text.
2. Services we use
We require third-party service providers that process personal data on our behalf to provide at least the same level of privacy protection as described in this policy. OpenAI’s API services terms and Data Processing Addendum provide these contractual protections for personal data sent for transcription and text processing, including requirements for confidentiality, security, processing instructions and comparable protections at subprocessors.
OpenAI’s published API terms and Data Processing Addendum describe its obligations as a provider. Aivo’s customer contract and data processing agreement are separate documents. Confirm the legal parties, scope and processing configuration that apply to the offer; links to provider policies do not establish a particular processing region or retention setting.
- OpenAI: transcription and text processing. Its API services terms restrict use of customer content, and its Data Processing Addendum sets confidentiality, security, processing-instruction and subprocessor-protection obligations. These are the contractual protections for the personal data sent to OpenAI. API content is not used to train models by default unless the customer explicitly opts in; this describes OpenAI’s published default, not a separate audit of every account setting. Retention varies by endpoint and configuration, including possible security and abuse-monitoring retention. See OpenAI’s API data controls. These protections do not establish EU-only processing or universal zero retention.
- ElevenLabs: audio and language information for speaker-labelled transcription in an explicitly enabled company Notetaker pilot, after its separate acknowledgement. It is a separate processing route from ordinary dictation. Review the pilot processing notice and the service inventory for its scope and retention limits.
- Microsoft Entra: optional company authentication when configured and used in an updated SSO-capable app. See Microsoft’s privacy statement.
- Supabase: account-related records, saved vocabulary, preferences and service data.
- Railway: backend hosting and operational logs.
- RevenueCat and Apple: iPhone subscription management and purchase verification.
- Stripe: Mac and company subscription payments, billing information and invoice access. Payment details are handled by the payment provider.
- Vercel: website hosting and technical request information. Website analytics count public page views and iPhone/Mac download-link clicks, including page and language. These clicks are not confirmed installations or subscriptions. We do not attach account details or form contents; page query strings and fragments are removed. Analytics are skipped when your browser sends Do Not Track or Global Privacy Control.
The iOS app includes attribution and diagnostic integrations, including TikTok and Meta/Facebook SDKs. These SDKs can collect app launches, installs and purchase events with device or advertising identifiers for analytics and advertising measurement, depending on SDK configuration and applicable platform permissions. Apple’s tracking permission can be managed in iOS Settings.
We use operational information to maintain reliability, investigate errors and prevent abuse. Operational and device diagnostic logs are separate from usage and cost records. From 1 November 2026, new first-party server application log messages use allowlisted technical metadata instead of dictated text, prompts, saved vocabulary, account emails, private URLs or raw provider error bodies. The new Mac and iPhone app updates apply the same content-minimizing diagnostic approach once installed. Older installed app versions can still include text excerpts or error details; check the linked rollout status before relying on device diagnostics. Older server/platform records are not erased by the rollout, and external providers have their own retention. Separate operational records can retain validated opaque device IDs, while usage and cost records can retain account/team attribution; this is not a promise that all records are anonymous. Retention can differ from the 90-day detailed cost-record cleanup. See the current logging rollout status and review diagnostic information before sharing it with support. If you contact support, we also process what you send us.
Our Teams data-handling guide explains the data flow, owner/member visibility, service providers and requirements to review before workplace rollout.
3. Where processing happens
Aivo’s current production processing route is global. Cloud providers can process information in different locations. Aivo does not currently guarantee exclusively EU-based processing or that no data is transferred outside the EU. Contact us before using Aivo where your organization requires specific hosting, retention or contractual arrangements.
4. Retention and deletion
Detailed AI request usage and cost records are scheduled for deletion after 90 days. Account records, subscription records, usage counters and saved vocabulary are retained as needed to provide the service and meet applicable obligations. Local recent history remains until it is removed or displaced by the app’s history limit. Payment providers retain billing records under their own policies and legal obligations. Provider processing and operational retention can differ from local app storage.
You can remove saved content in the app and request account deletion or assistance at team@aivolabs.eu. Some billing or security records may need to be retained after an account is closed.
5. Your choices and rights
You can manage microphone, keyboard, Accessibility and tracking permissions in your device settings. Depending on applicable law, you may have rights to access, correct, export or delete personal information, withdraw consent where processing relies on it, and complain to a relevant data protection authority. Contact us to exercise a right or ask how your data is handled.
6. Children and updates
Aivo is not directed to children under 13. Contact us if you believe a child has provided personal information. We may update this policy as the service changes; the date above identifies this version.