Skip to content

Landing page: privacy policy and terms of service, for publishing the Google consent screen #85

Closed

Description

@Lin1er

Owner: Ancung (@AncungAulia) · Branch: feat/85-privacy-terms · Milestone: M3 · Reviewer for the wording: Axel (@Lexirieru) · Blocks: #86 (publishing the Google consent screen)

Why

The Google sign-in that reads a creator's AdSense revenue (#78, #75) runs on an OAuth consent screen in Testing status. In Testing, only Google accounts we add by hand can sign in, up to 100. That is fine for us, but not for anyone else: a judge or a creator who isn't on the list is refused with "Access blocked".

Publishing the consent screen needs, at minimum:

  • a privacy policy and terms of service on our own domain, forepay.xyz;
  • both linked from the home page.

Google reviews the privacy policy against what the app actually does with Google data, so it has to be specific, not boilerplate. Review can take days or more. That is why this should start now and not the week of the demo.

What to build

Two static pages on the landing page (landing-page/):

  • /privacy, Privacy Policy
  • /terms, Terms of Service

Link both from the footer (sections/ClosingAndFooter) on every page. Plain, readable layout, using the type scale we already have. These are documents, not marketing.

What the privacy policy must say

Every point below is how the code behaves today. Rewrite it in plain words, but don't add claims the code does not back up. @Lin1er can confirm any detail.

What we access

  • One Google permission only: https://www.googleapis.com/auth/adsense.readonly, which is read-only AdSense reporting.
  • It cannot change anything in AdSense. It cannot read Gmail, Drive, contacts or anything else in the Google account.
  • Google's own sign-in window grants it. Forepay never sees the creator's Google password.

What we read with it

  • The list of AdSense accounts, and the state of the one used (whether it is approved).
  • One report: estimated earnings, in USD, for the last three complete calendar months, for that one account.

What happens to the access token

  • The browser sends it once, over HTTPS, to our proof server (api-forepay.jameshub.fun).
  • It is held in memory only while that one proof is made, which takes about a minute.
  • It is never written to disk, a database or logs, and it is scrubbed from error messages.
  • It is never shared with anyone, and it is discarded when the proof ends.
  • Google expires it after about an hour.
  • The creator can revoke access at any time at https://myaccount.google.com/permissions.

What becomes public — the most important part, say it prominently

  • To get an advance, the creator submits a proof to the Stellar network, a public blockchain (testnet).
  • The proof contains:
    • the AdSense publisher id;
    • the three-month date window;
    • the revenue figure to the cent;
    • the creator's Stellar address.
  • Anything on the ledger is public and permanent: it cannot be deleted, by us or anyone.
  • Nothing else from the AdSense report is revealed: not the account name, the sites, or the per-day figures.

What we keep

  • Nothing about the creator in a database.
  • The proof server keeps a finished proof job in memory for up to one hour so the page can collect it, then forgets it.
  • A restart forgets everything.

What we never do

  • We don't sell Google user data.
  • We don't use it for advertising.
  • We don't transfer it to anyone, except the revenue figure the creator chooses to publish on chain, as above.

Limited Use — include Google's required statement, word for word:

Forepay'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.

Also include: contact m.ulinasidiki@gmail.com, the effective date, and that this is a testnet product: no real money moves.

What the terms must say

Short is fine. It must cover:

  • testnet only, with no real funds, no lending offer and no financial advice;
  • provided as is;
  • the creator must own, or be authorised for, the AdSense account they sign in with;
  • the public, permanent nature of what they submit on chain (point to the privacy policy);
  • contact.

Done when


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
    documentationImprovements or additions to documentation
    M3-appWeek 3 — proof relay and the creator front end
    on Oct 21, 2026
  2. added a commit that references this issue on Oct 23, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

M3-appWeek 3 — proof relay and the creator front enddocumentationImprovements or additions to documentation

Type

No type

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions