What we measure

Who is responsible

Antikatoptis Pareidolia S.R.L., Romania, is the controller for this product telemetry. You can contact the controller through the public ATKP contact form linked below.

What is measured

The product records a small allowlisted set of first-party events so we can understand whether the dashboard works and whether readers reach useful energy information.

• Page views and dashboard actions: country or pair focus, ticker pause/resume, archive use, card sharing and deep-link entry.
• Technical context: page path, language, timestamp, coarse country, coarse device class, referring hostname and allowlisted campaign parameters. Full referring URLs are not stored.
• Core Web Vitals: LCP, INP and CLS. Available values are rounded and batched into at most one compact event per page lifecycle.
• Operational browser errors are sent separately to the ATKP error service with release and technical error context. Session replay is not enabled.

Short-lived pseudonymous signals

A random journey ID exists only in JavaScript memory for the current tab/runtime. The server transiently processes the request IP address and user agent to derive coarse country, a daily HMAC signal and a separately keyed weekly HMAC signal. Raw IP addresses and full user agents are not written to the analytics tables, event metadata, rollups or Command Center logs.

These signals are pseudonymous, not anonymous. They estimate devices or network contexts—not people. Shared networks can merge different readers, while network or browser changes can split one reader, so the estimate can be wrong in both directions.

Purpose and legal basis

The purposes are to operate and improve the product, identify reliability and usability problems, understand aggregate demand for dashboard features and evaluate aggregate acquisition sources. Telemetry is not used for advertising, third-party profiling, credit decisions or individual targeting.

The documented candidate legal basis is the controller’s legitimate interest under GDPR Article 6(1)(f), after a necessity and balancing assessment. That assessment is recorded in the repository LIA and must be reviewed if the purpose, scale, vendors or identifiers change. Applicability of Romanian Law 506/2004 and ePrivacy rules is assessed against the concrete implementation; this notice does not claim a blanket exemption.

Retention and aggregation

Daily and weekly aggregate rollups are computed inside the database. The Command Center and pump services can read those bounded rollups but are explicitly denied the raw event table.

• Journey IDs and daily signals are removed after the daily rollup plus an approximately seven-day recovery buffer.
• Weekly signals are removed and their random weekly key is destroyed after the weekly rollup plus its recovery buffer.
• Remaining non-identifying raw event facts are pruned after 90 days.
• Aggregate daily and weekly rollups may be retained indefinitely because the short-lived identifiers have been removed.
• Browser error diagnostics are retained under ATKP’s central operational policy only while needed to diagnose or prevent recurring errors; they are not part of the indefinite analytics rollups.

Infrastructure and transfers

Vercel handles delivery and the first-party event endpoint; Supabase stores the private analytics data in its EU West project region; ATKP’s GlitchTip service receives bounded browser error diagnostics. These providers are used to deliver, secure and operate the product—not to build advertising profiles.

Some delivery processing may occur outside the EEA. Where an international transfer requires safeguards, the relevant provider terms incorporate the European Commission’s Standard Contractual Clauses. Links to the current provider DPAs are below.

Your choices and rights

When the browser sends Do Not Track (DNT=1) or Global Privacy Control, first-party analytics and browser error reporting remain silent; the Core Web Vitals module is not loaded. There is no analytics cookie, localStorage/IndexedDB analytics identifier, persistent visitor ID, cross-site tracking or fingerprinting script.

You may ask for access, correction, erasure or restriction, and you may object to processing based on your particular situation. Because the service deliberately has no account or persistent identifier and destroys rotating keys, we may be unable to link a request to a past pseudonymous row after the relevant key is destroyed. We will not request more information than reasonably necessary to handle a rights request.

You may also complain to the Romanian supervisory authority, ANSPDCP, or another competent supervisory authority. No automated decision with legal or similarly significant effect is made from this telemetry.