Analytics Privacy & Data Dictionary

What the analytics system collects

Precision Peaks measures short-lived estimated sessions, broad device/browser/operating-system families, viewport ranges, coarse traffic categories, Studio release, funnel steps, safe product-option categories, performance timings, and fixed sanitized error codes. Approximate city, region, and country may be derived transiently by the hosting edge; an IP address is not stored or hashed by the analytics application.

What analytics never collects

Analytics does not collect IP addresses, exact coordinates, searches, selected place names, plaque wording, uploaded files or tracks, route geometry, Design IDs, order links, customer details, form contents, keystrokes, screenshots, recordings, fingerprints, full URLs, error messages, or stack traces.

The Studio may separately use information you intentionally enter to preview, save, manufacture, or fulfill your design. Those operational workflows are distinct from analytics and are not copied into the analytics database.

Saved projects and account sync

Without signing in, saved projects remain in that browser. When you choose Sign in with ChatGPT, the Studio stores projects under the account identifier supplied by the hosting platform so they can be opened across devices. A saved project can include its name, selected place, exact carving footprint, map and terrain settings, plaque wording, notes, named landmark metadata, a small rendered preview, version information, and created/updated timestamps.

Saved-project data is operational data, not analytics. It is used to restore and search your designs. Active projects can be moved to an archive and restored later; permanently deleting an archived project removes its project record and preview. Manufacturing exports and order files remain in their separate production workflow and are not embedded in the ordinary project record. A minimal deletion marker containing the account identifier, project identifier, and deletion time is retained so an old browser copy cannot silently recreate a permanently deleted project.

Identifiers, choices, and location safeguards

A random identifier exists only in memory, rotates after inactivity, and is transformed into a day-specific server value. It is used to estimate sessions, not identify a person. No cross-day new/returning measurement is active. Global Privacy Control and Do Not Track stop collection. City and region breakdowns are hidden whenever the selected cohort has fewer than five estimated sessions.

Retention and access

The default is 90 days for detailed sanitized events and 24 months for daily aggregate statistics. The owner can shorten retention and delete analytics data. Synthetic verification events are excluded from owner reports and targeted for deletion after 24 hours at the next maintenance run. The private owner console exposes aggregate results only.

Policy review

This page describes the implemented analytics boundary; it is not a guarantee of legal compliance. Precision Peaks should have counsel review lawful basis/consent language, city-level geolocation, processor and backup disclosures, cross-border processing, data-rights wording, and children's privacy before treating this as final policy language.

Questions: info@precisionpeaks.com