AI Email Management
Privacy policy
Operator and scope
Scotty McGee operates AI Email Management and this information portal. This policy describes how the application handles Google user data after the owner authorizes access. Questions or privacy requests may be sent to privacy@jdmcgee.me.
Google user data accessed
When authorized, the application may access the following Gmail data as needed to provide email-management functionality:
- message and thread identifiers;
- sender and recipient information, dates, subject lines, and Gmail label or Inbox state;
- message content when needed to classify or summarize a message;
- Gmail labels and the ability to apply or remove labels and archive messages.
The application does not access Gmail before the owner grants authorization.
How Google user data is used
Google user data is used only to operate the owner's email-management workflow. The application may identify a sender, apply deterministic sender protections, classify an eligible message into an owner-approved routing category, apply Gmail labels, preserve selected messages in Inbox, or archive mail according to owner-approved rules.
Known Inbox and Observe protections take precedence over semantic classification. An unknown exact sender enters a New Sender review workflow and is not silently granted authority to archive future messages. Uncertain or conflicting routing can be held for owner review.
Storage and retention
Messages remain in the owner's Gmail account unless the owner changes or deletes them there. Archiving removes a message from Inbox; it does not delete the message.
The private runtime may retain limited operational records needed for reliability and audit, such as message identifiers, sender identity, routing result, timestamps, and processing status. Raw message bodies are not stored in this public portal, its Git source, or routine runtime audit records. Message content may be processed transiently when it is needed for classification.
OAuth tokens and other credentials are kept in the owner's approved private credential boundary. They are not stored in this public site or its source repository. Public portal hosting is separate from the application's private runtime.
Sharing and disclosure
Google user data is not sold. Limited message data may be transmitted to service providers that support the private application, such as Google for Gmail operations and an AI processing provider for bounded message classification. Such processing is limited to providing the application functionality and is not used to offer a public advertising or data-broker service.
Data may also be disclosed when required by law or to protect the security and integrity of the application, accounts, or systems. This policy does not claim a certification, independent security audit, or completed Google verification.
Owner control, deletion, and revocation
The owner controls the connected Google account and may review, relabel, archive, restore, or delete messages through Gmail. The owner may revoke the application's Google access through the Google Account permissions interface. Revocation prevents new authorized access but does not itself delete messages or labels already present in Gmail.
Because the operator is also the sole current user, requests to inspect or delete private operational records can be handled directly by the operator, subject to any records still needed to diagnose active processing or preserve system integrity. Contact privacy@jdmcgee.me for assistance.
Public portal data
This public portal is a static information site. It does not use analytics, advertising trackers, cookies, forms, or third-party JavaScript. It does not host Gmail data, credentials, or private application audit state.
Changes
This policy may be updated when the application's data use or operating boundaries materially change. The updated effective or revision date will appear at the top of this page.