Trikzik Labs / Plain-language record

Privacy

Trikzik Labs uses a small, first-party counter to understand which experiments get opened and used. It is designed to count actions, not identify people.

What the public counter records

When collection is enabled, an allowed action increments an aggregate count in a five-minute time bucket. The stored fields are the event category, experiment identifier, fixed source category, fixed export format when relevant, site context, and code-release label.

The allowed categories are: selecting a specimen, opening an experiment, the first interaction with an experiment, exporting Scribble artwork or setup, creating a Scribble replay link, and opening the support link.

What it does not record

• No analytics cookies, persistent visitor identifiers, session identifiers, names, email addresses, or account IDs.
• No raw page URLs, URL queries, replay-link payloads, referrers, free-form text, keystroke content, slider values, pointer trails, animation frames, or artwork.
• No IP address is written to the Trikzik analytics database. Cloudflare may process ordinary connection information to deliver and protect the site under its own terms.

Retention and access

Public events are stored only as aggregate counts. Dashboard queries are limited to the most recent 90 days, and database cleanup removes older event buckets when new events are written. The private dashboard is restricted to Ernest Turner’s exact verified Firebase account.

The owner sign-in is separate from public analytics. Google and Firebase may process the owner’s authentication information; public visitors are not asked to sign in.

Operational limits

The collector accepts only exact allowlisted values, rejects oversized or cross-site requests, and applies a global write budget. If configuration, quota, or network requests fail, the games continue working and the event is simply not counted.

Effective for the prepared analytics-v2 release · October 2026