# Google reviewer access: native Desktop installation This guide describes independent access to the current macOS source package of Lumetio Studio. The reviewer installs the application locally, creates their own Lumetio account and connects their own YouTube channel through Google's system-browser consent screen. No operator account, Google password or existing account data is included in the package. This is a review build. Successful packaging or local tests do not establish Google OAuth approval, YouTube audit approval or permission for unrestricted distribution. The operator must provide the actual controlled download and matching integrity report before these instructions constitute a delivered reviewer-access path. ## Operator handoff checklist - Provide the exact review ZIP through the agreed review channel, with its SHA-256 and version/date. Provide this guide alongside it. A local filesystem path alone is not accessible to Google's reviewer. - Confirm in Google Cloud Console that the issued client belongs to the existing Lumetio project and has application type Desktop app. Keep the existing project and client identity used by the submitted consent screen and review video. Do not create reviewer-owned Cloud projects or substitute a Web client. - Build with `--desktop --google-desktop-client-json /private/path/to/existing-desktop-export.json`. Only minimal `installed` metadata goes into `desktop-config.json`; no original download file goes into the ZIP. This native public credential is different from confidential Web client credentials. Controlled packaging does not authorize embedding it in an open source repository or arbitrary redistribution. - Run the independent check: `.venv/bin/python review/verify_google_release.py /path/to/review.zip`. The report contains the package hash, a file count and fixed validation results, with no credential values. It checks artifact shape, not Google's server-side registration. - Verify this exact ZIP on a fresh installation, including account creation, consent, local callback, reads and the available upload workflow. Record observed results and unresolved failures. Tests against fake responses do not prove live reviewer access. - Check actual reviewer account eligibility if Google still limits the unverified application. Supply any requested application-level test account through Google's specified channel, never by sharing a Google password. This build supports local self-registration; verify that it is usable before stating all requested features are accessible. - Support contact: support@lumetio-studio.pro. Never request OAuth codes, tokens, passwords or the user's `.state` folder in a support message. ## Reviewer installation and consent 1. Use a Mac with Python 3.11 or newer and FFmpeg available on PATH. The package is a source distribution with shell launchers, not a signed macOS application. If macOS blocks a launcher, report the exact warning to support; do not disable system security protections. 2. Check the supplied SHA-256, then extract the ZIP into a fresh permanent folder. Do not copy an existing `.state`, `.env` or another user's configuration into this folder. Quit any other Lumetio instance using local port 8767. 3. Run `Setup.command`. It creates a Python virtual environment, installs the declared dependency versions and prepares the local plugin configuration. Dependency downloads need internet access. 4. Run `Start.command`. The browser opens `http://127.0.0.1:8767`. Publishing is off by default. Create a new local Lumetio account with your own email address, name and a password of at least 12 characters. The first local account owns its workspace and has the administration role. The default local review installation does not require a central email-verification service. 5. Open **Verbindungen** (Connections). Choose **Konto verbinden** (Connect account) in the YouTube card. A system-browser Google authorization window should display Lumetio Studio. Choose your own Google account and channel and review both requested permissions: YouTube upload and YouTube read-only access. Google passwords are entered only on Google's own page. 6. Consent returns to `http://127.0.0.1:8767/oauth/youtube/callback`. Check that the connected card shows your selected channel. The package supplies the existing application's Desktop identity; the reviewer does not create or import a separate Google Cloud client. 7. If you decline a required permission or see a Google account/app restriction, record the result and contact support. Do not substitute another OAuth client, broaden scopes or try to bypass Google's warning or eligibility restrictions. ## Read and upload checks - In the YouTube connection card choose **Beiträge & Kennzahlen lesen** (Read posts and metrics). The application reads the connected channel's accessible uploaded videos and available original view, like and comment counters. Inspect the channel identity and source label **Provider API**. No uploaded videos is a valid empty result; unavailable counters remain unknown. Reading does not publish anything. - Import your own small MP4 in the library. Prepare a video post with only your connected YouTube account selected. Review the title, description, file, channel, selected visibility, audience choice and realistic altered/synthetic-content choice. Save the draft and approve its exact preview. - To test an actual upload, stop `Start.command` using Ctrl-C, run `Start-Live.command` and consciously confirm `ja`. Only explicitly approved, scheduled posts may be processed. Schedule the reviewed draft for a suitable time and inspect its status. Google processing and private visibility must be confirmed separately from file transfer. A queued or unclear result must be reconciled, not submitted again. - Current API uploads are restricted to private. The app does not demonstrate public or unlisted API publishing. OAuth verification and the YouTube API compliance audit are separate procedures. - Stop the live launcher and return to `Start.command` after the test. This returns publishing to its default disabled state, provided no local environment override was supplied. ## Disconnect and data checks In **Verbindungen**, select **Trennen** (Disconnect) on the YouTube card and confirm. Lumetio attempts programmatic Google revocation and removes local YouTube tokens and API copies. If Google cannot confirm revocation, the application reports that separately from local cleanup. Original media remains local. Provider-side videos remain on YouTube. You may also revoke Lumetio in your Google account's third-party connections. With the local application running, its daily authorization recheck detects invalid authorization and cleans API copies; it cannot run while the computer is off. Reconnection requires a new Google consent. Access/refresh tokens are stored locally encrypted and are not sent through a Lumetio Google-token broker. API calls and uploads go directly from the local installation to Google/YouTube. ## Open access and compliance items The native login package addresses independent installation; it does not close the whole audit. A remotely accessible controlled package, an independent clean-install record and any reviewer-specific account eligibility requested by Google still need concrete evidence. YouTube's upload minimum functionality requires user-set title, description and a choice of public/private/unlisted visibility. These choices are now available and preserved through exact-draft approval. Until the separate API audit is confirmed, public and unlisted uploads are blocked before any provider write. The operator-only audit gate is disabled in this review build and cannot be changed through customer settings. Keep the restriction visible in the review response and obtain Google's applicable audit instruction before claiming full compliance. No additional quota request or completed audit is implied by this guide. ## Official sources checked on 5 October 2026 - [Google native OAuth](https://developers.google.com/identity/protocols/oauth2/native-app): installed application type, system-browser consent, loopback, PKCE and native credential handling. - [Google OAuth verification requirements](https://support.google.com/cloud/answer/13464321): required app information, accessible homepage/privacy policy and demonstrable requested scopes. - [YouTube Developer Policies](https://developers.google.com/youtube/terms/developer-policies): credential identity and disclosure rules, user authentication, data handling and access for a requested review. - [YouTube required minimum functionality](https://developers.google.com/youtube/terms/required-minimum-functionality#uploading-videos): upload choices and required user controls. This guide is an implementation and review-access description, not a declaration that Google has approved the app.