Last updated: October 21, 2026

This policy explains how Coastline Revenue OS, Coastline Mall's internal operations tool, accesses, uses, stores and shares Google user data. Coastline Revenue OS is used only by Coastline Mall's owner.

1. Google data we access

With the owner's explicit permission through Google's sign-in, Coastline Revenue OS uses two read-only Google permissions:

  • Google Search Console (https://www.googleapis.com/auth/webmasters.readonly): the list of Coastline Mall's Search Console properties; search performance data such as queries, pages, clicks, impressions, click-through rate and average position; and URL inspection results.
  • Google Analytics (https://www.googleapis.com/auth/analytics.readonly): Coastline Mall's Analytics accounts and properties, property metadata, and standard and realtime reports.

Analytics requests that use user-level identifiers (for example user ID or client ID) are refused, and each report is limited to 500 rows. The tool has no ability to create, change or delete Google data.

Separately, Coastline Revenue OS reads Coastline Mall's own Google Merchant Center account through a dedicated read-only Google Cloud service account. That access does not use anyone's Google sign-in.

2. How we use the data

Google data is processed by Claude, an AI assistant made by Anthropic, at the owner's request to generate reports, evaluate search performance, analyze conversions, and improve Coastline Mall's marketing and revenue decisions. We do not sell this data, use it for advertising, or use it to build profiles of individuals.

3. Where data is processed and stored

  • Coastline Mall's connector (Google Cloud Run). The connector processes each request in memory and keeps no database of Search Console or Analytics data. Google access and refresh tokens are kept only inside credentials encrypted with AES-128-CBC and HMAC-SHA256. The encryption key is held in Google Cloud Secret Manager. Access credentials expire within one hour. The refresh credential remains valid until Google ends the authorization or the owner revokes it.
  • Google Cloud (hosting and logs). Google Cloud hosts the connector and records operational logs. Request logs contain request metadata such as time, path, status, client type and IP address. For sign-in requests they also include one-time OAuth parameters, for example the single-use "state" value. Application logs contain event messages and permission names. Logs do not contain Google tokens, client secrets or report data. Operational logs are kept for 30 days and Google Cloud audit logs for 400 days.
  • Anthropic (Claude). Anthropic stores the encrypted connector credentials so Claude can use the connector. Anthropic cannot read the Google tokens inside them. Results returned to Claude become part of the owner's Claude conversations. They are kept in the owner's chat history until the owner deletes them, and Anthropic removes deleted conversations from its systems within 30 days. Conversations that Anthropic's systems flag for a usage-policy review may be kept longer under Anthropic's policies.
  • Coastline Mall's working records. Reports and analyses derived from this data may be saved in Coastline Mall's internal working documents, in Claude projects and on Coastline Mall's own computers. They are kept until Coastline Mall deletes them.

4. Sharing

Google user data is shared only with Anthropic, which processes it to answer the owner's requests, and with Google Cloud, which hosts the connector. It is not sold or shared with advertisers, data brokers or other third parties. Data may be disclosed if required by law.

5. AI model training

Coastline Mall has turned off model training ("Help improve our AI models") in its Claude account. Anthropic states that, with this setting off, new conversations are not used for model training, and that raw content from connectors, including remote MCP servers such as this one, is excluded from training. Anthropic's terms list exceptions: conversations flagged for safety review may be used to improve Anthropic's safety systems, and conversations a user submits as feedback or explicitly opts in to share may be used. Coastline Mall itself does not use Google user data to develop or train artificial-intelligence or machine-learning models.

6. Google API Services User Data Policy

Coastline Revenue OS is subject to the Google API Services User Data Policy, including its Limited Use requirements.

7. Security

Connections use HTTPS. Sign-in uses Google OAuth with PKCE, and the connector accepts only its own credentials, bound to this service. Access is limited to the two read-only permissions above.

8. Your choices: revoking access and deleting data

Access can be revoked at any time at myaccount.google.com/permissions, or by disconnecting the connector in Claude. After revocation, the connector can no longer read any Google data. Claude conversations and Coastline Mall's working documents can be deleted by Coastline Mall at any time.

9. Changes and contact

We will update this page if these practices change. Questions: coastlinemallcontact@gmail.com