Google access is feature-specific
PR Genie requests Google access only for the connected Google feature a user chooses, such as identity, OAuth setup, or Google Business Profile account/location workflows.
Google API Use
How PR Genie uses Google APIs for authorized account, local, and business-profile workflows.
This disclosure explains what Google access may be requested, why it is needed, what data may be used, how Limited Use applies, and how PR Genie keeps Google actions approval-aware.
Limited Use commitment
Google user data is not sold, not used for unrelated advertising, and not used to train generalized AI models.
Last updated May 15, 2026
Google API use overview
PR Genie may use Google APIs when a user or authorized account owner chooses to connect Google-related features. These features can include Google OAuth identity, Google account authorization, Google Business Profile account/location access verification, and future approved local-search or business-profile workflows.
Google access is not required for every PR Genie feature. PR Genie can still support public website browsing, plan comparison, sales questions, public contact requests, content strategy, and many account workflows without a Google connection.
When Google access is used, it is tied to the authorized feature and the connected account. PR Genie does not treat a successful OAuth setup as proof that Google Business Profile account/location access is connected; account/location proof remains a separate verified workflow.
Scopes and Google data
Requested Google access depends on the feature being connected.
| Google access | Why PR Genie may request it | Data or capability involved |
|---|---|---|
| Google OAuth identity | To confirm the Google account a user is authorizing and to support a connected Google workflow. | Basic account identity, authorization metadata, OAuth token references, and scope proof. |
| Google Business Profile | To verify whether an authorized user can access account/location information for a business profile workflow. | Account/location metadata, profile access proof, location selection, and readiness signals. |
business.manage scope | To support Google Business Profile account/location access and approved business-profile workflows where required. | The scope https://www.googleapis.com/auth/business.manage may be requested for authorized Google Business Profile features. |
| Operational logs | To show whether a connection or access test succeeded, failed, expired, or needs review. | Status, timestamps, safe diagnostics, masked credential state, and error summaries. |
Limited Use
PR Genie follows Google API Services User Data Policy requirements.
Oceanside PR and PR Genie’s use and transfer of information received from Google APIs follows the Google API Services User Data Policy, including the Limited Use requirements.
- We do not sell Google user data.
- We do not use Google user data for unrelated advertising.
- We do not use Google user data to train generalized AI models.
- We use Google user data only to provide or improve the specific Google-connected feature authorized by the user.
- We transfer Google user data only as needed to provide the authorized service, comply with law, protect security, or with the user’s direction/consent.
Google Business Profile boundaries
Google Business Profile workflows stay approval-aware and access-proof driven.
PR Genie separates identity authorization, scope evidence, and actual business-profile account/location access so the platform does not overstate readiness.
Until proof passes, Business/Local workflows remain held and no location connection should be created from public page load or ordinary chat.
PR Genie may prepare drafts or recommendations, but final connected-channel actions remain gated by account, role, plan, channel, and approval controls.
Actual Google profile actions remain subject to Google access, account permissions, platform policies, and PR Genie approval gates.
Storage, security, and retention
Google authorization records are handled as sensitive connection data.
Credential handling
Secrets and tokens are not shown publicly. PR Genie stores connection records and masked credential states only as needed to operate authorized features and diagnose safe connection status.
Access limits
Google-connected workflows use role, plan, client, project, and channel boundaries. Public pages and Guest Genie do not expose private Google account or client workspace details.
Retention
Connection records, token references, logs, and access proof may be retained while the feature is active and as needed for security, audit, troubleshooting, legal, or service-integrity purposes.
Revocation and contact
You can revoke Google access or ask questions about Google API use.
You may revoke PR Genie’s Google access through your Google Account permissions page or by using disconnect controls inside PR Genie where available. After revocation, connected Google features may stop working until access is reauthorized.
If you need help with a Google connection, use the public contact form for general questions or log in for account-specific support. We must verify authorization before discussing private account, client, billing, permission, or Google connection details.