What is AnalyticsTrend

Product analytics for browser extensions and for websites. It answers what people actually do in your product, and how many of them come back, without collecting anything about who they are. There is one SDK for each surface and they report into the same dashboard, so an extension and the site that sells it can sit in one account.

Why not a general analytics tool

Two reasons, and the first one only applies to extensions. A conventional analytics snippet loads more JavaScript from the vendor's servers at runtime, which is remote code execution. Chrome's Manifest V3 disallows it outright, and Mozilla's add-on reviewers reject it manually. An extension shipping one is not merely slower to approve; it is rejected, and the reason is often reported in terms that do not name the cause.

This SDK is a package you bundle. Nothing is fetched at runtime.

The second reason applies to both. General analytics tools identify people — with a cookie, a device fingerprint, or both — which is what obliges a website to put up a consent banner and what makes an extension's privacy disclosure something reviewers read twice. Nothing here identifies anyone, so neither problem arises.

What it collects

• A random identifier generated on first run and kept in your extension's own storage. It is not derived from anything about the device or the person, and it is scoped to your extension alone, so it cannot be joined to any other extension or site.
• The event names you choose to send, with whatever properties you attach.
• A country, resolved from the request's IP address, after which the address is discarded rather than stored.

No cookies. No fingerprinting. No personal data unless you put it in an event property yourself, which the naming guide asks you not to do.

What it costs

Nothing during the beta. There is no billing, no card, and no trial clock. Access is by invite code.

Where the data lives

Canada, on infrastructure we run. See self-hosting if that is not close enough for your customers.