Vendor page
Whisperly privacy policy
BlazedLabz, 2026
Read the originalRead on October 23, 2026
- What it is
- The privacy policy of Whisperly, last updated 9 October 2026. It says where speech is turned into text, what leaves the device, which recordings are kept and for how long, and what the maker receives.
- How much weight it carries
- The maker's own policy, so it states what BlazedLabz says happens to data. It cannot promise what third parties such as ElevenLabs or Apple do with data, and the policy says so itself.
Facts taken from this source
- Whisperly's privacy policy says that when Apple's servers cannot be reached, the model on the user's device does the tidying of dictated text.
“When Apple’s servers cannot be reached, and on older systems: the model on your device does the tidying.” (How the text is tidied)
- Whisperly's privacy policy says the maker never receives dictations, so audio is not kept on the maker's servers.
“No ads. No analytics. No tracking. We never receive your dictations.” (The short version)
- Whisperly's privacy policy says the maker never receives dictations, so recordings from users do not reach the maker.
“No ads. No analytics. No tracking. We never receive your dictations.” (The short version)
- Whisperly's privacy policy says speech is turned into text by recognition that runs on the device, unless the user picks ElevenLabs or a Mac of their own as the engine.
“The speech is turned into text by speech recognition that runs on your device, unless you chose ElevenLabs or your own Mac as the speech engine” (The short version, and 'What Whisperly hears')
- Whisperly's privacy policy says that on an iPhone with iOS 27 or later, the tidying of text runs on Apple's Private Cloud Compute by default, and the text goes to Apple's servers.
“On an iPhone with iOS 27 or later, Whisperly tidies the text with Apple’s Private Cloud Compute by default. Your text goes to Apple’s servers for that.” (The short version)