Legal
Privacy policy
What personal data AEVONA collects through the app, why, who it is shared with, and the rights you have over it under the DPDP Act 2023.
Last updated 13 August 2026 · AEVONA Healthcare Pvt. Ltd.
In plain language
Your health diary is yours. We store it encrypted on servers in India, and we do not sell it or use it for advertising.
The only people who see it are you and any caregiver you have invited. AEVONA operations staff see booking requests so they can arrange them — they do not browse your diary.
You can export everything you have entered, correct it, and have it erased. Erasure destroys the encryption key for your records, so afterwards nobody can read them, including us.
We ask for your consent before processing your health data, and you can withdraw it.
We measure how the app is used so we can fix what confuses people. That measurement never records a health value, and you can switch it off.
This summary is for orientation only. Where it and the formal text below differ, the formal text applies.
1.Who this applies to, and who is responsible
AEVONA Healthcare Pvt. Ltd. is the Data Fiduciary for the personal data described here, within the meaning of India's Digital Personal Data Protection Act, 2023 (“DPDP Act”). This policy covers the AEVONA mobile application, this website, and our operations systems.
Health data is sensitive. We have designed AEVONA to hold as little of it as the product needs, to encrypt it at the level of individual fields, and to make it genuinely deletable.
This policy describes the system as specified and built. It has not yet been reviewed by legal counsel qualified in Indian law, and must be reviewed before public launch.
2.What we collect
| Category | What it includes | Why we need it |
|---|---|---|
| Identity and contact | Mobile number, name, and optionally age, gender, city, preferred language, and dialysis frequency. | To create and authenticate your account, address you correctly, show content in your language, and arrange bookings. |
| Health records you enter | Weight readings, blood-pressure readings, fluid intake and your prescribed fluid limit, medications and doses taken, and lab results. | This is the product. Without it there is no diary and no trend. |
| Emergency contacts | Names and phone numbers you add, plus the clinic's number added automatically when a booking is confirmed. | So the numbers you need are reachable from the app, including offline. |
| Caregiver links | Which accounts you have linked as caregivers, and when. | To grant and revoke caregiver access, and to show who logged an entry. |
| Bookings | Requested centre, date, time, any notes you add, status, and the AEVONA reference. | To arrange a session with the centre and show you its status. |
| Consent records | That you consented, and when. | To evidence the lawful basis for processing your health data, as the DPDP Act requires. |
| Technical and security logs | Request timestamps, error diagnostics, and authentication events. | To keep the service running and to detect misuse. We do not use these to profile you. |
| Website enquiries | What you type into our contact or clinic-certification forms. | To answer you. Please do not put clinical details in these forms. |
| How you use the app | Which screens you open and in what order, which actions you complete, how long a screen was open, app version, device model, operating system, language, and network type. Tied to a random install identifier, and to your account once you sign in. | To find where the app confuses people or fails them, and to fix it. You can turn this off — see “Your rights”. |
Usage data never carries a health value. It records that you saved a weight reading, never what the reading was. It cannot contain your name, mobile number, address, notes, medication names, lab values, or the identity of a dialysis centre, because the collection format has nowhere to put them.
We do not collect your location, your contacts list, or your device identifiers for advertising. We do not operate advertising networks in the app, and we do not use a third-party analytics service: the usage data above is collected by us, sent only to our own servers in India, and never shared with an analytics vendor.
The install identifier is generated on your device when the app is first installed. It is not an advertising identifier and not a hardware identifier, it is not shared with anyone, and it is replaced if you reinstall the app or ask us to erase your data.
3.Why we are allowed to process it
- Your consent, which we ask for during onboarding and record. This is the basis for processing your health records, and you can withdraw it.
- Performing the service you asked for — for example passing the details a centre needs in order to confirm your session.
- Complying with law, and keeping records we are legally required to keep.
Withdrawing consent stops further processing for that purpose. It does not undo processing already carried out lawfully, and it may mean parts of the service can no longer work for you.
4.How we protect it
- Sensitive fields — your mobile number, your name, and centres' contact details — are encrypted individually with AES-256-GCM, under a key derived per user, rather than relying on disk encryption alone.
- Where we must be able to look a value up without decrypting it, we store a keyed HMAC blind index instead of the value.
- All traffic between your device and our servers is encrypted in transit using TLS.
- Data is stored on servers located in India (Mumbai region).
- Access by AEVONA staff is limited by role. The operations panel exposes booking requests and centre records; it does not expose patients' health diaries.
- A confirmed booking is the only thing that releases a centre's name, address, and phone number to a patient, and that rule is enforced on the server rather than in the app.
No system is perfectly secure. If a breach occurs that is likely to affect you, we will notify you and the Data Protection Board of India as the DPDP Act requires.
5.Who can see your data
| Who | What they can see |
|---|---|
| You | Everything in your own account. |
| Caregivers you invite (up to two) | Your health records, and the ability to add entries. Revocable by you at any time. |
| AEVONA operations staff | Booking requests, including the name, mobile number, city, and any notes needed to arrange the session, plus centre records. Not your health diary. |
| The dialysis centre you book with | The details needed to hold a session for you — typically your name, contact number, and requested date and time. Shared only for a booking you submitted. |
| Nobody else | We do not sell personal data, and we do not share it for advertising or profiling. |
6.Service providers we rely on
We use a small number of providers to deliver parts of the service. Each processes data only on our instructions and only for the stated purpose.
| Purpose | What is shared |
|---|---|
| SMS delivery of one-time passwords | Your mobile number and the code, passed to an SMS gateway operating in India. |
| Push notifications | A device token and the notification text, for example that a booking has been confirmed. Health readings are not sent in notifications. |
| Booking confirmation by WhatsApp | Your mobile number and the confirmation details, sent through the WhatsApp Business API using a pre-approved template. |
| Operations booking log | Booking rows — name, mobile number, city, centre, date, time, notes, status — recorded in AEVONA's operations spreadsheet so coordinators can work the queue. |
| Cloud hosting | All stored data, held in an India region and encrypted as described above. |
AEVONA has not launched. Of the providers above, the SMS gateway, push, WhatsApp, and operations-spreadsheet integrations are specified and built against interfaces but not yet connected to live third-party accounts. This table will be updated with the named providers before launch, and we will not begin sharing with any of them before then.
7.How long we keep it
In outline: your health records are kept for as long as you keep your account, and erased when you ask. The periods for each category, and what survives an erasure request, are set out in full in our data collection and retention policy.
Detailed usage records are kept for 90 days and then deleted. We keep the anonymous daily totals calculated from them — for example how many people opened the app on a given day — indefinitely, because those totals contain no information about any individual.
This is why an erasure request does not change our historical usage totals. Erasure permanently detaches your usage records from your account, so nothing in them can be traced back to you, but a count of app openings from last March stays a count.
8.Your rights
Under the DPDP Act you have the following rights, and AEVONA is built so you can exercise most of them yourself from inside the app.
| Right | How to use it |
|---|---|
| Access and export | Export a complete, machine-readable copy of your data from the app. |
| Correction | Edit your profile and your entries directly in the app. |
| Erasure | Request erasure in the app. We delete your records and destroy the key used to encrypt them. |
| Withdraw consent | Withdraw in the app. Processing that depends on consent stops. |
| Turn off usage analytics | Turn it off in the app's settings at any time, or decline it when you sign up. The app keeps working exactly as before. We honour the setting on our servers, not only on your device. |
| Nominate someone | Contact us to nominate a person to exercise your rights if you are unable to. |
| Complain | Raise it with our grievance contact below. You may also complain to the Data Protection Board of India. |
9.Children
AEVONA accounts are for adults. We do not knowingly create accounts for anyone under 18, and we do not process children's data. If you believe a child's data has reached us, tell us and we will erase it.
10.Contact and grievances
Write to our privacy contact, listed on the contact page, for any question about this policy or any request about your data. We aim to respond within thirty days. A named Grievance Officer will be published here before launch, as the DPDP Act requires.
11.Changes to this policy
We will update this page when our processing changes, and the date at the top shows when it last changed. If a change materially affects how we use your health data, we will ask for your consent again rather than assuming it.
Questions about this document
Write to us and we will answer in Hindi, Gujarati, or English. Requests about your own data are handled under the data collection and retention policy.