Current public version published on the date shown.
Help Center / Privacy
How is privacy reviewed?
What the Aura Capture viewfinder flags, what a flag does and does not prove, how audio is decided, and what data residency means.
Contributor help version 1.0 · Reviewed September 11, 2026
Document record
- Version
- Contributor help version 1.0
- Effective
- Reviewed September 11, 2026
- Scope
- Public policy and review contact
- Control
- Print, save, or request review
Document summary
What this public document covers
- What the Aura Capture viewfinder flags, what a flag does and does not prove, how audio is decided, and what data residency means.
- Customer-specific architecture, controls, commitments, and contractual terms are confirmed during review and contracting.
What the viewfinder flags
The viewfinder may flag faces, screens, documents, and other sensitive regions for review.
A flag is not proof that a blur was applied. It marks a region for review. Blur and watermark lineage is recorded only when an actual transform artifact proves it, so the app does not claim a protection it cannot evidence.
What happens to a capture under review
Raw captures stay quarantined while privacy and rights review are pending. A quarantined capture is not delivered onward during that period.
How audio is decided
Audio follows the approved task preset rather than a global setting. The capture manifest records whether audio was requested, prohibited, or still pending server media inspection, so the decision for a specific capture is auditable.
What residency means
Residency is the region your data is stored in. AuraOne selects the closest region — US, EU, or APAC — so captures stay near you for performance and to satisfy local privacy law. You consent to the data agreement once per region.