Security and data handling

How QUCHR handles your data.

QUCHR is designed to help organisations work with their safety information while keeping the source of each answer traceable. This page explains how customer documents, AI processing, access and deletion are currently handled.

Customer document storage

New customer-uploaded document originals are stored in AWS S3 in the Sydney region (ap-southeast-2).
These S3 originals are encrypted at rest using AES-256 server-side encryption.
Traffic to QUCHR is protected using HTTPS/TLS.

Document-original storage is only one part of the QUCHR service. Other application data and third-party processing may occur outside Australia depending on the service involved.

AI processing

QUCHR extracts text from uploaded documents for analysis and retrieval.
Extracted text and relevant document sections may be processed by OpenAI for analysis, embeddings and answer generation.
During chat, the user's question, relevant conversation context and retrieved evidence may also be sent for processing.
The current QUCHR document-analysis and RAG pathways send extracted text rather than the original uploaded file bytes.

Traceable answers

QUCHR grounds answers in organisation documents and governed sources.
Relevant citations/source references are returned with supported answers.
This lets users trace an answer back to the source information used — a citation shows where an answer came from, not a guarantee that the answer is correct or complete.

Document deletion

Users can delete customer documents from QUCHR.
Under the current S3-backed storage architecture, deletion removes the original S3 object.
Indexed retrieval material — including document sections, knowledge records and vectors — is removed.
Customer-derived extracted text and AI-generated document profile information retained by QUCHR is purged as part of deletion.

Conversations and account deletion

Individual conversations can be deleted.
Conversations are retained until the user deletes them or deletes their account.
Account deletion is protected by explicit confirmation.
Account deletion removes customer content that QUCHR can technically delete, revokes active sessions, removes conversations, and removes the user account after document cleanup succeeds.
If physical deletion of a current S3-backed original fails, account deletion fails rather than falsely reporting success.

Older documents stored through QUCHR's previous storage provider may be subject to different physical-deletion limitations.

Authentication and account isolation

Passwords are hashed using bcrypt.
Authentication cookies use HttpOnly, Secure and SameSite protections.
QUCHR applies login throttling and temporary lockout protections against repeated failed sign-in attempts.
Customer documents and conversations are scoped to the authenticated organisation/account.

Our approach

QUCHR is being developed with a focus on practical security controls, clear data-handling boundaries and truthful disclosure of current capabilities. We do not represent infrastructure-provider certifications as QUCHR certifications and we do not make security claims that the product cannot substantiate.