Legal Document
This Privacy Policy ("Policy") governs the collection, use, storage, and disclosure of information in connection with DavAI (the "Application"), a medication reminder and adherence-tracking application — covering any prescription across any medical specialty — developed and maintained by Arsh Duggal (the "Developer"). The Developer is based in India, and this Policy is intended to align with India's Digital Personal Data Protection Act, 2023 ("DPDPA") and its rules, in addition to describing the Developer's practices generally. By downloading, installing, or using the Application, you ("User," "you") acknowledge that you have read, understood, and agree to be bound by this Policy. If you do not agree with any part of this Policy, you should not use the Application.
The Application collects the following categories of information, each described below with its purpose and storage location:
| Category | Examples | Collected When |
|---|---|---|
| Profile identifiers | The name entered for yourself, and for anyone you add as a dependent | App setup, and whenever a new profile is added |
| Pairing codes | A short code associated with each profile, used to link a guardian's Device to the Self Profile they're watching (see Section 7) | Profile creation |
| Medication records | Medicine name, dosage form, frequency, duration, free-text instructions, and daily dose-taken status | Manual entry, or extraction from a scanned prescription; a Self Profile's current medication list syncs to the Developer's server (Section 7) if any guardian is watching it |
| Push notification token | A device identifier issued by Apple (iOS Devices) or obtained via Google's Firebase Cloud Messaging service (Android Devices), used only to deliver a missed-dose alert to a guardian's Device | When a Device is set up to watch a Self Profile as a guardian |
| Missed-dose alert log | Which profile, medicine, and date a missed dose relates to | Automatically, when a watched Self Profile's dose goes unmarked 30+ minutes past its scheduled time |
| Prescription imagery | A photograph captured or selected by the User, passed through the Developer's scan relay described in Section 6 and not retained by it | Use of the optional "Scan Prescription" feature |
| Consent record | Timestamp of acceptance of this Policy | App setup |
The Application does not collect analytics identifiers, advertising identifiers, precise or coarse location data, contact lists, biometric data, or any category of information not expressly listed above.
Information described in Section 3 is used exclusively for the following purposes:
Information is not used for advertising, is not sold, and is not used to build behavioral or marketing profiles. The Application does not track Users — including child Users, see Section 16 — across other apps or websites for any purpose.
Where applicable data protection law requires a legal basis for processing, the Developer relies on: (a) the Data Principal's consent, obtained via the in-application acceptance step prior to profile setup and prior to any use of the prescription-scanning feature, consistent with the DPDPA's requirement that consent be free, specific, informed, unconditional, and unambiguous, given through a clear affirmative action; and (b) legitimate interest (referred to under the DPDPA as a "legitimate use" in certain circumstances) in operating the core reminder, tracking, and guardian-alert functionality of the Application, as described in Sections 7 and 8. Consent for prescription-photo processing, and separately for guardian cross-device sync, may each be withdrawn at any time — the former by declining to use the "Scan Prescription" feature, the latter by removing the relevant Profile or guardian link — as easily as it was given, without affecting the lawfulness of processing carried out prior to withdrawal.
This transmission constitutes the entirety of data disclosed by the Application to any third party. Per OpenAI's published API data usage terms, data submitted through the API is not used to train OpenAI's models by default, and is subject to OpenAI's own Privacy Policy, which governs OpenAI's independent processing of that data as a separate data controller for its own retention and security practices. Cloudflare processes the transient scan request, and the persistent guardian-sync dataset described in Section 8, as the Developer's infrastructure provider and is subject to Cloudflare's Privacy Policy in that capacity. Google processes an Android guardian Device's push token and the missed-dose alert content solely to deliver that notification, subject to Google's Privacy Policy. No API key or credential of any kind is stored on, or ever visible from, the User's Device. Users who wish to minimize the information contained in a submitted photograph may crop or redact portions of a document not necessary for medication extraction (e.g., full addresses or identification numbers) prior to submission.
Other than the disclosures described in this Section, the Developer does not sell, rent, lease, or otherwise disclose Personal Data to any advertiser, data broker, analytics provider, or other third party.
A pairing code is generated for each Self Profile. A guardian must enter that code — obtained directly from the person they're caring for — to link their Device; the code is validated against the Developer's server before linking succeeds. Once linked, the Self Profile's Device automatically syncs its current medication list (medicine name, dosage form, frequency, instructions, duration, and today's dose-taken status) to the server on every change. This synced copy does not include the User's name beyond what was entered for the Profile, adherence history, or any data from other Profiles on the same Device. A guardian's view is read-only: the Application does not allow a guardian to edit, delete, or mark doses taken on someone else's Profile.
To deliver a missed-dose push notification, a guardian's Device registers a platform push-notification token — issued by Apple for iOS Devices, or obtained via Google's Firebase Cloud Messaging service for Android Devices — with the Developer's server, associated only with the pairing code they're watching. The server checks, on a recurring automated schedule, whether any watched Profile has a dose that has gone unmarked 30 or more minutes past its scheduled time; if so, it sends the notification directly to Apple's Push Notification service or Google's Firebase Cloud Messaging service, as applicable to the guardian's Device, which delivers it. This check-and-alert log (which profile, medicine, and date — not the medication list itself) is retained on the server so the guardian's Application can display a short history of past alerts.
A User may remove a guardian link (or a Self Profile may stop syncing) at any time by removing the relevant Profile within the Application, which deletes that Profile's synced data and any registered push token from the Developer's server. A User who never sets up or is never linked to a guardian relationship has no data described in this Section transmitted to or stored on the Developer's server.
The full Personal Data described in Section 3 — every Profile's complete medication records, adherence history, and settings — is held in Local Storage on the User's Device only, using the standard application-storage mechanisms provided by the Device's operating system (iOS or Android). The Developer does not operate, and this Application does not transmit data to, any centralized database for that full dataset.
The exception is the narrower guardian-sync dataset described in Section 7: for a Self Profile that has at least one linked guardian, a reduced copy (current medication list and today's dose-taken status only — not adherence history, and not data from any other Profile on the Device) is stored in a Cloudflare D1 database the Developer operates, along with any guardian push notification tokens and a log of past missed-dose alerts for that Profile. This copy persists on the server for as long as the guardian link remains active, is overwritten on every sync (not accumulated as a history), and is deleted from the server when the Profile or the guardian link is removed within the Application, as described in Section 7.
Data held in Local Storage is retained for as long as the Application remains installed on the Device, or until the User deletes a specific Profile or record within the Application. Removing a Profile deletes that Profile's medications, reminders, and any related missed-dose log entries from the Device, and (where applicable) its synced copy and push token from the Developer's server. Uninstalling the Application permanently and irretrievably deletes all associated Local Storage data in accordance with the Device operating system's standard app-removal behavior; because a push token tied to the uninstalled Device also stops functioning, no further guardian alerts are sent for Profiles it was linked to, though the last-synced server-side copy may persist until separately removed or naturally superseded.
The Application relies on the security architecture provided by the underlying mobile operating system (iOS or Android) to protect Local Storage, including operating-system-level application sandboxing that prevents other applications from accessing the Application's stored data without authorization. Transmission of a prescription photograph to the Third-Party Service Provider described in Section 6, and of the guardian-sync dataset described in Section 8, occurs over an encrypted (HTTPS/TLS) connection. While the Developer takes commercially reasonable steps consistent with these platform protections, and with the DPDPA's requirement to implement reasonable security safeguards to prevent a personal data breach, no method of electronic storage or transmission is completely secure, and the Developer cannot guarantee absolute security.
Requested solely to allow the User to capture or select a prescription image for the scanning feature described in Section 6. This permission may be revoked at any time via Device settings; doing so disables only the scanning feature, and does not otherwise restrict the Application's core functionality of manual medication entry and reminders.
Requested for two purposes. First, to deliver the User's own medication reminders: this content and scheduling are generated and delivered entirely on-device by the operating system's local notification framework, and no reminder data is transmitted to any server in connection with this purpose. Second, on a Device set up as a guardian, to receive a missed-dose push notification from the Developer's server as described in Section 7; this requires the Device's platform push token to be registered with that server, as disclosed in Sections 3 and 7. Revoking notification permission stops both reminder display and push delivery, but does not otherwise restrict the Application's core functionality.
As a Data Principal under the DPDPA, and because substantially all Personal Data described in this Policy resides in Local Storage under the User's direct and exclusive control, the User is able to exercise the following rights, most of them directly within the Application without contacting the Developer:
For any request the User is unable to complete directly within the Application, or for questions regarding this Policy, the User may contact the Developer using the details in Section 23.
Under the DPDPA, a Data Principal has the right to nominate another individual to exercise their rights under the Act on their behalf in the event of the Data Principal's death or incapacity. Because the Application does not operate an account or sign-in system, this nomination is handled outside the Application: a User who wishes to designate a Nominee may do so by writing to the Developer at the contact details in Section 23 with the Nominee's identity and contact information. On reasonable verification of the Nominee's identity and of the circumstances (the Data Principal's death or incapacity), the Developer will treat requests from that Nominee as if made by the Data Principal, solely with respect to the Personal Data described in this Policy.
This mechanism is distinct from, and not a substitute for, the Application's in-product Guardian feature described in Section 7. The Guardian feature is a live medication-monitoring feature a User sets up voluntarily while active and able to do so themselves, and linking a guardian does not itself grant that guardian any rights over the User's Personal Data or account under this Policy or the DPDPA.
In accordance with the DPDPA, the Developer has designated the contact details in Section 23 as the point of contact for grievances regarding the processing of Personal Data under the Application. A Data Principal may submit a grievance by email; the Developer will acknowledge receipt and endeavor to resolve the grievance within a reasonable time, and in any event within the period prescribed under the DPDP Rules. If a Data Principal's grievance is not resolved to their satisfaction, they may escalate the matter to the Data Protection Board of India, established under the DPDPA, or to any other competent authority.
In the event of a personal data breach affecting Personal Data processed by the Developer — practically, this means the guardian-sync dataset described in Section 8, since substantially all other Personal Data never leaves the User's Device and so is not something the Developer could breach — the Developer will notify the Data Protection Board of India and affected Data Principals in the manner and within the time prescribed under the DPDPA and the DPDP Rules. Because Local Storage data resides solely on the User's own Device under the User's control, the Developer has no visibility into, and bears no notification obligation for, a compromise of a Device itself (e.g., loss, theft, or malware) — Users should follow their Device manufacturer's guidance for securing a lost or stolen Device.
The Application may be downloaded and used by Users located in jurisdictions outside the Developer's home jurisdiction. Substantially all Personal Data is held in Local Storage on the User's own Device, with three exceptions: the transmission described in Section 6, processed by OpenAI; the guardian cross-device sync described in Section 7, processed by Cloudflare on its global network; and, for Android guardians, push delivery via Google's Firebase Cloud Messaging service — each in accordance with that provider's own privacy practices and applicable international data-transfer safeguards as described in its respective privacy policy (linked in Section 6).
Under the DPDPA's cross-border transfer regime, transfer of Personal Data outside India is permitted by default, except to a country or territory the Central Government of India has specifically restricted by notification. As of the Effective Date of this Policy, no such restriction applies to the jurisdictions in which OpenAI, Cloudflare, or Google process data as described in this Policy.
The DPDPA defines a "child" as an individual under the age of 18 and requires verifiable consent from a parent or lawful guardian before processing a child's Personal Data, and separately prohibits processing that involves tracking, behavioral monitoring, or targeted advertising directed at children. The Application does not track, behaviorally monitor for advertising purposes, or serve targeted advertising to any User of any age, so that prohibition is satisfied by the Application's design regardless of age.
The Application's Self Profile setup is intended for use by an individual capable of providing consent to this Policy in their own right, and the Developer does not knowingly permit a child under 18 to create a Self Profile and accept this Policy in their own name. A minor's medication information may instead be entered and managed by their parent or lawful guardian, acting as the User, via a Dependent Profile the parent or guardian themselves operates on their own Device — in which case the parent or guardian's own acceptance of this Policy, together with their exercise of parental or guardian authority in choosing to enter that minor's data, is the basis on which that data is processed. A parent or lawful guardian may withdraw consent at any time by removing the relevant Profile, which deletes that minor's data as described in Section 8. If a parent or lawful guardian believes a child has independently created a Self Profile and provided Personal Data about themselves, they may contact the Developer using the details in Section 23 to request deletion; because data is held in Local Storage, deletion may also be accomplished directly by removing the relevant Profile or uninstalling the Application.
The Application is a reminder and tracking tool only. It is not a medical device, is not intended to diagnose, treat, cure, or prevent any disease or condition, and does not constitute medical advice. Information extracted by the artificial-intelligence scanning feature described in Section 6 may contain errors, omissions, or misinterpretations, regardless of medical specialty — the feature flags readings it was not confident in, but even an unflagged reading is not guaranteed correct. The User is solely responsible for verifying all medication information — for themselves and for any Dependent Profile they manage — against the actual prescription, and for consulting a licensed physician or pharmacist with any questions regarding medication or treatment.
The Application is provided "AS IS" and "AS AVAILABLE," without warranty of any kind, whether express, implied, or statutory, including without limitation any implied warranties of merchantability, fitness for a particular purpose, or non-infringement. Without limiting the foregoing, the User acknowledges and agrees that:
This Policy shall be governed by and construed in accordance with the laws of India, including the DPDPA, without regard to conflict of law principles. Any dispute, controversy, or claim arising out of or relating to this Policy, or the collection, use, or disclosure of information described herein, shall be subject to the exclusive jurisdiction of the competent courts of India, without prejudice to a Data Principal's right to approach the Data Protection Board of India as described in Section 13. Nothing in this Section limits any mandatory consumer-protection or data-protection rights the User may hold under the law of their own place of residence that cannot be waived by agreement.
If any provision of this Policy is held by a court or other tribunal of competent jurisdiction to be invalid, illegal, or unenforceable, such provision shall be modified to the minimum extent necessary to make it valid, legal, and enforceable, or, if it cannot be so modified, shall be severed from this Policy, and the remaining provisions shall continue in full force and effect.
This Policy, together with any in-application disclosures presented at setup, constitutes the entire agreement between the User and the Developer regarding the collection, use, and disclosure of information in connection with the Application, and supersedes any prior understanding on that subject.
The Developer may revise this Policy from time to time. Any revision will be reflected by an updated Effective Date and Document Version shown at the top of this page. Material changes affecting how previously collected data is used will, where practicable, be accompanied by a notice within the Application. Continued use of the Application following the posting of a revised Policy constitutes acceptance of that revision.
Questions, requests, grievances, or nominations regarding this Policy or the handling of your information should be directed to:
Arsh Duggal (Developer, DavAI)