YAO LifeOS Owner Admin Preview Gmail readonly demo

This public demo is retained as historical support for the previously submitted Gmail readonly OAuth verification path. Public production approval for the restricted Gmail readonly scope is currently suspended, and the current no-cost posture does not start Gmail OAuth.

No-login reviewer access

This page is the public reviewer packet for the submitted Gmail readonly OAuth review flow. It does not require Cloudflare Access, a one-time PIN, a shared password, or reviewer credentials. The protected Owner/Admin app remains available for owner operation, but the scope explanation, message-body processing explanation, source-account impact explanation, demo video, and direct MP4 fallback are available here without login.

The current status page is available at /oauth-live/. It confirms that public Gmail readonly OAuth has been suspended and no ADA-CASA assessment has been started.

Requested Gmail scope

The previously submitted Gmail readonly review flow requested https://www.googleapis.com/auth/gmail.readonly. The app uses this scope only for user-started, bounded read-only workflows that read a selected Gmail thread or one user-provided counterparty thread, derive a sanitized LifeOS source-pointer preview, and return readback counts. This scope is not currently requested for public production approval.

Maximum user-facing feature enabled by this scope: after a user opens the Gmail readonly review surface and starts the OAuth flow, the app can read metadata, headers, labels, thread membership, and message body content for the bounded Gmail item the user selects or provides. The app then displays a sanitized project-context preview/source pointer so the user can decide whether the email exchange should inform a LifeOS project. It does not perform background mailbox monitoring, broad mailbox export, or automated ingestion outside that user-started review action.

A narrower Gmail metadata-only scope is not sufficient for this feature because headers and snippets cannot substantiate or summarize the body of the Gmail exchange that the user selected. The app must read message body content transiently to generate the user-requested project-context preview and sanitized source pointer. The app does not use this flow to send, modify, archive, trash, or delete Gmail messages.

Message body processing

The previously submitted flow read Gmail body content only during a user-started bounded review action. Body content is used transiently to create a sanitized body summary, source pointer, and readback metrics for the selected or user-provided Gmail thread. Raw Gmail bodies are not returned in public output, not committed to Git, not written to ordinary database records, and not used for generalized AI/ML model training.

Limited Use and AI/ML disclosure

YAO LifeOS adheres to the Google User Data Policy, including the Limited Use requirements. Raw, aggregated, anonymized, or derived Google Workspace API user data is not used to develop, improve, or train generalized or non-personalized AI/ML models.

The previously submitted Gmail readonly review flow did not transfer raw Gmail bodies to third-party AI services for generalized model training or model improvement. Current and planned LifeOS AI processing is backend controlled and must use providers and configurations that do not train generalized models on API payloads unless the user explicitly opts in outside this submitted review flow. See the Privacy Notice for the provider disclosure.

Source account impact

Because the previously submitted flow was readonly, the expected Gmail source account impact is no Gmail state mutation. The demo shows the synthetic source message before the LifeOS action, performs the in-app Gmail readonly readback action, and then shows the same Gmail source account after the action with the message still visible and unchanged. No read/unread, archive, star, trash, send, modify, or delete operation is part of this submitted scope.

Scope alignment

The previously submitted Gmail readonly OAuth review flow was expected to match the Google Cloud Console Data Access configuration exactly: https://www.googleapis.com/auth/gmail.readonly. The review path starts Google OAuth with scope_profile=gmail_readonly and a clean consent request, so the authorization URI for this review flow contains this Gmail readonly scope and does not depend on a broader Gmail send, modify, or Calendar scope. The current public no-cost posture is to cancel or remove this restricted scope from public verification rather than proceed with paid ADA-CASA.

Reviewer navigation

  1. Open this public review packet: https://lifeos-review.mojage.club/oauth-demo/.
  2. Review the requested scope, maximum user-facing feature, message body processing, Limited Use disclosure, and source account impact sections on this page.
  3. Open the current status page: https://lifeos-review.mojage.club/oauth-live/.
  4. Confirm that public Gmail readonly OAuth is suspended and no Gmail API readback is active.
  5. Open the YouTube demo video or the direct MP4 fallback on this page for the recorded walkthrough.
  6. Confirm that the shown Gmail readonly readback returns sanitized source-pointer preview output without raw Gmail bodies, OAuth tokens, client secrets, raw provider IDs, or raw email addresses.
  7. Confirm that the Gmail source message remains visible and unchanged after the readonly action because send, modify, archive, trash, and delete operations are outside the submitted flow.

YouTube demo video: https://youtu.be/Ixq-3ecX4Ik