Talkuza offers no BAA
Talkuza does not offer a Business Associate Agreement (BAA), and there is no signed BAA available to view. If you are a covered entity or business associate under HIPAA (US) and you need a BAA, Talkuza is not the right tool for protected health information (PHI) today.
Any “View signed BAA” button you may have seen in older app screens was a leftover placeholder and has been removed. There is no BAA to view, download, or request.
What Talkuza actually does with your data
- Your voice audio, dictations, transcripts, and notes are processed on your Mac and (for AI correction) sent directly from your Mac to Groq/Fish with your keys. Talkuza's backend never receives them.
- Our servers store only account and licence data: name, email, username, order records, subscription dates, and device hashes for the device limit. See the Privacy Policy.
- Data in transit to our servers uses TLS. Data at rest in our database is encrypted by the database provider. Account access is protected by signed tokens that are invalidated on ban.
- We do not claim HIPAA, SOC 2, or ISO 27001 compliance. We do claim the architecture above, and we describe it plainly so you can judge it.
If you handle health information
Do not dictate, record, or store PHI in Talkuza unless you have assessed the risk yourself and your organisation allows it. In particular:
- Do not use Echo Notes to record clinical encounters containing PHI.
- Do not sync Talkuza notes containing PHI into AI tools over MCP.
- Remember that your Groq/Fish keys send text to Groq/Fish under their terms — review those terms before sending any sensitive content.
Will this change?
If we ever pursue a BAA or a formal compliance certification, this page will say so — with the actual agreement linked. Until then, assume the answer is no.
Questions: support@talkuza.online or the contact form.