Trust
The layer underneath everything.
TRUST is not a page QUANT wrote after the fact. It is where the architecture starts.
Privacy
Data minimisation by default. QUANT asks for the least it can work with, and holds it for the shortest time that is useful.
Consent
Memory is opt-in. Nothing is inferred and quietly persisted, and every stored item is visible and removable.
Child safety
KidSafe has its own age modes, restricted memory, guardian controls and a category-only safety log.
AI safety
Requests are screened before they reach a provider. Blocked categories are recorded; blocked content never is.
Provenance
Every answer says whether it came from a live provider or QUANT's demo engine. We never imply an integration we do not have.
IP awareness
Placeholder media is drawn originally in-product. No third-party imagery, no scraped assets.
Human oversight
QUANT suggests, drafts and organises. It does not send, book, buy or commit on your behalf.
Auditability
Every provider call is recorded as a normalised run — provider, model, feature, usage, latency, status. Prompts are not logged.
In writing
Where the detail lives.
Two documents are maintained in the repository alongside the code, so the architecture and the promise stay in the same place.
- SECURITY.md — key handling, request validation, provider failure behaviour, and what is never logged.
- PRIVACY_ARCHITECTURE.md — data categories, consent, storage, deletion, memory, minors, analytics and provider data flows.
You can review what this build is holding about you right now on the memory page, and clear it from settings.