SERP MobileAbout the pilot

Privacy and data

See what SERP Mobile accesses and how to manage the data you save in a private workspace.

Signing in and connecting sources

Google sign-in supplies your account identifier, email address, and profile information so SERP can open your workspace. A session cookie keeps you signed in. You grant reporting access separately, when you choose to connect a source.

Google Search Console
Read the properties your Google account can access. After you choose a property, SERP reads aggregate search performance for it, including dates, queries, pages, clicks, and impressions.
Google Analytics 4
Read available properties and streams. SERP reads aggregate metrics for the selected property and stream, such as sessions, engagement, landing pages, and configured key events.
Google Play reports
Read-only Google Cloud Storage permission can cover other data your account can access. SERP uses it to read install and ratings report files for the selected Play report bucket and Android package.

When you connect another provider, review its consent screen or the key permissions shown in setup. The connection and saved reports belong to the project you selected.

Saved reports, agents, and support

SERP uses connected data to display source reports, compare saved periods, and help you record improvements. Firebase hosts the workspace and stores saved reports, project settings, and workspace activity. Provider credentials are encrypted before being saved on the server.

An MCP client can read saved data after you approve its projects and read permissions. You can revoke access under MCP access settings. If you run Answer sampling, the questions you enter are sent to the configured model. The model request uses your entered questions and does not attach saved Google reports.

Sentry receives app diagnostics and support messages. Help & support lets you choose whether to share your reply email or the project name. When reporting from Integration health, you can also choose to share the displayed connection and sync status. Use your support receipt ID to request removal of a submitted message. This browser tab can recover the latest receipt for two hours. SERP keeps a short-lived lookup with delivery status and the receipt ID.

For pilot invitations, SERP stores the invited Google email and invitation status. The pilot operator can see who accepted and can remove the invitation record. If you share a pilot check-in, the operator can see your report progress, optional paid plan interest, and the date you shared it. You can optionally share the elapsed time from accepting to your first qualifying saved report from Search Console, App Store Connect, or Google Play. The timing check-in shares the report source and duration with the operator. Your project, report and metrics stay private. You can remove timing separately or remove your check-in from Plan & usage. An invitation is separate from project access and billing.

If you opt into pilot referrals, SERP counts your signup by UTC date. In pilot test billing, you can separately include a paid Stripe sandbox invoice in the campaign totals. The referral result stores a hashed account reference and the signup and invoice payment timestamps. Use the same billing view to remove it or contact support for an account data request.

Disconnect, export, or delete

  1. Disconnect a source from its settings to stop new syncs through that connection. Saved reports stay in the workspace. To remove access at Google itself, review your Google Account connections. Removing Google access there can affect multiple projects.
  2. Export your project from Project settings to download supported saved reports and workspace records. The download window is 24 hours from when the export starts. You can discard a prepared copy to close that window early. Temporary server data follows the original expiry. Provider credentials are excluded.
  3. Delete your project from Project settings to remove its saved workspace data, stored credentials, and access through MCP grants. A grant that also covers other projects still works for those projects. If cleanup is interrupted, the workspace shows a retry action. The provider keeps its original records. Support messages in Sentry and copies you already downloaded are outside project deletion.

Report availability depends on the source and its retention window. Saved Answer sampling results are available for up to 90 days.

For account data or privacy requests, contact tomas@rdev.co.nz or use Help & support from your workspace.