Privacy Policy

Effective date: October 25, 2026
App: GmailDesk New
Operator: Lucy
Privacy contact: pritzkerlucy@gmail.com

This policy explains how the GmailDesk New Windows desktop application accesses and uses Google user data. This policy is intended to describe the current local desktop design and must be updated if application behavior changes.

1. Information accessed

With the user's permission, GmailDesk New uses Google's OAuth authorization to access the selected Gmail account. It requests gmail.send for user-initiated email sending and gmail.readonly to read emails and threads for reply notifications and conversation management. It may process account email addresses, recipient addresses, subjects, message bodies, Google message/thread identifiers, timestamps, and reply information as needed for these features.

2. How information is used

Google user data is used only to provide user-facing features such as sending messages, displaying sent records, checking replies, and replying to conversations. The app is not designed to use Gmail data for advertising, sale, or training general-purpose AI models. The user controls which accounts to connect and which messages to send.

3. Local storage and transfers

In the current local desktop design, customer records, message status, and related history are stored in a local application database on the user's Windows computer. Google authorization credentials are stored using the operating system's credential storage via the app's keyring integration. Gmail data is exchanged with Google services as needed to provide the requested features. GmailDesk New does not operate a central mail-content collection server in this design.

The public website is hosted separately. The website hosting provider may process ordinary website access logs under its own policies; visiting the website does not require connecting a Gmail account.

4. Sharing

GmailDesk New does not sell Gmail data or share Gmail data with advertisers. When the user sends an email, the email is delivered through Google to the recipients selected by the user. Gmail data may also be processed by Google as needed to operate the Gmail API.

5. Retention and deletion

Local records remain on the user's computer until removed by the user or through available application controls. Revoking Google access stops further authorized API access but does not automatically delete every local record. Users can revoke access from their Google Account third-party connections and request help removing local application data by contacting the operator. Deleting data from a local computer or backup is the user's responsibility unless otherwise agreed.

6. Security

GmailDesk New uses Google's OAuth flow and operating system credential storage in its current desktop implementation. No software can promise absolute security. Users should protect access to their Windows account, device, and backups.

7. Google API Services User Data Policy

GmailDesk New's use and transfer of information received from Google APIs is intended to adhere to the Google API Services User Data Policy, including the Limited Use requirements. Google data is not used outside the functions disclosed above without an appropriate update and user permission.

8. Changes and contact

We will update this page when our data practices materially change. Questions, requests, and privacy inquiries may be sent to pritzkerlucy@gmail.com.

Before publication: The operator must validate every statement against the distributed application and replace the operator/contact placeholders. This draft is not legal advice.