Skip to content

Frequently asked questions

Get verified answers about Supermetry privacy, requirements, upgrades, storage, licensing and operations.

Use these answers to resolve common questions before installing or operating Supermetry.

  1. Find your question below, then follow the linked guide when you need a procedure.

No. Pageview and custom-event tracking is cookie-free. The dashboard uses secure authentication cookies for signed-in users; those cookies are not used to track website visitors.

No. It uses the client address during ingestion for location and a daily visitor ID, then discards the raw address. API responses do not expose IP addresses, user agents or visitor IDs.

No. Visitor IDs use a random daily salt, and old salts are deleted after about 48 hours. The ID is scoped to a site and local day rather than being a durable cross-day identity.

Yes. Sec-GPC: 1 and DNT: 1 stop event and heatmap submissions. The browser tracker also honors consent denial or withdrawal and the visitor opt-out API.

What does a self-hosted installation require?

Section titled “What does a self-hosted installation require?”

Use Linux, macOS or Windows on AMD64 or ARM64. Docker mode needs Docker Compose. Binary mode needs a reachable PostgreSQL database; the server itself is a single Go binary.

Do I need Redis, ClickHouse or Node.js in production?

Section titled “Do I need Redis, ClickHouse or Node.js in production?”

No. Supermetry uses PostgreSQL and does not require Redis or ClickHouse. The production server does not require Node.js.

Run supermetry. It reads ./.env unless SUPERMETRY_ENV_FILE selects another file. Process environment values take precedence.

What is the minimum account password length?

Section titled “What is the minimum account password length?”

Passwords must contain at least 6 characters.

Run the installer again. It keeps the existing configuration and secret key, replaces the binary or image, restarts the service, and applies database migrations at startup.

Analytics and account data are stored in your configured PostgreSQL database. Replay files use the configured local replay directory or S3-compatible storage; downloaded GeoIP data uses SUPERMETRY_DATA_DIR.

Supermetry Cloud is hosted in the EU. Self-hosted data stays in the PostgreSQL and replay storage that you configure.

The core project is licensed under Apache License 2.0.

supermetry backup includes a PostgreSQL dump and manifest. It excludes SUPERMETRY_SECRET_KEY, GeoIP databases and replay files, so back those up separately.

  1. If an operational problem remains, use the troubleshooting guide and include the exact command or startup error.

What you should see: a verified answer above or a linked guide for the next task.