Security at Ariqu
Clinical data deserves more than promises.
Ariqu holds some of the most sensitive data there is — medical records. This page describes, in plain language, how that data is protected in production today. Nothing here is a roadmap item, and where a claim can be checked from your own browser, we’ve told you how.
Where your data lives
Every byte of clinical data stays inside India, encrypted wherever it rests.
Hosted in India, always
All infrastructure — database, file storage, compute — runs in the AWS Asia Pacific (Mumbai) region. Patient data is never stored outside the country.
Encrypted at rest
The database and every stored document (prescriptions, reports, letterheads) are encrypted at rest with AES-256 on AWS-managed storage.
Sensitive credentials double-locked
Payment gateway credentials are additionally encrypted at the application layer with AES-256-GCM, with keys held outside the database — a database copy alone reveals nothing.
On the wire
Nothing travels in the clear, and browsers are told to never try.
TLS on every connection
All traffic between your browser and Ariqu is encrypted with modern TLS. Plain HTTP is never served.
See for yourself: Check any ariqu.com domain at ssllabs.com/ssltest
Strict security headers
Every page ships a Content-Security-Policy that only executes scripts we signed for that specific response, plus HSTS (browsers refuse insecure connections for a year), clickjacking denial, and MIME-sniffing protection.
See for yourself: Scan ariqu.com at securityheaders.com
Sessions that scripts cannot steal
Sign-in tokens live in httpOnly cookies — invisible to any JavaScript running in the page, including anything an attacker might inject. Every state-changing request additionally carries an anti-forgery token.
See for yourself: DevTools → Application → Cookies: the session cookie shows HttpOnly ✓ Secure ✓ SameSite=Strict
Who can see what
Isolation and least privilege are enforced in the database and the API, not just hidden in the interface.
Hard tenant isolation
Every clinic is a separate tenant. Postgres row-level security and per-request tenant binding mean one clinic’s staff can never query another clinic’s patients — even a bug in application code hits the database wall.
Role-based access, enforced server-side
Doctors, receptionists, nurses, pharmacists and admins each hold an explicit permission set checked on every API call. A pharmacist cannot read consultation notes; a receptionist cannot print a GST invoice; clinical records open only to a patient’s own doctors.
Audit trails
Administrative and clinical actions are logged with who, what and when — including every action taken by Ariqu’s own staff on the platform. Plan or feature changes to any clinic trigger an immediate internal notification naming the person who made them.
Signing in
A stolen password alone opens nothing.
Two factors on every staff login
Clinic staff sign in with a password plus a one-time code emailed on every login. Ariqu’s own admin panel goes further: no passwords at all — access is a fresh code to a company mailbox, every time.
Patients too
The patient portal uses one-time email codes — no passwords for patients to reuse, forget, or have breached elsewhere.
Sessions that end properly
Sign-out revokes the session on the server, not just in your browser. Deactivating a staff member cuts their access immediately, across every device.
Payments & third parties
The least data we can hold is the safest data we can hold.
We never touch card details
Online payments run through Razorpay, a PCI-DSS Level 1 certified gateway. Card numbers, UPI credentials and bank details go directly from the payer to the gateway — Ariqu’s servers never see or store them.
Named sub-processors only
A short, fixed list of vetted providers supports the platform (cloud hosting, AI transcription, email, WhatsApp delivery, payments). Each receives only the minimum data its function needs, under contract. The full list is available to any customer on request.
AI with boundaries
AI features (consultation scribe, document drafting) process data through enterprise APIs whose terms exclude using customer data to train models. AI output is always reviewed by the clinician before it becomes part of a record.
Where we are honest about the journey
Ariqu is a young company and we’d rather under-claim than over-promise: we do not yet hold ISO 27001 or SOC 2 certification. The controls on this page are what an auditor would find if they looked today, and formal certification is on our path as we grow. Hospital and chain security teams are welcome to send us their assessment questionnaires — we answer them specifically, not with boilerplate.
Found a vulnerability? Tell us first.
We take reports from security researchers seriously and respond quickly. Please give us a reasonable window to fix an issue before any public disclosure.
support@ariqu.com