Disconnect.
Request deletion.

1. Stop future Google data access

Ask your authorized integration administrator to disconnect the relevant GA4 or GSC connection. The administrator uses the service API with connections:manage permission:

DELETE /v1/ga4/connections/{connection_id}
DELETE /v1/gsc/connections/{connection_id}

Use the endpoint for the connection you intend to disconnect, not both automatically. The service checks the organization and connection type, attempts revocation at Google, deletes the local stored credential, invalidates the local access token and disables the connection's resource bindings. Local report access through that connection is blocked, including cached reads, even if Google revocation cannot be completed.

You can also remove hyperseo's access in your Google account's third-party connections. Google-side revocation for the same account and OAuth application can affect both GSC and GA4. Another independently authorized active connection may still allow access; review all connections you intend to stop. Google-side revocation alone does not delete data already held by hyperseo.

2. Request deletion of stored data

Email huliqiong1124@gmail.com with the subject hyperseo data deletion request. Include:

• The organization or integration you use and a reply address we can verify.
• The affected website or GA4 property identifier; a connection ID if available.
• The scope of your request: stop access, delete retained connection/resource records, delete HyperAtlas reports/evidence, or all applicable data, including backup handling.

Do not send your Google password, API key, OAuth code, access token or refresh token. We may ask for confirmation through your existing integration administrator or another verifiable channel. Knowing a website URL alone is not proof that you may delete an organization's data.

3. What happens next

After verifying your authority, we identify the affected live records and any saved reports, audit records and backups. We explain the scope, any records that need to be retained for a specific legal or security reason, and the expected handling time. We confirm what has been deleted when the work is complete. Deletion is handled by request; there is no automatic account-wide purge triggered by disconnecting.

HDS report cache entries expire within 300 seconds. Disconnecting is not a claim that historical reports, metadata, audit records, backup copies or copies held by your API/MCP clients have all been erased. We cannot delete the underlying data in your Google Analytics or Search Console account with our read-only permissions, or independently controlled copies you exported to another client.

4. Contact and related policy

Operator: hyper.hu, individual developer. Contact: huliqiong1124@gmail.com. For the data categories, uses and retention boundaries, read the privacy policy.