Privacy policy

1. Information we handle

Brioxa stores the information submitted to the product, including account details, email verification and consent records, guided-intake conversations, uploaded images or PDFs, care-team messages, care plans, prescription drafts and issued documents, clinician decisions, medical records, appointments, notifications, and support requests. Use fictional health information and sample files in this development release.

Onboarding waitlists

When you join a patient or doctor waitlist, we store your name, email, city, optional phone number, doctor specialty when relevant, and your permission to contact you. We use these details to manage the waitlist and contact you when onboarding reopens. Joining does not create an account. These details are stored in Cloudflare D1. When configured, Resend delivers an email alert containing these details to the Brioxa operator, and Google Sheets stores a copy for waitlist management. Access is restricted to authorized operators; waitlist details are not sent to the clinical AI service. Waitlist entries are kept until onboarding processing no longer needs them or you request removal through our contact page. Removal requests are handled across the database, spreadsheet and operator email copies. There is currently no automated waitlist deletion schedule.

2. How information is used

Information is used to provide and secure the service, keep a continuous care record, organize patient-provided context, present drafts for clinician review, screen for urgent symptoms and vital-sign reports, respond to support requests, and maintain audit records. AI-generated material is treated as a draft and does not become a care decision without clinician review.

3. Who can access information

Patients can access their own workspace and uploaded files. Clinicians can access information for their assigned patients. Opening a patient chart or file is recorded in an access log. Cloudflare provides database and file storage. When account email delivery is configured, Resend processes the recipient address and verification or password-reset email; those messages do not include clinical content. When AI is configured, OpenAI receives the session text and relevant health-profile fields to screen urgency, ask intake questions, summarize source statements, and format clinician-directed prescription drafts. Uploaded file contents are not sent for interpretation. Model calls request no stored response. Information is not sold.

4. Safety and emergency signals

Every intake message is screened using reported symptoms, vital signs and risk modifiers before any reply. Uncertain assessments and AI outages pause intake for human assessment. Escalations create a priority review item, audit event and, when a clinician is assigned, an in-app notification. Emergency numbers use the country selected in your profile. Brioxa is not an emergency service and a flag does not guarantee that a clinician has seen or acted on it.

5. Security

Brioxa uses encrypted transport, secure session cookies, password derivation, role-based authorization, parameterized database queries, and audit logging. Personal accounts can enable an authenticator and save one-use recovery codes. Each new demo has an isolated copy of fictional data. No system can promise absolute security.

6. Current retention schedule

The table describes the controls implemented in this development release. Access expiry and physical deletion are different. There is no automated retention purge for clinical records, support requests or fictional demo workspaces.

Retention periods for a real clinical service, legal holds, provider backups and a guaranteed deletion deadline must be approved and implemented before real patient information is accepted. This policy does not promise immediate deletion from infrastructure backups.

7. Your choices

Use Account settings to correct your profile, choose in-app notifications, review consent history, download your data, or delete your account. Withdrawing data-use or remote-care consent pauses clinical features while leaving account and privacy controls available. Account deletion removes profile and clinical data, revokes sessions, and anonymizes related audit details. Uploaded files become inaccessible immediately and are queued for deletion; temporary storage failures are retried. Privacy questions can also be submitted through the contact page.

8. Children

Brioxa is not intended for independent use by children. A production release involving minors would require an appropriate guardian-consent and age-assurance process.

9. Governing law

This India-focused service and this policy are subject to applicable laws of India. Nothing in this policy limits statutory privacy or consumer rights. India’s Digital Personal Data Protection Act, 2023 and its rules apply as their provisions come into force; the official 2025 Rules notification provides for phased commencement. This development release does not claim completed regulatory compliance.

10. Privacy grievances and operator identity

Grievance Officer: Appointment and name have not yet been confirmed for this development release.

A designated officer’s contact address is awaiting confirmation. You can submit a privacy or data request at support@brioxa.app or through our contact form. This is the current product-support route, not a claim that a statutory grievance process is operational.

The registered entity, address and support-channel status are shown on the contact page. Verified operator and officer details are required before a real-data launch.

11. Changes and contact

This policy may change as Brioxa’s services and legal obligations develop. Material changes will be reflected by an updated effective date. Privacy questions and requests can be submitted through the contact page.