# Encryption and access

*Updated 2026-10-20*

## In transit

Every connection to meaty uses HTTPS, and browsers are told to never connect
without it.

## At rest

- **Integration connections** (calendar, Slack, Notion and webhook
  secrets): *(To be confirmed.)*
- **API keys:** stored only as a fingerprint. meaty can't show or recover a
  key after creating it.
- **Meetings** (audio, transcripts and notes): *(To be confirmed.)*

## Who can see your meetings

Only you — unless you share one. A [share link](/docs/share-a-meeting):

- is unguessable, and can be limited to email addresses you invite;
- includes only the sections you choose, and never audio;
- can expire, and stops working the moment you revoke it;
- isn't indexed by search engines.

Someone signed in can save a copy from a link while it's active; that copy
is theirs and stays after you revoke.

Staff access to meeting content: *(To be confirmed.)*

## What integrations can reach

| Integration | Access |
|---|---|
| Google Calendar | Read-only. Never creates or changes events. |
| Slack | Posts to the channel you picked. |
| Notion | Only the pages you shared with meaty. |

## Private glossary terms

Glossary terms marked private are masked before your text reaches the AI
that writes the notes.

## Who processes your data

*(To be confirmed.)*

The full details are in the [privacy policy](/legal).