Zero unintended access
Your clinic's patient names, phone numbers and addresses are encrypted before leaving your device. Even cloud administrators cannot read your patient lists.
NexOP›Data Safety
🔒 Data privacy & security
Bank-grade privacy for your clinic and patients.
NexOP keeps your patient records, contact details and clinical data fully protected — so you can focus on patient care with complete peace of mind.
In one line: patient names, numbers and addresses are scrambled on your device before they ever reach the cloud. Only your clinic can read them back.
The three pillars
How NexOP keeps your practice private
Three things do most of the work. Everything else supports them.
Isolated clinic vaults
Every clinic receives its own unique digital key. Your data is strictly segregated from other practices using NexOP.
Automatic sync and backup
Lost or damaged phone? Sign in securely from a new device to restore access to your entire practice.
How it works
Three steps, none of which you have to think about
The protection happens quietly in the background while you work.
1
Enter data normally
You type in patient information exactly as you do today. Nothing changes in how you use NexOP.
2
Automatic shielding
NexOP scrambles sensitive details on your phone before anything is synced to the cloud.
3
Seamless recovery
Authorised staff see normal, readable details instantly. Anyone else sees only unreadable code.
What is protected
Which information is covered
Patient identity gets the strongest layer. Everything else sits behind account and platform protections.
Encrypted patient identity
- Patient names
- Mobile numbers
- Addresses
- ABHA IDs
Platform protections
- Encrypted connections (HTTPS / TLS)
- Multi-factor account protection
- Role-based staff access
- Clinic-by-clinic separation
Our privacy commitments
How your records are treated
NexOP is paid software for clinics. That is the whole business model, and it shapes how your data is handled.
No advertisementsZero ad tracking or profiling within NexOP.
No shared keysYour clinic key belongs exclusively to your practice.
No public directoryNothing you enter becomes searchable or visible to other clinics.
Recovery codes
Your safety net, and how to look after it
Clinic owners can generate recovery codes that restore access to the clinic's key if normal sign-in recovery is not enough.
✓
Each code works once
Generating a new set invalidates any codes issued earlier.
✓
Store them like keys
Keep them offline or in a password manager — never in a group chat or shared inbox.
Signing out
When you sign out or switch clinic, the key is cleared from that device. It is fetched again once your clinic membership is confirmed at your next sign-in. In a browser it is never stored at all — it lasts only for that session.
Records added before this
Patient records saved before encryption was in place are converted automatically when your clinic loads. Nothing is lost, and there is nothing for you to do.
Frequently asked questions
Plain answers to the usual questions
What happens if I lose my phone or tablet?
Simply sign in on a new device. Your clinic key and records are securely restored without losing data.
Can other clinics see my patient records?
No. Each clinic's records are isolated and protected with a key unique to that clinic.
Who owns my clinic's data?
You do. NexOP and our cloud hosting partners only store and safeguard it on your behalf.
Does using Supabase or AWS mean they own my data?
No. They provide the infrastructure NexOP runs on. That role does not transfer ownership of your clinic's data to them.
Do the exports I download stay protected?
Exported files are readable so you can use them, which means they are not encrypted. Store them as carefully as any other patient document.
Can you guarantee a breach is impossible?
No online system can promise that honestly. What NexOP can say is that patient identity is encrypted before it leaves your device, your clinic's key is kept apart from the database, and only active clinic members can retrieve it.
Technical detail
For IT administrators and technical reviewers
The specifics, for anyone running a security review. Clinical staff can skip this.
Architecture and specifications
- Client-side AES-256-GCM field-level encryption applied before synchronisation via PowerSync.
- Per-clinic 32-byte data encryption key, provisioned through Supabase Edge Functions and released only to active clinic members.
- Envelope encryption: the clinic key is stored wrapped, with the master key held in AWS Secrets Manager — never in the database or the client.
- Supabase cloud database with row level security policies enforcing clinic scope.
- Per-value random nonce and authentication tag, with additional authenticated data binding clinic ID, row ID and column name.
- Key caching: Android encrypted SharedPreferences, iOS Keychain, web in-memory for the session only; cleared on sign-out or clinic switch.
- HTTPS / TLS 1.3 encryption in transit.
Talk to us
Have specific compliance or security questions?
If you are evaluating NexOP for your practice and need detail on how a particular type of record is handled, ask us before you deploy.
Talk to our team