Simple Analytics vs Stormly

Compare Simple Analytics and Stormly on capabilities, jurisdiction, assurance, and fit for European buyers.

Both listed as alternatives to: Google Analytics

Logo: Simple Analytics

Simple Analytics

Netherlands· Web Analytics

Needs review

Shortlist when you need EU-operated, cookieless web metrics without visitor IDs or stored IPs—especially as a visibility layer beside GA4. Skip when you need self-host/open-source control, session replay, or identity-rich marketing analytics; consider Plausible Analytics or Matomo/Piwik PRO instead.

Cookieless analyticsNo stored IPs / visitor IDsEU-hosted (NL focus)Dutch B.V.Works beside GA4API & BI export
Logo: Stormly

Stormly

Netherlands· Web Analytics

Needs review

Shortlist Stormly when you need Dutch-contracted, e-commerce-first product analytics: SKU-aware report packs, Shopify/Adobe-oriented setup, inbox-style AI anomaly narratives, and a public DPA. Skip when you need cookieless privacy web stats only (consider Plausible, Simple Analytics, or Pirsch), open-source self-hosting, verified ISO/SOC on a public cert page, or a subprocessor chain free of US-group cloud and Azure OpenAI.

E-commerce product analyticsSKU-aware reportsAI anomaly insightsShopify / Adobe CommerceNL entity + public DPASaaS (not self-host)
Simple Analytics vs Stormly: Snapshot
FeatureLogo: Simple AnalyticsSimple AnalyticsLogo: StormlyStormly
Country of originNetherlandsNetherlands
CategoryWeb AnalyticsWeb Analytics
Open sourceNoNo
Self-hostedNoNo
HeadquartersNetherlandsNetherlands
Legal entitySimple Analytics B.V., Amsterdam (KVK 88269922, VAT NL864560011B01)Monon B.V. (Lutmastraat 1-3, 1072 JL Amsterdam; KvK 76248747 per Terms)
Governing lawNetherlands / EUNetherlands (Dutch law; Amsterdam courts)
US parent / controlNo known US parentNo known US parent
CLOUD Act exposure (indicative)LowMedium
Hosting / residencyAnalytics data claimed processed in the Netherlands/EU. Public subprocessors (May 2026): Worldstream + Leaseweb (NL hosting), Hetzner (DE hosting), Bunny (SI CDN/DNS), Hyperping (FR uptime), Intention (NL domains). Vendor states this list covers website visitor-data subprocessors only—not payments/internal ops.Client analytics subprocessors (Security Architecture): Hetzner (EU); Amazon AWS (US company, vendor states EU regions only for encrypted analytics backups); Vultr (US company); Microsoft Azure OpenAI (US company, vendor states EU Azure region). Plans market EU data residency. Controller privacy policy also references Vultr/AWS for account data, AuthSMTP EU + Amazon SES USA for email, Stripe for payments; marketing site uses Google Analytics and Hotjar.
Summary

Dutch privacy-first web analytics SaaS: cookieless pageviews and campaigns without visitor IDs or stored IPs, EU-hosted by Simple Analytics B.V. in Amsterdam.

Dutch SaaS product analytics for e-commerce teams: SKU-aware reports, AI-assisted anomaly and root-cause insights, and Shopify/Adobe Commerce/Segment/GTM-oriented connections under Monon B.V. (Amsterdam).

Tags
At a glance: Simple Analytics vs Stormly
At a glanceLogo: Simple AnalyticsSimple AnalyticsLogo: StormlyStormly
HQAmsterdam, NetherlandsNot listed
Legal entitySimple Analytics B.V. (KVK 88269922)Not listed
Founded2018Not listed
Product typeHosted web analytics SaaS (not self-hosted)Not listed
Open sourceNo (proprietary)No
Data focusCookieless, non-identifying aggregate metricsNot listed
Primary hostingNetherlands (EU); see subprocessorsNot listed
Commercial modelFree hobby tier + usage-based paid + enterpriseFree tier + monthly plan + custom; trial path on paid
HQ / entityNot listedMonon B.V., Amsterdam, Netherlands
CategoryNot listedE-commerce product analytics (SaaS)
Hosting (public)Not listedHetzner; AWS EU-region backups; Vultr; Azure OpenAI EU region (vendor docs)
Self-hostNot listedNo
Governing lawNot listedDutch law; Amsterdam courts
Key capabilities: Simple Analytics vs Stormly
Key capabilitiesLogo: Simple AnalyticsSimple AnalyticsLogo: StormlyStormly
Cookieless analyticsYesNot listed
No stored IPs / visitor IDsYesNot listed
EU-hosted (NL focus)YesNot listed
Dutch B.V.YesNot listed
Works beside GA4YesNot listed
API & BI exportYesNot listed
E-commerce product analyticsNot listedYes
SKU-aware reportsNot listedYes
AI anomaly insightsNot listedYes
Shopify / Adobe CommerceNot listedYes
NL entity + public DPANot listedYes
SaaS (not self-host)Not listedYes

Simple Analytics

  • Cookieless metrics without visitor IDs or stored IPs

    Collects pageviews, referrers, UTMs, time-on-page, and scroll depth without cookies, localStorage, fingerprints, or stored IP addresses. Unique visits are inferred from referrer hostname matching, not device IDs. Built for sites that want analytics without a consent banner solely for this tool—and without building visitor profiles.

  • Country from time zone, not geo-IP

    Country-level location is derived from the visitor’s IANA time zone rather than IP lookup, so IPs can be dropped end-to-end. City/region is not available; some border and multi-country zones can mis-tag. Useful when legal teams reject IP-based geolocation even when hashed.

  • Cookieless layer beside GA4 and BI stacks

    Positioned to measure traffic lost when consent is denied in cookie-based tools. Import historical Google Analytics data; export via Stats/Export APIs and integrations toward Looker Studio, Power BI, and warehouse workflows so analysts can compare consented vs observed traffic without replacing every GA report.

  • Lightweight script, events, goals, and ad-blocker bypass

    Vendor claims a single script under 5 KB. Supports events, automated events (e.g. downloads, outbound links), goals, filters, email reports, and robot/referrer-spam controls. Ad-blocker resilience is via first-party proxy or custom subdomain CNAME—not automatic immunity for every blocklist.

  • Team access, SSO, and EU-operated SaaS

    Hosted product from Simple Analytics B.V. (Amsterdam) with role-oriented team features on higher tiers and documented SAML SSO for Okta and Microsoft Entra. No official self-host edition—operations and residency follow the vendor’s EU infrastructure and public subprocessor list.

Stormly

  • AI agent for trends, anomalies, and root-cause style digs

    Stormly positions an AI agent that watches connected e-commerce data for trends and anomalies (for example conversion drops or product spikes), then delivers plain-language findings—often to the inbox—with root-cause style exploration for questions like mobile conversion drops or regional return spikes. AI assistant access is plan-dependent; the public DPA documents Azure OpenAI (Microsoft) handling of assistant queries with a 30-day retention window and property stripping rules. Best for merchandising and growth leads who want narrative answers without waiting on a data team.

  • SKU-aware e-commerce report library (plus custom builds)

    Ready reports target commerce questions: New Arrivals Performance (early SKU winners/laggards), Unviewed & Unsold Products, cart abandonment and revenue contribution by product/category, Conversion Journey and funnels by device/region, A/B test insights, Aha Moment Discovery, cross-selling analysis, and broader library items (retention, CLV, forecasting, SQL report, and more). Vendor materials state custom reports are included without a separate fee when a needed view is missing—useful for mid-market retailers that outgrow generic event charts.

  • Shopify, Adobe Commerce, Segment, and GTM-oriented connections

    Homepage setup emphasizes linking Shopify, Adobe Commerce, or Segment quickly, with Google Tag Manager also listed among integrations. The DPA describes additional programmatic paths (JS library, import, custom endpoints, third-party sources). Fits stores already on common commerce stacks; teams on exotic storefronts should validate event coverage and product-feed depth in a pilot before replacing an existing analytics stack.

  • End-user tracking with IP anonymization defaults

    Per the DPA, IP addresses for end-user analytics are not stored in full: the last octet is removed and geo/timezone are derived from the anonymized value. Web integrations automatically capture first-party cookie user ids, page/referrer/UTM context, and device metadata; app properties depend on client or CDP configuration. This is still full product analytics (not cookieless aggregate-only web stats)—clients remain responsible for consent banners and lawful basis for shopper tracking.

  • Public DPA, security architecture, and Dutch contracting

    B2B buyers can download a Data Processing Agreement (effective 2023-09-06) and a Security Architecture page listing subprocessors, encryption expectations, backup retention (analytics backups up to six months), and logical tenant isolation. Contracts and DPA are governed by Dutch law with Amsterdam courts. Useful for EU procurement packages—but US-group subprocessors (AWS, Vultr, Azure OpenAI) still require transfer and CLOUD Act diligence.

Assurance & compliance: Simple Analytics vs Stormly
Assurance & complianceLogo: Simple AnalyticsSimple AnalyticsLogo: StormlyStormly
Independent security / no-logs audit
Not found

Searched security/trust pages; no public independent audit PDF found.

Not found

Security Architecture describes encryption, monitoring, isolation, and vulnerability contact (security@stormly.com); no public third-party audit PDF found.

ISO 27001
Not found

No ISO 27001 certificate claimed on primary security pages.

Not found

No public ISO 27001 certificate located on official legal/security pages reviewed.

SOC 2 / SOC 3
Partial

Vendor states SOC 2 Type II is in progress / coming soon—not completed certification at research time.

Not found

No public SOC 2/3 report located on official pages reviewed.

GDPR / EU data protection
Vendor claimed

Dutch EU entity; vendor claims no personal data collection (no cookies/IPs/visitor IDs) and GDPR-friendly design. Not legal advice—confirm for your processing facts.

Vendor claimed

NL entity; public privacy policy and DPA (GDPR-oriented); IP last-octet anonymization for end-user analytics; SCCs language for restricted transfers in DPA.

US CLOUD Act exposure (indicative)
Partial

EU entity, no known US parent, public analytics subprocessors are EU-based (Worldstream, Leaseweb, Hetzner, Bunny, Hyperping). Residual risk remains; reconcile Cloudflare mention on GDPR page vs Bunny on subprocessors. Assessment by EuropeanStack—not a vendor 'safe' claim. Not legal advice.

Partial

EU entity / no known US parent, but public client subprocessors include AWS, Vultr, and Microsoft Azure OpenAI (US-group companies). Account path historically also lists Amazon SES and Stripe. Residency claims do not remove US-group legal exposure. Indicative only—not legal advice.

Data processing agreement (B2B)
Partial

Vendor says DPA usually not required (no personal data) but will review/sign customer-provided DPAs aligned with architecture.

Vendor claimed

Downloadable DPA PDF linked from stormly.com/dpa (effective 6 September 2023); audit rights and subprocessor notice described; Security Architecture lists subprocessors.

EU AI Act
Not applicable

Web analytics product; not marketed as an AI system subject to AI Act high-risk regimes.

Partial

Product includes an AI assistant via Azure OpenAI; not positioned as a high-risk AI system marketing claim. Buyers should map AI assistant use to their own AI Act / internal AI policy—vendor does not publish a full AI Act conformity package on the pages reviewed.

Considerations & known limitations: Simple Analytics vs Stormly
Considerations & known limitationsLogo: Simple AnalyticsSimple AnalyticsLogo: StormlyStormly
Hosted SaaS only—no self-host
Medium

No official self-host edition. Orgs with air-gap or on-prem telemetry mandates need Plausible self-host, Matomo, or similar instead.

Not listed
SOC 2 not yet complete
Medium

SOC 2 Type II is publicly 'in progress'. Enterprise security reviews may block until a report is available or accept compensating controls (minimal data + EU hosts).

Not listed
Referrer-based uniques and timezone country
Low

Uniques are not durable visitor IDs; country is timezone-based with known mis-tag edge cases. Totals will differ from GA client-ID models—set stakeholder expectations.

Not listed
CDN/DDoS vendor documentation inconsistency
Low

Subprocessors list Bunny (EU) for CDN/DNS; GDPR page still references Cloudflare for CDN/DDoS. Ask for current edge path before asserting zero US-group infrastructure touch.

Not listed
Small independent operator
Low

Public About page describes a three-person self-funded team. Fine for many sites; large enterprises should assess continuity, support SLAs, and roadmap capacity explicitly.

Not listed
US-group cloud and AI subprocessorsNot listed
Medium

Despite Dutch HQ and EU residency marketing, client data paths publicly include AWS, Vultr, and Microsoft Azure OpenAI. Transfer tooling (SCCs) and encryption of backups are documented, but CLOUD Act / US legal process risk remains a diligence item for sovereignty-sensitive buyers.

No public ISO/SOC or independent auditNot listed
Medium

Enterprise security questionnaires may stall without ISO 27001/SOC 2 packs. DPA offers information/audit rights—plan time for NDA evidence requests.

Azure OpenAI retains assistant context 30 daysNot listed
Medium

AI queries and aggregate report results are stored on Microsoft Azure OpenAI for 30 days per DPA. Property stripping reduces some identifiers, but misconfigured event properties could still expose sensitive content—govern AI use and property hygiene.

Controller privacy policy vs security architecture driftNot listed
Low

Privacy policy (controller, effective 2019) still emphasizes Vultr USA wording in places, while Security Architecture (client data) lists Hetzner/AWS/Vultr/Azure. Ask for a single current subprocessor and region matrix at contract time.

Not a privacy web-analytics substituteNot listed
Low

Full product analytics with cookies/identifiers for web integrations—not a cookieless aggregate counter. Consent UX remains on the client.

Fit

Simple Analytics

Best fit when

  • Teams measuring traffic lost when consent is denied in cookie-based analytics (GA4/Adobe)
  • Public-sector and regulated sites that need no cookies/IPs/visitor profiles for web stats
  • EU procurement that requires Dutch legal entity + published EU subprocessors for visitor data
  • Agencies/multi-site operators wanting a simple hosted dashboard, reports, and API/BI egress
  • Sites that want essential pageview/referrer/UTM metrics without an analytics-only consent banner

Poor fit when

  • Product analytics needing session replay, heatmaps, or person-level funnels
  • Organizations that must self-host analytics or prefer open-source governance (see Plausible/Matomo)
  • Buyers requiring city/region geolocation accuracy (country is timezone-derived)
  • Teams whose primary need is identity-rich attribution, audiences, and marketing automation inside the analytics suite

Consider instead when

  • When: You need open-source and/or official self-hosting of privacy-first analytics

    Consider: Plausible Analytics (catalog: plausible_analytics) or Matomo

    Simple Analytics is hosted SaaS only; Plausible and Matomo cover self-host paths many security policies require.

  • When: You need a deeper EU enterprise analytics platform with configurable processing and on-prem options

    Consider: Piwik PRO (catalog: piwik_pro)

    Heavier suite and procurement surface than Simple Analytics’ minimal cookieless product.

  • When: You need identity graphs, remarketing audiences, and full marketing analytics depth

    Consider: Google Analytics or Adobe Analytics

    Keep those for consented deep analysis; Simple Analytics is the opposite design tradeoff.

  • When: You want another lightweight EU cookieless tracker and are comparing peers

    Consider: Pirsch Analytics (pirsch_analytics) or Friendly Analytics (friendly_analytics)

    Compare retention, multi-site, SSO, and API maturity rather than GDPR slogans alone.

Stormly

Best fit when

  • Merchandising, product, UX, and growth teams on Shopify or Adobe Commerce who need SKU, cart, and assortment analytics without a dedicated data science org
  • Retail brands that want ready e-commerce report templates (new arrivals, unviewed/unsold, funnels, A/B, aha moments) plus vendor-built custom reports
  • EU buyers who want a Dutch legal entity, Amsterdam courts, and a downloadable DPA/Security Architecture package
  • Teams that value AI-generated trend/anomaly narratives delivered to the inbox more than building every chart from a blank event schema
  • Stacks already using Segment or Google Tag Manager as the event pipe into analytics

Poor fit when

  • Publishers or marketing sites that only need lightweight privacy-friendly page analytics (not product/SKU depth)
  • Orgs that require open-source self-hosting or full control of a private analytics warehouse as the default
  • Procurement policies that forbid US-group subprocessors (AWS, Vultr, Microsoft Azure OpenAI) even when EU regions are claimed
  • Assurance programs that require public ISO 27001/SOC 2 evidence before pilot (not found on vendor pages reviewed)
  • Companies operating blockchain products/services—restricted by Stormly’s terms

Consider instead when

  • When: You only need privacy-oriented website metrics (pageviews, sources) rather than SKU-level product analytics

    Consider: Plausible Analytics, Simple Analytics, or Pirsch Analytics

    EU web-analytics peers; different category from e-commerce product analytics

  • When: You need deep general-purpose product analytics, large ecosystem, and mature multi-product SaaS event modeling

    Consider: Mixpanel or Amplitude

    US incumbents; stronger breadth, different jurisdiction and commercial model

  • When: You primarily need free/universal marketing acquisition reporting already embedded in the stack

    Consider: Google Analytics (incumbent) or dual-run GA for marketing + Stormly for product/merch

    GA is not SKU-first product analytics; Stormly is not a GA replacement for every report

Open questions for due diligence

Simple Analytics

  • Is Cloudflare still used for any CDN/DDoS path, or has Bunny fully replaced it for edge services?
  • When will SOC 2 Type II complete, and will the report be available under NDA?
  • What exact data-retention windows apply per plan for your expected traffic volume?
  • Will the vendor sign your standard DPA/SCC pack as-is for public-sector procurement?
  • Are any non-EU subprocessors used for account email, payments, or support that could affect broader vendor risk (visitor analytics list excludes these)?

Stormly

  • Can Stormly provide a current region map (which data classes live on Hetzner vs Vultr vs AWS) under NDA for our DPIA?
  • Are ISO 27001, SOC 2, or penetration-test summaries available on request for enterprise security review?
  • Which event properties from our Shopify/Adobe feed are excluded from Azure OpenAI prompts by default in our tenant?
  • Do custom report builds and SQL access sit only on the custom tier, and what SLAs apply?
  • Has the 2019 controller privacy policy been superseded for hosting wording relative to the Security Architecture list?