Security

All connections to Noteary — the web app, the REST API, and the live-recording WebSocket — are encrypted with TLS. There is no unencrypted path between your device and our servers.

Recording audio is encrypted at rest with AES-256-GCM before it’s written to storage, using a key we generate and control ourselves — not a third-party key-management service. This is in addition to the access controls below, not instead of them.

Every recording is scoped to its owner. There is no code path that lets one account read another’s recording content, and our internal admin tooling is deliberately limited to account bookkeeping (plan tier, active/suspended status, aggregate usage stats) — it cannot read recording audio, transcripts, or summaries. Recordings can be made readable to a shared workspace only when a member explicitly enables sharing.

You control how long we keep your recordings — keep forever, or auto-delete after 30, 90, or 365 days. When a retention window passes, the recording, its audio file, and its searchable memory are permanently purged, not just hidden. Deleting a recording or your account purges the underlying audio file immediately, not just the database row.

Your audio and transcripts are sent to commercial inference APIs to produce transcripts and summaries — not to consumer AI products. API-tier usage from these providers is governed by terms that exclude submitted content from model training, distinct from their consumer-facing products. We do not use your recordings, transcripts, or summaries to train any AI model, ours or anyone else’s, and we do not sell your data.

TOTP-based two-factor authentication (compatible with any standard authenticator app) is available for password-based accounts, with single-use backup codes issued at enrollment. Manage it from Settings on the web app.

We run nightly backups of the database and recording storage, retained for 14 days, with an optional off-site copy. Backups inherit encryption at rest automatically, since they capture the same encrypted files. Backups exist to recover from operational failure, not as a substitute for your own copies of anything irreplaceable.

Our internal security practices are informed by ISO 27001’s control categories (access management, incident response, asset handling). We are not ISO 27001 certified — certification requires a paid third-party audit we have not pursued.