Security and privacy
Enterprise-secure by design.
Only you see it
Brieflee never posts to a channel and never broadcasts to the room. The private side-panel it will fill for one seat, when that ships, is built the same way.
Never trained on
Excluded from speech-model training. No model is trained on them: raw, aggregated or derived.
Encrypted in transit
Industry-standard protection, with Teams single sign-on where your organisation requires it.
Delete means deleted
Delete a meeting and its recording goes with it. Disconnect any account at any time.
What each connection can reach
Every connection is optional, and Brieflee asks only for what the feature you turned on actually needs.
- Calendar, read-only: reads your upcoming events so Brieflee can prepare a brief and join the calls you pick. It never creates, edits or deletes events.
- To Do / Tasks: writes the action items from a meeting to your task list, when you ask it to.
- Basic profile: identifies the account you connected, and powers Teams single sign-on.
- Calendar, read-only: reads your upcoming events so Brieflee can show your schedule and send the notetaker to the meetings you pick. It never creates, edits or deletes events.
- Google Tasks: writes the action items from a meeting to your task list, when you ask it to.
- Basic profile and email: shows you which Google account is connected.
- Deals: read and write, to list your deals and attach the summary and action items you push to the one you pick.
- Contacts: read and write, because HubSpot only lets an app create tasks and notes with these. Brieflee does not read or change your contact records.
- Owners: read-only, to assign each pushed action item to the HubSpot user with your email address.
- Notes and activities: creates the post-call note and the follow-up activity you choose to push.
- CRM modules, notes and tasks: read and write across your CRM modules, so the summary, its note and its follow-up tasks land on the right record.
- Your user and organisation: read-only, to identify the account you connected and the org it belongs to.
Brieflee’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. The same limits apply to data from every other provider we connect to. You can disconnect any account at any time; see our Privacy Policy.
The recording can live in your bucket, not ours.
Data-residency clauses, a bucket your own team audits, keys you rotate. Point Brieflee at storage you already own and the recording never has to rest on ours.
The call sends audio to Recorder sends signed upload to Your bucket.
Amazon S3
Bucket, region, access key
- Transfer
- Signed straight to youThis provider can issue a signed URL, so the recording is uploaded straight into your storage. It is never written to a Brieflee disk on the way.
- Also supports
- Server-side encryptionYour own KMS keyFolder prefix
- Credentials
- Write-onlySaved keys come back masked and stay masked, so editing a folder prefix can never wipe the access key you pasted in months ago.
- What stays with us
- Everything lands in your storageThe recording, the video, the transcript, the summaries and the exports are all written to storage you own. What remains with Brieflee is the metadata a listing needs (title, counts and timestamps) and any minutes you send, kept so the people you send them to can read them.
- 1Writeputs a canary object in your bucket
- 2Read backfetches it again to prove it landed
- 3Deleteremoves it, proving cleanup rights too
“Connected” means all three worked. Storing a credential and hoping is not a connection test.
Looking for the full picture? The trust page lists every control that is in place, the ones that are not, and the transfers a reviewer should ask about. It is dated, and written to be checked against the product.