dksc97

Privacy Policy

Effective date: 10 October 2026 · Applies to dksc97 and the website dksc97.com

This policy describes how dksc97 (the "app", "we", "us") handles information when it is connected to a Google Account. The app is a private mail-archiving tool operated by its owner. It is not a public service and it is not offered to other users.

1. What this app is

dksc97 connects to the Google Account of the person who authorises it (the "account owner") for a single purpose: to keep a portable archive of that account's email. It is built for one user — its owner — and does not serve anyone else.

2. Google user data we access

The app accesses the following Google user data, and only the following:

• Gmail messages. The app reads messages in the account owner's mailbox — message headers, the body, and any attachments — so that each message can be written out as a .msg (Microsoft Outlook) file. This access is read-only.
• Google Drive. The app creates and uploads files into a folder in the account owner's own Google Drive. This is used only to store the .msg files it has produced.

The app accesses no other Google service. It does not touch data belonging to anyone other than the account owner, and it does not read, change, send or delete mail beyond reading it for export.

3. Why we access it

The sole purpose is to back up and archive email in a portable, provider-independent format. Gmail data is read so that each message can be saved to a file; Google Drive is used only as the storage destination for those files.

4. How access is granted

The account owner signs in to Google and grants the app access through Google's OAuth flow. The app then holds a token that lets it act on that account only. The account owner can revoke this access at any time at myaccount.google.com/permissions.

5. How the data is stored, and where

• The app has no server of its own and no central database. It runs locally on the account owner's machine.
• Exported .msg files are written to the account owner's own computer and uploaded to a folder inside the account owner's own Google Drive. Both copies stay under the account owner's control.
• OAuth tokens and configuration are stored locally on the account owner's machine and are not sent to us or to any third party.
• Operational logs (which may record file names and counts, but not message contents) are kept locally for troubleshooting and deleted after 30 days.

6. Retention period

We keep no separate copy of Google user data. The exported files exist only in the account owner's Google Drive and on the account owner's own computer, and are kept until the account owner deletes them. Local operational logs are deleted after 30 days.

7. No sale or sharing

We do not sell, rent, trade or share Google user data with any third party. The data is not used for advertising or profiling, and is not used for any purpose other than the archiving described above.

8. Limited Use disclosure

9. Access, correction and deletion

The account owner, or anyone acting with the owner's authority, may:

• request a copy of the data held about them;
• ask for that data to be corrected or deleted;
• withdraw consent and stop all access.

To make any of these requests, email kosun834@gmail.com. We aim to respond within 30 days. You can also revoke the app's access immediately at myaccount.google.com/permissions, and delete any uploaded files directly from your own Google Drive.

10. Security

Access tokens are held only on the account owner's own computer. We recommend that the computer is protected with a passphrase and kept up to date.

11. Changes to this policy

If this policy changes, we will publish the revised version on this page and update the effective date above. For a material change, we will also give notice to the contact email on file before the change takes effect.

12. Contact

Questions about this policy or about your data: kosun834@gmail.com.