Start here
Review the controls and evidence below with the clinic owner. Confirm access and patient-data handling in the product, then request any missing contractual or deployment evidence before approval.
What this guide establishes
Use this guide to prepare a clinic security review. It describes product controls and the evidence you can inspect in the clinic app. It is not an independent audit report or a determination that your clinic meets a legal obligation.
The public security page states that Orvexa AI does not yet hold a SOC 2 report or certification. Confirm the current assurance position and your clinic's requirements before sharing patient data.
- Available evidence includes the public security description, the clinic's membership and role settings, connection state, and Team activity.
- Clinic responsibility includes lawful use, access decisions, source permissions, clinical approval, and secure handling of exported files.
- Request deployment-specific and contractual evidence when a requirement cannot be verified in the product.
Clinic isolation
Every signed-in request is scoped to the user's clinic membership. Integration credentials, patients, templates, reports, billing records, and team activity belong to that clinic boundary.
Account security
Use an individual account, a strong unique password, and the required second sign-in step. Recent verified sign-ins can remain valid for up to two hours of activity; inactivity and explicit sign-out end local access.
- Never share an account or verification code.
- Sign out on shared computers.
- Remove former team members instead of reusing their accounts.
- Review Team activity after an unexpected role, key, or template change.
Patient data and report handling
Orvexa AI minimizes stored patient information and keeps clinic data scoped to the clinic workflow. Uploaded source PDFs and generated reports should be handled as clinical documents even when the product does not retain the finished file.
- Use non-identifying data in templates, screenshots, and support requests.
- Verify patient identity before upload, generation, download, or chart filing.
- Store downloaded PDFs only in the clinic's approved system.
- Do not send patient content to a new vendor without clinic approval.
Audit evidence and support
Use the clinic ID, time, route, integration name, and non-sensitive error message when requesting help. Activity records can establish who changed a configuration without exposing report content or credentials.
- Inspect Team activity for membership, role, SDK-key, and template changes. Record the time, actor, action, and target needed for your review.
- Compare the member list with the clinic's approved access list and remove access that is no longer required.
- Use a synthetic report to verify provider review and final-file handling. An activity entry alone does not prove that clinical content is correct.
Request evidence for your clinic review
Ask for the current security documentation and describe your clinic's requirements without including patient information. Obtain written answers for the deployed service and relevant contract before treating a requirement as satisfied.
- Request the current subprocessor list, each processor's purpose, and applicable data-processing terms.
- Confirm hosting regions, data residency, cross-border processing, and the scope of encryption for stored data.
- Request retention and deletion schedules for source records, uploads, generated files, backups, and activity records. Report-file minimization is not a promise that all patient information is absent from storage.
- Request incident-notification terms, recovery and backup evidence, support coverage, and any contractual service levels.
- Request available independent assessments and their scope. Do not infer certification or legal compliance from a product-control description.
Read the public security controls or request current security documentation. For a suspected vulnerability, use the contact form with “CONFIDENTIAL SECURITY REPORT” and omit patient information and credentials.