Source-linked memory
Durable records preserve the source, time, state, and history needed to inspect why the system remembers something.
Light Reach privacy standard
Every durable claim keeps its source. Processing rules, retention, and deletion paths stay visible across Light Reach products.
Durable records preserve the source, time, state, and history needed to inspect why the system remembers something.
Records can deny external AI, require redaction, or allow processing. Restricted records are excluded before retrieval.
The semantic index holds embeddings and policy metadata, not source text. Every hit is re-authorized against the source record.
Delete a source and dependent memory is reconciled. Account erasure retries across configured providers and reports progress.
Why this matters
Clear data practices are not legal-page decoration. Research connects them directly to customer confidence and AI adoption.
How retrieval works
Scope, state, expiry, sensitivity, and processing mode filter semantic search.
A vector match is never accepted as authorization by itself.
Denied and restricted records stay out; redacted-only records are redacted first.
Deletion receipt
Account deletion enters a durable retry queue. Provider cleanup fails closed, retries with backoff, and a capability-protected receipt reports progress without putting a secret in a URL.
How we compare
Major providers already make meaningful privacy commitments, especially for enterprise products. A blanket superlative would be hard to substantiate. Our narrower advantage is concrete: operating memory that is source-linked, per-record controllable, exportable, and deletable with a visible path.
Open the Actionairy Trust Center