Aivo for Teams · Handbook

Understand the data before rollout.

A factual overview for team owners and workplace reviewers. Read it alongside the privacy policy and confirm any required arrangements with Aivo before rollout.

Security and privacy at a glance

  1. Cloud dictationAivo sends submitted audio to OpenAI for transcription. The live service processes data globally.
  2. History on your deviceRecent dictations can be saved on the device. On supported app versions, members can limit new local history. Provider retention is separate.
  3. Company accessRoles control access to company records and audit events. The Teams console does not show employees’ dictated text or personal tools.

What leaves the device?

  1. You choose whether to allow AI processing.The new app updates explain the OpenAI data flow and ask for permission before dictation or AI writing. Aivo records and submits your dictation only after permission and a separate recording action.
  2. Aivo requests transcription.Audio is sent to OpenAI. Selected languages and relevant personal dictionary vocabulary may accompany the request.
  3. Optional text processing runs.Writing modes and applicable Norwegian normalization send text, instructions and relevant vocabulary through Aivo to OpenAI.
  4. Text returns to your app.You review it before sending. Usage accounting, account synchronization and diagnostic logging are separate from local history.

Each member makes this choice for their own Aivo account on each device. A company subscription or Microsoft sign-in does not grant it for them. Choose Not now to leave AI processing off; saved tools and account management remain available. Review or withdraw in iPhone Settings → AI processing. On Mac, open Settings, find AI processing with OpenAI in the Privacy section, and choose Review or Withdraw. Withdrawal stops new work and pending local flows, but cannot recall data already sent. It preserves history, counters and paid access. The current public releases are Mac 1.0.25 (build 36) and iPhone 2.2.14. The iPhone update was released on 11 November 2026 and includes the AI-processing and privacy/history controls described here. Check availability before relying on them. Older installed versions are unchanged.

For ordinary dictation, the server processes transcription uploads in memory and does not maintain a library of dictation recordings. Devices use temporary audio files. Mac Notetaker saves recordings separately from dictation history; confirm the storage, processing and retention arrangements for any enabled company pilot before using it. These distinctions do not establish immediate erasure after every interruption or zero retention across all service providers.

Optional Microsoft Entra sign-in.

Company sign-in is an optional, administrator-assisted rollout. Contact Aivo before activating a tenant; the setup guide gives app availability, linking steps and external-tenant limits. It is not automatically enabled for existing companies.

Microsoft authenticates the work identity. Aivo verifies the token signature, tenant, app and sign-in request, and uses the stable Microsoft tenant ID and object ID to identify the linked Aivo account. When a new member confirms an eligible private invitation, Aivo creates their account and adds them to the team. Email and display name do not merge accounts. Aivo retains the account’s Microsoft identity mapping so a new eligible invitation for that same identity can restore access to the same account after removal.

The flow requests openid profile, without 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 sign-in. Microsoft still processes authentication identifiers and browser/network information under its own policies.

Aivo keeps identity links and flow/session records needed for authentication and revocation. Sign-in flows expire after 10 minutes; company sessions last up to eight hours. Expiry is an access limit, not a promise of immediate physical deletion. Provider tokens are validated in the server flow rather than kept as a library of Microsoft tokens or returned to the apps.

Apple sign-in and existing personal subscriptions remain available. This phase does not include enforced SSO, SCIM, automatic directory provisioning, centralized device-content controls or verified immediate directory-driven offboarding. Remove departing members through Aivo; their separate personal subscriptions and local content need their own treatment.

Technical diagnostics, without dictated content.

New first-party server application messages use allowlisted technical metadata: fixed event names, timings, counts, HTTP status, safe error categories and generated request identifiers. They exclude dictated text, prompts, saved vocabulary, account emails, private URLs and raw provider error bodies.

The new Mac and iPhone app updates apply the same content-minimizing approach to their diagnostic messages. Protection applies after the relevant update is installed; older installed versions and historical server/platform logs may still contain excerpts or error details. Check update availability. The iPhone update also clears an obsolete correction-debug buffer without deleting saved vocabulary or lifetime totals.

Diagnostic messages are separate from saved history and from the content the service must process to transcribe or rewrite. Account/team usage attribution and validated opaque device identifiers can remain in separate operational records. This is not a promise that all records are anonymous, that old logs were purged, or that provider retention changed. The 90-day detailed cost-record cleanup does not apply to every log. Review any support bundle before sharing it.

Account-bound history and local-content choices.

In the updated apps, new recent history and pending results are bound to an Aivo account and local session. Late results from another account are rejected. History remains device-local; it is not a shared company archive. See the switches, release availability and recovery steps.

Mac: Don’t save new history stops new recent-history entries and the last-result buffer, with normal-path temporary-audio cleanup after upload data is prepared. iPhone: Limit saved dictation content also stops automatic correction learning and prevents correction/undo text from carrying into the next keyboard session, with cleanup in normal completion and cancellation flows. The settings are off by default and apply to the current account on that device, not centrally to all company members.

Existing recent history and earlier recovery archives remain until separately removed. Unknown earlier entries are preserved instead of being assigned to whichever account signs in first. Reviewing or exporting the preserved archive requires device-owner authentication: Face ID, Touch ID or passcode where supported on iPhone; the Mac’s supported device-owner credentials on Mac. Recovery requires an explicit selection and does not increment lifetime word totals.

These are bounded local controls. They do not guarantee cleanup after every crash, remove copies in other apps or the clipboard, control operating-system backups, stop cloud processing or establish provider-wide zero retention. An owner removing a team seat does not erase the person’s local content.

What is saved, and where?

CategoryWhere / purposeRetention and controls
Temporary dictation audioDevice recording files; Aivo and OpenAI process submitted audio.Recording files are cleaned up in normal app flows. Provider handling follows its terms and configuration; no universal zero-retention guarantee.
Recent dictated textLocal app history, separate from lifetime word totals and feature sync.The updated apps keep recent history per account, up to the app limit. Optional local-content switches stop new saved history; existing entries and preserved earlier archives require separate removal. See local-content controls and limits.
Personal dictionary, snippets and custom modesDevice storage and account synchronization through Aivo/Supabase.Kept for the account until removed or dealt with through an account request. Saved entries may themselves contain personal or confidential text. They are not shared team collections.
Identity, membership and accessApple sign-in identifiers, account/relay email, team, invitations, seats, subscription status and usage counters. Optional Microsoft sign-in also uses tenant/object identifiers, identity links, sign-in flow and session records.Kept as needed to provide account access, operate billing and meet applicable obligations. Removing a seat is not account deletion.
Detailed AI usage and estimated costsAccount/guest and active-team attribution, model, request/retry status, timing, audio duration, token counts and estimated cost.Scheduled cleanup targets records older than 90 days. These records have no audio, transcript or prompt fields. This is not the retention period for every other log or record.
Operational diagnostics and supportApp/server error and diagnostic logs, plus information you choose to send support.New first-party server and updated-app messages use allowlisted technical metadata. Older app versions and historical records may contain content; see the diagnostic rollout details. Retention can differ from cost telemetry. Review diagnostic bundles before sharing them with support.
Payments and invoicesStripe for company/Mac purchases; Apple and RevenueCat for iPhone purchases.Payment providers retain billing records under their policies and applicable obligations. Deleting an Aivo account does not automatically delete all provider records.

Cloud backup and operational-log deletion windows depend on the provider and account configuration. Aivo does not publish a verified, universal deletion deadline for every copy or service. Ask us to confirm required retention, backup and export arrangements before relying on them.

Who can see what?

Owners and administrators can see the company roster, names, account or Apple relay emails, roles, joining dates and pending invitations. Owners and billing managers can access company billing details and invoices. Owners, administrators and auditors can review and export the company security-event log. Ordinary members see their own team/access status. Read the role matrix.

No company role opens employees’ dictated text, device-local history, personal dictionary, snippets or custom prompts in the Teams console. Aivo and its service providers still process the information needed to operate the service, including submitted dictation. Console permissions do not establish that no provider processes or retains content. Central device-content controls, enforced SSO and SCIM are not included.

Company separation on shared infrastructure.

Company records are logically separated by company ID and verified membership. The server and protected database operations check the caller’s current role and the requested company before returning company data or changing members, invitations or roles. Knowing another company’s ID, invitation ID or member ID does not grant access to it. Audit queries and exports are restricted to the authorized company.

Aivo uses a shared backend and database, not a dedicated database, server or encryption key for each customer. Operational service access remains privileged; these controls are not a claim of physical isolation or independent certification. Personal saved tools remain bound to the person’s account rather than becoming a shared company collection. This change does not alter dictation providers, processing locations or their retention.

Review and export company audit events.

Owners, administrators and auditors can open the company audit section in the Teams console, filter events by type and date, and load more results. Events cover company setup, invitations, membership and role changes, supported billing and company-sign-in actions, recorded denied actions and audit exports. This is an operations log, not a recording of everything someone does in an app.

Visible events contain a timestamp, event type, actor account ID when available and allowlisted operation metadata such as a target account ID, role or count. They do not display dictated text, audio, prompts, saved vocabulary, email addresses, invitation secrets or credentials. Older stored events are filtered through the same safe view; publishing this view does not purge historical backend records.

The audit API returns at most 100 events per page. CSV and JSON exports contain the newest 1,000 matching events at most and identify truncation when more remain. Narrow the date or event filter for a smaller export. Permission is rechecked for each export page and before delivery. Limits are 60 audit reads and five exports per signed-in account per minute. An export is a filtered company-event file, not a complete personal-data export or a guaranteed point-in-time archive.

Company audit records are append-only through ordinary application access. Administrators cannot edit, delete or truncate them; the export itself is logged. Aivo has not published a fixed automatic deletion period for these security records. The separate 90-day detailed cost-record cleanup does not apply to them. Security records, including account IDs, can remain after account closure; contact support about retention and deletion requests. Privileged maintenance and legal obligations require separate handling. These controls are not a universal zero-retention or tamper-proof-storage guarantee.

Services involved.

This is a practical service inventory, not a signed subprocessor schedule or data processing agreement.

ServiceRole and data involved
ElevenLabs ScribeSpeaker-labelled transcription in the separately enabled company Scribe pilot. This workflow requires pilot access and its own processing acknowledgement. Review the agreed scope and provider arrangements in the procurement information. Procurement information
OpenAISubmitted audio and relevant vocabulary for transcription; text, instructions and relevant vocabulary for writing/normalization. API data controls and endpoint-specific retention.
RailwayAivo backend hosting, request processing and operational logs. Provider privacy information.
SupabaseAccount records, personal feature synchronization, team membership, usage and service data. Provider privacy information.
StripeCompany and Mac checkout, billing contact details, subscription and invoice records. Provider privacy information.
Microsoft EntraOptional company authentication when configured and used with an updated SSO-capable app. Tenant/object identity and sign-in protocol data are separate from dictation processing. No Microsoft Graph, mail or document permissions are requested. Microsoft privacy information.
Apple and RevenueCatApple sign-in and iPhone purchase verification/subscription management. Apple privacy · RevenueCat privacy.
VercelPublic website hosting and technical requests. Website download-link clicks are not confirmed installations. Provider privacy information.
iOS attribution/diagnostics integrationsThe iPhone app includes TikTok and Meta/Facebook SDK integrations, including automatic install/launch and purchase-event measurement with device or advertising identifiers. Behavior depends on SDK configuration and platform permissions; review the privacy policy and iOS tracking controls.

Provider policies do not by themselves confirm Aivo’s account settings, contractual arrangements or your organization’s approval. Specific model, region and retention requirements must be confirmed for the complete service.

Controls available to owners and members.

  • Members use their own Aivo account and personal synced tools. A company administrator must set up Microsoft sign-in. Eligible new members join through a private invitation, while existing users link from their signed-in Aivo account.
  • Owners create, revoke and privately share single-use invitations. The contact email is not an acceptance restriction. Read invitation handling.
  • Browser pairing codes expire after 10 minutes and console sessions last up to eight hours. Sign out of shared browsers.
  • Device settings control microphone, iPhone keyboard/Full Access, Mac Accessibility and applicable tracking permissions.
  • The new per-account local-content switches and separate recent-history controls require the updated app. They do not erase earlier archives or change provider handling. Read the local-content boundaries.
  • Remove a departing member in Aivo and handle personal renewal and saved content separately. No SCIM or central device erasure is provided.

Use the company roles to delegate membership, billing and audit access. Administrators can handle invitations and ordinary members; only the owner assigns roles. Check each permission and the company audit log before rollout. These permissions do not provide a shared company dictionary or central erasure of personal devices.

Deletion, exports and support requests.

Remove saved dictionary entries, snippets and local history using the app’s controls. iPhone provides account deletion; company owners need support to resolve ownership and billing first. Cancel any continuing paid renewal separately. For personal-data access, export, correction or deletion assistance, email team@aivolabs.eu.

There is no documented self-service full personal-data export or guaranteed export turnaround in this guide. Account closure, deleting local history, ending company access, provider-record retention and cancelling renewal are distinct. Billing or security records may need to remain after an account closes.

Before your workplace approves the workflow.

Start with a non-sensitive example. If you need to use restricted information, first agree the requirements with your organization and confirm them with Aivo:

  • Which data categories and writing tasks are approved, and whether confidential, client, deal or patient information is excluded.
  • Required data processing terms, service providers, international-transfer arrangements and locations of processing/storage.
  • Audio/text handling, diagnostic content, provider retention, backup deletion windows and export/deletion procedures.
  • Who may administer the company, how invitations are shared and how departing colleagues’ access and local content are handled.
  • Any required security evidence, incident notification process, service commitment or sector-specific assessment.

Aivo does not currently guarantee EU-only processing, universal zero retention or a sector-approved deployment. Optional company sign-in requires administrator-assisted setup and a supported app, with the limits described above. This guide does not establish SOC certification, HIPAA suitability, GDPR certification or an available signed DPA. Contact us about requirements before treating them as part of the offer.

For professional examples, use an ordinary scheduling email, your own non-confidential next-step note, an administrative update or a generic teaching outline. Review important wording before sending. See the privacy policy and terms for the wider service description.

Security and privacy FAQ

When is the microphone active?

On Mac, you start and stop dictation yourself. On iPhone, a microphone session you start can stay active in the background for keyboard use, including between dictations. Aivo sends the dictated audio for transcription when you finish a dictation. The privacy policy explains AI-processing permissions and which versions support them.

Privacy policy

Can Aivo read what I type?

The iPhone keyboard can use text near the cursor for formatting and, where enabled, to learn corrections. Learned words may be sent as vocabulary hints. Aivo does not upload a continuous stream of keystrokes. On Mac, Accessibility lets Aivo insert the result where you’re typing.

What is kept, and is it used for training?

Aivo processes transcription uploads in memory. Recent history can stay on your device. OpenAI retention depends on the service and configuration. OpenAI says it does not train on API content by default.

What can my company see or enforce?

Depending on their role, authorized people can see membership, billing or audit events. Members choose their local history settings on supported app versions. Aivo does not provide a company-wide control for those settings.

What happens when someone leaves?

Removing a member in Aivo ends access to the company seat and revokes related company sessions. Their personal account, any separate subscription and device history are handled separately.

Where is data processed?

The live Aivo service processes data globally. Aivo does not guarantee that processing stays within the EU. The service inventory explains what each provider handles.

What can IT review before a trial?

Review the service inventory, retention details, role permissions and audit information. Contact Aivo to discuss a data processing agreement (DPA) or other requirements, and confirm your workplace’s requirements before using restricted data.

team@aivolabs.eu

Need a hand?

Email team@aivolabs.eu with your app version, device, the time of the issue and the error message. Keep private invitation links, pairing codes, credentials, dictated content and card details out of the message.