lock
End-to-end encrypted cloud records
When E2E encryption is enabled in supported apps, new cloud-synced transcripts and summaries are encrypted before they leave the device.
Privacy & Security
Meeting memory with user-controlled privacy.
Minom is built for sensitive meeting records: encrypted cloud sync, device-only offload, recovery key portability, and clear controls for how transcripts and summaries are stored.
Secure Controls
Four controls protect meeting data across devices.
Minom separates convenience from control. Cloud sync helps recovery and access, while E2E encryption and offload give users stronger privacy when needed.
vpn_key
User-held recovery keys
Users can export a password-protected recovery key and import it on another device to unlock encrypted summaries there.
cloud_off
Offload to device only
Offload removes a selected meeting from Minom Cloud and keeps the local copy on the current device or browser.
visibility_off
Redacted processing logs
Backend and worker results are designed to avoid exposing raw transcripts and generated summaries in operational logs.
Encrypted Cloud Flow
What happens when E2E encryption is on?
The readable meeting content is encrypted on the client before cloud storage. The backend stores the encrypted payload, not the plain transcript or MoM.
- Turn on E2E encryption from Settings before creating future summaries.
- Minom generates or reuses a device key and encrypts the transcript, MoM and reminders locally.
- The encrypted payload is saved to Minom Cloud with metadata needed for syncing and display.
- Another device can show the record but cannot read its content until the user imports the correct recovery key.
User Guide
How users control encrypted and local-only records.
These controls are designed to be understandable for mobile, desktop and Chrome extension users.
Enable encryption
- Open Settings.
- Find Cloud History or Privacy controls.
- Turn on End-to-End Encryption.
- Future summaries are encrypted; older summaries stay as they were.
Export recovery key
- Open Settings.
- Choose Export Key.
- Set a strong password for the key file.
- Store the file somewhere safe outside the app.
Import on another device
- Install and sign in to Minom.
- Open Settings.
- Choose Import Key.
- Select the recovery key file and enter its password.
Offload a meeting
- Open a saved transcript or summary.
- Press Offload.
- Confirm the warning.
- The cloud copy is deleted and the item becomes device-only.
Access Boundaries
Who can see what?
The strongest privacy mode depends on the user keeping the recovery key safe. Without the key, encrypted meeting content should remain unreadable.
Signed-in user on original deviceCan read normal records and encrypted records whose key is present.
Same user on a new deviceCan see encrypted record metadata, but must import the recovery key to read encrypted content.
Minom backendStores encrypted payloads and metadata; it should not have the user recovery key.
Internal developersShould not be able to read E2E encrypted transcript or summary content from cloud storage.
Processing providersReceive only the content needed for transcription or summary generation during processing.
Important Note
Encryption applies to future records after it is enabled.
If a user turns on E2E encryption after creating five summaries, those five older summaries remain in their original storage mode. New summaries created after enabling encryption use the encrypted flow where supported.