Privacy policy

Gmail access and purpose

The application requests https://www.googleapis.com/auth/gmail.readonly. This permission technically permits viewing Gmail messages and settings; Google does not restrict the grant to the application’s search query. The application’s actual calls search recent matching messages and read their headers, message identifiers, dates, subject lines, body text, and attachment metadata to identify actions and source details. It also checks the connected account’s email address to ensure that the intended account was authorized. It does not retrieve mailbox settings.

The current intake does not download attachment files. Its read-only authorization does not permit sending, forwarding, deleting, labeling, or modifying Gmail messages. The search window selects what is reviewed; it is not a retention deadline.

Local processing and storage

The script extracts actions and relevant source details using local rules. It makes no direct calls to an AI model. Captures can contain sender and subject information, dates, requested actions, relevant deadlines or other details, a Gmail message identifier, and a link back to the source message. The workflow is designed to record the ask rather than reproduce the full email thread.

OAuth credentials and tokens are stored in configured local files outside the Dropbox capture folder. They are not uploaded to this website. Local run logs, summaries, and state records can contain message identifiers, subjects, file paths, processing decisions, and error information. Test previews can contain the same information as a proposed capture.

Privacy checks can hold messages for human review, including messages with attachments, unreadable or encrypted content, or detected sensitive information. These checks do not guarantee detection of every sensitive detail. The owner remains responsible for screening what enters this workflow.

Dropbox and assistant access

Successful captures are written to the owner’s Dropbox-synced workspace. Dropbox syncs those files to its service and connected devices according to the owner’s account configuration. The script also reads existing workflow notes, pending and archived captures, and task records to avoid duplicates.

The owner has configured workflows in which Claude and ChatGPT may read captures for review, extraction, and task organization, including scheduled processing. This is disclosure to the relevant service provider, even when the owner controls both accounts. Those services’ retention and processing depend on the account settings and applicable terms. This policy does not promise that every copy remains local or that third-party services never retain data.

Limited Use

Brian Gmail Intake’s use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements.

Google-derived information is used for the owner’s disclosed email and task workflow. It is not sold or used for advertising or credit decisions. It must not be used or transferred to create, train, or improve a machine-learning or AI model beyond the owner’s personalized model for the disclosed workflow. Downstream assistant use must be configured consistently with these restrictions.

Retention

There is no fixed automatic deletion period for captures, archived captures, task records, test previews, or accumulated state records. They remain until the owner removes them through the relevant workflow or service. Archiving a capture preserves a copy; it is not deletion.

Local logs rotate when they reach their configured size, and the latest run summaries are replaced by later runs. These mechanisms do not remove every historical record or backup. OAuth tokens, including recovery backups, remain in local storage until removed. Dropbox version history, deleted-file recovery, computer backups, and assistant service records may retain additional copies under their respective settings and terms.

Stop access, revoke permission, or delete data

1. Disable the Windows scheduled task and stop any running intake process to stop further collection. Pause downstream assistant workflows if they should no longer process existing captures.
2. Open your Google Account’s third-party connections, select Brian Gmail Intake, and remove its access. A later authorization will require consent again.
3. Remove the configured local token file and any token backups. To remove retained intake data, separately remove applicable local logs, state records, test previews, Dropbox captures and archives, and derived task records. Handle Dropbox’s deleted files and version history, other-device copies, and backups using their own controls.
4. Use Claude and ChatGPT’s applicable conversation, file, connector, and account controls to manage copies those services already received.

Revoking Google access does not delete existing captures or third-party copies. Deleting a capture does not delete the source email. If collection remains enabled and all records identifying a message are removed, a matching message may be captured again.

This public website

This site contains informational pages only. It has no Gmail connection, sign-in form, advertising, or application analytics script. Cloudflare hosts the pages and may process ordinary connection information, such as IP addresses and request details, to deliver and protect the site, under its privacy policy. Email contents, capture files, and OAuth credentials are not part of this site’s published assets.

Contact and changes

For questions about Brian Gmail Intake or its handling of data, contact the owner using the support address displayed on the application’s Google consent screen. This policy will be updated if the application’s data handling changes; the effective date appears above.