Privacy Policy

Dx Core. Effective 12 October 2026.

1. Scope

This policy covers Dx Core, a self-hosted personal application operated by a single individual ("the operator"). Dx Core is not offered to the public and serves exactly one Google Account: the operator's own. This policy explains what Google user data the application accesses, how it is used, where it is stored, and with whom it is shared.

2. Google user data accessed

The application requests access only to data belonging to the operator's own account. The exact OAuth scopes requested are shown on the Google consent screen at the time of authorization.

Google service	What is accessed	Why
Google Drive	Files and folders owned by the operator, including reading file contents and listing metadata.	To write backup archives into a private folder, to verify that an upload completed, and to produce links to files the operator selects.
Gmail	Messages in the operator's own mailbox.	To detect newly arrived messages and forward a short notification to the operator's private alert channel.
Google Docs, Sheets and Slides	Documents owned by or shared with the operator.	To read and edit those documents when the operator asks the application to do so.

3. How Google user data is used

Only to carry out operations the operator explicitly requests, or that the operator has previously scheduled.
Only on the operator's own data.
No profiling, advertising, analytics or behavioural tracking.
No use of Google user data to train, fine-tune or evaluate machine-learning models.

4. Limited Use disclosure

Dx Core'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.

Human review of Google user data does not take place, except by the operator themselves, and only where necessary to fix a fault the operator has reported.

5. Storage and security

OAuth credentials and refresh tokens are stored in files readable only by the operating system's privileged account, on servers controlled by the operator.
Backup archives are stored in a private folder inside the operator's own Google Drive, and temporarily on the operator's own servers.
All traffic between the application and Google APIs uses HTTPS.
Data is never copied into third-party cloud services, analytics platforms or databases.

6. Sharing and disclosure

Google user data is not shared, sold, rented or transferred to any third party. It is not disclosed to advertisers, data brokers, or any person other than the operator. The application is not used to determine creditworthiness or for lending purposes.

7. Retention

Backup archives are retained according to the operator's own retention settings and are deleted on a rolling basis.
OAuth refresh tokens are retained until the operator revokes access.
Notification records are transient and are not kept beyond what is needed to avoid duplicate alerts.

8. Access, deletion and revocation

The operator can revoke this application's access to the Google Account at any time at myaccount.google.com/permissions. Revoking access stops all further data access immediately. Because the operator is the only data subject, deletion requests can be made directly to the contact address below and are carried out by deleting the corresponding files and credentials from the operator's servers and Google Drive.

9. Children

The application is not directed at children and does not knowingly process data belonging to anyone under the age of 13.

10. Changes

This policy may be updated. The effective date at the top of this page always reflects the current version.

11. Contact

Questions about this policy or about how Google user data is handled: dexter.omics@gmail.com