SABERISTIC

SABERISTIC / PRIVACY AND ANALYTICS

Measure the product, not the person.

Saberistic uses a self-hosted Umami installation to understand whether the site is useful. The tracker is cookie-free, honors your browser's Do Not Track setting, and is limited to a small set of public pages and explicitly named interactions.

01 / THE SERVICE

Self-hosted analytics

Analytics is served from umami.saberistic.com and applies only on saberistic.com and www.saberistic.com. It is operated with the Saberistic application rather than used for advertising or cross-site tracking. Saberistic does not call Umami's visitor-identification function and does not enable session replay.

02 / WHAT IS MEASURED

A narrow product signal

A pageview can include the approved hostname, the public page path, the page title, an external referrer reduced to its origin, approximate browser, device, country and session information derived by Umami, and standard web-performance measurements. Query strings and URL fragments are removed before collection.

  1. Clicks on the primary readiness, prototype, and architecture-diagnostic calls to action.

  2. Visits to the three service sections on the homepage.

  3. Starting one of the fixed readiness-preview examples.

  4. Opening a prototype card or detail page, launching an approved prototype, or following its source link.

03 / WHAT IS EXCLUDED

Content stays out of analytics

Event fields are checked against a small, versioned allowlist before they are sent. The following information is deliberately excluded:

  • Names, email addresses, companies, phone numbers, contact-form content, or other contact details.
  • Readiness answers, free text, prompts, generated explanations, results, or report identifiers.
  • Source code, credentials, logs, repository identifiers, internal service identifiers, or customer data.
  • URL query strings, URL fragments, full referrer paths, search terms, or filter text.

04 / YOUR CHOICE

The site works without analytics

You can enable Do Not Track in your browser or block requests to umami.saberistic.com. Either choice prevents or limits collection and does not change the site's content, readiness preview, or prototype links. Analytics failure also never blocks those features.

05 / RETENTION AND CURRENT LIMITS

Temporary launch infrastructure

During this launch-validation phase, analytics and website content use separate database roles and schemas on one shared Render Free PostgreSQL instance. Analytics remains there until it is manually deleted or that temporary database is replaced or expires. The current database is scheduled to expire on September 27, 2026 and has no backup or automatic time-based deletion policy. This means the data is disposable, not a durable business or audit record.

The public collection endpoint can receive fabricated events, so dashboard numbers are treated as directional product signals only. A dedicated database, documented retention procedure, and tested backup and restore process are still required before this is treated as production-grade analytics.

06 / CHANGES

This notice follows the implementation

This page will be updated if the collected fields, event allowlist, retention process, or analytics infrastructure changes. Last updated August 30, 2026.