Data processing in the Gate DATMI pilot

Updated 18 September 2026. This describes the current server stage: account sign-in and connecting a Google source. The application requests only the technical identifier of the source profile.

Sign-in and source connection

At sign-in, Google provides an account identifier and email address to check access eligibility. The server stores the account identifier, protected sessions, and technical security events.

Google Health is connected separately from sign-in. The server verifies and stores the Google Health user identifier, the single read-only profile permission actually granted, the access expiry, and tokens in encrypted storage.

Tokens are used only to manage the source connection, refresh access, and revoke permission. Health, activity, sleep, nutrition, ECG, measurement, and location data are not requested, received, or stored. Supporting them will require a separate software update and new user consent.

Disconnection and revocation

Disconnection immediately prevents the server from issuing the token again. Revoking permission with Google is a separate operation: until confirmed, the token may be retained in encrypted form solely to complete revocation. After confirmation, the server clears tokens and the source identifier from the active record. The technical event history remains.

If the result of an exchange or revocation is unknown, the connection is blocked. Completing cleanup may require revoking access in Google Account settings and a server-side status check. Disconnection does not cancel a request already in progress or immediately remove data from backups.

Backups and the previous stage

At the previous stage, the service provided sign-in and encrypted backup uploads. The Google Drive uploader uses drive.file for files it creates; the current and previous confirmed backups are retained and older copies are deleted. The recovery password and plaintext private key are not stored on Google Drive. Connecting Google Health adds separate storage and does not automatically include it in previously configured backups.

Controls and contact

Source status and disconnection controls are available in your account. For questions about data processing or deletion: kgsrus@gmail.com.

Manage data source · Home