What data does 0xDoktor collect from users?
When a user interacts with the 0xDoktor widget on your site, the following occurs:
- The text of the question is sent to the 0xDoktor API for processing
- Every response is recorded in an answer-audit trail for compliance and quality analysis, scoped to your tenant
- What that record contains depends on the configured storage mode:
- hash_only — only a one-way cryptographic hash of the question/answer is stored; the text itself is not
- truncated (default) — the first 200 characters of the question and answer are stored as a preview, alongside the hash
- full — the complete question and answer text is stored, alongside the hash
- Your account's storage mode is configurable from the admin dashboard; contact the 0xDoktor team if you need it changed from the default
In hash_only mode, 0xDoktor cannot reconstruct what any individual user asked — the hash can be used for usage analytics and deduplication, but not to recover the original question. In the default truncated mode, a bounded preview of the question and answer is retained, not the full text.
What is query hashing and why does it matter?
Query hashing means taking a user's question text and running it through a one-way cryptographic function (like SHA-256). The result is a fixed-length string that uniquely identifies the question content without revealing it. Every storage mode records this hash, in addition to whatever text (if any) that mode retains.
This is a privacy-by-design choice for accounts configured with hash_only. For most support and documentation use cases, you need to know:
- How many questions were asked (volume)
- Whether a question pattern was already seen (deduplication)
- Whether a question was resolved (resolution rate)
If your account doesn't need the exact wording of every question, hash_only mode gives you that analytics value while storing no readable question text.
How long is answer-audit data retained?
Answer-audit records have a configurable retention window (30 days by default). Rows older than that window are deleted by a cleanup job. Contact the 0xDoktor team to confirm the retention window and cleanup cadence currently active for your account.
Does 0xDoktor store conversation history?
In-session context (used so a follow-up question like "can you explain that in simpler terms?" makes sense) is session-scoped and cleared when the session ends. This is separate from the answer-audit trail described above, which persists per the configured storage mode and retention window regardless of session state. 0xDoktor does not build long-term conversation profiles for individual users.
If your team uses 0xDoktor's authenticated admin/operator chat surface, that conversation text is stored in full and is not subject to the answer-audit minimization settings above.
What about the knowledge base content?
Your knowledge base (the documents, PDFs, and web pages you upload) is stored in a private vector database scoped to your tenant. It is not shared with other 0xDoktor customers. It is not used to train any AI model.
You can delete your knowledge base content at any time from the admin dashboard. When you delete content, it is permanently removed from the vector database.
Is 0xDoktor GDPR compliant?
0xDoktor is designed with GDPR principles in mind:
- Data minimization: answer-audit storage mode is configurable per account, from full text down to hash-only
- Purpose limitation: data is used only for answering user questions and usage analytics for your account
- Storage limitation: in-session context is not persisted beyond the session; answer-audit records follow a configurable retention window
- Right to erasure: you can delete your knowledge base content at any time from the admin dashboard; erasure of individual answer-audit or conversation records is not currently supported — contact the 0xDoktor team if this applies to your compliance obligations
For enterprise customers with specific data processing agreements (DPA) requirements, please contact the 0xDoktor team.
Where is data stored geographically?
0xDoktor's production infrastructure runs on EU-based servers by default. If you have data residency requirements for a specific country or region, enterprise plans offer dedicated deployment options.
Who has access to my knowledge base content?
Only your tenant's account has access to your knowledge base. 0xDoktor staff do not access customer knowledge base content in the normal course of operations. Access to customer data for support purposes requires explicit customer authorization and is logged.