Ackee is a self-hosted, privacy-oriented analytics service. It records domain traffic through a tracking script, stores anonymized event data in MongoDB, and exposes a GraphQL API and a dashboard. Its design intentionally avoids cookies and unique user tracking. That privacy property changes what an exposed dashboard means.

The project describes Ackee as a two-part application with a tracking endpoint and an administrative interface. Permanent tokens authenticate API requests. A deployment can use a reverse proxy, create domains, and build custom dashboards. A public analytics page may be intentional; an exposed token or administrator session is not.

What the measurement shows

On 2026-11-21 between 06:47 and 06:49 CST, a bounded SDK query used sub_type=all, page 1, and page size 1. title="Ackee" returned 545 index matches. The exact app="Ackee" query returned 0. The title is also an ordinary word with several unrelated meanings, so the 545 count should be treated as a broad lead, not an Ackee population.

The query can be inspected through the ZoomEye search link.

Separate tracking from administration

The tracking endpoint receives events from public websites. The dashboard reads aggregates and may expose page paths, referrers, countries, and event names. The GraphQL API can create permanent tokens and access domain data. Review each route on its own: a public tracker does not imply a public administrator console.

A permanent token should be owned by a named integration, stored outside the web root, and rotated when the integration changes. Test a read-only token against the queries it needs, then try a data mutation that should fail. Do not use one administrator token for every dashboard, status bar, and report.

Review the public dashboard as data disclosure

Open the dashboard as a logged-out visitor and record every visible field. URL paths can contain customer names, account identifiers, or internal product names. Referrer data can reveal partner relationships. Event names can expose business processes even when no individual user is identified.

Ackee's anonymization reduces the privacy impact of the collected events, but it does not make the aggregate data non-sensitive. Apply retention limits, restrict the dashboard to the intended audience, and remove stale domains. If the dashboard is embedded, verify the frame policy and the origin that receives the iframe.

Test the deployment

Create a test domain and send a controlled event. Confirm that the tracker accepts the event and that the dashboard shows only the expected aggregate. Revoke the API token and test a GraphQL query. Remove the domain and confirm that its public routes stop serving data.

For a discovered title, identify the owner without attempting a login or querying GraphQL. Ackee is useful because it makes privacy-preserving traffic reporting practical. The review should keep that privacy promise intact while protecting the administrative path that controls the data.

References