Hume

Name: Hume business-data verdict
Item: Hume
Author: Aaron Simmons

Hume AI

Careful

Last checked 10 Nov 2026 · Reviewed by Aaron Simmons, security practitioner · How we decide

Hume's public privacy policy, updated February 25, 2025, says it does not apply to content processed for business API customers. Those uses are governed by separate agreements that this review did not treat as read. On the public offerings, user content includes inputs, file uploads, and feedback. The policy does not say whether voice or audio is used to train models, how long audio is kept, or whether a speaker must consent before a voice model is built. Do not put business audio into Hume until the contract for that API account is in hand.

Data-safety checklist

Trains on your data by default

Unknown

The public privacy policy lists user content as information in inputs, uploads, or feedback. It does not say that content is used to train models, and it does not say it is excluded. It expressly does not cover content processed for business API customers.

How to opt out

Steps

Unknown for model training. The public policy describes choices and access in general. It does not describe a training opt-out for audio.

Data retention

What they keep

Unknown. The policy says Hume wants users to understand how long personal information is retained. The text we read does not state a period for audio, voice models, or uploads.

BAA / HIPAA

Unknown

The public privacy policy does not offer a business associate agreement. Business API content is pointed to separate agreements.

Certifications

1 listed

Unknown

Enterprise and admin controls

Controls

Business API processing is outside this privacy policy and depends on the customer's separate agreement. The public policy does not describe an admin switch for training or voice-clone consent.