Privacy Policy
Last updated: 10 November 2026
This Privacy Policy explains how Nimo (“Nimo”, “we”, “us”, “our”), operated by Asif Asharaf, sole proprietor, trading as “Nimo”, collects, uses, stores, shares, and protects personal data in connection with the gonimo.in software and services (the “Service”). The Service helps independent doctors and small clinics manage patients, appointments, online booking, clinical notes, prescriptions, lab results, pharmacy, and billing.
Our role under the DPDP Act. When a clinic uses Nimo, the clinic is the Data Fiduciary for its patients’ personal and health data under India’s Digital Personal Data Protection Act, 2023 (the “DPDP Act”) and decides why and how that data is processed. Nimo acts as a Data Processor, processing patient data only on the clinic’s documented instructions to provide the Service. This includes data a patient enters themselves on a clinic’s booking page or walk-in form. For the account data of doctors and staff who sign up directly, and for visitors to our own website, Nimo is the Data Fiduciary. This policy should be read with our Terms of Service.
Our promises, in short
Your patients’ records belong to your clinic.
Only your own staff can open them, and only as far as their role allows. Every clinic is walled off from every other clinic inside the database itself.
Your money details never touch Nimo.
Card, UPI and bank details are typed straight into Razorpay, our payment partner. Nimo never sees or stores them. Your bills and payment records stay private to your clinic.
We never sell your data.
We don’t use patient or clinic data for advertising, and the AI providers we use are not allowed to train their models on it.
Everything is encrypted.
Data travels over encrypted connections and is stored encrypted. The most sensitive secrets, like calendar and payment-partner keys, get an extra layer of encryption of their own.
Patient screens are never recorded.
Our analytics never run on any page that can show a patient’s details, and our logs never contain patient names, mobile numbers or clinical notes.
You stay in control.
The clinic owner can take a full copy of the clinic’s data, or delete the account and everything in it, at any time.
The rest of this policy gives the detail. How we protect data day to day is explained in plain words on our Security page.
1. Data we collect
- Account data (doctors, clinic owners, staff): name, mobile number, role, the clinics you belong to, optional recovery email, and authentication credentials (including passkeys or Google sign-in, if you use them).
- Patient data entered by the clinic: name, age or date of birth, sex, contact details, emergency contact, and clinical information such as visit notes, vitals, allergies, diagnoses, prescriptions, lab results, medical certificates, and bills. This is sensitive health data.
- Data patients enter themselves when they use a clinic’s online booking page, booking link, or walk-in QR code: name, mobile number, and — only where the clinic asks for them — month and year of birth, gender, and the reason for the visit.
- Consultation audio, only when a doctor uses the recording feature, which is transcribed into a draft clinical note (see Sections 3 and 7).
- Appointment and operational data: bookings, schedules, working hours, time off, and (if connected) Google Calendar free/busy and event data.
- Clinic profile data that a clinic chooses to publish, such as clinic name, address, logo, opening hours, and its doctors’ names and qualifications.
- Subscription and payment data: plan, billing status, and payment references for the clinic’s Nimo subscription; and, where a clinic takes online payments from its patients, the amount, status, and payment reference of each payment. Card, UPI, and bank details are entered directly with our payment processor and are never seen or stored by us.
- Usage, log, and device data needed to operate, secure, and improve the Service, including analytics described in Section 12. We design our logs not to contain patient names, mobile numbers, dates of birth, or clinical content; we reference records by internal identifiers only, and we hash IP addresses rather than storing them.
2. How and why we use data
We process data to:
- authenticate users and secure accounts;
- store and display patient records to the clinic’s own authorised staff;
- take appointments from patients on the clinic’s behalf, and tell the clinic’s staff about them (in the app, by email, or by Telegram if they turn it on);
- transcribe and summarise visits, draft notes, certificates and summaries, suggest prescriptions, and answer staff questions through Nimo’s assistant (AI features);
- generate prescriptions, documents, bills, and printable records;
- send transactional messages such as login and password-recovery codes;
- publish a clinic’s public page and directory listing, where the clinic has one;
- process subscription payments for the Service;
- provide support, prevent abuse, understand how the product is used, and keep it reliable; and
- comply with applicable law.
We do not sell personal data, we do not use patient or clinical data for advertising, and we do not permit our AI sub-processors to use clinic or patient data to train their models.
3. Sub-processors
We use the following sub-processors, each under their own data-protection terms, strictly to deliver the Service:
- Supabase — database, authentication, and file storage (patient records, accounts, documents).
- Google (Gemini), Groq, OpenAI, Anthropic (Claude), and Sarvam AI — AI transcription, summarisation, drafting, and the assistant. When a doctor uses an AI feature, the data needed for that task (for example consultation audio, the transcript, or the relevant parts of a visit) is sent to the provider configured for that feature. Some of these services process data outside India.
- Vercel — application hosting and performance analytics.
- Resend — email delivery (login and recovery codes, booking notifications to clinic staff, and reports a clinic owner asks for).
- Meta (WhatsApp Business Platform) — delivery of login codes over WhatsApp.
- Telegram— optional new-booking alerts to staff who link their Telegram account. These alerts contain only the time, the doctor, and a link into Nimo — never the patient’s name, mobile number, age, or reason for visit.
- Razorpay— subscription payments to Nimo, and, where a clinic turns on online payments, patients’ payments into the clinic’s own Razorpay account.
- Google Analytics and Microsoft Clarity — product analytics (see Section 12).
We maintain this list as our sub-processors change and remain responsible for their handling of data processed on our behalf.
4. Nimo’s assistant and connected AI apps
Staff can ask Nimo’s built-in assistant questions about their clinic (for example today’s appointments). To answer, the assistant reads only the data that staff member is already allowed to see, and sends what is needed for the answer to the AI providers listed above.
A doctor may also connect an outside AI app (such as Claude or ChatGPT) to their Nimo account from Settings › Me › AI assistants. That app can then read and act on the doctor’s clinic data with the same permissions as the doctor. Once data reaches that app, it is handled under the app provider’s own terms, not ours. The doctor can disconnect it at any time from the same page.
5. Google user data (Google Calendar)
A doctor may optionally connect their own Google Calendar to Nimo from Settings › Me › Calendar. Connection is done through Google’s standard OAuth consent screen, where the doctor explicitly grants access. If connected, Nimo uses the Google Calendar API (the calendar.events scope) to:
- read the connecting doctor’s busy intervals (free/busy) so the patient booking page does not offer time slots that clash with existing calendar events; and
- create, update, and cancel calendar events on that doctor’s own calendar to mirror appointments booked, rescheduled, or cancelled in Nimo.
We access only the calendar of the doctor who connected their account, and only for the scheduling purposes above. Google OAuth tokens are encrypted at rest and are never shared with other clinics or third parties. We do not sell Google user data, use it for advertising, or use it to train AI or machine-learning models. A doctor can disconnect Google Calendar at any time from the same settings page, which revokes Nimo’s access and deletes the stored tokens.
Limited Use. Nimo’s use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
6. Data location & cross-border transfers
Data is stored and processed with the providers above. Some processing — notably AI features, messaging, and analytics — occurs outside India. We transfer only the minimum data needed for the feature in use, and we will not transfer personal data to any country or territory restricted for such transfers by the Central Government under the DPDP Act.
7. Retention & deletion
We retain personal data for as long as the relevant account is active and as needed to provide the Service. Consultation audio is held only until it has been transcribed and is then deleted — and in any case within 24 hours. We do not keep it as a recording.
A clinic (as Data Fiduciary) can exercise its access and erasure rights itself, from Clinic settings → Your data & account:
- Copy of your data. The clinic owner can request a full copy of the clinic’s records (patients, appointments, visit notes, prescriptions and bills). We prepare it and send it to the clinic, usually within a few working days.
- Account deletion. The clinic owner can delete the clinic account. Deletion takes effect 30 days later; until then the clinic keeps working and the owner can cancel at any time. On that date we permanently erase the clinic’s data and every staff login. We keep only a minimal record that the request was made and completed (the clinic’s name, the dates and any note the owner left with it), plus anything the law requires us to retain.
The clinic remains responsible for its own medical record-keeping obligations, so we recommend taking a copy of the data before deleting the account. Requests can also be made by contacting us.
8. Security
Each clinic’s data is isolated from every other clinic at the database layer (row-level security), and access is restricted to that clinic’s own authorised staff by role. Where one person works at several clinics, they see each clinic’s data only while working in that clinic; a clinic group owner’s combined view shows summary figures, not patient records. We use encrypted connections, encrypt particularly sensitive fields (such as third-party access tokens) at rest, apply least-privilege access and rate limits, and take other reasonable security safeguards. No method of transmission or storage is perfectly secure. In the event of a personal-data breach, we will notify the affected clinic and the Data Protection Board of India as required by the DPDP Act, and cooperate in the clinic’s notification to affected individuals.
Financial data. A clinic’s bills, collections, and payment records are protected in the same way as its patient records. The clinic’s own payment-partner keys are encrypted by us before they are stored and are never displayed back. Payment confirmations are accepted only when they carry the payment partner’s valid signature. More detail is on our Security page.
9. Consent & legal basis
Clinics are responsible for having a lawful basis (including obtaining patient consent where required) before entering patient data into Nimo, and for obtaining patient consent to recording where the recording feature is used. By using the Service, clinic users confirm they have such basis. Patients who book through a clinic’s page share their details with that clinic for the purpose of the appointment. Doctors and staff who create accounts consent to our processing of their account data as described here.
10. Your rights
As provided under the DPDP Act, data principals may:
- access and obtain a summary of their personal data we process;
- request correction, completion, updating, or erasure of their data;
- nominate another individual to exercise rights in case of death or incapacity; and
- raise a grievance (see Section 13).
Because the clinic controls patient records, patients should contact their clinic to exercise rights over their clinical data; we will assist the clinic as its processor. Doctors and staff may contact us directly about their own account data.
11. Children’s data
The Service is intended for use by healthcare professionals, not by children. Where a clinic records data about a minor patient, the clinic is responsible for obtaining verifiable consent from a parent or lawful guardian as required by the DPDP Act.
12. Cookies & analytics
We use essential cookies to keep you signed in and to operate the Service securely. We also use Google Analytics and Microsoft Clarity to understand how the website and app are used — for example which pages are visited and where people get stuck — so we can improve them. Clarity can record how a page is used (clicks, scrolling, and what was on screen) to help us find problems. These tools set their own cookies. When you are signed in, we link these records to your internal account ID, clinic, and role so our support team can help you; we never send them your mobile number, email, or patient details. We do not use advertising or cross-site advertising cookies, and analytics data is never used to advertise to you.
13. Contact & grievance redressal
For any privacy question, request, or grievance, contact our Grievance Officer:
Asif Asharaf — Asif Asharaf, sole proprietor, trading as “Nimo”
[Add registered business address], India
support@gonimo.in
We aim to acknowledge grievances promptly and resolve them within the timelines required by law. If you are not satisfied, you may escalate to the Data Protection Board of India.
14. Changes to this policy
We may update this policy as the Service or the law evolves. We will revise the “last updated” date above and, for material changes, take reasonable steps to notify account owners. Continued use after an update means you accept the revised policy.