Privacy Policy

Information the integration handles

If enabled, the poller reads identity, parent, owner, authorization, and permission metadata for the fixed owner-selected ULTRON-Command-Inbox spreadsheet, then reads its CSV export to find valid command rows. The staged protocol supports limited commands such as a status request or a read-only task proposal. It does not provide arbitrary shell execution, spending, marketplace publishing, or unrestricted agent dispatch.

Validated requests are handed to ULTRON’s local queue, where command identifiers, processing state, approval state, and sanitized outcomes are recorded under existing safeguards. The poller writes its result to a protected local handoff; it does not write to Google Drive. A separate service-account publisher is planned to update two fixed status-report files using a different Google identity and credential. That publisher is not authorized by this OAuth app.

Google Drive permission

The app requests only https://www.googleapis.com/auth/drive.file. Google describes this as per-file access to files opened or created with an app, or otherwise explicitly made available to it by the user. Although the staged poller uses fixed HTTPS GET requests for the one configured Inbox, Google’s scope can allow changes to files authorized to the app; it is not itself a Google-side guarantee of read-only access or a one-file allowlist.

The owner is asked to select only ULTRON-Command-Inbox during authorization. Before a token is retained, the app must verify the exact active grant includes only that file and the approved scope. No such token is currently retained for unattended production use.

How information is used and shared

Command rows are used only to validate and route owner requests through ULTRON’s local queue and approval controls. This website does not display command rows or system reports. Google processes the selected spreadsheet under the owner’s account and applicable terms. If the owner separately uses a connected provider to retrieve status reports, that provider handles the retrieved report copy under its own terms and privacy settings.

The integration is not designed to sell Google user data, use it for advertising, or share it with other ULTRON users. There is no public user signup or customer account system.

Storage and retention

The production command poller is inactive and has not processed Inbox command data. A read-only check on October 24, 2026 found zero task, event, and approval rows in the local ULTRON queue. The reviewed application has no age-based deletion period for command or audit records: tasks and audit events are protected against deletion through normal application operations. If the bridge is activated, those records may remain until a separately authorized maintenance process changes or removes them. No fixed retention duration is promised.

The controller's daily database backups are configured to retain up to 30 verified snapshots, pruning older verified snapshots only after a new verified backup is created. System logs use systemd's default size-based journal rotation; no fixed time-retention setting was found. The status publisher and its recurring timer are inactive, so no automatic Drive report writes are currently occurring. Google Drive revision-history retention has not been inspected and remains subject to the owner's Drive settings.

No Inbox refresh token is currently retained for unattended production polling. If separately approved and deployed, the reviewed design stores it in a root-protected file and exposes it only to the dedicated poller through a systemd credential. Access tokens remain in process memory. Credentials are excluded from backups; tokens and private command contents must not appear in ordinary logs or published reports.

Access controls and choices

The owner controls the selected Inbox and may manage or revoke ULTRON Inbox Reader’s Google Account access through Google account security settings. Revoking access stops future polling. The owner separately controls sharing for status-report files and their publisher identity; this app does not change those permissions.

Hosting-provider request logs may contain ordinary technical connection data when these public pages are served. No analytics or tracking scripts are included.

Contact

Project operator: Oshea Spahr. For questions about Google sign-in or this project, use the User Support Email displayed on the Google OAuth consent screen. The project does not publish that address in this policy or operate a separate support mailbox.