Security & Google data

What SyncingBeam is

SyncingBeam is a reporting and monitoring service for marketing teams and agencies. It connects to the analytics accounts you manage, including Google Analytics 4 and Google Search Console, fetches aggregated report data on a schedule, normalizes it into one per-client view, flags anomalies, and renders dashboards and monthly reports. SyncingBeam is operated by SyncingBeam.

Signing in to SyncingBeam is separate from connecting Google data. You sign in with an email and password or an emailed one-time sign-in link. Where a "Continue with Google" option is shown on the sign-in screen and you choose it, Google shares only your name, verified email address, and profile picture (openid email profile) to sign you in. That grants no access to any Analytics, Search Console, or Ads data. Google data access is requested only when you explicitly connect a GA4 property, a Search Console site, or, where the Google Ads connector has been enabled for your workspace, a Google Ads customer account.

The Google scopes we request and why

When you connect a Google data source, SyncingBeam requests the OAuth scope for that source:

• https://www.googleapis.com/auth/analytics.readonly (Google Analytics Data API). Lets SyncingBeam read GA4 report data (sessions, users, conversions, channel and page breakdowns) for the properties you choose to connect. Read-only: we can never change, add to, or delete anything in your Analytics account.
• https://www.googleapis.com/auth/webmasters.readonly (Google Search Console API). Lets SyncingBeam read Search Console performance data (clicks, impressions, queries, pages) for the sites you choose to connect. Read-only: we can never change your Search Console settings or data.
• https://www.googleapis.com/auth/adwords (Google Ads API). Requested only where the Google Ads connector has been enabled for your workspace. It is not part of the standard service today. Where it is enabled, it lets SyncingBeam read campaign performance and account currency for the customer account you choose to connect. Google does not offer a narrower reporting-only OAuth scope for Google Ads; SyncingBeam uses this scope only for reporting reads and does not create or change campaigns, budgets, ads, or account settings.

GA4 and Search Console use their narrowest read-only scopes, and they are the connections available to every workspace. The Google Ads scope is listed because it is registered on our OAuth consent screen, but the connector behind it is enabled per workspace rather than offered as standard, and Google Ads is not listed on our connectors page. Google provides no reporting-only Ads scope, so where the connector is enabled that scope is broader than the reporting calls SyncingBeam makes; SyncingBeam does not invoke Ads mutation operations. We request no sign-in scopes (no openid, email, or profile).

What we do with Google data

• Fetch aggregated report data (metrics and dimension breakdowns) on a schedule from the properties and sites you connected, and from the Google Ads customer accounts you connected where the Google Ads connector is enabled.
• Normalize it into a consistent per-client model so numbers from different sources can be compared side by side.
• Store the resulting aggregates (counts, totals, and trends) in your workspace. If you explicitly enable GA4 session analysis through BigQuery, also store pseudonymous session and event records under the configured retention policy. See the Privacy Policy for the data involved and the limits of pseudonymization.
• Render dashboards, anomaly alerts, and monthly reports for the business or agency that connected the account.
• Only where a Slack delivery target is configured for your workspace, post the resulting report or brief content into the Slack workspace you nominated, through the incoming webhook you supplied. Slack then handles that content under your own agreement with Slack. Nothing is posted anywhere if no delivery target is configured, and the monthly report has no send at all: you copy the draft and send it yourself.

What we never do with Google data

• We never sell it, or share it with data brokers.
• We never use it for advertising, ad targeting, or retargeting.
• We never use it to train machine-learning or AI models, generalized or otherwise.
• We never transfer it beyond what is needed to provide the features you enabled. Humans do not read it except with your permission (for support), for security, or where the law requires.

Limited Use disclosure

Syncingbeam's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Retention, disconnecting, and deletion

Disconnection and deletion are handled by an operator on written request. You can revoke Google access directly through your Google account.

• Ask us to disconnect a source and we stop collecting from it and destroy its stored Google credentials. Authorized administrators can disconnect supported connectors in the application. Workspace owners can request data return or deletion, and use the available workspace deletion control. Disconnecting stops future collection; it does not by itself erase retained reports or remove data from the original provider. For a verified privacy request, contact [email protected]. We confirm completion and explain any retained records or outstanding processor actions. Backup copies expire through the backup rotation. Email [email protected] to start either request.
• Ask us to delete your workspace and the analytics aggregates and reports stored for it are deleted, by the same operator-performed process. Retention periods: Analytics aggregates and generated reports are retained for the life of the customer relationship, and deleted within 30 days of account termination or of a verified deletion request.
• Revoke access from the Google side at any time at myaccount.google.com/permissions. Revocation takes effect regardless of anything in SyncingBeam.

More detail

How we handle personal data in general, including data about the agency users who sign in, is covered in our privacy policy.