Every record.
Every boundary.
A medical record carries someone’s most sensitive story. Its protection deserves a closer look.
An open view of our architecture and the work still ahead. Production PHI readiness has not been established.
Protection starts
before processing.
The proposed intake pipeline checks a document’s identity, integrity and validation state before making it available.
- 01Scope to organization & matter
- 02Check file integrity & format
- 03Require a clean scan result
If scanning is unavailable, the proposed pipeline blocks the document. Live scanning and storage controls still require validation.
BasisDocument security and storage implementation.
Access has
an address.
A valid identity is the beginning. The organization, matter and document define the context of each request.
Verified in code · organization checksThe October 30 backend review found identity-token checks and organization-scoped queries. Deployed controls, granular permissions and end-to-end isolation still require verification.
BasisBackend identity and chronology code; identity integration plan. Provider details below.
An active membership must connect the person to the firm. The backend must establish this context.
Planned boundary model · not a live permission testProtection is
a system of layers.
Transport, compute and storage have different responsibilities. Our planned architecture makes those boundaries explicit.
In transitHTTPS at ingress; TLS for the database connection in the infrastructure code.
At restEncrypted database and document storage in the proposed implementation.
Before activationVerify deployed settings, key access, tenant isolation and recovery. Deployment remains approval-gated.
BasisStaging infrastructure code and document storage implementation. The live backend environment has not been independently verified.
record.
Keep the source
in the story.
A chronology is easier to scrutinize when each event can be traced back to the record behind it.
The review implementation binds approvals to source versions and integrity checks. Production audit coverage and retention remain open.
BasisVersioned chronology review and integrated evidence code.
AI assists.
People remain accountable.
Organizing evidence does not replace professional judgment. The source, the draft and the reviewer each have a distinct role.
Third-party processing.
Clear responsibilities.
The product uses third-party document and AI processing integrations. These are separate from the website’s AI guide. Review provider identities and status, or read the website AI privacy notice.
Vendor terms, training use, retention, location and BAA applicability must be reviewed before processing sensitive records. No no-training or zero-retention commitment is asserted here.
BasisCurrent AI engine and vendor review requirements.
Clarity is part
of the protection.
What the code shows. What still needs proof.
Product source observations below date from October 30, 2026; website controls were reviewed November 5, 2026. “Verified in code” means source inspection at that date, not a current production security certification. The product frontend remains a synthetic-data preview.
Discuss your requirements (opens Gmail in a new tab)Public website & AI guideThe public site and its optional AI product guide are separate from a medical-record processing service. Website examples use synthetic records only.Website controls
Product demonstration state stays in browser memory. Questions sent to Ask Aureon are processed by this website's AI service providers using public website context. The site uses managed hosting; the separate business mailbox uses a hosted business email service. Requests are bounded and rate-limited; obvious credential patterns are rejected. This application has no chat-transcript database. Account-level retention, access, transfer and provider-agreement settings still require verification. These controls do not authorize confidential or patient information and do not establish product-wide compliance.
BasisWebsite implementation reviewed November 8, 2026; current website Privacy Policy; owner-confirmed service configuration.
Identity & accessSource review found identity-token verification and organization-scoped access. Integration and full isolation testing remain in progress.Verified in code
The October 30 source review found code that verifies signed identity tokens and filters chronology access by organization. A separate identity-provider integration and full cross-tenant validation remain in progress. The product frontend currently simulates sign-in. Backend checks are not proof of a connected, authenticated production workflow. Active memberships, granular roles, database and storage isolation must be verified together.
BasisCurrent backend identity and chronology code; identity integration gate.
Document intake & storageA proposed implementation scopes document access, checks file integrity and requests encrypted storage.In progress
An unmerged implementation binds document access to organization, matter and document identifiers, checks file integrity, and requests encrypted object storage. The October 30 source snapshot used a local storage adapter. The proposed pipeline refuses to release a document when scanning is unavailable. Live malware scanning, storage permissions and recovery tests remain activation gates.
BasisDocument storage implementation and secure ingestion contract.
Encryption & infrastructureThe planned cloud architecture includes HTTPS, private compute and encrypted database storage. Production controls remain unverified.In progress
The infrastructure design specifies HTTPS ingress, private compute and encrypted database storage with TLS. These controls are not verified on a running production stack. Managed hosting serves the product frontend. It does not establish where medical records are processed. Infrastructure provisioning is approval-gated; backend and legacy database location, region and configuration need operational verification. No US-only residency promise is made.
BasisStaging infrastructure code; infrastructure cost and security gates.
Audit & provenanceThe review implementation links source versions, document hashes and approval revisions. Integrated production audit coverage is not yet verified.In progress
Source identity and approval history are distinct from a complete security audit log. Event coverage, storage, access restrictions and retention require verification. A cryptographic hash is an integrity reference; it is not a digital signature or certification.
BasisVersioned chronology and integrated evidence implementations.
AI & subprocessorsSource code includes third-party document parsing, AI processing and optional retrieval. Provider approval is still required.Verified in code
Backend code contains integrations for document parsing, AI processing and optional retrieval of organization rules. These integrations are not evidence of approved production services. Provider identities, agreements, training use, retention, data location and BAA applicability require review before sensitive records are processed. No no-training commitment is established by this source review.
BasisCurrent AI processing code; provider and data-flow review gate.
Retention, deletion & recoveryRetention schedules, deletion evidence, backup limitations and a demonstrated restore remain open requirements.Release blocked
A delete control or backup setting does not prove erasure or recoverability. Policies must cover source files, derived records, logs, legal holds and backups. Recovery objectives and incident escalation need an approved runbook and exercises.
BasisPHI readiness requirements: retention, deletion, restore and incident response.
HIPAA, BAAs & independent reviewPHI readiness depends on contractual review, verified controls and independent assessment. Completed HIPAA compliance or SOC 2 certification is not claimed.Release blocked
Executed BAAs and applicable service coverage have not been established by this review. There is no verified BAA request or download flow. Production use with sensitive medical records remains gated on technical, legal and founder sign-off.
BasisSecurity Foundation release gates and PHI readiness requirements.
Start with
the right questions.
Let’s discuss your data-handling requirements, contractual review and the evidence your firm needs before moving forward.
Talk security with Aureon (opens Gmail in a new tab)Gmail opens a draft. Please do not include medical records or confidential case information.