Weaver Privacy Policy
Last updated: 14 November 2026
Who we are
Weaver is a work tool made by a small independent team. It turns scattered meeting notes into one connected picture: who was there, what was decided, and what needs doing. Our goal is to make that useful without turning your working conversations into someone else's product.
privacy@weavecompanion.com
What we collect
Account information. When you sign up we store your email address, a hashed (unreadable) version of your password, and your first name. We never store your password in plain text.
Meeting content. Transcripts you paste, files you upload, audio the Weaver mobile app captures to transcribe, and audio captured by the meeting bot when you connect a live call. These are stored on our servers because they are the material Weaver works from.
Extracted data. Weaver derives structured information from your meetings: participants, decisions, action items, project summaries, and vector embeddings used for search. This is tied to your account and used only to answer your questions and organise your projects.
Usage and billing. If you subscribe, Stripe processes your payment. We receive a customer ID and subscription status. We never see or store full card details. We log basic usage counts for abuse prevention.
Calendar data (only if you connect a calendar). If you choose to connect Google Calendar or Microsoft Outlook, Weaver reads your upcoming events. See "Connecting your calendar" below for exactly what and why.
People you send minutes to. If you email a meeting's minutes, we store the addresses you send them to. See "Sharing minutes with people outside Weaver".
Technical data. Standard server logs (IP address, timestamp, HTTP status code) retained for up to 30 days for security monitoring.
Where you came from
If you arrive through a link with campaign tags (for example from an ad), your browser remembers those tags and the website you came from (its address only, not the page) for this browser tab, in its session storage. There are no cookies, except those of the Meta pixel described below, which exist only if you accept it. If you sign up, we store them once with your new account so we can see which campaigns bring people to Weaver. The tags are not linked to a visitor before you sign up: the website only adds one to a daily count per campaign, and that count stores no IP address and no device or visitor identifier. On such a visit the website also adds to daily counts of a few page events, for example that the page was scrolled to the end, that it stayed open for 30 seconds, or which kind of link was pressed. These counts are per campaign and page and cannot be traced to a person either. Some landing pages exist in more than one version so that we can see which one works better. If you come from an ad, your browser keeps one letter (A, B or C) for 14 days in its local storage, so that you see the same version again; it identifies nobody, and the counts per version work like the counts above.
Wenn du über einen Link mit Kampagnen-Angaben kommst (zum Beispiel aus einer Anzeige), merkt sich dein Browser diese Angaben und die Website, von der du kommst (nur die Adresse, nicht die Seite), für diesen Browser-Tab im Session Storage. Es gibt keine Cookies, ausser denen des unten beschriebenen Meta-Pixels, die nur entstehen, wenn du es akzeptierst. Wenn du dich registrierst, speichern wir die Angaben einmalig bei deinem neuen Konto, damit wir sehen, welche Kampagnen Menschen zu Weaver bringen. Vor der Registrierung sind die Angaben keiner Person zugeordnet: Die Website zählt nur einen Tageszähler pro Kampagne hoch, und dieser Zähler speichert weder IP-Adresse noch Geräte- oder Besucherkennung. Bei einem solchen Besuch zählt die Website ausserdem einige Seitenereignisse in Tageszählern hoch, zum Beispiel dass die Seite bis zum Ende gescrollt wurde, 30 Sekunden offen blieb oder welche Art von Link angeklickt wurde. Auch diese Zähler gelten pro Kampagne und Seite und lassen sich keiner Person zuordnen.
Meta pixel and Conversions API (only with your consent)
On our advertising and information pages (for example weavercompanion.com, /start, /bau and the industry pages) we may use the Meta pixel to measure whether our ads on Facebook and Instagram work. It is loaded only if you click "Accept" in the banner. If you click "Decline" or make no choice, the pixel is not loaded and no data is sent to Meta. The pixel is never used in the app, at sign-in or in your meetings; the content of your meetings, minutes or tasks never reaches Meta.
Data. If you accepted, Meta receives information about your visit: the page, the time, your IP address, browser and device details (user agent), and identifiers from Meta cookies (_fbp, _fbc). In addition our server reports two events to Meta (Conversions API): that you opened the demo ("ViewContent") and that you signed up ("CompleteRegistration"). At sign-up we send your email address only as an irreversible hash (SHA-256), never in plain text. Each event also carries IP address and user agent. We send no other data.
Purpose. Measuring advertising results and improving our ads.
Legal basis. Your consent (Art. 6(1)(a) GDPR, Art. 31(1) Swiss FADP). You can withdraw it at any time with effect for the future through the "Privacy choices" link in the page footer. Withdrawal does not affect the lawfulness of processing before it.
Recipient and responsibility. Meta Platforms Ireland Limited, Merrion Road, Dublin 4, Ireland. Under the CJEU's Fashion ID judgment we and Meta are joint controllers for collecting the data and passing it to Meta; Meta alone is responsible for what it does with it afterwards (see Meta's data policy and Business Tools Terms).
Third countries. Meta may transfer data to the USA. Meta participates in the EU-US Data Privacy Framework; for Switzerland the Swiss-US Data Privacy Framework applies.
Retention. For the pixel, Meta sets the period under its own policies. Our server does not store the events it sends to Meta; it forwards and discards them. Our own anonymous counters (no cookies, no IP address) keep running regardless of your choice and contain no personal data.
Meta-Pixel und Conversions API (nur mit deiner Einwilligung). Auf unseren Werbe- und Informationsseiten (zum Beispiel weavercompanion.com, /start, /bau und den Branchenseiten) können wir das Meta-Pixel einsetzen, um zu messen, ob unsere Werbung auf Facebook und Instagram wirkt. Es wird nur geladen, wenn du im Banner auf "Akzeptieren" klickst. Bei "Ablehnen" oder ohne Auswahl wird das Pixel nicht geladen und es werden keine Daten an Meta gesendet. In der App, bei der Anmeldung und in deinen Meetings ist das Pixel nie im Einsatz; Inhalte deiner Meetings, Protokolle oder Aufgaben gelangen nie zu Meta.
Daten. Wenn du zugestimmt hast, erhält Meta Informationen über deinen Besuch: die aufgerufene Seite, Zeitpunkt, deine IP-Adresse, Angaben zu Browser und Gerät (User Agent) sowie Kennungen aus Cookies von Meta (_fbp, _fbc). Zusätzlich melden wir von unserem Server aus (Conversions API) zwei Ereignisse: dass du das Beispiel (Demo) geöffnet hast ("ViewContent") und dass du dich registriert hast ("CompleteRegistration"). Bei der Registrierung übermitteln wir deine E-Mail-Adresse nur als nicht umkehrbaren Hash (SHA-256), nicht im Klartext. Zu jedem Ereignis gehören auch IP-Adresse und User Agent. Weitere Daten übermitteln wir nicht.
Zweck. Messung des Werbeerfolgs und Verbesserung unserer Werbung. Rechtsgrundlage. Deine Einwilligung (Art. 6 Abs. 1 lit. a DSGVO, Art. 31 Abs. 1 revDSG). Du kannst sie jederzeit mit Wirkung für die Zukunft widerrufen: über den Link "Cookie-Einstellungen" in der Fusszeile der Seite. Der Widerruf berührt die Rechtmässigkeit der bisherigen Verarbeitung nicht.
Empfänger und Verantwortlichkeit. Meta Platforms Ireland Limited, Merrion Road, Dublin 4, Irland. Für die Erhebung und Übermittlung der Daten an Meta sind wir und Meta nach dem Urteil des EuGH in der Rechtssache Fashion ID gemeinsam verantwortlich; für die weitere Verarbeitung durch Meta ist Meta allein verantwortlich (siehe die Datenrichtlinie und die Bedingungen für Meta-Business-Tools von Meta). Drittland. Meta kann Daten in die USA übermitteln. Meta ist unter dem EU-US Data Privacy Framework zertifiziert; für die Schweiz gilt das Swiss-US Data Privacy Framework. Speicherdauer. Beim Pixel setzt Meta die Dauer nach eigenen Richtlinien fest. Unser Server speichert die an Meta gesendeten Ereignisse nicht; er sendet sie und verwirft sie. Unsere eigenen, anonymen Zähler (ohne Cookies, ohne IP-Adresse) laufen unabhängig von deiner Auswahl weiter und enthalten keine personenbezogenen Angaben.
Website analytics
The website is hosted by Lovable, which also runs basic page statistics for us: which page was opened, how fast it loaded, the website you came from, and the browser and device type. This uses no cookies. Links that carry a secret, such as a password reset, an account deletion or a shared minutes link, keep that secret out of the address (it is sent after the # sign, which is never sent to a server, and the website removes it from the address before the statistics run). The statistics do not include the content of your meetings. Lovable is listed on our subprocessors page.
Die Website wird von Lovable gehostet, die für uns auch einfache Seitenstatistiken führt: welche Seite geöffnet wurde, wie schnell sie geladen hat, von welcher Website du kommst sowie Browser- und Gerätetyp. Dabei werden keine Cookies verwendet. Links mit einem Geheimnis, etwa zum Zurücksetzen des Passworts, zum Löschen des Kontos oder zu geteilten Protokollen, halten dieses Geheimnis aus der Adresse heraus (es steht hinter dem #-Zeichen, das nie an einen Server gesendet wird, und die Website entfernt es aus der Adresse, bevor die Statistik läuft). Die Statistik enthält keine Inhalte deiner Meetings. Lovable ist auf unserer Seite der Unterauftragsverarbeiter aufgeführt.
What we do not collect
- Location data
- Your contacts
- Your calendar, unless you choose to connect it (see below)
- Advertising identifiers (except the Meta identifiers described above, and only if you accept them)
- Device usage data or analytics beyond what is described in this policy
Connecting your calendar
Connecting Google Calendar or Microsoft Outlook is optional. You can disconnect at any time in Settings.
- What Weaver reads. Events in the next 14 days: title, start and end time, description, the call link, and the names and email addresses of the guests. Access is read-only (Google calendar.events.readonly, Microsoft Calendars.Read). Weaver never creates, changes or deletes events.
- What it is used for. To show your meetings in Weaver's calendar, to have Weaver's notetaker join your calls that have a Zoom, Teams, Google Meet or Webex link, to remind you on your phone to transcribe an in-person meeting when it starts, to write you a short brief before a call (from its agenda and guest list), and to suggest the guests when you email the minutes afterwards. All-day events, events marked private and events you declined are skipped and not stored.
- What is stored. For each meeting in the next 14 days: its title, time, place, call link and guests, encrypted, with your account, until a day after it has ended; for each call Weaver joins also its description. The access granted by Google or Microsoft is stored encrypted too. Disconnecting deletes that access (and revokes it at Google), deletes the stored meetings and cancels the upcoming calls Weaver scheduled from that calendar.
- Who else sees it. The call link goes to Recall.ai, whose bot joins the call. The agenda and guest names of an upcoming call are processed by Google Cloud Vertex AI in the EU to write your brief. Calendar data is never sold, never used for advertising and never used to train AI models.
Weaver's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Your folders and who sees them
You can keep your private life in Weaver too: notes, to-dos, reminders and transcriptions of things like a doctor's appointment or a call with the bank. These can include health or financial details. They are treated like all your content: encrypted in our database, processed in the EU and Switzerland, never used to train AI models, and visible only to you and the people you share a folder or project with. Your Team or Office admin sees who holds a seat, not your own folders, projects or notes unless you share them. Please ask before transcribing someone, a doctor included.
Reminders you set are sent at their time as a notification on your phone and, if you linked the Weaver Telegram bot, as a Telegram message.
Sharing minutes with people outside Weaver
You can email a meeting's minutes to anyone, or create a link that opens them without an account.
- Emailed minutes go out from Weaver's address with your first name as the sender and your email address as the reply-to, through our email provider (Resend). We store the addresses you sent them to, encrypted, so we can show who already received them and suggest them next time. Recipients are not put on any mailing list. The email ends with a link to try Weaver.
- A share link lets anyone who has it read that one meeting's minutes: the title, date, attendees' names, what was discussed, decisions and action items. Never the transcript, files, the project or any other meeting. We count how often it is opened. You can stop sharing at any time, which turns the link off, including in emails already sent.
Transcribing with the mobile app
The Weaver app for iPhone and Android uses your device's microphone to capture audio, which it transcribes, either for a meeting you are in or for a note you dictate to yourself. Audio is only ever captured after you tap transcribe, and the app shows you that it is transcribing for as long as it continues, including a persistent notification on Android while the screen is locked.
Audio is held on your device only until it is uploaded for transcription, and the local copy is deleted as soon as it has been sent. We do not access your microphone at any other time, and the app never captures audio in the background without you starting it.
You are responsible for making sure that capturing the audio of a given conversation is permitted, and that the people in it are aware, as required where you and they are located.
Transcribing live calls
When you connect a Zoom, Teams or Google Meet call, a bot joins the meeting and is visible to everyone in it. The same responsibility applies: please make sure transcribing is permitted and that participants know.
How your data is used
Your data is used for one purpose, which is making Weaver work for you.
Transcripts, audio and questions are processed by Google's Gemini models on Google Cloud Vertex AI to transcribe speech, extract structure and generate answers, in the European Union (see "Where your data is" below). Google does not use this data to train its models. Extracted data is stored on our infrastructure and queried on your behalf when you ask a question.
We do not sell your data. We do not share it with advertisers. We do not use it to train AI models.
Where your data is
- Your account and meeting data are stored on our server in Nuremberg, Germany. Encrypted backups are kept in Germany.
- AI processing (transcription, extraction, answers and voice calls) runs on Google Cloud's European Union endpoint, so it stays within EU member states.
- Search processing, and large audio files while they are being transcribed, are handled in Zurich, Switzerland. Those audio files are deleted right after transcription, and after two days at the latest.
- Live meeting bots run in Recall.ai's European region (Frankfurt).
Service providers
These providers process data on our behalf, each only for the purpose listed. A small amount of data can leave the EU through some of them, as noted; those transfers rely on the EU-US Data Privacy Framework or the EU Standard Contractual Clauses.
- Hetzner (Germany): hosting of our server, database and encrypted backups.
- Google Cloud Vertex AI (EU, Switzerland): transcription, extraction, answers, voice calls and search.
- Recall.ai (EU), only when you connect a meeting bot to a call.
- Cloudflare: network protection and encryption in transit for our website and API; all traffic passes through it.
- Resend (Ireland): emails such as address confirmation and meeting briefs.
- Stripe: payment processing. No meeting content.
- Apple and Google: app store purchases, sign-in with Apple or Google, and push notifications. A notification can contain a meeting title or a task's wording.
- Lovable: hosting of this website's pages, including basic page-visit statistics. Your meeting content goes directly to our servers, not through Lovable.
- Telegram, only if you connect the Weaver Telegram assistant: the messages you send it.
The providers that process your meeting and account data on our behalf, with what each handles and where, are on our subprocessors page. Business customers can request our data processing agreement at privacy@weavecompanion.com.
Data retention and deletion
You can delete an individual meeting or an entire project at any time. Deleting a project removes its meetings, transcripts, decisions, action items and embeddings.
You can permanently delete your account from the account settings in the app or on the web. Deleting your account irreversibly erases your profile and credentials, all meeting content, and all extracted data from our live systems straight away, with no waiting period. Our encrypted backups are overwritten on a rolling schedule, so deleted data disappears from them as they rotate out, within six months at the latest. Backups are only ever used to recover from a loss of our systems.
Stripe retains billing records as required by financial regulations. We cannot delete those on your behalf, and they contain no meeting content.
Security
- Meeting content, including transcripts, titles, project names and summaries, is encrypted at rest with AES-256-GCM, using a separate random nonce for every stored value.
- Passwords are hashed with Argon2id, the current OWASP recommendation, using the argon2-cffi defaults. Older accounts still holding a legacy PBKDF2 hash are upgraded to Argon2id automatically the next time they sign in.
- Data in transit is encrypted with TLS.
- Access to production systems is limited to the core team.
Children
Weaver is not intended for users under 16. We do not knowingly collect data from children.
Your rights
Depending on where you live, you may have the right to access, correct or export your data, in addition to the deletion right described above. Contact privacy@weavecompanion.com for any of these requests. We will respond within 30 days.
Changes to this policy
If we make material changes we will notify you by email and update the date at the top of this page. Continued use of Weaver after changes constitutes acceptance.
Contact
privacy@weavecompanion.com
See also our Terms of Use.