Privacy Policy
Effective Date: October 22, 2026
This Privacy Policy describes how ConvRadar ("we," "us," or "our"), operated by Ivan Pika, Sole Proprietor, registered in Georgia, collects, uses, and protects your personal information when you use our website at https://convradar.com and related services, including our remote MCP (Model Context Protocol) connector accessible from Claude (Anthropic) and ChatGPT (OpenAI) (the "Service"). By using the Service, you agree to the practices described in this policy.
ConvRadar is an independent service. It is not made by, affiliated with, endorsed by, or sponsored by OpenAI, Anthropic, Google, or any other third party. References to ChatGPT, Claude, GA4, MCP, and other product or company names are made solely to describe interoperability. All trademarks belong to their respective owners.
1. Information We Collect
Account Information
When you create an account, we collect your email address. We use a passwordless magic-link authentication system powered by Supabase.
Google Analytics Data
When you connect your Google Analytics 4 (GA4) property, we access your GA4 data via Google OAuth 2.0 with read-only scope. This includes metrics such as sessions, conversions, revenue, page views, funnel data, and device and geographic breakdowns. The connection itself never writes to your property.
If ConvRadar finds that your conversions are not being measured, you can let it fix the tracking for you. This is a separate Google consent with edit permissions for Google Analytics and Google Tag Manager. With that consent ConvRadar can mark an existing event as a key event, create an event rule (for example, a lead event from a thank-you page), turn on enhanced measurement, and add the tags, triggers and variables you approve (for example GA4 event tags, and the Google tag if your container has none) to your Tag Manager container. To avoid duplicates it reads your Tag Manager accounts, containers and the live container version before proposing a change. When you ask for a tag in your own words, the request, a summary of your container (tag and trigger names and types), your GA4 event names with their counts and the buttons and links of the page you named are sent to an AI model from Anthropic, which drafts the change; Anthropic does not use this data to train its models. Every change is shown to you before it is made, is applied only when you click, is written to a log you can see in your account, and can be rolled back from the same page. ConvRadar never deletes or edits tags, triggers, or events it did not create, and never publishes a Tag Manager version without your click. You can revoke this access at any time from your Google account or from the tracking page in ConvRadar.
MCP Tool Requests and Responses
When an AI assistant calls a ConvRadar MCP tool, we may keep a limited copy of the arguments sent to that tool and the answer ConvRadar returned. We remove known credentials and sensitive details before storage and mark fields that were removed. This record helps us verify that the connector delivered the requested analytics. It does not include the assistant's conversation with you or the final answer the assistant writes.
Shopify Store Data
When you install the ConvRadar app in Shopify, ConvRadar reads your store's orders, products, inventory and Shopify analytics (sessions, funnel, conversion, devices, traffic sources, landing pages, countries) through the Shopify Admin API with read-only access. From each order it keeps the order number, dates, amounts, discounts, refunds and line items, the visit that led to it (landing page, referring site, UTM source, medium and campaign, first and last visit time) and the shopper's language setting. Shopify's analytics API requires the protected customer data permission (names, emails, phones, addresses). ConvRadar never queries or stores those fields. The terms ConvRadar processes store data under are in the Data Processing Addendum.
Store data serves only your own account. It never enters a benchmark or any number shown to someone else.
Usage Data
We collect basic usage data through Google Tag Manager, such as pages visited and interaction events, to improve the Service.
2. How We Use Your Information
- To authenticate your account and provide access to the Service.
- To connect to your GA4 property and run automated analytics audits.
- To generate audit reports with findings, diagnoses, and actionable recommendations.
- To improve the Service and user experience.
- To communicate with you about your account or changes to our policies.
3. Legal Basis for Processing
- Consent: You voluntarily provide your email and authorize access to your GA4 data.
- Contract performance: Processing is necessary to deliver the Service you signed up for.
- Legitimate interest: We process usage data to maintain and improve the Service.
4. Data Sharing & Third-Party Services
We do not sell, rent, or trade your personal information. We share data only with the following third-party service providers, solely to operate the Service:
- Google APIs: Used to access your GA4 data via OAuth 2.0 with read-only permissions, and, only with your separate consent, to apply the tracking fixes described above through the Google Analytics Admin API and the Tag Manager API.
- Supabase: Used for user authentication and secure data storage.
- Render: Used to host the ConvRadar web application and the MCP connector server.
- Resend: Used to send passwordless magic-link sign-in emails and account emails, which can quote numbers from your connected property or store.
- Anthropic and OpenAI: Used to write the answers in ConvRadar's own chat, on convradar.com and inside the Shopify app, from the numbers of the property or store you ask about. Neither provider trains models on this data under its API terms.
- Stripe: Used to process subscription billing where you choose to subscribe.
- ScreenshotOne / Browserless: Used solely to capture screenshots of public pages on your own site that you ask the Service to verify.
- Google Tag Manager: Used for website analytics tracking.
We maintain a complete list of third-party processors with the categories of data they handle and their hosting regions on our Subprocessors page. The list is updated when our stack changes.
5. Google API Services User Data Policy
ConvRadar'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.
Specifically:
- Reading your GA4 data uses read-only access. Edit access to Google Analytics and Google Tag Manager is requested only through the separate consent described in section 1, and is used only to apply a change you approved.
- We do not sell, share, or use Google user data for advertising purposes.
- We do not allow humans to read your Google user data except where necessary to provide the Service, with your explicit consent, for security purposes, or to comply with applicable law.
- We limit our use of Google user data to providing and improving the Service.
6. Data We Do Not Collect
When you use ConvRadar through Claude (Anthropic) or ChatGPT (OpenAI) as an MCP connector, we only receive the specific tool arguments the assistant sends to fulfil your request (for example, a date range, a metric name, or a page URL on your own site). We do not request, receive, log, or store:
- The full content of your conversations with ChatGPT, Claude, or any other AI assistant.
- Claude memory, chat history, conversation summaries, system instructions, or files you upload to Claude or ChatGPT.
- Your OpenAI account, ChatGPT account, Anthropic account, or Claude account identifiers, API keys, or session tokens.
- Any GA4 OAuth scope wider than
analytics.readonly. - Personally identifiable information of GA4 end-users (we read only aggregated metrics and dimensions; the GA4 Data API does not expose raw IPs or user IDs to us).
- Payment card numbers, government IDs, health records, or other special-category personal data.
We follow the principle of data minimisation: we collect only what is required to deliver the audit you requested.
7. Data Retention
Account data is retained for as long as your account is active. GA4 data fetched for audits is retained while your account is active, on any plan including Free.
For each tracking fix ConvRadar keeps the change you approved, its status and times, the IDs of the Google Analytics settings and Tag Manager entities it created, and the ID of the container version that was live before, so the change can be rolled back. For a tag you asked for in your own words ConvRadar also keeps the request, the draft and the names of the tags and events it compared against. Other contents of your Tag Manager container are read when you open the tracking page and are not kept. The fix log and the requests are deleted with your account.
Authentication credentials have hard-coded lifetimes in our MCP server: OAuth refresh tokens auto-expire after 30 days, OAuth authorisation codes after 5 minutes, and JWT access tokens after 1 hour.
Redacted MCP tool arguments and responses are kept for up to 30 days. Operational tool-call metadata may be kept for up to 90 days. These records are removed when your account is deleted.
Shopify store data, including what ConvRadar derived from it (findings, exports and chat messages about the store), is deleted when Shopify sends its shop/redact request 48 hours after you uninstall the app, and in any case within 30 days of the uninstall. When Shopify forwards a customer's erasure request, ConvRadar clears the visit details of that customer's orders and does not load them again. A customer's data request is answered in the app under Settings, Data requests, with the order details ConvRadar holds.
You may request deletion of your data at any time by contacting us. Upon account termination, we will delete your personal data within 30 days, except where retention is required by law.
8. Data Security
We use industry-standard security measures to protect your data, including encrypted connections (HTTPS), secure token storage for Google OAuth credentials, row-level security (RLS) for tenant isolation in our database, and least-privilege access controls. While no method of transmission or storage is 100% secure, we strive to protect your information using commercially reasonable means.
If you believe you have discovered a security vulnerability in ConvRadar, please report it through our Security Policy or email . We aim to acknowledge reports within 72 hours.
9. Your Rights
Depending on your location, you may have the following rights regarding your personal data:
- Right to access your personal data.
- Right to rectification of inaccurate data.
- Right to erasure (right to be forgotten).
- Right to restrict processing.
- Right to data portability.
- Right to object to processing.
- Right to withdraw consent at any time.
To exercise any of these rights, please use our Contacts page (subject line [privacy]). You may also revoke ConvRadar's access to your Google account at any time through your Google Account permissions.
10. Cookies & Tracking
We use cookies for the following purposes:
- Authentication cookies: To manage your login session (set by Supabase).
- Analytics cookies: Google Tag Manager may set cookies to collect usage data.
You can control or disable cookies through your browser settings. Disabling cookies may affect the functionality of the Service.
11. Children's Privacy
ConvRadar is a B2B analytics tool and is not intended for, marketed to, or designed for use by anyone under the age of 16. We do not knowingly collect personal information from children. We comply with the U.S. Children's Online Privacy Protection Act (COPPA) and the UK Online Safety Act. If we become aware that we have collected data from a child under 16, we will take steps to delete that information promptly.
12. International Data Transfers
Your data may be processed and stored in countries other than your country of residence, including the United States, where several of our third-party processors (Supabase, Render, Google, Stripe, Resend) operate.
Where the data subject is located in the European Economic Area, the United Kingdom, or Switzerland, transfers of personal data to countries that have not received an adequacy decision are governed by the European Commission's Standard Contractual Clauses (Module 2: Controller-to-Processor, Implementing Decision (EU) 2021/914), supplemented where required by the UK International Data Transfer Addendum and Swiss FDPIC guidance. The relevant clauses are passed through to our processors via their respective Data Processing Agreements, which are listed on our Subprocessors page.
13. Changes to This Privacy Policy
We may update this Privacy Policy from time to time. Changes will be posted on this page with an updated effective date. We encourage you to review this policy periodically. Continued use of the Service after changes constitutes acceptance of the updated policy.
14. Contact Us
If you have any questions about this Privacy Policy, please use our Contacts page.
- Ivan Pika, Sole Proprietor
- Email:
- Location: Georgia