Hospital workspace privacy

This initial product is for scheduling and administration, not medical records. Do not enter real patient information before the hospital and AURTIV have completed appropriate privacy, legal, security and contractual reviews.

Information the pilot stores

Hospital account and team details; clinician and department names; patient registration identifiers, names and optional contact details; appointment dates, times, attendance states and creator IDs; account and operational audit events.

Who can view it

Hospital administrators, managers and authorised reception operators can access patient registration and appointment records belonging to their hospital workspace. Read-only viewers see aggregate operational numbers and public-facing clinician/department lists, but not identifiable patient records. AURTIV authorised database operators can access underlying infrastructure records for administration.

Privacy, security and retention

Authenticated sessions, company separation and role checks are used. Clinical notes, diagnoses, treatment information, prescriptions and test results are not supported. Account and operational records are retained until a separate agreed export, deletion or retention process is carried out. Subscription expiry does not automatically delete records.

Third parties

Cloudflare provides hosting and database infrastructure. The pilot does not connect to a healthcare exchange, government identity system, messaging gateway, insurance system or medical AI service.

Questions

For a privacy request, contact AURTIV through the form on the company website. Each hospital remains responsible for determining its lawful data collection and access processes.

Return to hospital workspace ↗︎

Optional Firebase sign-in

If you choose Google, email-link or mobile OTP sign-in, Google Firebase processes your sign-in identity and verification information. Phone numbers are processed by Google for authentication and abuse prevention; SMS OTP is available for Indian mobile numbers. AURTIV stores the linked Firebase user identifier and a sign-in label, while existing company permissions control business-data access. This integration does not send your business records to Firebase. The browser temporarily stores the email address used to complete an email sign-in link. Existing password login remains available. See Firebase privacy information and Google privacy.