Privacy Policy

Last updated 22 August 2026

This policy explains what Whispifys stores, why, and who else sees it. It covers both the Chrome extension and the web application.

What we collect

• Your identity. When you sign in with Google we receive your name, email address and profile picture. We never receive your Google password, and we ask for no access to your Gmail, Drive or Calendar.
• Your transcripts. The captions Teams produced during meetings you chose to record: the text of each line, who said it, and when. Plus the meeting's title, start and end time.
• Summaries and questions you generate, and what they cost in credits.
• Basic operational logs — request times and errors — used to keep the service running.
• How you found us. If you arrive through a link carrying a ref or utm_source — from a video, say, or a forum post — we keep that one word in a cookie and store it on your account when you sign up. It tells us which of the places we write actually reaches people. It is a single label, recorded once, never shared, and it follows you nowhere else on the internet.

We do not collect audio, video, your screen, your Teams chat messages, or anything from meetings you did not record.

Email

We send you two kinds of message and no others: a welcome when you sign up, explaining the one setting Whispifys needs, and a note when your AI credits run out. Payment receipts come from Polar, who take the payment. There is no newsletter, and we never sell or share your address. Every message has an unsubscribe link that works without signing in, and unsubscribing stops all of it while leaving your account and transcripts untouched.

Other people in your meetings

If someone in one of your meetings asks us to remove their data, we will refer them to you as the person who recorded it, and will help you action it.

Who else processes your data

• Anthropic — when you press Summarise or ask a question, the relevant transcript text is sent to Anthropic's API to generate the answer. Anthropic does not train models on data submitted through their API. If you never use the built-in AI, your transcripts are never sent to them.
• Google — sign-in only.
• Railway — hosting for the application and its database.
• Polar — payments, as merchant of record. They handle your card details; we never see them. We store only a customer reference and which plan you are on.

We do not sell your data, we do not share it with advertisers, and we do not use your transcripts to train any model — ours or anyone else's.

Connecting your own AI

You may connect your own AI assistant to Whispifys over MCP. If you do, you are authorising that assistant to read your transcripts, and what it does with them is governed by whoever provides it. You can revoke that access at any time from the Connect page.

Keeping and deleting

Transcripts are kept until you delete them. Deleting moves a transcript to a bin where you can restore it; emptying the bin removes it permanently. Closing your account deletes your transcripts, summaries and account record. Backups may retain deleted content for a short period before being overwritten.

Your rights

You can read, export and delete your own data from within the application at any time — every transcript can be downloaded as a text file. Depending on where you live you may also have rights to correction, restriction, portability, or to complain to a data protection authority. Write to us and we will action it.

Security

Data is encrypted in transit. Transcripts are scoped to the account that recorded them and every request is checked against the signed-in user. No system is perfectly secure; we will notify you of a breach affecting your data as required by law.

Children

Whispifys is not intended for anyone under 16, and we do not knowingly collect their data.

Changes and contact

We will notify you of material changes to this policy. For any privacy question, or to exercise a right above, write to support@whispifys.com.