Privacy Policy

Who we are

HushCall is made by CoolSolve LLP. You can reach us at support@hushcall.app.

What stays on your Mac

HushCall keeps these in its own database and folders on your Mac:

Meeting audio, and screen video if you turn on Record screen video
Transcripts, speaker labels, summaries, action items and chat history
The search index for your recordings
Pictures of the slides and key screens shared in a recording's video, and the text read from them, which can include IDs, keys and passwords shown on screen
For a recording linked to a calendar event: the event's title, time, meeting service, a cleaned excerpt of its agenda, its organizer, its attendees' names, email addresses and responses, and the event's identifiers (see Calendar and About You)
The name, nicknames and role you enter in About You, if you do
Your settings and any API keys you add

On-device transcription uses Apple Speech (macOS 26 or later) or WhisperKit. On-device AI uses Apple's on-device model (Apple Intelligence, macOS 26 or later) or a local model that runs on your Mac. We have no access to any of this. It leaves your Mac only if you choose one of the cloud options below.

Model downloads

Some on-device features need model files. HushCall asks before downloading any of them, and shows the size: the speaker-separation models (about 23 MB), the WhisperKit speech model (about 490 MB, used on macOS 15 or when you choose WhisperKit) and the local AI model (about 659 MB). The first two download at your first transcription, the local AI model only if you choose it. The app gets these files from Hugging Face (huggingface.co). It also asks our server for the current list of local AI models, sending only the app's version number. None of these requests carry your recordings or your account details.

No analytics, no tracking

HushCall has no analytics, no ads and no tracking. We don't know how many recordings you make, which features you use or when you open the app. HushCall never sends a crash report on its own. It asks first, and only a report you send leaves your Mac. See Crash and problem reports.

Crash and problem reports

HushCall never sends one of these on its own. A report leaves your Mac only when you click Send, and the window shows you exactly what it holds first.

After an unexpected quit

When HushCall quits unexpectedly, macOS hands the app a crash report through Apple's MetricKit. HushCall keeps it in its own folder on your Mac (up to 5 reports, for up to 30 days) and, the next time it opens, asks whether to send it. Once you send it, or choose Don't Send, the saved copy is deleted. If you tick Don't ask again, HushCall stops keeping crash reports. You can turn the offer back on in Settings → About. A crash report holds:

Where in its code HushCall stopped (the code libraries and addresses on the call stack) and the exception type
The app version and build, whether it is the Mac App Store or the direct download, your macOS version, your Mac model, its processor type, and your language and region setting
The app version and build, that it is the Mac App Store version, your macOS version, your Mac model, its processor type, and your language and region setting
Your plan, and the transcription engine and AI provider you chose
A note about what you were doing, if you write one

Report a Problem

You can open Report a Problem from HushCall's menu bar menu or from Settings → About. It sends what you type in the description box, plus the following if you choose them:

An email address, so we can reply
Diagnostics, switched on by default: the same version, Mac, plan and provider details as a crash report
HushCall's own log lines since it was opened (the latest 500 at most), switched off by default. They can include recording titles, file names, and the names of meeting windows, apps and audio devices.

What is left out, and where it goes

Diagnostics and crash reports never include recordings, transcripts, summaries, titles or your account details. In a crash report and in log lines, your Mac account name in a file path (the part after /Users/) is replaced with “redacted”. What you type in the description is sent as you wrote it.

The report goes to our server at api.hushcall.app, which files it as an issue in our private issue tracker on GitHub. The issue holds the whole report, including your email address if you gave one. Your IP address is used only to limit how many reports can be sent per minute. We don't store it.

Update check

The Mac App Store version and the version you download from hushcall.app each check for updates, in different ways.The Mac App Store version checks for updates. You can turn off the automatic check in Settings → About.

Mac App Store version

When it starts, and about once a day after that, it asks Apple's public App Store lookup (itunes.apple.com) for the latest version. The request carries only HushCall's App Store ID and your Mac's region, so Apple can pick the right storefront. Apple receives it like any other web request. If a newer version is out, HushCall tells you and opens its page in the App Store. It never downloads or installs anything itself.

Version from hushcall.app

About once a day it asks hushcall.app for a small list of releases. The request carries only HushCall's version (in the request's user-agent header); no device or account identifier, and no profile of your Mac. Like any web request, it reaches our server with your IP address. If a newer version is out, HushCall says so in its menu and in Settings → About. Each update is signed by us, and HushCall refuses one whose signature doesn't match. You choose whether updates install on their own: by default they don't. If you turn on automatic installs, an update downloads in the background and installs when you quit HushCall, or when you choose Restart to Finish Updating. HushCall never restarts for an update while it is recording.

HushCall Cloud Pro

Cloud Pro is optional. Nothing below happens unless you choose HushCall Cloud as your transcription or AI provider.

Cloud transcription

The app sends the recording's audio to our server at api.hushcall.app, which runs on Cloudflare Workers. Our server passes the audio to Cloudflare Workers AI, which returns the transcript. Neither we nor Cloudflare store the audio. If you filled in About You, your name and nicknames go along with it as a spelling hint. No calendar data is sent for transcription.

Cloud AI

For summaries, action items, titles, speaker names and chat, the app sends the text a request needs to our server. That is usually part of a transcript, plus your question in chat. It can also include the recording's title, the names of people on the call (from its calendar event, the meeting app or the recorded video), the text HushCall read from slides and shared screens in the recorded video (which can include IDs, keys and passwords shown on screen), the notes you took during the recording (with text read from pictures in them), and your About You details (see Calendar and About You). Our server passes it through our own relay server to OpenLimits, which sends it to the company that runs the AI model and returns the answer. If that fails, Cloudflare Workers AI answers instead. Our servers don't store the text or the answer.

What our providers say about your content

Cloudflare says it doesn't use Workers AI inputs or outputs to train AI models. See Your data and Workers AI.
OpenLimits says it doesn't log, store, read or inspect the content of requests or responses. See the OpenLimits Privacy Policy.
The company that runs the AI model handles the request under its own terms. It may keep the request for a limited time, for example to check for abuse.

We send these requests on without your email address, account ID or IP address. We don't sell your content, and we don't use it to train AI models.

Your own API keys

Instead of Cloud Pro, you can add your own API key for one of these providers. The app then sends the audio or text straight from your Mac to that provider. It doesn't pass through our servers.

Google Gemini, for transcription and AI
OpenAI, for AI. If you enter a different server address for this option, requests go to that server instead.
Deepgram, for transcription

The provider's own privacy policy and terms apply, including how long it keeps what you send. Some providers use data sent on free plans to improve their models, so check before you add a key. Your keys stay on your Mac and are never sent to us.

Calendar and About You

Calendar access (optional)

HushCall works without calendar access and never asks for it on its own. macOS asks only after you click Allow Calendar Access or Grant Access, or turn on Remind me before meetings in Settings → General. You can turn access off at any time in System Settings → Privacy & Security → Calendars.

If you allow it, HushCall reads your events from an hour ago to the end of tomorrow and keeps the ones that have a Zoom, Microsoft Teams or Google Meet link in their URL, location or notes. For those events it reads the title, the start and end time, the link, the agenda in the notes (with links, passcodes and dial-in numbers removed) and the attendees' names and email addresses.

On your Mac, HushCall uses this to show a reminder before a meeting (by default a banner 15 minutes before and a full-screen reminder 1 minute before), to open the meeting link, to name a recording after the event, and to suggest attendee names when it labels speakers. Reminders are off until you turn them on. Allowing calendar access in Set Up HushCall or in Settings → Permissions turns them on, and you can turn them off in Settings → General.

When a recording is linked to an event (you chose Join & Record on its reminder, or an automatic recording started near the event's time on the same service), HushCall saves a copy of the event with the recording: the title, time, meeting service, up to 1,000 characters of the cleaned agenda, the organizer's name, each attendee's name, email address and response, and the event's identifiers. The copy is deleted when you delete the recording.

What leaves your Mac

The calendar features themselves send nothing to us. Event details leave your Mac only inside AI requests to a cloud AI service (HushCall Cloud, Google Gemini or OpenAI) that you chose and agreed to. If that service is HushCall Cloud, the request passes through our server like any other Cloud AI request, and we don't store it. Such a request can hold:

For a title: the event's title and up to 400 characters of its agenda
For speaker names: the attendees' names, and the title of the recording
For chat: the title of the recording. A chat across meetings sends the title, date and app name of each recording it searches

A recording named after an event carries the event's title as its own. The email addresses on an attendee list are never sent, but an address typed into an event's title or agenda goes out with that text. With on-device AI, nothing leaves your Mac. Transcription requests carry no calendar data.

About You (optional)

In the About You step of Set Up HushCall, or in Settings → General under You, you can enter your name, nicknames and role. HushCall keeps them on your Mac and uses them to tell your voice from the others, spell your name correctly and write summaries from your point of view. Two things leave your Mac, and only for a cloud service you chose:

A cloud transcription service (HushCall Cloud, Google Gemini or Deepgram) gets your name and nicknames with the audio, as a spelling hint. It does not get your role.
A cloud AI service gets your name, nicknames and role in a line added to its requests.

Speaker-naming requests to a cloud AI service can also hold the names of people on the call, as read from the meeting app, the recorded video or a calendar event's attendees. Names read from the meeting app or the recorded video also go into the requests that write action items.

Your HushCall Cloud account

You only need an account for Cloud Pro. Signing in has no password: you enter your email address, and we email you a one-time code. If you sign in, we store:

Your email address
An account ID
Your sign-in sessions: a random token for each app or browser you sign in on, and when it expires
One-time sign-in codes
Cloud Pro purchase records: Apple's original transaction ID, the plan, the dates of the current period, whether it renews automatically, and whether the purchase came from Apple's live or test environment
Purchase records from Paddle for the direct-download version, once they are linked to your account by signing in with the email address you bought with (see Payments below)

Your recordings, transcripts, questions and AI answers are not stored with your account, or anywhere on our servers.

Payments

Mac App Store. In the Mac App Store version, Apple takes the payment for every plan. We never see your card or billing details. HushCall Pro and HushCall Pro Lifetime bought there are checked on your Mac with Apple's StoreKit, and nothing about them is sent to us.

For Cloud Pro, the app sends us the purchase record that Apple signed, so we can turn on Cloud Pro for your account. Apple also tells our server when that subscription renews, changes or ends. See the Terms of Use for the subscription and cancellation terms.

Direct download. HushCall Pro for the direct-download version is sold by Paddle.com Market Limited, our Merchant of Record. Paddle takes the payment and we never see your card or billing details. When someone buys, Paddle tells our server about the purchase, and we store a purchase record under the buyer's email address, even if the buyer never signs in. The record holds:

Your Paddle customer ID and your email address
The plan (yearly or lifetime), its status, and whether it is a free trial
The Paddle subscription ID, or for Lifetime the transaction ID
For a yearly plan, the end of the current period, any scheduled cancellation or pause, and the date it became past due
Whether the purchase was refunded or charged back
Whether it was made in Paddle's live or test environment

We also keep the ID, type and time of each notification from Paddle for 30 days, so none is processed twice. They hold no personal data. Purchase records are deleted with your account: sign in with the email address you bought with, then delete your account. Deleting your account does not cancel a yearly plan, so cancel it first with Manage Pro billing on your account dashboard.

Companies that process data for us

Cloudflare runs our server (Workers), stores account data and the problem and crash reports you send (D1), and runs cloud transcription and the fallback for cloud AI (Workers AI). Privacy policy
OpenLimits forwards cloud AI requests to the company that runs the AI model. Privacy policy
Resend sends the email with your sign-in code. It receives your email address and the code. Privacy policy
Paddle handles payments for the direct-download version and tells us the status of those purchases. Privacy policy
Apple handles payments in the Mac App Store and tells us the status of Cloud Pro subscriptions. Privacy policy
GitHub holds the crash and problem reports you choose to send, as issues in our private repository. Privacy statement

We run the relay server between our server and OpenLimits ourselves. We don't sell or share your data with anyone else, unless the law requires it.

How long we keep data

Audio and text sent to HushCall Cloud are not kept after the request is answered.
Sign-in codes expire after 10 minutes and are deleted within 24 hours.
A sign-in session ends when you sign out or after 30 days. Expired sessions are deleted within 24 hours.
Our server keeps technical logs for up to 7 days, to find and fix faults. They contain no user identifiers.
Your email address, account ID, sessions and purchase records are kept until you delete your account. That includes Paddle purchase records, which also exist for a buyer who never signed in. Email support@hushcall.app from the purchase email address to have those deleted.
The ID, type and time of each Paddle notification are deleted after 30 days.
A calendar event's copy stays with its recording on your Mac until you delete the recording. Our servers keep no calendar data.
Crash and problem reports stay on our server for 30 days, then are deleted. Each one is also filed as an issue in our private issue tracker on GitHub, where it is kept while the problem is being fixed. Email support@hushcall.app to have yours deleted. We also keep a short code for each kind of crash, with the number of its issue. It holds no personal data.
Our database provider keeps backups for up to 30 days, so deleted data can stay in a backup for up to 30 days.

Deleting your data

Your account: in HushCall, open Settings → Plans (Cloud Pro in version 1.0) → Delete Account, or sign in at hushcall.app/dashboard and choose Delete account. This deletes your email address, account ID, sessions, sign-in codes and purchase records, Paddle purchase records included, from our database.This deletes your email address, account ID, sessions, sign-in codes and purchase records from our database. It doesn't cancel an App Store subscription, so cancel that in your App Store account settings. It doesn't cancel a Paddle yearly plan either: cancel that first with Manage Pro billing on the dashboard. You can also email support@hushcall.app from the address on your account.
Your recordings: they are on your Mac, and you can delete any of them in the Library.

You can also ask us for a copy of the data we hold about you, or ask us to correct it, by emailing support@hushcall.app. If you are in the EU or the UK, you can also complain to your data protection authority.

Permissions the app asks for

Microphone — to record your side of a meeting.
Screen Recording — macOS puts system audio behind this permission, so HushCall needs it to record the other people in a call. It also covers the optional screen video. What it captures is saved on your Mac.
Calendars (optional) — to remind you before Zoom, Microsoft Teams and Google Meet meetings, open their links, name recordings after the meeting and suggest attendee names for speaker labels. You allow it with a click, in Set Up HushCall or in Settings. HushCall asks for full access, the only level that lets an app read events. What it reads and where that goes is under Calendar and About You.
Notifications (optional) — to tell you when an automatic recording starts.

The Mac App Store version doesn't ask for Accessibility access. The direct-download version can ask for it, as an option, to read participant names and who is speaking in the Zoom and Teams Mac apps and in Google Meet on Chrome, Edge, Arc, Brave or Safari. You can turn off any permission in System Settings → Privacy & Security. HushCall then loses the feature that needs it and keeps working otherwise.

Our website

The HushCall app has no analytics. On hushcall.app's public pages (home, pricing, support, terms, refund and this policy) we use Microsoft Clarity to see how visitors use the site: clicks, scrolling and anonymised session recordings. Clarity sets cookies in your browser and Microsoft processes the data under its privacy statement. It is not loaded on the web dashboard or checkout, and never in the app.It is not loaded on the web dashboard, and never in the app. If you sign in to the web dashboard, your browser keeps the sign-in token until you sign out.

Children

HushCall is not directed at children under 13, and we do not knowingly collect personal data from them.

Changes to this policy

If this policy changes, we will update this page and the date at the top. We will also mention important changes in the app's release notes.

Contact

Questions about this policy, or requests about your data, go to support@hushcall.app.

The short version