Privacy policy

What we collect on this website

• What you type into the demo, quote or contact form: name, work email, phone, organisation, facility details and your message.
• Attribution parameters in the link you arrived by (for example a campaign tag), so we know which page brought you here.
• Standard server logs: IP address, browser, pages requested and timestamps, kept for security and capacity planning.
• A bot-check token from Cloudflare Turnstile on the form, if enabled. No tracking cookies are set. If you allow it in the notice, we count visits with Vercel Web Analytics, which sets no cookies and records the page viewed, the referring site, country and device type, plus a count of demo requests with the plan and page they came from, never what you typed. You can change that choice any time from the Cookies link in the footer. Your theme preference and your choice are stored only in your browser.

Mobile app

The Curanto app for Android and iPhone is for the staff of hospitals and clinics that use Curanto. It has no sign-up: the hospital creates each login, and it is the data fiduciary for what its staff see and record in the app, just as on the web.

• So that staff can keep working without a connection, the app keeps an offline copy of the records the signed-in person's role lets them see. Each person gets a separate encrypted database, and its key stays in the phone's secure keychain only while that person is signed in. Signing out, or the app learning that the session has ended, deletes the key, after which the copy cannot be read. Changes that had not uploaded yet wait in it until the same person signs in again. One phone keeps copies for at most three people and deletes the least recently used copy that has nothing left to upload. Android's backup of the app's data is turned off.
• Also kept on the phone: the sign-in token, in the secure keychain; settings such as theme and language; and documents you open or share from the app, such as an invoice PDF, which pass through the app's temporary cache and are not removed when you sign out.
• The app asks for the microphone (voice dictation and, when a doctor starts it, the AI scribe) and for the camera or photo library (patient photos, photos of lab reports and expense receipts, the hospital logo) when you first use those features. It also asks for Face ID, a fingerprint or the phone's passcode to unlock it when app lock is on, and, where push notifications are enabled, for permission to show them. It does not ask for location, contacts or calendar access.
• Dictation and scribe audio is sent to our server in short clips and on to a speech recognition provider for transcription. Each clip is deleted from the phone once sent, and the audio is not stored. Photos are uploaded to the hospital's file storage and attached to the record they belong to; a photo attached to a question for the Medi assistant is sent with that question to the AI provider through OpenRouter, as described below.
• When push notifications are on, the app registers the phone's push token with us, and alerts are delivered through Expo and Apple or Google. An alert carries only a category and a count, such as "1 dose is due now", never a patient's details. Signing out of the app while online stops alerts to that phone.
• The app has no crash reporting or usage analytics.

Account and data deletion

Inside the product the hospital or clinic decides what is kept and what is deleted, because it is the data fiduciary and the law requires it to keep medical and billing records for set periods. Curanto gives it the tools below and does not delete its records on its own.

• Staff accounts. The hospital creates its staff's logins, and there is no button, in the app or on the web, for staff to delete their own. When someone leaves, the hospital's administrator deactivates them (Staff, the person, Deactivate). They lose access to that hospital at once, every session they have on the web, desktop or mobile app is ended, and the next time their phone connects, the app deletes the key to its offline copy. What they recorded stays in the hospital's records under their name, and the audit log is never edited, because the hospital must be able to show who did what. To ask for your staff login to be removed, contact your hospital's administrator; if you cannot, write to hello@curanto.in and we will pass your request to the hospital.
• Patients. A patient who wants a copy of their data, a correction or erasure, to nominate someone to act for them, or to complain, asks the hospital. Where the hospital offers Curanto's patient portal, the patient can also raise it there after signing in with a one-time code sent to the mobile number on their record. Each request goes into the hospital's Data & privacy requests register, which shows the deadline (30 days unless the hospital sets another) and flags requests that are overdue. Staff must confirm the requester's identity before a request is fulfilled.
• Erasure. Curanto has no one-step erasure of a patient's records, and closing a request deletes nothing by itself. The hospital decides what it may erase: records the law requires it to keep cannot be erased, and its reply says so. It can correct a patient's details, archive a patient record so it leaves everyday use, and permanently anonymise a stored document, which also deletes the file. Retention settings flag documents that are past their retention period for the hospital to act on; nothing is deleted automatically.
• When a hospital leaves. The hospital can export its data at any time (Backup & data export, then Export all data: a copy of all its records with a list of its stored files). When the contract ends, its data stays exportable for 90 days and is then deleted from the live database and file storage. If the hospital asks in writing, we provide a final export and delete its data sooner, within 30 days of the written instruction, and confirm the deletion in writing. Encrypted backups are not edited to remove one hospital; if a backup is ever restored, we delete that hospital's data again before the restored system is used.

Grievance Officer

Under the Digital Personal Data Protection Act, 2023 and the Digital Personal Data Protection Rules, 2025, you can ask our Grievance Officer any question about how we process your personal data, or raise a grievance about it.

Role

Grievance Officer, Ralyxion Labs Private Limited

Email

grievance@curanto.in

• Tell us your name, how to reach you and what the grievance is about. If it concerns your records at a hospital or clinic that uses Curanto, say which one. We may ask you to confirm who you are before acting on a request about your data.
• We acknowledge every grievance within 2 working days and aim to resolve it within 30 days. In every case we respond within 90 days of receiving it, the outer limit the Digital Personal Data Protection Rules, 2025 allow.
• For records a hospital or clinic keeps in Curanto, that hospital is the data fiduciary. We pass your grievance to it and help it respond within the same limits.
• If you are not satisfied with our response, you may complain to the Data Protection Board of India once this process is complete.