AskGSC vs Insights

Compare AskGSC and Insights on capabilities, jurisdiction, assurance, and fit for European buyers.

Both listed as alternatives to: Google Analytics

Logo: AskGSC

AskGSC

France· Web Analytics

Needs review

Shortlist AskGSC when a French-operated, hosted MCP layer is enough to query authorized Google Search Console data inside ChatGPT, Claude, or similar assistants. Skip when you need self-hosted control, write access, a site crawler, or first-party web analytics. Consider Plausible Analytics or Piwik PRO for on-site analytics, or a self-hosted GSC MCP when infrastructure ownership is the requirement.

EU-operatedHosted GSC MCPRead-only Google OAuthNo local MCP serverMulti-assistant MCP
Logo: Insights

Insights

Austria· Web Analytics

Needs review

Shortlist when you need cookie-free hosted analytics with first-class custom events for SPAs from an Austrian operator. Skip when you need self-host, public ISO/SOC packs, or infrastructure without Google Firebase—consider Plausible Analytics, Simple Analytics, or Pirsch Analytics instead (or self-hosted Matomo).

Cookie-free trackingCustom eventsMIT client (insights-js)Austrian entityHosted SaaSFirebase data path
AskGSC vs Insights: Snapshot
FeatureLogo: AskGSCAskGSCLogo: InsightsInsights
Country of originFranceAustria
CategoryWeb AnalyticsWeb Analytics
Open sourceNoYes
Self-hostedNoNo
HeadquartersFranceAustria
Legal entityKALYVOX SASUUnsourced Digital OG
US parent / controlNo known US parentNo known US parent
CLOUD Act exposure (indicative)MediumMedium
EU-hosted statusPartialNot listed
Hosting / residencyFrench operator; public providers include Lovable (web app hosting), Supabase (auth/DB/backend), Google APIs, Stripe for payments, and Cloudflare in front of the MCP host (mcp.askgsc.app CNAME to askgsc.pages.dev). Exact DB/hosting regions are not disclosed on AskGSC pages.Operator: Unsourced Digital OG (Austria). Vendor-documented infrastructure includes Google Firebase—Cloud Functions, Firebase Authentication (customer accounts), and Firebase Hosting—with temporary IP handling described for those Google services. Visitor analytics designed without cookies and without IP storage in DB/logs; still a US-group cloud path for processing/hosting/auth.
Summary

French hosted MCP connector that gives ChatGPT, Claude, and other assistants read-only Google Search Console analytics for SEO decisions without CSV exports.

Austrian privacy-first hosted web analytics: page views and custom events without cookies or stored visitor IPs, with an MIT open-source JS client (backend uses Google Firebase).

Tags
At a glance: AskGSC vs Insights
At a glanceLogo: AskGSCAskGSCLogo: InsightsInsights
HQToulouse, FranceNot listed
Legal entityKALYVOX SASU (SIREN 999 458 409)Not listed
Product typeHosted MCP connector for Google Search ConsoleHosted privacy web analytics + custom events
Google scopewebmasters.readonlyNot listed
Self-hostNo (hosted SaaS)No public self-host option
Open sourceNot claimedNot listed
HQ / lawNot listedAustria (Unsourced Digital OG; Austrian governing law)
Client licenseNot listedMIT (insights-js); backend proprietary
Commercial modelNot listedFree low-volume tier; paid by monthly event/pageview volume
Known infraNot listedGoogle Firebase (Functions, Auth, Hosting) per vendor docs
Cookieless trackingNot a site tracker; reads GSC via Google OAuth/APINot listed
Data residency regionsNot published; privacy policy allows non-EEA processing by providers/assistantsNot listed
Key capabilities: AskGSC vs Insights
Key capabilitiesLogo: AskGSCAskGSCLogo: InsightsInsights
EU-operatedYesNot listed
Hosted GSC MCPYesNot listed
Read-only Google OAuthYesNot listed
No local MCP serverYesNot listed
Multi-assistant MCPYesNot listed
Cookie-free trackingNot listedYes
Custom eventsNot listedYes
MIT client (insights-js)Not listedYes
Austrian entityNot listedYes
Hosted SaaSNot listedYes
Firebase data pathNot listedYes

AskGSC

  • Hosted remote MCP for Search Console

    Provides a remote MCP URL (mcp.askgsc.app) that compatible assistants call on demand. No local MCP server, Google Cloud project, or CSV export is required for the standard flow.

  • Eleven read-only GSC analysis tools

    Tools cover overview trends, query/page/country/device search analytics, period comparisons, opportunity signals, URL inspection (last-known indexing), and sitemap checks. None can modify Search Console or the website.

  • Read-only Google OAuth scope

    Uses https://www.googleapis.com/auth/webmasters.readonly plus identity scopes for sign-in. Users can revoke access from Google account connections; AskGSC states it does not sell Google user data or train its own models on it.

  • Works across multiple MCP clients

    Documented integrations include ChatGPT, Claude, Notion AI, Cursor, Claude Code, and Codex using one hosted MCP server rather than a separate connector per assistant.

  • Trial then limited free access, optional Pro

    A card-free trial starts when Search Console is connected. After the trial the account can remain on a limited free allowance; Pro is an express paid subscription for fuller tool access. Plan figures belong on the vendor pricing page.

Insights

  • Cookie-free page views and user flows

    Tracks bounce rate, referrers, visits, and user-flow style page statistics without setting analytics cookies, so sites can avoid cookie banners driven solely by analytics. Script init plus trackPages() is the usual path for SPAs.

  • Custom and cancelable event tracking

    insights-js supports named events with string parameters, unique-per-session flags, parameter-only updates, and remove/cancel for long-lived events (e.g. subscribe then unsubscribe). Built for product and funnel metrics, not pageviews only.

  • MIT open-source TypeScript client

    The browser/npm client (insights-js) is MIT-licensed on GitHub with TypeScript types and helpers for locale, screen type, path, referrer, and duration buckets. Supports React, Angular, Vue, UMD script, and multi-project App instances. Backend remains proprietary SaaS.

  • Visitor anonymization pipeline (vendor-described)

    Vendor docs: IPs hashed only in RAM for fraud checks (not stored in DB or logs); user agents reduced to browser/OS; optional screen sizes rounded to 50px; Do Not Track honoured. Confirm fit with your DPO—anonymous design is not a legal certification.

  • Developer-oriented integration

    One-minute script install or npm package; docs cover multi-project tracking, ignoreErrors/disabled flags for production environments, and hash/search options on page paths. Lightweight client positioned against heavier GA-style tags.

Assurance & compliance: AskGSC vs Insights
Assurance & complianceLogo: AskGSCAskGSCLogo: InsightsInsights
Independent security / no-logs audit
Not found

No public independent audit PDF or report linked from the site.

Not found

Vendor describes no IP storage in DB/logs and RAM-only hashing; no public third-party audit PDF found.

ISO 27001
Not found
Not found

No public certificate on getinsights.io at research time.

SOC 2 / SOC 3
Not found
Not found

No public SOC report found.

GDPR / EU data protection
Vendor claimed

French controller; GDPR rights section and CNIL reference on privacy policy. Confirm DPA for B2B.

Vendor claimed

Austrian entity; privacy policy and data-collection docs; cookie-free/no-stored-IP design for visitors. Firebase/Google processing still requires transfer/DPA diligence.

US CLOUD Act exposure (indicative)
Partial

EU entity / no known US parent, but Google, Supabase, Stripe, Cloudflare/Lovable, and user-selected US AI assistants appear in the public data path. Not legal advice.

Partial

EU entity / no known US parent, but Google Firebase (US-group) used for Cloud Functions, Auth, and Hosting per vendor data page. Indicative medium exposure. Not legal advice.

Data processing agreement (B2B)
Not found

No public DPA download found; ask vendor.

Not found

No standalone public DPA page found; request from contact@getinsights.io for B2B use.

EU AI Act
Partial

AskGSC is an MCP data gateway to user-selected AI assistants rather than a published generative model. AI Act obligations may still matter for how connected assistants are used; confirm with counsel.

Not applicable

Web analytics product, not an AI system product page.

Considerations & known limitations: AskGSC vs Insights
Considerations & known limitationsLogo: AskGSCAskGSCLogo: InsightsInsights
US-group cloud and SaaS in the data path
Medium

Privacy policy names Google, Supabase, Lovable, and Stripe; MCP DNS uses Cloudflare Pages. Search Console results also flow to the AI client you connect. Teams with strict EU-only subprocessor rules need a written region and subprocessor schedule.

Not listed
No public independent audit or cert package
Medium

ISO 27001, SOC 2, and independent security audits were not found on public pages. Security claims rest on vendor documentation (encrypted refresh tokens, read-only scope).

Medium

No ISO 27001, SOC 2, or third-party no-logs audit found on the public site. Rely on vendor claims plus your own review of the open client.

Depends on Google Search Console data quality
Low

Vendor docs note GSC data may be delayed, aggregated, or incomplete, and average position is not a real-time ranking. AI interpretations remain the user's responsibility.

Not listed
Very new legal entity
Low

KALYVOX appears in the French registry as created in January 2026. Expect limited public operating history and incomplete legal placeholders (retention periods, mediator contact) on some policy pages.

Not listed
Google Firebase on critical pathNot listed
High

Vendor documents Firebase Cloud Functions, Auth, and Hosting. Anonymous visitor design does not remove US-group cloud dependency for hosting/auth/processing—material for sovereignty-sensitive buyers.

Client open source only; no self-hostNot listed
Medium

insights-js is MIT; dashboard/backend are closed SaaS. You cannot run the full product on your infrastructure.

Small team / continuityNot listed
Medium

Product presented as built by two freelance developers under Unsourced Digital OG. Assess vendor longevity and support SLAs for business-critical analytics.

Bounce/unique metrics need SPA routingNot listed
Low

Client docs: trackPages bounce and unique views expect a client-side router and do not use cookies/localStorage; multi-page full reloads can skew metrics.

Fit

AskGSC

Best fit when

  • Founders and SEO operators who already decide inside ChatGPT, Claude, Notion AI, or coding agents
  • Teams that need recurring GSC questions (period compare, losing pages, low CTR) without CSV exports
  • Buyers who want read-only Google access and a hosted MCP URL rather than running their own server
  • Organizations that prefer a French contracting entity for a lightweight SEO analysis connector

Poor fit when

  • Needs to write to Search Console, request indexing, or edit the website through the connector
  • Requires self-hosted MCP, custom tool code, or fully controlled token storage and regions
  • Looking for cookieless first-party web analytics instead of Google search performance data
  • Procurement blocked without a public DPA, ISO 27001, or independent audit package

Consider instead when

  • When: You need first-party site analytics rather than Google Search Console metrics

    Consider: Plausible Analytics or Piwik PRO

    Different data source: on-site collection vs Google search reports

  • When: You must operate the MCP stack and credentials yourself

    Consider: Self-hosted Google Search Console MCP

    AskGSC's own compare pages frame this as higher setup for more control

  • When: Manual one-off analysis is enough

    Consider: Google Search Console UI and CSV exports

    No third-party MCP or assistant data path

Insights

Best fit when

  • Indie developers and small teams who want pageviews plus product/funnel events without analytics cookies
  • SPA and web-app builders using client-side routers who can call insights-js track/trackPages APIs
  • Teams that accept a free low-volume tier then event-volume paid plans (check current limits on getinsights.io)
  • Buyers who value an MIT-auditable client library even if the backend stays closed
  • EU sites prioritizing no-stored-visitor-IP design over full stack self-host control

Poor fit when

  • Orgs that require self-hosted or fully open-source analytics backend
  • Procurement needing published DPA, ISO 27001, or SOC 2 on the vendor site today
  • Policies that forbid Google Firebase / US-group cloud on any analytics path
  • Classic multi-page sites expecting accurate cookie-free bounce/unique metrics without SPA routing
  • Teams needing GA-class free segmentation, ads integrations, or data warehouse export

Consider instead when

  • When: You want simple hosted EU privacy page analytics with a strong Plausible-style product footprint

    Consider: Plausible Analytics

    Compare event depth: Insights markets custom events as a core differentiator vs simpler page-focused tools.

  • When: You want cookie-free analytics with an explicit privacy brand and different commercial packaging

    Consider: Simple Analytics

    Verify each vendor's hosting and subprocessor pages side by side.

  • When: You prefer a German peer privacy analytics product

    Consider: Pirsch Analytics

    Compare event features, regions, and legal docs for your DPA process.

  • When: You need full control of the stack or on-prem processing

    Consider: Self-hosted Matomo (or similar open analytics)

    Higher ops cost; no dependency on Insights SaaS or Firebase.

Open questions for due diligence

AskGSC

  • Will KALYVOX sign a B2B DPA and publish an authoritative subprocessor list with regions?
  • Which Supabase and Lovable regions host AskGSC production data today?
  • Are ISO 27001, SOC 2, or independent penetration-test reports available under NDA?
  • What exact retention applies to technical logs and backups (privacy page still has placeholders)?

Insights

  • Will Unsourced Digital OG sign a customer DPA and provide a current subprocessor list with regions?
  • Which Firebase/GCP regions process analytics and auth data today?
  • Are there any independent security assessments available under NDA?
  • What is the data retention schedule for events and account data after cancellation?
  • Is there an official path for enterprise SSO, invoice billing, or custom retention?