The rights articles, as product mechanisms.
Every deployment is a single-tenant system processing only the client's own documents, on infrastructure the client chooses. Compliance is built in, none of it is paperwork after the fact, and all of it is verifiable below.
Article by article, mechanism by mechanism.
Self-service "Export my data" for every signed-in person (JSON, complete), plus an administrator subject-access export for any subject the deployment knows
Correct the source document; the next sweep re-indexes it; the corpus mirrors its sources
Hard delete, everywhere: store and search index in one action; erasure itself lands on the audit log; no tombstone remains
The same export, machine-readable by construction
Not applicable by design: the system answers questions with citations; it decides nothing about persons and executes nothing
Each deployment contracted under a DPA including the sub-processor notice procedure
The deployment generates its own record-of-processing manifest from the configuration that actually runs
Conversation and audit retention are explicit, configurable values enforced nightly; live values shown read-only in the console
Erasure means deletion. Watch it happen.
A deletion that leaves a stub is not an Article 17 erasure, a title or file path can identify a person on its own. So erasure in a Naxis deployment removes the record itself, everywhere it lives, and what remains is only the audited fact that an erasure happened: who ordered it, when, over what scope. Never the content.
Deployments that must not retain message content at all can run the audit log in metadata-only mode, the shape of every event, none of the words.
For your DPO's file.
The DPA template every deployment is contracted under: subject matter, sub-processor notice procedure, audit rights, deletion on termination. Signed per client; shared under NDA where appropriate.
An account action, the request files under your Naxis account, and the answer arrives on its thread.
The GDPR Art. 30 record every deployment generates from its own live configuration: data categories, retention, sub-processors, technical measures, rights handling.
An account action, the request files under your Naxis account, and the answer arrives on its thread.
GDPR Articles 15, 16, 17, 20 and 22 mapped to the product mechanism that fulfils each one: the page your DPO checks first.
An account action, the request files under your Naxis account, and the answer arrives on its thread.
The DPA structure and the sub-processor notice are also readable in the trust library, request forms never gate the reading.
GDPR and your knowledge engine, answered
Is AI over company documents even GDPR-compatible?
Yes, when it is built as a processor should be: a single-tenant deployment processing only the client's own documents, under a DPA, with export, erasure and records of processing implemented as product mechanisms. That is the entire design position of Naxis Assistant.
How does erasure actually work?
As deletion, not flagging. Erasing a person's conversations or a single document removes the records from the store and the search index in one action; no tombstone remains. Only the audited fact that an erasure happened survives.
What are the Article 30 records, and who writes them?
Nobody writes them, the deployment generates its own record-of-processing manifest from the configuration that actually runs: data categories, retention values, sub-processors, technical measures, rights handling. Generated paperwork cannot drift from reality.
Who are the sub-processors?
At most two categories, and the fullest configuration has none: a self-hosted deployment answering on its own self-hosted AI model processes everything in-house. Otherwise: the Naxis AI service (zero-retention DPA terms, receives only the question and permitted excerpts) and, for managed hosting, an EU data-centre provider. Changes follow the DPA's written notice procedure.
How do we get the DPA?
Request it from your account, the template arrives on your own thread, and the signed copy is executed per client. Your legal team can see the structure on this page first.
What does this website itself collect?
No analytics, no third-party scripts, no cookies while signed out. An account stores what you give it; the interactive demo records usage under an explicit opt-in described in the privacy notice.
Read the whole record.
Architecture, audit chain, sub-processors, the manifest, one page, no forms.