Skip to content

AdMob (#90): consent screen and privacy policy, the second scope #98

Open

Description

@Lin1er

Owners: @AncungAulia (privacy policy, terms) and @Lin1er (OAuth client) · Branch: docs/admob-consent · Parent: #90 · Was blocked by: #93, done 2026-10-26 (both parts) · Start: now on the branch, pending @Lexirieru's go on #90 for merging before 2026-10-30 (otherwise after 2026-11-08) · Label: out-of-sow · Also after: #86 published

Add admob.readonly to the Google consent screen and the legal pages.

Lead time nobody controls

admob.readonly may restart Google's sensitive-scope verification. So:

What

  1. OAuth client (@Lin1er). Add admob.readonly in Data Access, write the scope justification, and resubmit for verification if Google asks.
  2. /privacy (@AncungAulia).
    • The second scope, what is read (AdMob estimated earnings over three months, nothing else), and what becomes public (the same four fields).
    • content/legal.test.ts checks the scopes against be/, so it fails until both sides match.
  3. /terms. "AdSense or AdMob account" where ownership is required.

Done when

The consent screen lists both scopes, is published, and verification (if required) has passed. The legal pages are updated and live.


Working agreement

  1. One issue, one owner. 2. Branch per issue, named above, not the GitHub-suggested one. 3. MCP Stellar Raven for any Stellar/Soroban fact that gets written down. 4. Merge through PR review by Axel (PM); no self-merge. If an ACC has not arrived within two days on something already verified, merge and say so in the PR. 5. Deploys need evidence: contract address or tx hash on stellar.expert, recorded in docs/deployments.md. 6. Secrets live in .env, gitignored, chmod 600: never printed, never committed, never pasted into an issue or PR. Only public G… and C… addresses appear anywhere. 7. Issues, commits and PRs in English.

Activity

  1. added
    ready-to-devUnblocked: development can start on the issue's branch
    on Oct 26, 2026
  2. Lin1er commented on Oct 27, 2026

    @Lin1er
    CollaboratorAuthor

    Unblocked: #86 is published (2026-10-27).

    Order: submit the scope for verification only once #105's /privacy is live, because Google reviews the scope against that page. Merging #105 waits on @Lexirieru's go on #90, like the rest of the AdMob work.

  3. Lin1er commented on Oct 27, 2026

    @Lin1er
    CollaboratorAuthor

    OAuth client half, done 2026-10-27:

    • AdMob API is enabled on the Cloud project.
    • https://www.googleapis.com/auth/admob.readonly is in Data Access, next to adsense.readonly, with its justification.

    Not submitted for verification yet. Submitting waits for #105's /privacy to be live, because Google reviews the scope against it. Until then a sign-in for AdMob works on the published screen, past the "unverified app" warning.

    Left on this issue: #105 (legal pages, @AncungAulia's wording), then submit the scope.

  4. added a commit that references this issue on Oct 31, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

out-of-sowNot an Instawards deliverableready-to-devUnblocked: development can start on the issue's branch

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions