etracker vs TelemetryDeck

Compare etracker and TelemetryDeck on capabilities, jurisdiction, assurance, and fit for European buyers.

Both listed as alternatives to: Matomo

Logo: etracker

etracker

Germany· Web Analytics

Needs review

Shortlist etracker when you need German-hosted marketing-grade web analytics with a cookieless default, integrated tag/consent tooling, and optional ad conversion sync. Skip when you must self-host open source (prefer Matomo) or only need lightweight pageview charts (prefer Plausible or similar). Treat ePrivacyseal consent-free claims as vendor-audited posture—confirm with your counsel and DPIA.

Cookieless default trackingEU/DE hosted (IPHH)ePrivacyseal (claimed)Tag + consent suiteAd conversion syncSaaS only (not self-host)
Logo: TelemetryDeck

TelemetryDeck

Germany· Web Analytics

Needs review

Shortlist TelemetryDeck for multi-platform app analytics when on-device double-hash anonymization, cookieless signals, open SDKs, and a German-operated SaaS matter more than self-host or profile-heavy product suites. Skip when you need website-only simplicity (Plausible/Pirsch), full self-host control (Matomo/Plausible CE), or Mixpanel/Firebase-class identity and ecosystem depth—and have legal review the vendor’s “not personal data / not Art. 28 processor” DPA model plus AWS/Azure subprocessors.

Multi-platform app SDKsOn-device anonymizationCookieless signalsEU-operated (DE GmbH)Open-source client SDKsManaged SaaS (no self-host)
etracker vs TelemetryDeck: Snapshot
FeatureLogo: etrackeretrackerLogo: TelemetryDeckTelemetryDeck
Country of originGermanyGermany
CategoryWeb AnalyticsWeb Analytics
Open sourceNoNo
Self-hostedNoNo
HeadquartersGermanyGermany
Legal entityJustRelate Deutschland GmbH (Charlottenburg HRB 218235); product brand JustRelate etracker / etrackerTelemetryDeck GmbH, Von-der-Tann-Str. 54, 86159 Augsburg (HRB 37541)
Governing lawNot listedGermany (terms reference German law / Bayern courts; consumer protections may vary)
US parent / controlNo known US parentNo known US parent
CLOUD Act exposure (indicative)LowMedium
Hosting / residencyPrimary analytics processing on etracker's own servers in Germany/EU with housing at IPHH Internet Port Hamburg GmbH (vendor: no third-party access to apps/data for housing). Optional customer-enabled outbound paths to Google/Meta/TikTok/Microsoft Ads (conversion upload) and Google Looker Studio connectors—not core storage hosts.Product analytics: Microsoft Azure Amsterdam (NL), AWS Frankfurt (DE), Hetzner Falkenstein and Nürnberg (DE) per Privacy FAQ. Website privacy policy lists Microsoft Ireland Operations Ltd, Amazon Web Services Inc (US entity), and Hetzner Online GmbH as hosters with claimed Art. 28 contracts for site hosting. Account-side: HubSpot Inc (US CRM), Brevo/Sendinblue GmbH (DE email), Stripe payments per terms.
Summary

German SaaS web and marketing analytics from JustRelate: cookieless default tracking, integrated tag/consent management, e-commerce and ad conversion sync on EU-hosted servers.

German privacy-first app analytics SaaS: lightweight multi-platform SDKs, on-device double-hash anonymization, cookieless signals, and managed dashboards for mobile, desktop, and web products.

Tags
At a glance: etracker vs TelemetryDeck
At a glanceLogo: etrackeretrackerLogo: TelemetryDeckTelemetryDeck
HQ / legal entityJustRelate Deutschland GmbH, Berlin (product ops Hamburg)Not listed
Product typeWeb & marketing analytics SaaS (+ tag/CMP modules)Managed app/web analytics SaaS
HostingOwn servers, IPHH housing, Hamburg/GermanyNot listed
Open sourceNoNot listed
Self-hostedNoNot listed
Commercial modelUsage-based SaaS licence (hit tiers); trial commonly offeredFree tier + monthly event volume; plan-based query retention
HQNot listedAugsburg, Germany (TelemetryDeck GmbH)
Legal entityNot listedTelemetryDeck GmbH · HRB 37541 · VAT DE353418916
Self-hostNot listedNo (open-source client SDKs only)
Hosting (vendor)Not listedAzure Amsterdam; AWS Frankfurt; Hetzner Falkenstein/Nürnberg
DPANot listedPublic DPA/AVV asserting anonymized non-processor model; TOMs on request
Key capabilities: etracker vs TelemetryDeck
Key capabilitiesLogo: etrackeretrackerLogo: TelemetryDeckTelemetryDeck
Cookieless default trackingYesNot listed
EU/DE hosted (IPHH)YesNot listed
ePrivacyseal (claimed)YesNot listed
Tag + consent suiteYesNot listed
Ad conversion syncYesNot listed
SaaS only (not self-host)YesNot listed
Multi-platform app SDKsNot listedYes
On-device anonymizationNot listedYes
Cookieless signalsNot listedYes
EU-operated (DE GmbH)Not listedYes
Open-source client SDKsNot listedYes
Managed SaaS (no self-host)Not listedYes

etracker

  • Cookieless session analytics (consent-oriented default)

    Server-side session tokens link interactions without analytical cookies or device fingerprinting by default; IP truncation and daily-rotating hashes limit long-term recognition. Suits sites that want visit/conversion metrics under legitimate interest while keeping optional hybrid cookies behind consent.

  • Integrated tag and consent management

    One product surface to load etracker and third-party tags and sync them with consent rules, reducing dual maintenance between a separate CMP and GTM. Best when marketers need gated Maps/ads tags without rebuilding the full Google stack.

  • Server-side conversion sync to major ad platforms

    Upload conversions measured in etracker to Google Ads, Meta, TikTok, and Microsoft Ads so bid algorithms receive server-side signals. Customer-controlled outbound path—useful for paid media, but introduces destination-platform processing outside German housing.

  • E-commerce, UX scrollmaps, and multi-level drill-downs

    Shop funnels from product list to order (including vouchers and abandonment), scrollmaps projected on pages, and reports with multi-dimension drill-downs plus attribution model switching. Aimed at merchandising and growth teams, not just pageview counters.

  • First-party tracking domain and BI exports

    Optional own-subdomain tracking (including Let's Encrypt workflow docs) to reduce ad-blocker and ITP loss; connectors/API/SFTP-style raw data paths toward Looker Studio, Power BI, and warehouses. Ops teams still configure domains and data pipelines themselves.

TelemetryDeck

  • Multi-platform SDKs and HTTP signal ingest

    Official clients for Swift (Apple platforms including visionOS), Kotlin/Android, JavaScript, Flutter, React/React Native, Vue, and a one-line web snippet, with community Unity, Rust WASM, and Vapor clients. Any runtime can POST to the documented ingest API. Suits cross-platform product teams; not a drop-in replacement for a full marketing tag manager suite.

  • On-device salt-and-hash user anonymization

    Client SDKs salt and hash user identifiers on device; the server applies a second salt and hash so neither side can reverse the original ID. App analytics docs state IPs are never stored for signals; timestamps are rounded to the hour. Limit: publishers must not put personal data in custom metadata, or the anonymization model breaks for that payload.

  • Cookieless app and web tracking model

    No analytics cookies for product signals: apps keep a local anonymized identifier; web derives a hashed identifier from date, site, and partial IP context without storing full IPs. Aimed at leaner consent UX and simpler App Store privacy labels versus cookie-based trackers—still confirm legal posture for your jurisdiction and configuration.

  • Product dashboards, funnels, TQL, and notebooks

    Pre-built overview and AARRR-style customer journeys (acquisition, activation, retention, revenue), technical metrics (devices, versions, errors), visual funnel builder, Explore for raw signal types, TelemetryDeck Query Language for advanced insights, and Notebooks mixing live charts with markdown. Test mode separates IDE/dev traffic from production.

  • Volume-based SaaS with free tier and plan retention

    Commercial model is monthly event/signal volume with a free tier and paid plans that differ on included volume and how long data stays query-ready (cold storage may hold older data). Free accounts can stop ingesting when the budget is exhausted; paid plans warn and may auto-upgrade after sustained overage. Check current limits on the vendor dashboard—no self-host option.

Assurance & compliance: etracker vs TelemetryDeck
Assurance & complianceLogo: etrackeretrackerLogo: TelemetryDeckTelemetryDeck
Independent security / privacy audit
Vendor claimed

ePrivacyseal materials and vendor pages describe independent ePrivacy Consult audit of consent-free cookieless analytics posture; not a full public penetration-test report. Vendor also claims regular infrastructure pen tests.

Not found

Vendor claims no IP storage and open SDK code for inspection; no public third-party no-logs or security audit report found in this pass.

ISO 27001
Partial

IPHH housing described as ISO/IEC 27001:2013-certified. No public organisation-level ISO 27001 certificate for etracker/JustRelate analytics found in materials reviewed.

Not found

No public ISO 27001 certificate page located.

SOC 2 / SOC 3
Not found

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

Not found

No public SOC 2/3 report located.

GDPR / EU data protection
Vendor claimed

EU/DE controller-processor setup; cookieless default under legitimate interest; Art. 28 DPA on registration; privacy notice + objection patterns documented.

Vendor claimed

EU (German) controller entity; privacy policy and Privacy FAQ document anonymization, non-storage of IPs for signals, and EU hosting regions. Vendor asserts analytics signals are not personal data—validate with counsel for your config.

US CLOUD Act exposure (indicative)
Partial

EuropeanStack assessment: German entity, no known US parent, own-server housing at IPHH (no public AWS/GCP/Azure analytics store) → core exposure low. Partial because optional conversion sync and Google connectors can send data to US-group destinations when enabled by the customer. Not legal advice.

Partial

German GmbH, no known US parent, EU regions named—but public hosters include AWS and Microsoft (US groups) and HubSpot (US) for CRM. Indicative medium exposure. Not legal advice.

Data processing agreement (B2B)
Vendor claimed

Vendor states DPA/AV concludes on account registration; public DPA PDFs and in-app DPA under Settings → Data processing agreement.

Partial

Public DPA at telemetrydeck.com/dpa (German AVV prevails). Document asserts TelemetryDeck is not Art. 28 processor/joint controller because signals are anonymized; TOMs on request. Not a classic processor AVV—legal review required.

ePrivacyseal (privacy seal)
Vendor claimed

Vendor and ePrivacy listing materials assert seal for consent-free cookieless mode under GDPR/TDDDG. Scope is privacy/consent posture, not a general security cert.

Not listed
EU AI Act
Not applicable

Product is web/marketing analytics, not an AI-system offering as primary positioning.

Not applicable

Product analytics / telemetry; not marketed as an AI system core offering.

Considerations & known limitations: etracker vs TelemetryDeck
Considerations & known limitationsLogo: etrackeretrackerLogo: TelemetryDeckTelemetryDeck
Consent-free claims still need local legal review
Medium

ePrivacyseal and vendor guidance support cookieless default under TDDDG/GDPR, but hybrid cookies, marketing tags, and non-German supervisory interpretations can change the picture. Operators remain responsible for DPIA and notices.

Not listed
Optional conversion sync / BI connectors to US platforms
Medium

Core storage is claimed German; enabling Google/Meta/TikTok/Microsoft conversion upload or Looker Studio connectors creates additional processing at those destinations. Map each integration in your transfer assessment.

Not listed
Limited public enterprise security certs
Low

No public SOC 2 or org-level ISO 27001 package found; IPHH housing ISO and ePrivacyseal are the main published assurance artefacts. May slow enterprise security questionnaires.

Not listed
SaaS-only, closed source
Low

No self-host path. Exit requires export/API planning; multi-year usage contracts are common in this category—confirm terms on the vendor site.

Not listed
No exhaustive public subprocessor register
Low

Housing (IPHH) is named; a full live subprocessor schedule (support tooling, email, etc.) was not found as a single public table. Request under NDA/procurement if required.

Not listed
US-group cloud and CRM subprocessorsNot listed
Medium

Even with EU regions, AWS and Microsoft Azure are US-group providers; HubSpot processes customer CRM data in a US SaaS path. Buyers with strict no-US-cloud policies need written architecture confirmation or another vendor.

Anonymization / non-processor legal modelNot listed
Medium

Public DPA states TelemetryDeck is neither processor nor joint controller for service data. Strong if true for your configuration; risky if custom metadata reintroduces personal data or if counsel disagrees with the anonymization analysis.

No public ISO/SOC or independent auditNot listed
Medium

No ISO 27001, SOC 2, or independent no-logs audit found publicly. Enterprise security questionnaires may need NDA materials or alternate assurance.

Free-tier ingest hard-stopNot listed
Low

Free plans discard events after the included monthly budget; overage data is not recoverable. Production apps on free tier need monitoring or a paid plan.

No self-hosted productNot listed
Low

Only client SDKs are open source. Organizations that must keep analytics databases on-prem cannot use TelemetryDeck as a full stack.

Fit

etracker

Best fit when

  • EU/German organisations replacing GA4 to reduce consent-mode data loss and US-linked analytics storage
  • Performance marketers needing campaign attribution plus server-side conversion upload to major ad platforms
  • E-commerce teams measuring product-to-checkout funnels, vouchers, and abandonment in one privacy-oriented SaaS
  • Agencies managing multi-account portfolios that want integrated tag and consent management without a separate CMP licence stack
  • Publishers and regulated sectors that require a German processor, Art. 28 DPA, and documented objection mechanisms

Poor fit when

  • Teams that must self-host open-source analytics with full infrastructure control (Matomo, Offen, etc.)
  • Sites that only need minimal cookieless pageviews without shop, UX, or paid-media depth
  • Procurement that requires published SOC 2 or organisation-level ISO 27001 for the analytics vendor before shortlisting
  • Buyers expecting a durable free-forever tier comparable to Google Analytics

Consider instead when

  • When: You need open-source self-host or full data-plane control on your own infrastructure

    Consider: Matomo (self-host or Matomo by Stackhero / Friendly Analytics managed)

    etracker is closed-source SaaS only

  • When: You want a lightweight EU cookieless counter without marketing suites

    Consider: Plausible Analytics, Wide Angle Analytics, or digistats Analytics

    Simpler product surface; fewer e-commerce and ad-sync features

  • When: You stay fully inside Google Ads optimisation and accept consent/US-transfer tradeoffs

    Consider: Google Analytics 4

    Deeper Google ecosystem wiring; different privacy posture

TelemetryDeck

Best fit when

  • Mobile/desktop/web app teams that instrument events in code (Swift, Kotlin, Flutter, RN, JS) rather than only a website script
  • Product orgs prioritizing cookieless, double-hashed identifiers and leaner App Store privacy narratives versus ad-tech SDKs
  • Teams leaving Firebase Analytics or Mixpanel who accept a simpler event model for privacy-oriented defaults
  • European buyers wanting a German legal entity and EU-region hosting (Azure NL, AWS Frankfurt, Hetzner DE) with public privacy docs
  • Indie and small teams that want a free tier to start and volume-based paid plans as signal volume grows

Poor fit when

  • Organizations that must self-host the full analytics stack on their own infrastructure
  • Website-only traffic measurement without native app SDKs (Plausible/Pirsch are usually better fits)
  • Buyers that require public ISO 27001/SOC 2 certificates or a conventional Art. 28 processor DPA without the vendor’s anonymization legal model
  • Teams needing deep identity graphs, CRM-style user profiles, or full product-analytics marketing suites
  • Workloads that forbid US-group cloud providers entirely (AWS and Microsoft Azure are in the public host list)

Consider instead when

  • When: You only need privacy-friendly website analytics with a simple script

    Consider: Plausible Analytics or Pirsch Analytics

    Stronger web-first UX; weaker native multi-platform SDK story than TelemetryDeck

  • When: You must self-host analytics and own the database

    Consider: Matomo (self-host) or Plausible Community Edition

    TelemetryDeck is managed SaaS only

  • When: You need Firebase/Google ecosystem depth or free crash+remote-config adjacency

    Consider: Firebase Analytics (accept Google jurisdiction and tracking model)

    Different privacy and lock-in trade-offs

  • When: You need enterprise product analytics with rich identity and experimentation packaging

    Consider: Mixpanel or Amplitude

    Heavier privacy/cookie surface; more suite features

Open questions for due diligence

etracker

  • Will procurement receive a current subprocessor list covering support, email, and any non-IPHH infrastructure?
  • Does JustRelate publish an organisation-level ISO 27001 or SOC 2 report for the analytics service (beyond IPHH housing)?
  • For your jurisdictions outside Germany, does counsel accept the cookieless legitimate-interest posture without a consent banner?
  • Which optional outbound integrations (ads conversion upload, Looker Studio, third-party tags) will you enable, and how are those transfers documented?

TelemetryDeck

  • Will counsel accept the public non-processor DPA/AVV model for your app’s identifier and metadata configuration?
  • Can TelemetryDeck provide TOMs, subprocessor list for the analytics plane, and any ISO/SOC or pen-test reports under NDA?
  • Which exact AWS/Azure services and accounts process customer organization data versus anonymized signals?
  • What contractual options exist to exclude or pin HubSpot and other US SaaS tools for account administration?
  • Current free-tier and paid plan event limits and retention windows for your expected volume (confirm on live plans UI)?