Data protection
Data protection and HIPAA
Last updated: 24 October 2026
Our position
ArogyaSync is designed with HIPAA principles in mind. It is not HIPAA certified, and it has not been independently audited against HIPAA. Our primary operating jurisdiction is India, and hospital-specific data protection requirements need to be agreed before deployment.
What we do today
- Data travels between devices, apps and our servers over encrypted (TLS) connections.
- Stored data sits in Google Cloud in India (Mumbai region), which encrypts it at rest by default.
- People and devices sign in with their own credentials, and what each can see depends on their role.
- A powered, configured device can buffer readings during a network outage and retry delivery. Local retention and recovery depend on the installation.
- Users can ask for their account to be deleted from the account deletion page.
Readings and public proofs are different
Clinical readings and CSV evidence files are stored in the application database and Google Cloud Storage, separately from the ledger. The documented anchoring service computes a SHA-256 hash of a CSV batch and submits that hash with a timestamp to Polygon Amoy, a public test network. The contract also exposes the signing wallet. It does not submit raw readings, patient names or patient identifiers as contract fields. This is a batch integrity check, not proof that a reading is clinically accurate, that every reading was captured, or that an archive is always available.
Ledger transactions and proofs are publicly visible and cannot be erased through an account deletion request. A hash is not encryption or a guarantee of anonymity: someone with a matching file can link it to its proof. Access to patient records and evidence files is a separate, authenticated workflow; an on-chain proof does not itself grant access to those files.
Camera images
The camera processes the monitor screen to extract values. Separately, supported devices can collect monitor frames through an administrator-assigned capture campaign with a consent reference. Documented campaigns are time-limited and encrypted; moving captures into training storage requires a de-identification attestation and review. Do not assume that images are never stored. Agree capture permissions, image retention, access and any training use with the hospital before enabling it.
Retention, deletion and responsibilities
Account deletion is separate from deletion of clinical records, evidence archives, backups and public proofs. Required retention and approved deletion procedures must be confirmed for each data category with the hospital and ArogyaSync before use; this page does not promise immediate or complete erasure. The public proof remains even if its source file is deleted.
The hospital and ArogyaSync need to agree their data handling roles, authorised users, consent responsibilities and request-handling process in writing. Google Cloud provides the documented database and file-storage infrastructure; Polygon Amoy carries the public proofs. Contact our team for the data-flow and retention schedule applicable to your proposed deployment.
Business Associate Agreements
If your organisation needs a Business Associate Agreement, contact us and we will discuss what we can offer.
Contact
For data protection questions, contact compliance@arogyasync.com.