Legal
Privacy Policy
Effective November 3, 2026 · Last updated November 3, 2026
- Polymetric connects your marketing data sources (Google Search Console, Google Analytics 4, Google Ads and Shopify) to the AI assistants you choose, such as Claude and ChatGPT, over the Model Context Protocol (MCP).
- Access is read-only. We never change anything in your Google or Shopify accounts.
- By default Polymetric is a pass-through: we fetch data when your AI asks for it and hand it straight back. We do not keep copies of your reports.
- We store your account details, which sites and properties you chose to share, and an encrypted access token for each connection.
- We share your data only with the AI clients you connect, and with the service providers listed below that run Polymetric. We never sell it or use it for advertising.
- Disconnecting a source deletes its token right away. You can delete your workspace’s data, or your whole account, yourself at any time in Settings.
- 1. Who we are
- 2. What we collect
- 3. Google user data
- 4. Shopify data
- 5. How we use data
- 6. Your AI clients
- 7. Storage and retention
- 8. Sharing and subprocessors
- 9. Security
- 10. Disconnecting and deletion
- 11. Your rights
- 12. Cookies
- 13. International transfers
- 14. Children
- 15. Changes
- 16. Contact
1. Who we are
Polymetric (“Polymetric”, “we”, “us”) is a product of Polygon Digital LLC, a Texas limited liability company, 17350 State Hwy 249, Ste 220, Houston, TX 77064. This policy covers the website at polymetric.io, the dashboard at app.polymetric.io, and the MCP service at mcp.polymetric.io (together, the “Service”).
For data we process on behalf of our customers, the customer is generally the controller and we act as a processor. For account, billing and website data, we are the controller.
2. What we collect
Account information
When you sign up we receive your name, email address and a user ID from our sign-in provider, WorkOS. If you sign in with Google or another identity provider through WorkOS, we receive only these basic profile details. We also store your workspace name, your role, and when you last signed in.
Connection information
When you connect a data source we store the account it belongs to (for example your Google email address or your Shopify store domain), the permissions (scopes) you granted, an encrypted OAuth refresh or access token, and the list of sites, properties, stores or ad accounts available to you, including which ones you have chosen to share with your AI.
Data from your sources
When your AI asks a question, we request the matching data from the source on your behalf, for example search queries, clicks and impressions from Search Console, or sessions and conversions from Google Analytics. In the default pass-through mode this data is held in memory only for the time it takes to answer the request. See Storage and retention.
AI client and API key information
When you connect an AI client we store the client’s name, its redirect address, and hashed versions of the tokens we issue to it. If you create an API key, we store only a hash of the key, its name and when it was last used.
Billing information
Payments are handled by Stripe, through checkout and billing pages that Stripe hosts. You give your card or other payment details to Stripe, not to us, and we never see or store them. We keep the Stripe customer and subscription IDs for your workspace, your plan, billing period, trial dates and subscription status. When you start a plan, we share your workspace name, its ID and your account email with Stripe.
Usage and technical information
Our hosting provider records standard request logs such as IP address, time, URL, response status and user agent. We may record which tools your AI called, when, the parameters it used (such as a date range or site), and whether the call succeeded, so we can enforce plan limits, troubleshoot and prevent abuse. These records do not include the report data returned to your AI.
Messages you send us
If you email us, we keep the message and your contact details so we can reply.
3. Google user data
Polymetric lets you connect Google products so your AI can read their data. Each product is connected separately and asks only for its own read-only permission:
| Product | Scope we request | What we read |
|---|---|---|
| Google Search Console | webmasters.readonly | Your list of verified sites, and search performance data (queries, pages, countries, devices, clicks, impressions, CTR, position), sitemaps and URL inspection results for the sites you choose. |
| Google Analytics 4 | analytics.readonly | Your list of accounts and properties, and report data (dimensions and metrics such as sessions, users, events, conversions and revenue) for the properties you choose. |
| Google Ads | adwords (used for read-only reporting) | Your accessible customer accounts, and campaign, ad group, keyword and performance reports for the accounts you choose. Polymetric does not create, edit, pause or remove anything in Google Ads. |
How we use Google user data. We use it only to provide the feature you asked for: answering your AI’s questions about your own sites, properties and ad accounts, and showing you in the dashboard which ones are connected. We read the list of your sites, properties and accounts so you can choose which to share.
How we store it. We store the Google account email you connected, the scopes you granted, and an encrypted refresh token. By default we do not store report data. If you turn on history storage for your workspace (see section 7), daily Search Console and Google Analytics report data for the sites and properties you share is stored encrypted at rest, as described there.
How we share it. We send Google user data only to the AI clients you have connected to your Polymetric account, at your request, and to the infrastructure providers in section 8 that host and run the Service.
Limited Use disclosure. Polymetric’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
In line with those requirements, we:
- use Google user data only to provide or improve the user-facing features described above;
- transfer it to others only as needed to provide those features (for example to the AI client you connected), to comply with law, or as part of a merger or acquisition with notice to you;
- do not use or transfer it to serve ads, including retargeting, personalized or interest-based advertising;
- do not sell it, or use it for credit-worthiness or lending purposes;
- do not use it to develop, improve or train generalized artificial intelligence or machine learning models;
- do not let humans read it, unless you give us explicit permission for specific data (for example when you ask for support), it is needed for security purposes such as investigating abuse, it is needed to comply with law, or it is aggregated and anonymized for internal operations.
You can remove Polymetric’s access at any time from the Polymetric dashboard, or from your Google Account at myaccount.google.com/permissions.
4. Shopify data
What we access. When you connect a Shopify store, we ask Shopify for these read-only permissions: read_reports (sales and analytics reports), read_orders, read_products, read_customers and read_inventory. Shopify requires access to protected customer data (such as names, email addresses, phone numbers and addresses) for its analytics reports, so Shopify data may include personal information about your store’s customers.
How we use it. Shopify data is fetched on demand when your AI asks a question and passed to the AI clients you connected. We do not use it for advertising, sell it, or use it to train AI models.
How we store it. We store your store’s myshopify.com domain, name, primary domain, currency and time zone, the permissions you granted, and an encrypted access token and refresh token (Shopify access tokens expire after an hour and are refreshed as needed). We do not store orders, customers, products or report data. History storage (see section 7) currently covers Search Console and Google Analytics only, so Shopify data is always passed straight through. If we extend history storage to Shopify, we will update this policy first.
Shopify privacy requests. We handle Shopify’s mandatory privacy webhooks, and every request is verified with Shopify’s signature. When a store uninstalls Polymetric, or Shopify asks us to erase a store’s data (shop/redact), we delete that store’s connection, tokens and settings. When a store’s customer asks for their data (customers/data_request) or to be erased (customers/redact), we hold no records about individual customers, so there is nothing to export or delete. Disconnecting a store in Polymetric also removes our app from your Shopify admin.
5. How we use data
- To provide the Service: authenticate you, connect your sources, and answer your AI’s requests.
- To bill you and enforce plan limits.
- To keep the Service secure, investigate abuse and fix problems.
- To contact you about your account, security issues and changes to the Service. We will only send marketing emails if you opt in, and you can unsubscribe at any time.
- To comply with legal obligations.
Where the GDPR or a similar law applies, our legal bases are performance of our contract with you, our legitimate interests in running a secure and reliable service, your consent where we ask for it, and compliance with legal obligations.
6. Your AI clients
Polymetric’s purpose is to give the AI assistants you choose access to your data. When you connect an AI client, such as Claude (by Anthropic) or ChatGPT (by OpenAI), you authorize Polymetric to send it the data it requests from your shared sources. Data goes only to clients you have connected and approved, over an encrypted connection.
Once data reaches your AI client, that provider handles it under its own terms and privacy policy, not ours. Please review them, along with any settings they offer about using your conversations for model training. You can disconnect an AI client at any time from the Polymetric dashboard, which revokes its access immediately.
Your AI never receives your Google or Shopify tokens. It only receives the results of the requests it makes.
7. Storage and retention
Pass-through mode (default)
Every connection starts in pass-through mode. Data from your sources is fetched live for each request, returned to your AI, and not written to our database. It may sit in memory or a short-lived cache for up to a few minutes to avoid repeat requests and respect the source’s rate limits.
History storage (optional, opt-in)
History storage is off unless a workspace owner turns it on in Settings, and it is available only on plans that include it. When it is on, once a day we fetch and store a copy of report data for the Search Console sites and Google Analytics properties you share:
- Daily summaries (for example clicks, impressions, sessions, users, key events and revenue, in total and by device, country or channel), stored in our database.
- Daily detail (your top search queries, pages, landing pages and traffic sources for each day), stored as compressed files in Cloudflare R2 object storage.
This is aggregated report data about your sites. It does not include information about individual visitors. When you first turn it on, we also fetch past data, as far back as your plan allows and the source keeps (up to 16 months).
How long we keep it. Stored history is kept for as long as your plan allows: 90 days on Solo, 3 years on Pro and 5 years on Agency. We delete older data automatically each day.
Deletion. If you turn history storage off, or your plan no longer includes it, we stop storing new data straight away and delete everything stored for your workspace 30 days later, unless you turn it back on before then. Stopping sharing a site or property stops new data being stored for it. Disconnecting a source deletes its stored history within 30 days. Deleting your workspace data or your account in Settings deletes stored history immediately.
Other data
- Account and connection details: kept while your account is active, and deleted immediately when you delete your account in Settings (removal from backups follows the backup schedule below).
- OAuth tokens: deleted immediately when you disconnect the source.
- Usage records and request logs: kept for up to 90 days, unless we need them longer to investigate a security issue.
- Billing records: kept as long as tax and accounting law requires.
- Backups: our database provider keeps rolling backups that expire on their own schedule, usually within 30 days.
8. Sharing and subprocessors
We do not sell or rent personal information, and we do not share it for cross-context behavioral advertising. We share data only:
- with the AI clients you connect, as described in section 6;
- with the service providers below, who process it on our behalf under contracts that limit how they can use it;
- when required by law, or to protect the rights, safety and security of our users or the Service;
- as part of a merger, acquisition or sale of assets, in which case we will tell you and this policy will continue to apply to your data.
| Provider | Purpose | Data involved |
|---|---|---|
| Cloudflare, Inc. | Hosting, content delivery, request logs | All Service traffic, including data passed through to your AI; daily detail files (R2) if history storage is on |
| Neon (Databricks, Inc.) | Database hosting | Account, connection and encrypted token data; daily summaries if history storage is on |
| WorkOS, Inc. | Sign-in and user management | Name, email, sign-in events |
| Stripe, Inc. | Payments and subscriptions | Workspace name and ID, billing email, payment method (entered directly with Stripe), plan |
| Google LLC | Data source APIs (at your request); web fonts on polymetric.io | Tokens you granted; your IP address when loading fonts |
| Shopify Inc. | Data source API (at your request) | Tokens you granted |
We will update this list before adding a new subprocessor that handles customer data.
9. Security
- OAuth tokens for your data sources are encrypted with AES-256-GCM before they are stored. The encryption key is held separately from the database.
- Tokens we issue to AI clients, and API keys you create, are stored only as SHA-256 hashes.
- All traffic to and from the Service uses TLS.
- Access to source data is read-only, and limited to the sites, properties, stores and accounts you choose to share.
- Access to production systems is limited to the people who need it to run the Service.
No system is perfectly secure. If we learn of a breach that affects your personal information, we will notify you and the authorities as the law requires.
10. Disconnecting and deletion
- Disconnect a source: in the dashboard, choose Disconnect. We delete the encrypted token and the list of sites or properties for that connection immediately, ask Google to revoke the grant, and delete its stored history within 30 days.
- Disconnect an AI client: in the dashboard, revoke it. Its tokens stop working immediately.
- Delete your workspace data: in the dashboard, go to Settings and choose Delete data, then type the confirmation phrase. We disconnect every source (asking Google to revoke each grant and removing our app from your Shopify store), and immediately delete the encrypted tokens, your sites, properties and stores, your projects, all stored history and your workspace’s activity log. Your login, plan, API keys and connected AI clients remain.
- Delete your account: in the dashboard, go to Settings and choose Delete account, then type your email address to confirm. We immediately cancel any subscription (no further charges) and delete your customer record at Stripe, disconnect and revoke every source as above, and delete your workspace and everything in it: tokens, sites and properties, projects, stored history, API keys, AI client connections and activity logs. We also delete your login at our sign-in provider, WorkOS. If you belong to a workspace someone else owns, we remove only your access to it. Stripe keeps invoice and payment records that tax and accounting law requires, and database backups expire on their own schedule, usually within 30 days. You can also email hello@polymetric.io from the address on your account and we will do it for you within 30 days.
11. Your rights
Depending on where you live, you may have the right to access, correct, delete or export your personal information, to object to or restrict certain processing, to withdraw consent, and to complain to a data protection authority. California residents have the right to know, delete and correct personal information, and to not be discriminated against for exercising these rights. We do not sell or share personal information as those terms are defined under California law.
To make a request, email hello@polymetric.io. We will verify your identity and respond within 30 days. If your request is about data a Polymetric customer controls, such as a Shopify store’s customer records, we will pass it to that customer and help them respond.
12. Cookies
The dashboard uses a strictly necessary, signed session cookie to keep you signed in. Our sign-in provider may set its own necessary cookies during sign-in. The marketing site at polymetric.io does not use analytics or advertising cookies. If that changes, we will update this policy and ask for consent where required.
13. International transfers
We and our providers process data in the United States and other countries. Where we transfer personal information out of the European Economic Area, the United Kingdom or Switzerland, we rely on safeguards such as the European Commission’s Standard Contractual Clauses or the EU-U.S. Data Privacy Framework, as offered by each provider.
14. Children
The Service is for businesses and is not directed at children under 16. We do not knowingly collect personal information from them. If you believe a child has given us personal information, contact us and we will delete it.
15. Changes to this policy
We may update this policy as the Service changes. We will post the new version here and update the date at the top. If a change is significant, such as a new use of Google user data, we will tell you by email or in the dashboard before it takes effect, and ask for your consent where required.
16. Contact
Questions or requests about privacy: hello@polymetric.io
Polygon Digital LLC
17350 State Hwy 249, Ste 220, Houston, TX 77064
See also our Terms of Service.