Collect less
Data minimisation
Collect only what the task needs, so the medical context stays focused and the exposure stays small.
Security & privacy
Privacy sits at the centre of the design.
How we intend to protect medical information, and what we are not claiming today.
Read this first
Design intent, not certification.
This page describes how we are designing Astraon AI. It is not an audit result, a certification or a compliance claim.
Treat everything here as a statement of intent. If you need specifics for a security review, ask us and we will answer plainly.
Ask us for detail Design principles
Four principles, one foundation.
They shape every decision about how medical information is handled.
Gate access
Access control
Layered permissions, so only authorised users can reach sensitive information.
In transit and at rest
Encryption
Our aim is to protect data in transit and at rest with current, well-established cryptography.
Record who did what
Audit trails
Access and changes are designed to be recorded, so it is possible to verify who did what, and when.
Regulatory context
Built with the rules in view.
We know which frameworks govern medical data. Awareness is where we are; certification is not.
-
India's DPDP Act, 2023
We are designing with the principles of the Digital Personal Data Protection Act in mind.
Awareness · not certified -
HIPAA-aware
The architecture is informed by HIPAA principles. That is not a compliance certification.
Awareness · not certified
What we ask of you
Share context, not records.
Forms on this site are public and are not secure channels. If an evaluation needs sensitive information, we will agree a secure channel after first contact.
Fine to send
- Your organisation and role
- What you want to evaluate
- Questions about our approach
Please never send
- Patient names or identifiers
- Health records, scans or reports
- Any confidential medical information
Questions about our approach?
Ask about security, privacy and data handling. We will answer plainly.