Search Console Account Handling

This document describes how Duneside accesses, uses, stores, and protects data from Google Search Console properties you choose to connect. Duneside is a read-only analytics and reporting platform for marketing agencies. We access Search Console data solely to produce organic search performance reports and consolidated cross-channel insights.

This policy supplements our Privacy Policy and Terms of Service.

You retain full ownership and authorityover your Search Console properties and verified sites at all times. Connecting a property to Duneside is entirely voluntary. By connecting, you confirm that you have lawful permission to grant read access to the property's search performance data.

Duneside does not take ownership of, transfer, or resell your Search Console properties or verified sites. You may revoke access at any time using the procedure in Section 9 of this document.

Our application uses the Google Search Console API to retrieve read-only search analytics and visibility data. Specifically, we access:

• Search performance metrics (clicks, impressions, CTR, average position)
• Query-level performance data for user-selected reporting periods
• Page-level search performance (top pages, landing page visibility)
• Country, device, and search appearance breakdowns you configure for reporting
• Site-level indexing and coverage summary data available through the API
• Historical search performance data for user-selected reporting periods

We request only the minimum API scopes necessary to deliver the reporting features described above.

Data retrieved from your Search Console properties is used exclusively to:

• Generate organic search performance reports for your agency and clients
• Provide consolidated reporting across paid and organic channels within Duneside
• Display analytics dashboards and exportable summaries you configure

We do not use Search Console data for SEO manipulation, automated indexing requests, or any purpose unrelated to analytics and reporting.

Duneside is a read-only platform. Through the Search Console API, we do not perform:

• URL submission or removal requests
• Sitemap creation, submission, or deletion
• Indexing or de-indexing requests
• Property verification changes
• Any other site management or search console administrative actions

All Search Console configuration and site management remains your responsibility and must be performed directly in Google Search Console or through tools you separately authorize.

Duneside does not engage in, and does not permit use of our Platform for:

• Selling advertising inventory or media placements
• Generating artificial clicks, impressions, or search traffic
• Reselling, brokering, or transferring Search Console properties or verified sites
• Operating search traffic arbitrage or similar business models
• Submitting bulk indexing or removal requests on your behalf

Our business model is limited to SaaS analytics and reporting services for agencies.

Access to Search Console is established through Google's official OAuth 2.0 authorization flow. Duneside does not collect or store your Google account password. API tokens are stored securely and used only to retrieve authorized reporting data.

Data is transmitted over encrypted connections (TLS). We apply access controls and industry-standard security practices to protect stored search performance data.

Search Console data is retained only while your Search Console integration remains connected and as needed to provide reporting for your selected date ranges. When you disconnect in Duneside, or when Google authorization is revoked and our systems are notified, we delete the associated integration and stored Search Console data within a reasonable timeframe, subject to any legal retention obligations.

You may disconnect your Search Console property from Duneside at any time. Complete the steps below to stop future data access and remove data stored by Duneside.

1. Disconnect in Duneside: Sign in to Duneside. Open Clients and select the client whose Search Console property you connected. In the Integrations section, find Google Search Console and click Disconnect. When you disconnect, Duneside immediately stops retrieving new Search Console data for that connection, removes the stored integration connection from our systems, and deletes synced Search Console data associated with that integration. If you manage multiple clients, repeat this for each client where Search Console is connected.
2. Revoke Google authorization: After disconnecting in Duneside, the Google user who originally authorized the connection must revoke Duneside's access at myaccount.google.com/connections or via Google Account → Security → Your connections to third-party apps and services. Select Duneside and choose Remove access. If multiple team members have access to the same Search Console property, revocation must be performed by the Google user who completed the OAuth sign-in with Duneside.
3. If you cannot sign in to Duneside: You may complete Step 2 in your Google Account. Revoking access is sufficient to immediately stop Duneside from retrieving new Search Console data. If you also need confirmation that stored data has been removed from Duneside, email support@useduneside.com with your agency or company name, the email address on your Duneside account (if known), and the Search Console site URL(s) or property identifier(s) you disconnected. We will confirm removal and assist with any remaining data deletion requests within a reasonable timeframe.
4. Automated removal via Google: If you remove Duneside from your Google Account connections, Google may notify us through their platform removal processes. When that happens, Duneside will delete the associated integration and stored Search Console data linked to that authorization.

For questions about Search Console data handling, API access scope, or account removal, contact support@useduneside.com.