Purpose
Directed Intelligence uses Gmail only to send governed operational alerts to a recipient explicitly verified and activated by the system operator. It is not an email client, advertising service, mailbox-analysis tool, or marketing platform.
Google user data
The application requests only the OAuth scope https://www.googleapis.com/auth/gmail.send. This permits sending a message as the authorized account.
Directed Intelligence does not request or use permission to:
- read, list, search, or download email;
- inspect folders, labels, contacts, or attachments;
- modify, archive, move, or delete mailbox content;
- send advertising or messages to an unverified recipient.
DI processes the authorized account identity, OAuth credential material, intended recipient, and alert message long enough to authenticate and perform the requested send.
Storage and protection
- The OAuth client secret and refresh token are stored in the local macOS Keychain.
- Access tokens exist only in process memory and are not intentionally persisted.
- DI stores a cryptographic fingerprint of the registered credential, not the credential value.
- Operational evidence is designed to retain hashes, timestamps, status, response metadata, and chained governance events rather than Gmail message content or Google’s provider message identifier.
- This disclosure site sets no cookies and runs no analytics or tracking code.
Retention and deletion
The OAuth credential remains in Keychain until it is revoked or replaced through the governed credential lifecycle. Audit evidence is retained locally to preserve the integrity of approval, security, and recovery records. When a credential is replaced, its former Keychain item is removed only after the replacement has been commissioned and verified.
Temporary plaintext OAuth files are not part of normal operation and are removed after protected Keychain storage is confirmed.
Your control
The authorized Google account holder may revoke the application through Google Account security settings. Revocation prevents future token refresh and therefore blocks future Gmail sends until a new governed authorization is completed.
A recipient may request removal through the contact path below. Recipient replacement requires explicit verification and does not transfer ownership or administrator authority.
Questions, deletion, and revocation requests
Use the public Directed Intelligence repository’s issue tracker for privacy questions, recipient-removal requests, or deletion coordination. Do not include passwords, OAuth codes, access tokens, refresh tokens, or other credentials in an issue.
Open the contact channel