Product privacy & security

Privacy should be understandable and practical.

Amanua's local-first direction begins with a simple idea: keep personal recordings, transcripts, and documents close to the user wherever product quality allows, with clear processing boundaries and meaningful control.

A practical local-first approach

Keep work close. Make boundaries clear.

Product direction

Process with purpose

On-device and offline-capable processing are design priorities where they can meet product-quality requirements. Each supported capability will be documented as it is verified.

Product direction

Preserve source material

Amanua’s product rules are designed to keep original media, revisions, and receipts distinguishable within governed workflows.

Product direction

Use data deliberately

Names, paths, transcript text, model output, and imported material are treated as sensitive product data—not default telemetry, logs, or external input.

Planned

Make product controls clear

Specific storage, encryption, retention, export, deletion, and platform behaviors will be documented for each qualified build.

Four product principles

Privacy by Design. Confidence Through Control.

Amanua’s approach brings privacy, reliability, and clear product communication together from the start.

Local-first processing

Keeping processing on the user’s device is a current design priority. Offline behavior will be documented for each verified capability.

User control over information

Product rules are designed to preserve source material, make revisions visible, and keep storage, export, and deletion behavior understandable as it is implemented.

Reliability and recovery

Autosave, recovery, controlled revisions, and durable records are active areas of product development.

Transparency and responsible development

Amanua separates active development from planned work and will document privacy and security behavior as capabilities are verified.