Logo: Insights

Insights

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).

Open source

Insights is a hosted, privacy-oriented web analytics product from Unsourced Digital OG in Austria. Founders Anthony and Henrique built it for site and web-app owners who want page statistics and custom events without cookies or stored visitor IPs.

It exists as a lightweight alternative when other privacy analytics tools felt too limited for app-style event work. You add a small script or the insights-js npm package, then auto-track pages or emit named custom events.

The concrete differentiator is that MIT open-source JavaScript client. The hosted backend uses Google Firebase, which matters if you need an all-EU data path for analytics storage.

Cookie-free trackingCustom eventsMIT client (insights-js)Austrian entityHosted SaaSFirebase data path

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).

Key capabilities

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.

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.

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.

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.

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.

At a glance

HQ / law
Austria (Unsourced Digital OG; Austrian governing law)
Product type
Hosted privacy web analytics + custom events
Client license
MIT (insights-js); backend proprietary
Self-host
No public self-host option
Commercial model
Free low-volume tier; paid by monthly event/pageview volume
Known infra
Google Firebase (Functions, Auth, Hosting) per vendor docs

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.

Jurisdiction & ownership

Legal entity
Unsourced Digital OG
US parent / control
No known US parent
CLOUD Act exposure (indicative)
Medium
Hosting / residency
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.

No known US parent of Unsourced Digital OG. CLOUD Act exposure is indicative medium because of Firebase/Google subprocessors, not because of HQ alone. Not legal advice—confirm current regions and contracts with the vendor.

  • Independent security / no-logs auditNot found
  • ISO 27001Not found
  • SOC 2 / SOC 3Not found
  • GDPR / EU data protectionVendor claimed
  • +3

Considerations & known limitations

  • HighGoogle Firebase on critical path

    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.

  • MediumNo public independent audit or certs

    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.

  • MediumClient open source only; no self-host

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

  • MediumSmall team / continuity

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

  • LowBounce/unique metrics need SPA routing

    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.

Open questions for due diligence

  • 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?

Frequently Asked Questions

For many indie and SMB apps, yes for page views plus custom events (clicks, plan choice, scroll, cancelable subscriptions) without cookies. It will not match GA's full free segmentation, advertising integrations, or BigQuery export ecosystem. Evaluate whether named aggregate events are enough for your product questions.

Unsourced Digital OG is an Austrian operator under Austrian law. The vendor's own data page states the product uses Google Firebase (Cloud Functions, Authentication for customer accounts, Hosting). Even with visitor metrics designed to avoid stored IPs and cookies, Google-group infrastructure is on the path—treat US CLOUD Act exposure as indicative medium, not low, and confirm current regions with the vendor.

Only the JavaScript client is open source (MIT on GitHub). The hosted dashboard and backend are not published for self-hosting. If you need full stack control or air-gapped analytics, choose self-hosted Matomo/Umami-class tools instead.

Official client docs state trackPages() does not use cookies or localStorage and expects a client-side router. Bounce rate and unique views will not be accurate on classic multi-page full reloads; docs recommend disabling that behaviour when appropriate. Design around session-in-memory SPA routing expectations.

At research time the public site documents privacy practices and Firebase data categories but did not publish a standalone B2B DPA, ISO 27001 certificate, SOC 2 report, or third-party no-logs audit. Contact contact@getinsights.io for enterprise paperwork before treating it as procurement-ready.