kept.

public privacy & security notes

Your audio deserves a clear answer.

Kept is a personal audio library for voice notes and meeting audio. This page explains the controls we have, the boundaries we know, and the things we have not verified yet.

01 / What happens to a recording

A private library, with a visible chain of custody.

Background recording: It is available in native iOS and Android app builds, off by default, and can be enabled before a voice note starts. When enabled, recording can continue while you switch apps or lock your screen. Android shows an ongoing notification with a Stop control; on iOS, return to Kept to stop and save. Calls, system interruptions, or force-closing Kept may stop a session.
Upload path

The upload ticket expires.

Audio is uploaded through an expiring signed upload ticket. The ticket is the temporary handoff used to put a file in place; it is not a public audio URL.

Scope

Requests and recordings are account-scoped.

Kept treats your library as belonging to your account. Requests for recordings, transcripts, summaries, and exports are scoped to that account rather than being public resources.

AI output

Summaries are assistance, not a new source.

AI-generated summaries and search results are derived from your audio and transcript. Keep the original recording and transcript as the source when details matter.

02 / Controls that exist today

Useful controls, without pretending they are more than they are.

The product is still growing. These details are part of the current implementation, not a promise about an imagined future version.

Archive is not deletion.

Archiving only hides a recording from the main library. It does not permanently delete the recording or its associated data.

Exports are deliberately scoped.

Export currently supports selected scopes or 1–20 recordings. Generated packages expire after 7 days. Export history remains for 90 days.

Two important controls are not built yet.

Full account erasure and complete-library export are not implemented. We would rather say that plainly than make a broader promise than the product can keep.

03 / What we cannot verify yet

No easy absolutes.

We do not currently have verified answers for every infrastructure boundary. That matters when you decide what to record.

AI providers: retention and training terms for any AI provider used by Kept are not verified here. Do not infer zero retention or no model training from this page.
Operational access: the boundaries for staff access to recordings, transcripts, and generated output are not verified here. We do not claim exclusive staff access.
Backups and versions: deployed backup and version-retention settings are not verified here. We do not claim a specific deletion window for copies outside the product controls described above.
Not a certification claim: Kept does not claim end-to-end encryption, zero retention, security certifications, or regulatory compliance on the basis of this page.

04 / Your responsibility

Consent still belongs in the room.

Before recording another person or a meeting, follow the laws, workplace rules, and expectations that apply where you are. Kept can help you remember a conversation; it cannot decide whether you are allowed to record it.

Tell people when recording is on.
Keep only audio you have a reason to keep.
Treat AI summaries as fallible.
Use the source audio for important decisions.

read the product details

See plans and current limits.

View pricing