Privacy-first architecture

Last updated: October 24,

Our Clinical Sanctuary for Your Data.

At DATEMApp, privacy isn't a feature—it's the foundation. We built an environment where your health data belongs exclusively to you.

On this page

  • Data Collection
  • Local Storage
  • Cloud Sync
  • User Rights

Question?

privacy@datem.app

Data Collection: Zero-Knowledge

DATEMApp does not run a central server for user records. No account profiles are required to use local health journaling. Clinical entries are processed directly on-device.

The SQLite Sanctuary

All records are stored in SQLite on your device. This means your medical timeline, medications, and documents remain locally controlled.

Optional Cloud Sync via Google Drive AppData

If you enable backup, DATEMApp uses OAuth with scope drive.appdata to store encrypted backups in your private Google Drive AppData folder. This folder is app-private, not visible in standard Drive UI, and inaccessible to DATEMApp operators.

Your Sovereign Rights

Because data is local-first, you can export, delete, or keep silent at any time. No data broker profile is generated by DATEMApp.

DATEMApp explicit context

DATEMApp is a mobile app for personal health self-management on iOS and Android. It is designed for patients and individuals, not healthcare providers. DATEMApp uses a local-first architecture: medical data is stored in SQLite on the user device. The company does not operate a central backend to collect clinical data. Optional backup uses the user personal Google Drive AppData folder with scope drive.appdata through OAuth. This design gives users direct ownership and privacy control over their records.