Your conversation should have a visible boundary.
HiDock App’s default path keeps the recording, transcription, and summary work on your Mac. This page explains the product architecture—and where your choice can change it.
Follow each form of the conversation.
Privacy is easier to judge when each stage names its input, processor, destination, and exception.
Audio is captured on HiDock.
The recorder creates the source recording during a supported call or face-to-face conversation.
The recording moves to your Mac.
HiDock App receives the source file for local processing and storage.
Transcription runs locally.
The speech model reads the recording on the Mac; raw audio is not uploaded for this step.
The built-in summary model runs locally.
By default, the transcript is summarized on the Mac without an AI API key or summary server account.
You keep the result and the source.
The recording, transcript, and meeting note remain connected so generated text can be reviewed.
A cloud engine is a choice, not the default.
HiDock App can leave a cloud summary engine available in Settings for people who prefer it. Selecting one changes where transcript text is processed and subjects that processing to the chosen provider’s terms.
That option should not be confused with the default built-in model. The useful privacy promise is conditional and testable: in the local default, the raw audio stays on the Mac, transcription runs there, and the built-in summary runs there.
| Local default | Recording, transcript, and built-in summary processing remain on the Mac. |
|---|---|
| Optional cloud engine | Available only when selected; the chosen provider then receives the text required for that operation. |
| Raw audio | Not uploaded for local transcription or the built-in local summary workflow. |
| AI output | A draft that can contain errors and should be checked against the source. |
| Legal terms | Governed by the official HiDock Privacy Policy and any terms of an optional provider you choose. |
Privacy claims with their conditions attached.
Does my raw meeting audio leave the Mac for transcription?
No in the published local workflow. The speech model reads the recording on the supported Mac.
Does the summary leave the Mac?
The built-in summary model runs locally by default. If you deliberately select a cloud engine, that choice changes the processing path for the required text.
Does local processing guarantee perfect confidentiality?
No single feature can guarantee that. Device security, backups, account access, exports, optional engines, and the way you share notes still matter.
Is this page the legal privacy policy?
No. This page explains product architecture. The maintained legal policy is published on hidock.com and should be read for formal terms and disclosures.
Choose the boundary before the meeting.
Use the built-in local path on a supported Mac.