Security and data residency
How this platform protects what you upload, described plainly rather than in marketing terms.
Encryption of your files
Every file you upload is encrypted individually with AES-256-GCM, using its own data key. Those per-file keys are themselves wrapped by a master key that never leaves this platform's own key storage.
Reading a file back includes a SHA-256 integrity check, so silent corruption or tampering with the stored bytes is detected rather than served to you unnoticed.
Tamper-evident audit trail
Every meaningful action on your account, including sign-in, submissions, AI processing steps and reviewer decisions, is written to an append-only audit log.
Each row is chained to the one before it with a SHA-256 hash. Changing or deleting a past row breaks the chain, so tampering is detectable rather than invisible. Nothing can update or delete an existing row, by database permission, not just by application code choosing not to.
Human review before anything is signed
AI assistance is used to understand submissions, search prior art and draft comparison notes. None of that draft output reaches you as a finished opinion: a qualified human reviewer checks and signs every opinion first.
Your confidential content is never used to train AI models
Confidential customer content is never used to train general-purpose AI models without your explicit, informed permission. This holds regardless of which AI provider or driver processes your submission.
Subscription and usage data
Your plan, seats and usage (screening quota consumed, opinions requested) are stored against your account and used only to enforce your plan's own limits and to show you your own usage on your billing page. This data is not shared between accounts or organisations.
Data residency
This platform is designed to run entirely on infrastructure in the UAE North (Azure) region: application, database and encrypted file storage all in the same region, under this venture's own subscription. This is target architecture - effective at go-live: today, the platform runs in local development only, and this statement will be updated once that architecture is proven live rather than just planned.
Full technical detail: docs/RESIDENCY.md in this project's own repository.
Data residency status: target architecture - effective at go-live.