Privacy Policy & Data Security
Google API Services User Data Policy
Bitclin's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Google Scopes: Bitclin requests access strictly to drive.file and appDataFolder to save and retrieve encrypted EMR JSON records. We do not access, scan, or store any other files in your Google Drive.
Revoking Access: You can disconnect Bitclin from your Google Drive at any time by visiting your Google Account Security Settings and removing app access.
Decentralized Storage: In accordance with data protection guidelines, Bitclin employs a decentralized architecture. Patient Health Information (PHI) and clinical ledgers are stored natively within the authenticated physician's Google Drive (`appDataFolder`). Jepsons Solutions does not host, read, aggregate, or sell your patient data to third-party advertisers.
Local Caching: To support Offline Resilience and seamless queue management, encrypted fragments of the daily roster and recent EMRs are stored locally on the clinic's device using IndexedDB. This data is synchronized directly with your Google Drive upon internet restoration.
Consent & Erasure: Patients retain the right to request data erasure. Due to our decentralized architecture, data deletion requests must be fulfilled manually by the presiding clinic directly from their secure storage node. Jepsons Solutions cannot delete patient data on behalf of a clinic as we do not possess it.
Data Residency: All system architecture and routing infrastructure are deployed on servers located within India to maintain compliance with domestic data residency laws.
AI & Sub-Processors
SGI Labeling: Automated clinical notes are Synthetically Generated Information (AI).
Third-Party Processing: Voice Dictation utilizes Google Gemini APIs. These sub-processors are bound by zero-retention policies; your clinical audio and images are NOT used to train their foundational models.