Vigzar MedCare — Data Policy

This Data Policy provides a precise, technical record of every category of data that Vigzar MedCare collects, processes, stores, and transmits. It is intended to complement the Privacy Policy with granular, developer-grade transparency. Last updated: June 7, 2025.

1. Policy Purpose & Scope

This Data Policy applies to:

The Vigzar MedCare Android application (com.vigzar.medcare)

All future platform releases (iOS, Web Portal, Caregiver Portal) — each governed by the version of this policy current at the time of their launch

All data interactions between end-user devices and Vigzar Technologies infrastructure

Our guiding principle: Collect the minimum data necessary. Store health data exclusively on the user's device. Never monetise personal or health information.

2. Data We Collect — Complete Inventory

2.1 Health & Medication Data

Stored exclusively on-device. Never transmitted to Vigzar servers.

Medication names, generic names, brand names

Dosage amounts, units, and form (tablet, capsule, liquid, etc.)

Administration routes and instructions

Reminder schedules (times, frequencies, repeat rules)

Dose event logs (taken, missed, snoozed — with timestamps)

Adherence scores and streaks (computed locally)

Stock quantities and refill dates

Medication start and end dates

Prescribing doctor references (linked from Doctor Directory)

2.2 Family Profile Data

Stored exclusively on-device. Never transmitted to Vigzar servers.

Profile names and relationship labels (e.g., "Mother", "Son")

Date of birth (optional — used for age-relevant context)

Per-profile medication and health record sets

Profile avatars (stored locally, not uploaded)

2.3 Health Records Data

Stored exclusively on-device. Never transmitted to Vigzar servers.

Prescription images and PDF scans (stored in encrypted local storage)

Medical notes and free-text health observations

Diagnosis references (user-entered, not verified)

Lab result records and report uploads

Hospital and clinic visit notes

Allergy and adverse reaction records

Emergency health information (blood type, conditions, contacts)

2.4 Doctor & Appointment Data

Stored exclusively on-device.

Doctor names, specialisations, and clinic affiliations

Contact numbers and addresses

Appointment dates, times, and notes

Consultation history notes

2.5 Authentication Data

Collected and processed via Firebase Authentication.

Google account email address

Google display name

Google profile photo URL (display only, not stored persistently)

Firebase UID (anonymous identifier used for account reference)

Authentication tokens (managed by Firebase SDK, not accessible to app code)

We do not store passwords. Authentication is delegated entirely to Google.

2.6 Backup Data

Transmitted only when the user explicitly initiates or schedules a backup.

AES-256 encrypted binary blob of all on-device health data

Destination: user's personal Google Drive account only

Vigzar Technologies has zero access to backup file contents

Backup file metadata visible to Google Drive (file name, size, modified date) — governed by Google's Privacy Policy

2.7 Crash & Diagnostic Data

Collected anonymously via Firebase Crashlytics.

Stack traces and exception logs (no health data included)

Device model and Android version

App version and build number

Crash timestamp (UTC)

Session ID (randomly generated per session, not linked to user identity)

Health data is explicitly excluded from all crash reports via Crashlytics data scrubbing configuration.

2.8 Analytics Data

Collected anonymously via Firebase Analytics (if enabled).

Screen view events (screen name only, no content)

Feature interaction events (e.g., "reminder_created", "backup_initiated")

Session duration and app open frequency

Device locale and timezone (for reminder accuracy research)

All analytics events are designed to contain zero health information. Event parameters are reviewed before implementation to ensure no PII or PHI leakage.

2.9 Payment Data

Processed via Razorpay (India) and Google Play Billing.

We do not store payment card numbers, UPI IDs, or banking credentials

Transaction IDs and subscription status flags are stored locally and in Firebase (for entitlement verification only)

All payment processing is handled by the respective payment processor under their own data policies

3. Data Classification

|---|---|---|---|---|

PHI = Protected Health Information (equivalent standard applied regardless of jurisdiction)

4. Encryption Specifications

4.1 At-Rest Encryption (On-Device)

Algorithm: AES-256-GCM (Galois/Counter Mode)

Key derivation: Keys are generated using Android Keystore System

Key storage: Android Keystore — hardware-backed where device supports it

Database: Hive (local NoSQL) with box-level encryption

File storage: Flutter secure storage for encryption key references

4.2 In-Transit Encryption (Backup)

Pre-transmission encryption: AES-256 applied on-device before any data leaves the device

Transport layer: HTTPS / TLS 1.2+ for all network communications

Google Drive API: OAuth 2.0 authenticated, encrypted in transit

4.3 Key Management

Encryption keys are generated locally and never leave the device

Keys are bound to the device's hardware security module where available

Loss of device without backup = loss of data (by design — no server-side key escrow)

5. Data Retention

5.1 On-Device Data

Data persists until:

The user explicitly deletes individual records or profiles within the app

The user deletes their account (all app data is cleared)

The user uninstalls the app (local data is removed per Android standards)

A factory reset is performed on the device

5.2 Firebase Authentication Records

Retained while the account is active

Deleted within 30 days of account deletion request

Users may request deletion at any time from Settings → Account → Delete Account

5.3 Crash & Analytics Data

Firebase Crashlytics: retained for 90 days per Firebase's standard policy

Firebase Analytics: retained for 14 months per Firebase's standard policy (configurable to shorter durations — we use the minimum available)

5.4 Google Drive Backups

Stored indefinitely in the user's own Google Drive

The user controls retention entirely — they may delete backup files at any time from Google Drive

We have no mechanism to access or delete backups on the user's behalf

5.5 Payment Records

Transaction IDs retained for 7 years in accordance with Indian financial regulations (GST compliance)

No payment instrument data is retained by us

6. Data Access Controls

6.1 Internal Access

Health data: Zero access. No Vigzar employee or system can read your health records, medications, or family data.

Authentication data: Limited to Firebase Authentication admin console, accessible only to authorised engineering staff for account support purposes.

Crash & analytics data: Accessible to engineering and product teams for quality and improvement purposes. All data is aggregated and anonymised.

6.2 Third-Party Access

We do not sell, rent, or share personal data with third parties for commercial purposes. Authorised processors:

Google Firebase — Authentication, Crashlytics, Analytics. Google Cloud Data Processing Addendum applies.

Google Drive API — Backup only, to user's own account.

Razorpay — Payment processing. Razorpay Privacy Policy applies.

6.3 Legal Disclosure

We may disclose data if required by:

A valid court order or subpoena under Indian law

A legal obligation under the Information Technology Act, 2000 or its rules

Protection of the rights, property, or safety of Vigzar Technologies, our users, or the public

We will notify affected users of legal data requests to the extent permitted by law.

7. User Rights & Data Control

7.1 Right to Access

All your health data is accessible at any time within the app. There is no separate data access request needed — it is always visible to you.

7.2 Right to Portability

Export health records and medication data from Settings → Export Data

Backup files can be downloaded from your Google Drive

Export formats: JSON and PDF (roadmap: CSV)

7.3 Right to Rectification

All data can be edited directly within the app at any time.

7.4 Right to Erasure

Individual records: delete from within the app

Full account + all Firebase data: Settings → Account → Delete Account

Google Drive backups: delete manually from your Google Drive

Crash / analytics data: cannot be individually deleted (already anonymous)

7.5 Right to Restrict Processing

Disable analytics: Settings → Privacy → Usage Analytics → Off

Disable crash reporting: Settings → Privacy → Crash Reporting → Off

Disable backup: Settings → Backup & Restore → Disable

7.6 Response Timeline

We respond to formal data rights requests within 30 calendar days. Submit requests to privacy@vigzar.com.

8. Children's Data

The app is not directed at children under 13. We do not knowingly collect personal data from children under 13. Child medication profiles created by parents or guardians are stored on-device under the parent/guardian's account and are subject to the same protections as all health data.

If you believe a child under 13 has created an independent account, contact privacy@vigzar.com immediately.

9. Data Breach Response

In the event of a confirmed data breach that affects personal data:

We will assess the scope and nature within 72 hours of discovery

Affected users will be notified within 72 hours of the assessment if their data is at risk

We will report to relevant Indian data protection authorities as required by applicable law

A public incident report will be published at vigzar.com/security for significant incidents

Given our offline-first architecture — where health data never resides on our servers — the blast radius of any server-side breach is limited to authentication metadata only.

10. Cross-Border Data Transfers

Health data: No cross-border transfer (stays on user's device)

Firebase data: Google operates globally; Firebase data may be processed in Google data centres outside India, governed by Google's Standard Contractual Clauses

Google Drive backup: Stored in Google's global infrastructure under the user's Google account region settings

Razorpay: Processes data within India in accordance with RBI guidelines

11. Regulatory Compliance

Vigzar MedCare is designed with the following frameworks in mind:

India: Information Technology Act, 2000 · IT (Amendment) Act, 2008 · Digital Personal Data Protection Act, 2023 (DPDP Act)

International standard: GDPR principles applied as a baseline for all users globally

Healthcare data: We apply PHI-equivalent protections to all health data regardless of jurisdiction

We are not a HIPAA-covered entity, but we voluntarily align with HIPAA's minimum necessary and safeguard principles.

12. Changes to This Policy

Material changes to this Data Policy will be communicated via:

In-app notification on next launch

Updated "Last updated" date on this page

For significant changes affecting data rights: direct notification to the email address associated with your account

13. Contact & Data Requests

Data rights requests: privacy@vigzar.com

Security disclosures: security@vigzar.com

General enquiries: support@vigzar.com

Location: Thiruvananthapuram, Kerala, India

Last updated: June 7, 2025

Version: 1.0.0

This Data Policy is binding and forms part of the Vigzar MedCare Terms & Conditions.