Richiesta GBP API Basic Access — artefatto pronto

Form ufficiale: https://support.google.com/business/contact/api_default Prerequisito 60gg: ✅ GIÀ SODDISFATTO — l'account metaverbe@gmail.com gestisce il GBP "Metaverbe" verificato/attivo dal 17 feb 2026 (≈94 giorni al 22 mag). La doc Google consente che il profilo-prova sia "the applicant's own business or belong to a client they manage". Quindi non serve attendere che il GBP Multiverbe nuovo invecchi. NON INVIARE finché: (a) Search Console verificata su multiverbe.com + multiverbe.app, (b) consent screen OAuth completo (logo+privacy+terms+support), (c) checklist sotto tutta verde.

Dati identità (verificati)

Campo	Valore
Nome richiedente	Gregorio Ciurleo
Email contatto	`metaverbe@gmail.com` (inbox account · garantita) — alt `gregorio@multiverbe.com` (catch-all ImprovMX)
Company name	Multiverbe
GCP Project ID	`multiverbe-production` (#297810897382)
Country	Switzerland
Number of locations	100-1000 (stima: 1 location per cliente PMI)
Type of business	SaaS / Business Software
Website	https://multiverbe.com
Scope richiesto	`https://www.googleapis.com/auth/business.manage` (solo questo, NON `full`)
OAuth redirect	`https://multiverbe.app/api/reach/google-oauth-callback` (apex — NON app.multiverbe.com)
Privacy policy	https://multiverbe.com/privacy
Sub-processor list	https://multiverbe.com/subprocessors

Use case description (copia-incolla, EN)

Multiverbe is a Swiss B2B SaaS platform (operated by Gregorio Ciurleo,
sole proprietorship / Einzelfirma, Ticino, Switzerland) serving small and
medium businesses — restaurants, hairdressers, gyms, hotels — primarily in
Ticino and Grigioni, Switzerland. We help each customer manage their own
Google Business Profile: keeping NAP (Name/Address/Phone) consistent, syncing
business info from our centralized dashboard to their GBP, and pulling back
reviews and insights into their analytics.

How we use the API:
1. Per-customer OAuth: each SMB customer connects their OWN Google Business
   Profile to their Multiverbe workspace via the standard OAuth consent flow.
2. Read GBP location info (name, address, phone, hours, categories).
3. Write back updates only when the customer edits NAP fields in their
   Multiverbe dashboard.
4. Read reviews and insights for the customer's own locations.
5. NO bulk operations across unrelated locations · NO data resale · NO scraping.

Operator track record as a GBP manager:
The requesting Google account (metaverbe@gmail.com) has owned and actively
managed a verified Google Business Profile since February 2026 (verified and
publicly live, receiving monthly performance insights). This is the same
account and Google Cloud project from which this API request is submitted.

Data handling:
- Per-customer OAuth tokens stored encrypted in Supabase EU (Frankfurt).
- Multi-tenant isolation via Row-Level Security (workspace_id).
- GDPR and Swiss revFADP compliant.
- Privacy policy: https://multiverbe.com/privacy
- Sub-processor list: https://multiverbe.com/subprocessors (Google listed as a
  data processor for customers who connect their GBP).

OAuth consent screen:
App "Multiverbe", domains multiverbe.com + multiverbe.app authorized, privacy
and terms published on multiverbe.com, scope limited to business.manage.

Scopes requested:
https://www.googleapis.com/auth/business.manage

✅ Checklist anti-rifiuto (TUTTO verde prima del submit)

[x] Search Console: multiverbe.app ✅ + multiverbe.com ✅ VERIFICATI (2026-05-31, metodo DNS TXT)
[ ] Consent screen completo: logo Multiverbe caricato (Branding) + privacy + terms + support email — verifica su https://console.cloud.google.com/apis/credentials/consent?project=multiverbe-production
[ ] Privacy policy copre esplicitamente il trattamento dati utenti Google (Iubenda doc 92115618 → ok standard)
[ ] Sub-processor list live (https://multiverbe.com/subprocessors) cita Google
[ ] Scope minimo: solo business.manage
[ ] Coerenza nome/dominio: app "Multiverbe" + dominio multiverbe.com — coerente
[ ] Redirect URI: apex https://multiverbe.app/... (no app. — fa 308 e Google non segue redirect sul callback)
[ ] Prerequisito 60gg: ✅ soddisfatto via profilo Metaverbe gestito dallo stesso account (17 feb 2026, ≈94gg)

Note coerenza (per il reviewer)

Il profilo-prova dei 60 giorni è il GBP "Metaverbe" (studio/agenzia, gestito dallo stesso account metaverbe@gmail.com), mentre il prodotto è "Multiverbe" SaaS. La doc Google ammette esplicitamente che il profilo qualificante sia "your own business or a client you manage": qui dimostra solo che l'operatore è un gestore GBP legittimo e attivo. Il use-case API riguarda i profili dei clienti del SaaS, connessi via OAuth per-utente — non il profilo Metaverbe. Storia coerente, nessun appiglio.

Tempi attesi review: 5-15 giorni lavorativi (email da googleapis-prod o simile). La GBP API NON blocca il gate 10 Giu (Reach C1b = post-MVP).