Privacy
Your care is not our advertising data.
Policy updated 27 September 2026 · Website, DocZen Patients, DocZen Clinic and independent clinic vault
Privacy
Policy updated 27 September 2026 · Website, DocZen Patients, DocZen Clinic and independent clinic vault
DocZen is operated by FORMIR TECHNOLOGIES PRIVATE LIMITED. This policy explains the actual distinction between our online services and the clinic's local vault. Read the security boundaries.
DocZen Patients combines native iOS and Android screens with DocZen web services. Booking, sign-in and account screens use the same online services and session cookies as the website. My Records lets you deliberately upload PDF, JPEG or PNG medical documents or photograph a paper record. Camera access is requested for capture. Optional video consultations request camera and microphone access before joining; audio/video is transmitted through LiveKit to participants. DocZen does not provide consultation recording. Video and clinician document delivery depend on the relevant service being enabled and your appointment or verified record access.
Uploaded originals are encrypted in DocZen's private database with service-managed keys. We also store the patient/profile label, document type, date, title, clinic/doctor labels, optional notes, consultation link and upload/edit/download/deletion events. Encryption of the original file does not mean every metadata field is application-encrypted or that DocZen cannot decrypt it. The library is private to the uploading account; it does not automatically send uploads to a clinic. Patient-entered labels and notes are not verified clinical findings. Only records specifically released to your verified access appear as clinician-released documents. Family booking profiles do not automatically grant access to another adult's clinical records. No OCR, AI interpretation or ABDM exchange is performed by this library.
You can choose individual records for encrypted offline storage on your device, protected by a passphrase you create. DocZen does not receive or store that passphrase. Each offline save expires after at most seven days, or earlier where a released document expires; device storage may be evicted sooner. Offline storage is not a permanent backup, and a disconnected device cannot learn about server deletion or revocation until it reconnects. Downloads, printable summaries and files shared through your device's sharing controls create readable copies outside DocZen. Native sharing uses temporary files, cleared after sharing and on the next launch following interruption. Copies retained by a receiving app cannot be recalled by DocZen. Protect exported files separately.
We do not sell or rent patient data, sell patient leads derived from private clinic records, use those records for advertising, or supply them to train AI models. Clinic subscriptions fund clinic software. This commitment covers identifiable records and commercial sharing of supposedly de-identified clinical datasets.
Formir Technologies Pvt Ltd operates DocZen's discovery, booking and account services. Clinics decide why their clinical records are created and how they are used for care. Where we host clinic operational records, we act on the clinic's documented instructions, alongside our responsibilities for DocZen's own services. Clinic control does not remove the patient's privacy and access rights.
Public doctor and clinic profiles contain professional information supplied for publication. Booking and clinic operations store patient names, contact details where provided, patient identifiers and family relationships, appointments, booking sources, queue events, quoted and recorded fees, and operational audit history. Optional booking reasons may reveal health information; do not enter a full medical history there. Legacy or explicitly enabled cloud clinical records may include consultation notes, diagnoses, vitals, prescriptions and follow-up dates. Shared clinic intake additionally stores DOB or recorded age, sex, allergy information and appointment-specific measurements, with author, time and revision history. These details can be reused by the connected desktop prescription form. These records are not local merely because the clinic uses our staff app.
The downloadable clinic vault encrypts saved archives and clinician-authored notes on the clinic's device with a clinic-selected passphrase. The standalone vault does not upload notes, keys or backups. The connected desktop app can explicitly save shared patient details and visit measurements to the clinic service; its clinical notes and saved prescriptions remain local unless a separate delivery or transfer action is used. DocZen does not receive the passphrase and cannot reset it or recover lost local records. The clinic controls who can unlock the vault, its backup locations and its retention. Downloading the vault does not automatically remove existing cloud copies. Readable JSON, CSV and printed exports are not encrypted; protect them separately.
A separate, optional online transfer page stores encrypted vault files with your clinic/account association, revision, time and size. It never asks for a passphrase or sends it to DocZen. Snapshots are private to the same authorised clinician account, not shared through reception access. The offline vault itself still does not upload anything. Transfer is explicit upload/download, not automatic shared editing. Retained snapshots remain downloadable without a paid subscription while clinic authorisation is valid; downloaded copies cannot be remotely recalled. Keep independent backups and download encrypted revisions separately from the clinic archive's snapshot index.
When enabled, inventory stores item, batch, expiry and staff-attributed stock movement records. Do not put patient information in inventory notes. Recurring clinic billing stores plan, subscription identifier, provider status, renewal/cancellation information and security event hashes. DocZen's subscription API notes contain clinic and subscription identifiers, not patient records. Payment mandate and billing details entered into the provider's checkout are processed by that provider. New recurring charges require an authorised clinic owner's explicit checkout approval.
The staff app sends booking and queue changes to DocZen. Its optional patient-details form sends shared intake only when you save online; those fields are not included in the offline queue cache. Unsaved intake is cleared when the app backgrounds or locks. On iOS and Android, its session token, minimised queue cache and unsynced changes use OS encrypted storage. Cached lists omit booking reasons, contact phone numbers and fees; pending walk-ins necessarily include their entered name and optional phone until synchronised. Failed operations remain available for reconciliation. The development web build uses memory for these values. Offline access requires a recent server verification and is limited to 24 hours. A revoked offline device cannot receive that instruction until it reconnects; remote revocation is not an instant remote wipe.
Staff access is scoped to authorised clinic operations. Receptionists can handle queues and collections and, where authorised for clinic intake, enter shared patient details and visit measurements. They cannot open cloud consultation notes through that access. The treating doctor and authorised clinic owner can access clinical records; a doctor at another clinic cannot. The platform administration interface does not provide unrestricted patient browsing. Authorised infrastructure operators may technically access cloud-held data for defined support, security or legal obligations. We do not describe that cloud service as end-to-end encrypted.
Running an online service requires hosting, database, email and, when enabled, messaging and payment providers. Our code uses Vercel hosting/storage, PostgreSQL hosting, Resend email, Meta WhatsApp and Razorpay payments depending on the deployed configuration. These providers receive the limited data needed for their function, not permission to advertise using private clinic records. Booking confirmations can expose the clinic or doctor's identity to the chosen messaging provider. Legal disclosures may be required. The production provider list, processing locations and contracts must be verified during clinic onboarding; we do not promise that every service or backup remains exclusively in India.
Appointment messages are for the booking, not marketing. Optional channels require their applicable consent and opt-out handling. Clinics must obtain appropriate permission when staff enter another person's details. A shared family phone number does not by itself prove identity, guardianship or permission to disclose clinical records. A parent or authorised guardian should handle a child's booking; no account should be created by a child independently.
Ending a clinic subscription does not authorise us to sell, delete or withhold the clinic's retained records. Clinic exports are not gated by payment status; authorised identity verification still applies. A clinic owner can export retained records for the clinic, and a doctor can export their authorised practices. The archive includes retained appointments, patients, clinical records, prescriptions, collections, schedules and available revision/audit history. Local vault records need a separate local backup. Saved archives and the independent vault remain readable without a DocZen account or subscription. Cancellation alone does not remove a free public listing.
If you allow it, Google Analytics measures visits to our general clinic and company information pages: For doctors, Pricing, Providers, For corporates, About and Apps. It receives the page category, referral website origin, device and browser information, and clicks that open the clinic application or contact page. Google processes network information when your browser connects to it. Analytics cookies are configured for 30 days. We do not load this tag on doctor or clinic profiles, search, application forms, patient accounts, bookings, consultations, chats or records, or on URLs with query strings or fragments. We do not send names, contact details, account identifiers or medical information. Advertising features are disabled. You can decline without affecting the service, or use Turn off analytics on an eligible page to withdraw consent. We respect Do Not Track and Global Privacy Control. Your analytics preference is stored in your browser. This optional analytics is separate from the first-party operational counters described below.
Different account, booking, financial and clinical records require different retention decisions. There is no universal automatic three-year deletion promise. Account deletion can be requested using the instructions at /account-deletion or from the account page and has a seven-day cancellation window; clinic clinical and legally required records may require separate handling. You can delete your uploaded originals and their library metadata from My Records. Minimal library audit events remain until account erasure. Recovery backups may retain earlier copies until the configured backup period expires; contact us for the applicable recovery-backup retention period. Contact us or the treating clinic for the applicable record category and a correction, copy or deletion request. We must verify authority before releasing records, particularly for family members. Clinics must keep encrypted backups and test recovery. Subscription cancellation is not a data-erasure request.
Use your account page for the available account export and deletion request, or contact us for help identifying the relevant records. A patient seeking their clinical record can also contact their clinic. Account exports are not a claim that all independently held clinic records are included. Requests concerning local vault copies must be handled by the clinic because DocZen cannot read those copies. Please do not email medical records, passwords or complete exports to support.
We use session cookies and essential security information for sign-in and abuse prevention, not advertising or cross-site tracking. The application does not include advertising pixels or session replay. Cloud access uses HTTPS and access controls; local vault backups use authenticated encryption. Encryption is not a guarantee against compromised devices, malicious software, shared credentials or an authorised person misusing access. We do not claim an independent security certification.
If you choose to use your current location on Find a doctor, your device gives DocZen an approximate position, rounded to about 100 metres, only to sort doctors by distance. We do not save it in our database or logs, and it is never put in a page address. It stays on your device in a cookie for at most 30 minutes, so later pages of the same search keep their order; Clear removes it sooner. We name the nearest area from India Post's PIN code list for that page only. Typing an area or PIN code instead searches by that place and does not use your location.
DocZen keeps daily counts of selected public-page navigation attempts, saved bookings, delivery failures and fixed error categories on its own database. These counters contain no patient or account identifiers, booking references, search terms, URLs, raw errors or session recordings. Browser reporting sends no account cookies, uses no tracking storage, and respects Do Not Track and Global Privacy Control. We retain 30 UTC calendar days of counters through scheduled cleanup; an outage may delay cleanup. Counts are approximate and are not a record of individual visitors. Security rate limits use separate short-lived buckets; hosting and delivery providers maintain their own operational logs.
The Digital Personal Data Protection Act and Rules have phased commencement. The November 2025 notification schedules the main processing and individual-rights provisions for eighteen months after gazette publication. This policy does not claim that every DPDP provision is already in force or that local storage alone establishes compliance. Other applicable privacy, professional, security and record-keeping requirements must also be considered.
DocZen is for appointments at clinics in India. You can use it from another country, for example to book for a parent in India, but the care, the clinic and the clinic's records are in India. We run DocZen under Indian law, including the Digital Personal Data Protection Act as its provisions come into force, and this policy does not claim that DocZen meets the privacy law of the country you are in. Formir Technologies Pvt Ltd operates DocZen from India. Our application servers and main database run in Singapore. The providers named above may process data in other countries. Your access, correction and deletion options are the same wherever you are: use your account page or contact the privacy contact named at the end of this policy. Book for another person only with their permission. Appointment times are Indian Standard Time. For an emergency outside India, call your local emergency number.
Official commencement notification
PIN code locations: Department of Posts, Ministry of Communications, All India Pincode Directory, data.gov.in. Published under GODL-India.
For privacy requests, contact the person named above or use our contact form. Please do not include medical records, passwords or complete account exports.