Privacy policy

Effective date: November 7, 2026. Operator: Jeremy Dow, acting in a personal capacity. This policy describes the current bounded Oracle Enterprise application.

Data accessed

With the owner's consent, the app receives OAuth credentials and can access Google Drive files and metadata under the granted drive.readonly and drive.file scopes. The deployed transport scans a designated task folder and downloads task content and metadata. It uploads task-discovery evidence, execution events, artifacts, and receipts. Evidence can include task identifiers, hashes, timestamps, outcomes, and local file paths.

Purpose and use

Google user data is used to retrieve designated task inputs, validate identity and integrity, deliver authorized evidence files, and maintain an auditable record. A Drive file is not an instruction to bypass local permits or reviewed execution limits. The app does not use Drive access to authorize trading, spending, or public publishing.

Storage and retention

Refresh credentials are stored on the owner's Mac in owner-only files. Local queues, snapshots, journals, artifacts, receipts, and private backups may remain until the owner removes them. Uploaded evidence remains in the owner's Google Drive until removed there. No automatic retention period is currently implemented. Owner-only file modes do not isolate data from other applications running under the same local account.

Sharing and processing

The application communicates with Google's OAuth and Drive services. The owner controls Drive sharing and access to the Mac. The deployed transport and dispatcher do not sell Google user data, use it for advertising, or send it to third-party AI services. If the owner separately shares evidence with ChatGPT, Work, Codex, or another service, that is a separate owner-directed workflow governed by that provider's terms and privacy practices.

Google user data is used only for the application functions described here. Oracle Enterprise's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Revocation and deletion

The owner can revoke this app's Google Account access from Google Account connections. Revocation prevents future authorized API access; it does not delete existing local or Drive copies. Removing retained data requires separately deleting the relevant local files, backups, and Drive evidence. Review audit and recovery needs first.

This information website

This website contains information pages only. It has no account-registration forms, uploads, or embedded analytics. The hosting provider may process ordinary web-request data needed to serve and protect the website. The private operational dashboard is separate.

Contact and changes

For questions or an owner-directed deletion request, contact jeremy.w.dow@gmail.com. Update this policy before materially changing the application's data practices.