Privacy Policy
Draft for review · 14 October 2026
This policy explains personal-data handling across Weeve for Mac, Weeve for Chrome and getweeve.io. It covers free and paid individuals, team members, business contacts and website visitors. The same core privacy boundaries apply regardless of who pays for your seat.
At a glance
Core recording, transcription, speaker recognition and local summaries run on your device. Weeve does not host that local library.
Accounts, subscriptions, usage accounting and support use online services.
If you choose external AI, relevant text leaves your device for that provider. Text protection reduces exposure but does not guarantee anonymity.
A company-paid seat does not give an administrator access to your recordings or transcripts.
We do not sell personal data or use your recordings, transcripts or notes to train AI models.
You control local files. We handle requests concerning the account-side data we hold.
1. Who is responsible
Weeve B.V., MediArena 2, 1114 BC Amsterdam-Duivendrecht, Netherlands (KVK 42068756), is an independent controller where it determines the purposes and means for its own business relationship, billing, service communications, security, product analytics and website processing. This is separate from any processing carried out on an organisation’s documented instructions under its business agreement.
For work recordings, your organisation normally decides the purpose and means of processing. It must explain its own recording, monitoring, retention and sharing practices. A personal user must also follow the laws that apply to their use.
Where Weeve processes personal data on an organisation’s instructions for seat administration, associated service communications or approved support, that organisation is controller and Weeve is processor. The integrated processing terms in the applicable business agreement define scope, instructions, safeguards and return or deletion. These are section 6 of the standalone Business Terms and section 10 of the website Terms of Service. Additional processing outside that scope must first be agreed in writing. Supplying local software alone does not give Weeve access to, or make it a processor of, locally held recordings. This privacy notice does not authorise processing by itself.
Privacy and legal: stefan@getweeve.io. Privacy requests, account deletion and support: support@getweeve.io.
2. Information used to run your account
We use service and onboarding email providers, including Loops, to deliver sign-in, account and product-use messages. Message-related personal data can include your email address, relevant account information and delivery records. Service emails do not contain the local meeting library. Optional marketing communications follow applicable consent and opt-out rules; receiving a service email does not mean you have agreed to marketing.
Account details: your email address and account identifier. Sign-in uses one-time email codes; we do not store a Weeve password.
Session information: short-lived access tokens and refresh tokens. Mac tokens are stored in the device’s Keychain. Extension tokens and sign-in details are held in Chrome extension storage.
Subscription information: plan, billing status, trial dates, payment references and Stripe customer ID. Stripe handles payment card details; Weeve does not receive your full card number or CVC.
Usage accounting: qualifying recordings and imports counted against your allowance across the app and extension. The standard free allowance is 10 in total, with recordings of at least five minutes counted. These are counters, not recording contents.
Business administration: buyer and billing contacts, organisation details, authorised account or domain scope, seat rosters, entitlement changes, activation dates, seat counts, invoices and service selections.
Support and workshops: contact details, correspondence, issue categories, booking information and material you choose to supply. Prefer synthetic or redacted examples.
Technical and security data: network information such as IP addresses, device and software details, and service logs needed for delivery, authentication and abuse prevention.
3. Recordings and other local content
On your Mac
Recordings, transcripts, speaker labels, summaries, notes, moments, templates, projects, people and saved chat content are held locally. The content library can be moved under Settings → Data & Storage → Where your data lives.
Downloaded models, device preferences, logs, credentials and encrypted biometric data have separate device-level locations. Moving the content library does not move those items. A cloud-synchronised folder can upload library files through your chosen provider; Weeve does not control that provider’s copies or backups.
The app normally retains source audio for playback. Turning off Keep recording audio affects new recordings; it does not delete audio already saved. Local recordings and notes are not automatically encrypted by Weeve. macOS permissions and FileVault, if enabled, provide separate protection.
In Chrome
The extension stores audio in its private browser storage and transcripts, actions, speaker labels, people and recording details in its local databases. Downloaded models and preferences also use the browser profile. Websites and other extensions do not have ordinary access to this extension-scoped storage.
Choose whether to include your microphone before recording. With it off, the extension does not request or capture microphone audio. Tab capture requires you to invoke Weeve on the selected tab. Recordings and people shown are scoped to the signed-in Weeve account.
Local hand-off and sharing
With the Mac bridge enabled and the same account signed in, the extension can exchange recordings with the Mac app on the same computer. That connection does not use the internet or our servers. Copies and subsequent edits can exist in both applications.
Shared storage is a customer-controlled data flow. It does not create shared in-app projects or safe simultaneous editing. You and your organisation control file permissions, exports, backups and retention. Weeve’s use of Chrome API information is subject to the Chrome Web Store User Data Policy, including its Limited Use requirements.
4. Voiceprints and speaker recognition
When you associate a speaker with a person, the Mac app can store a voiceprint and speaker embeddings to recognise that person in later recordings. Automatic speaker recognition is enabled by default. This is biometric processing and may involve special-category data when used to identify a person.
Voiceprints and embeddings are encrypted with AES-GCM using a device-local Keychain key.
They are stored outside the movable content library and do not follow it into a shared or synced folder.
They are scoped to the account on that device. Weeve does not upload, sync, share or log them, or use them for model training.
You can turn automatic recognition off in Settings → Preferences, remove a person’s voice samples in People, or remove local data in Settings → Data & Storage.
Device-local storage does not remove your legal obligations. Users and organisations must establish a lawful basis and any required special-category condition, inform people and respect their rights. Turning recognition off does not by itself delete existing samples.
5. Optional external AI and integrations
Optional beta chat and agentic tasks relate to recordings, transcripts and meeting notes. They can retrieve relevant local text and use it to produce answers or task results. You control the instructions and available permissions. Local execution and optional cloud execution have different data flows; review the selected mode before use. Features and tools depend on the version and agreed scope.
Local AI and external AI are different workflows. Where offered, you can deliberately connect ChatGPT through your own account or Claude through your own API credentials. External processing is not required for the core local recording and transcription workflow.
What may be sent: your prompt, conversation history, relevant text retrieved from recordings or notes, and follow-up context needed to answer. Provider authentication, model requests and normal connection metadata also go to that provider.
Recipients: OpenAI for ChatGPT and Anthropic for Claude, when selected. Your provider agreement, account settings, retention rules, processing locations and charges apply. Do not assume a provider promises zero retention or no training for every account type.
Text protection: the app can replace detected personal details with aliases before transmission and restore them locally in the answer. Detection can miss indirect or unfamiliar identifiers. This is pseudonymisation, not guaranteed anonymisation.
Your choices: select local processing to avoid this external-AI flow. Disabling protection, or reducing its categories, can send original or less-protected text. Disconnecting a provider does not erase information it already received.
External chat sends assembled text, not unrestricted access to your device library. Your organisation must authorise use of external providers with its information. Buying Teams does not promise central enforcement of those settings. Review the relevant OpenAI or Anthropic privacy information before use.
Other optional integrations, exports and customer-selected storage may also disclose information to the destination you choose. Weeve’s no-training commitment governs Weeve’s own use; independently selected providers are governed by their own terms.
6. Team administration and support access
For organisation-funded access, we obtain enrolment and billing information from the authorised administrator and from account activity needed to manage seats. We use the approved scope, including any exclusions, to enable access and calculate charges. A matching email domain alone is not an instruction to enrol someone.
The administrator may receive the roster, paid-access status, relevant seat dates and billing or seat-usage information needed to manage the subscription. This is not a right to receive recordings, transcripts, prompts, private notes or biometric data. An employer may separately control your device or storage; ask it about those arrangements.
Seat removal, sign-out and cancellation do not remotely erase local files. Your organisation is responsible for offboarding, device access, approved sharing and retention.
Support normally uses synthetic or appropriately redacted material. Do not send production recordings, transcripts, voiceprints or sensitive screenshots through ordinary support channels. Exceptional access requires prior documented approval of its purpose, scope, data types, categories of people, access controls and deletion arrangements under the applicable integrated processing terms or separately agreed DPA. Support access is not automatic with a paid seat or Enhanced Support.
7. Product analytics and website cookies
Product analytics
We use EU-hosted PostHog for feature-use and reliability events. Examples include app launches, recording starts, model downloads, onboarding steps and error categories. Events include technical context such as app version and platform, not recording contents.
Mac events use a SHA-256 hash of the signed-in Weeve account ID, or a random device identifier while signed out. Sign-in can link earlier device activity with the hashed identifier. This is pseudonymous personal data, not anonymous statistics. This hashing applies to analytics; account services still use account identifiers.
The extension uses a separate PostHog project with its own hashed or random identifiers. App and extension events are not combined into one analytics profile. Analytics exclude recording text, prompts, notes, recording titles, speaker names, email addresses and the URL of the recorded tab.
Chrome: turn off Product analytics in Settings → About. This stops new submissions, drops queued events and clears local analytics identifiers. It cannot retract events already received. Re-enabling while signed in may link new events to the same account hash.
Mac: if your version has no in-app analytics switch, email support@getweeve.io to object and request assistance. We will assess and action your objection and explain any device-side steps needed; we do not claim to remotely control local settings.
Website measurement
With your marketing-cookie consent, Google Tag Manager loads Google Ads, the LinkedIn Insight Tag and Meta Pixel for advertising measurement and remarketing. These can receive IP addresses, browser and device details, visited pages, referral information, advertising identifiers and conversion events.
Google and LinkedIn act as independent controllers for relevant advertising processing. Weeve and Meta act as joint controllers for certain collection and transmission of Meta Pixel data. The Mac app and Chrome extension do not contain those advertising trackers. Change your choice through Cookie settings in the website footer. See the Cookie Policy.
8. Why we process personal data
Purpose | Legal basis |
|---|---|
Provide an individual account, paid plan and requested support | Performance of our contract with you, where necessary (Article 6(1)(b) GDPR). |
Administer organisation accounts, business contacts, seats and invoices | Legitimate interests in delivering and administering the organisation’s contract (Article 6(1)(f)); contract where the individual is directly a party. |
Understand product use and improve reliability | Legitimate interests, subject to a balancing assessment and the right to object. Where consent is legally required, it must be obtained. |
Security, fraud prevention and handling claims | Legitimate interests in protecting users and the service; legal obligations where applicable. |
Tax, accounting and required records | Legal obligation (Article 6(1)(c)). |
Marketing cookies and advertising measurement | Consent (Article 6(1)(a)) and applicable cookie rules. |
Processing instructed by a business customer | The customer determines its lawful basis; Weeve follows the applicable DPA and lawful instructions. |
Providing a privacy notice or accepting terms is not consent to every use of personal data. Optional cloud providers apply their own legal bases and notices. For local recordings and biometric identification, the responsible user or organisation must establish the basis and any additional condition that applies.
9. Providers and recipients
The providers below support the service. Roles depend on the specific activity; an independent provider is not automatically a subprocessor for every customer.
Provider | Purpose |
|---|---|
Supabase | Account authentication, subscription metadata, usage counters and app update delivery. The account service is hosted in the EU. |
Loops | Service, authentication and onboarding emails. Receives recipient contact details and the account or delivery information needed for those messages. It does not host the local meeting library. |
Stripe | Payments and subscription management. Its role depends on the payment activity, including its own legal and fraud-prevention obligations. |
PostHog | EU-hosted pseudonymous product analytics. |
Hugging Face | Direct downloads of certain Mac AI models. It receives download connection data such as IP addresses under its own terms. |
Cloudflare | Delivery of models and related assets from Weeve’s CDN, including extension models and optional Mac feature assets. Downloads expose connection metadata. |
Framer | Website hosting and delivery. |
Notion | Feedback forms, when used, and business deal or support administration, including contacts, draft agreements and documents provided for that purpose. |
Google Workspace | Support emails, correspondence and attachments. Operated by Google Cloud EMEA Limited with Google LLC and listed affiliates for the relevant services. |
Google, LinkedIn and Meta | Consent-based website advertising measurement and remarketing, as described in section 7. |
OpenAI and Anthropic, only if selected | External AI requests through the user’s connected account or credentials, as described in section 5. |
Your chosen storage and integration providers | Files or outputs you deliberately place in, send to or synchronise through those services. |
We use appropriate contracts where a provider processes data on our behalf. We may disclose necessary information to professional advisers, authorities where legally required, or to protect legal rights. These disclosures do not imply routine access to the local recording library.
The applicable business processing terms require disclosure of actual subprocessors, functions, processing countries and transfer safeguards before processor services begin. The Customer gives general written authorisation under those terms. Unless separately agreed, an undisclosed subprocessor or later addition or replacement requires at least 14 days’ advance email notice, with an opportunity to object on specific, reasonable data-protection grounds. An objected-to provider is not used for the Customer’s data while the objection remains unresolved. The agreement sets the resolution and termination process. This privacy notice is not itself a blanket authorisation.
The initial business subprocessor disclosure identifies Supabase Pte. Ltd., Astrodon Corporation (Loops), Google Cloud EMEA Limited (Google Workspace) and Notion Labs, Inc., their functions, processing locations and transfer safeguards. It is section 6.1 of the standalone Business Terms and section 10.1 of the website Terms of Service. It distinguishes those Customer-instructed activities from Weeve’s own controller services and independently selected AI or storage providers. Those business disclosures, not this general provider table, govern contractual authorisation.
10. Processing outside the EEA
Some providers and their support operations process information outside the EU/EEA. EU hosting does not by itself mean there is no international transfer. Relevant locations may include the United States, depending on the provider, account and feature.
Where Weeve is responsible for a restricted transfer, we use the safeguards required by law, such as a valid adequacy decision or Standard Contractual Clauses with any necessary supplementary measures. A Data Privacy Framework route applies only where the actual recipient and processing are covered by a valid certification. Contact us for the safeguards applicable to your data.
For your independently chosen cloud AI, storage or other services, check the provider’s locations and transfer terms. Business processing is also governed by the applicable DPA and transfer arrangements.
11. Retention and deletion
Information | How long or how to remove it |
|---|---|
Account and authentication data | While the account is active. After a valid deletion request, we delete or genuinely anonymise account-side personal data from active systems within 30 days. We retain only records required by law and limited information lawfully necessary to establish, exercise or defend legal claims, and only for as long as necessary. Retained information is restricted to those purposes and is deleted when no longer needed. |
Invoices and tax records | For the legally required period; Dutch basic accounting records generally require seven years. |
Business contacts, seat records and correspondence | For the relationship and as necessary to administer charges, legal obligations or claims. We remove operational records when they are no longer needed. |
Product analytics | Weeve’s maximum is 24 months from collection. We periodically purge events to enforce that limit; it is not a PostHog default. A valid account-erasure request causes earlier deletion of linked events as explained below. |
Website cookies | According to the cookie or technology; see the Cookie Policy and your cookie settings. |
Exceptional support content | Only for the purpose and deletion period agreed before access, subject to applicable legal duties. |
Local recordings, notes, chat and models | Until you remove them from each device or storage location. Weeve does not centrally delete or back them up. |
External AI or independently selected storage | According to that provider’s policy and your settings. Disconnecting it does not itself erase earlier copies. |
For data processed on a business Customer’s instructions, the integrated processing terms require return or deletion from active systems, at the Customer’s choice, within 30 days after the relevant services end, unless retention is legally required. Residual provider copies, including backups, are isolated from ordinary use and removed within 180 days after those services end. Provider deletion is initiated promptly; if data is restored for disaster recovery, deletion is reapplied before ordinary use. Written confirmation is available on request. This is separate from Weeve’s controller records and does not delete customer-held files.
Analytics erasure
A valid account-erasure request includes the associated analytics profiles and their linked events in the separate Mac and Chrome projects. We use PostHog’s event-deletion process and verify completion; deleting a profile alone or retaining an account hash is not anonymisation. We include associated device identifiers that we can identify. We do not keep those events until the 24-month limit. Genuinely anonymous aggregate statistics may remain only where people can no longer reasonably be identified.
Requests and residual copies
Email support@getweeve.io to request deletion of Weeve-held account data. The current Mac “Delete account” action deletes local content and signs out; it does not itself delete the hosted account or historical analytics. Online erasure is handled through the request process. Isolated residual backup copies of erased controller data are removed within 180 days of the request and are not used for ordinary processing. Deletion is reapplied before any restored data returns to ordinary use. The narrow legal-record and legal-claims exceptions above apply only for as long as necessary.
Managing local copies
On Mac, use Settings → Data & Storage → Manage local data for recordings and related local data. Remove model files through the model controls. Check other folders, chat histories, exports and backups separately.
In Chrome, use recording and account-library deletion controls. Signing out hides the account library but retains its files. Shared downloaded models have separate removal controls.
Older extension recordings without an account owner stay outside account libraries until you choose to recover copies. Recovery leaves the originals unchanged.
Uninstalling the extension or deleting its browser profile removes extension-local content, including content retained for other accounts. It does not erase exports or copies already transferred to the Mac.
Deleting your online account, removing a paid seat and cancelling a subscription are separate actions. None gives Weeve remote access to erase files on your devices.
12. Your choices and rights
Depending on the law and circumstances, you can request access, correction, deletion, restriction, portability and objection to processing. You can withdraw consent without affecting processing that was lawful before withdrawal. You may object to legitimate-interest processing, including product analytics.
Send requests to support@getweeve.io. We may need reasonable information to verify identity. We normally respond within one month. If the law permits an extension for a complex request, we explain why within that first month. Our account-deletion process is described in section 11.
If a recording or an organisation’s workplace practices concern you, contact the person or organisation responsible for them. We can respond for data we hold, but cannot retrieve or erase a customer’s local library. Where we are a processor, we assist the customer under its DPA.
You may complain to the Dutch Autoriteit Persoonsgegevens or the supervisory authority available to you under applicable law. Contacting us first is welcome, but not required.
13. Security and incidents
Connections to our online account services use HTTPS/TLS. Authentication uses one-time codes and session tokens.
Mac account tokens and biometric keys use device-local Keychain protections. Extension sign-in data uses browser-profile storage.
Voiceprints and speaker embeddings are encrypted at rest. This does not mean that all local content is app-encrypted.
We use access controls and provider security measures for online systems. Device security, backups and access to customer-selected storage remain your responsibility.
No system is perfectly secure. As controller, we notify the competent authority without undue delay and, where feasible, within 72 hours after awareness where notification is required. We notify affected people without undue delay where there is likely to be a high risk, subject to legal exceptions. As processor, we notify the Customer without undue delay. Under our business terms we also notify the Customer without undue delay of a confirmed security incident materially affecting Customer Content or the security of its service, provide available details and updates, take reasonable containment and remedial action, and cooperate with the Customer’s required response. We promptly communicate material software vulnerabilities requiring customer action and available mitigation guidance. Support hours do not limit these duties.
14. Children, updates and contact
Weeve is not intended for users under 16. If you believe we hold a child’s personal data unlawfully, contact us so we can investigate and take appropriate action. Users remain responsible for permissions when recording other people, including children.
For material policy changes, we provide at least 14 days’ notice by email and/or in the app or extension before they take effect, unless a legal requirement requires another timetable. New consent is requested where required. Updating this notice does not amend a signed customer agreement or retroactively authorise a new use of data.
Weeve B.V. · MediArena 2, 1114 BC Amsterdam-Duivendrecht, Netherlands
KVK: 42068756
Privacy and legal: stefan@getweeve.io
Support and privacy requests: support@getweeve.io