Privacy Policy

Application: MiaGog — personal command-line client for Google Workspace

Effective date: 8 October 2026 · Last updated: 8 October 2026

Summary in one paragraph. MiaGog is a personal, locally installed command-line tool used by exactly one person to access her own Google account. It has no server, no other users, and no third parties. Google user data is fetched on demand to the owner's own computer, displayed in her own terminal, and never sold, shared, transferred, or used for advertising or model training.

1.Who we are

MiaGog (“the Application”) is a private, single-user software tool operated by an individual developer (“we”, “us”). It is not a commercial product, is not offered to the general public, and has no user base other than its owner. The data controller for the purposes of this policy is the Application's owner and operator, who can be reached at mia2026lu@gmail.com.

2.Google user data we access

The Application accesses Google user data only after the account owner has explicitly granted permission through Google's standard OAuth 2.0 consent screen. The categories of data, and the sole purpose for each, are:

Google service	Data accessed	Why it is needed
Gmail	Messages, threads, labels, attachments and mailbox settings of the owner's own account.	To let the owner search, read, send, label and organize her own email from the command line.
Google Calendar	Calendars and events of the owner's own account.	To list, create, update and delete the owner's own calendar events.
Google Drive	Files and folders in the owner's own Drive.	To list, search, upload, download and organize the owner's own files.
Google Docs	Documents in the owner's own Drive.	To read and export the owner's own documents.
Google Sheets	Spreadsheets in the owner's own Drive.	To read and write the owner's own spreadsheets.
Google Contacts	Contact names, email addresses and directory entries of the owner's own account.	To resolve names and email addresses when composing messages or inviting attendees.

Basic Google account information (email address and profile identifier) is also read during sign-in, solely to confirm which account is being used.

3.How we use Google user data

Google user data is used for one purpose only: to carry out the action the owner explicitly requests from her own terminal.

Data is processed only in response to a command the owner types.
There is no background collection, crawling, indexing, profiling or analytics.
No automated decision-making or machine-learning training uses Google user data.
No advertising is served or targeted using Google user data.

4.Storage and retention

The Application has no backend server. Nothing is uploaded to any infrastructure operated by the developer, because none exists.

Credentials. The OAuth refresh token issued by Google is stored locally on the owner's own computer in an encrypted credential file protected with owner-only file permissions (chmod 600). It is retained until the owner revokes access or deletes the file.
Content. Email bodies, calendar entries, documents, spreadsheets, files and contact records are fetched on demand, held transiently in the memory of the owner's own machine, displayed to the owner, and are not persisted to any remote system. Any local cache or exported file is created only at the owner's explicit request and remains under her sole control.
Retention. Because there is no server, there is no retention period imposed by the developer. The owner may delete all local Application data at any time by removing its credential and configuration files.

5.Sharing and disclosure

We do not sell, rent, trade, publish, or otherwise disclose Google user data to any third party. Specifically:

No data is transferred to third-party analytics, advertising, or marketing services.
No data is made available to other people, other applications, or other services.
No data is disclosed for credit-worthiness, lending, or insurance purposes.
The only external party the Application communicates with is Google itself, over HTTPS, using Google's own official APIs — this is inherent to the tool's function.
No human other than the account owner can access the data.

6.Limited Use disclosure

MiaGog'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.

In accordance with the Limited Use requirements, Google user data is used only to provide and improve the Application's clearly disclosed, user-facing features; is not transferred to others except as necessary to provide those features, to comply with applicable law, or as part of a merger or acquisition; is not used for advertising, including retargeting or personalized advertising; and is not used to determine creditworthiness or for lending purposes. No humans read the data except the account owner herself.

7.Security

All communication with Google APIs takes place over TLS-encrypted HTTPS.
OAuth tokens are stored in a locally encrypted credential store on the owner's device, readable only by the owner's operating-system account.
The Application requests only the specific OAuth scopes required for the features listed in section 2.
The scope of access can be reduced or revoked by the owner at any time (see section 8).
No credentials or API keys are embedded in public code, and no shared or hosted service holds them.

Because the Application runs entirely on the owner's own device and has no server, the security of Google user data depends primarily on the physical and account security of that device, which the owner maintains.

8.Your controls and choices

Review access granted. Visit myaccount.google.com/permissions to see the Application in your list of connected apps.
Revoke access. Remove the Application from that page. Access is revoked immediately and the stored refresh token stops working.
Delete local data. Delete the Application's credential and configuration directory on your computer to erase the token and any cached data.
Request deletion or ask questions. Write to mia2026lu@gmail.com. Because the Application stores no server-side data, deletion requests concern only the local credential file.

9.Children's privacy

The Application is not directed to children under 13 (or the applicable age of digital consent in your jurisdiction) and is not used by anyone other than its adult owner.

10.International data transfers

The Application performs no server-side processing and therefore does not transfer Google user data across borders by itself. Data exchanged with Google's APIs is handled under Google's own terms and infrastructure.

11.Changes to this policy

This policy may be updated if the Application's behaviour or the applicable Google policies change. Material changes will be reflected in the “Last updated” date above and, where relevant, communicated to the account owner before taking effect.

12.Contact

Questions about this policy or about the handling of Google user data can be sent to mia2026lu@gmail.com.