Custom Maps Studio
Studio Privacy Choices
Studio privacy · Version 1.6Your advertising choices
Meta Advertising measures visits, product interest and selected Studio actions. It is on by default for U.S. visits unless you opt out. Other locations, or an unavailable region check, require your choice first. The hosting provider supplies country information for this check; the check stores no identifier or location. A default is never saved as your consent.
Use Privacy choices in the header or footer to turn Advertising on or off. Saved refusals, Global Privacy Control and Do Not Track remain honored. Choices last up to 30 days in pp_advertising_consent_v2; earlier refusals in pp_meta_consent_v1 remain effective until you deliberately change them. We do not send custom design text, exact locations or private design links in Meta events.
First-party Studio Analytics remains off. Necessary design, saved-project, security, production and checkout functions work with advertising off. A prepared Studio handoff is not reported as a purchase.
Optional Microsoft Clarity session analytics
Microsoft Clarity helps us understand how people use the public Studio through session replay and interaction heatmaps. Clarity is on by default for verified U.S. visits unless you opt out. Other visits, including visits whose country cannot be verified, require your choice first. Clarity has its own setting in Privacy choices. Its input masking applies, and the visible map and design preview can appear in recordings.
Clarity runs on the public Studio page. This installation excludes sign-in, sign-out and Squarespace checkout. Turn it off any time in Privacy choices. The Studio honors Global Privacy Control and Do Not Track for Clarity. See the Microsoft Privacy Statement for Microsoft's data practices.
Main store and checkout limitation
These controls apply to this Studio. The main store and Squarespace checkout have separate controls. Use Cookie Preferences on the main store for its controls. Squarespace's native checkout integration and existing server event connection have not yet been verified to honor all regional choices, withdrawals and Global Privacy Control. Studio controls cannot guarantee that those separate systems stop contacting Meta.
A Studio tab opened before this update may still run the previous marketing code until it is reloaded. Reload open Studio tabs to use these restrictions. This does not erase data already sent to other services. Read Meta's privacy policy and cookie policy for Meta's processing and retention practices.
Previously collected first-party analytics
Before the pause, Precision Peaks measured 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 could be derived transiently by the hosting edge; an IP address was not stored or hashed by the analytics application.
What first-party analytics never collects
First-party analytics does not collect IP addresses, exact coordinates, searches, selected place names, titles or labels, uploaded GPX/KML files, route or map 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 a design. Those operational workflows are distinct from analytics and are not copied into the analytics database.
Identifiers, controls, and location
Before the pause, a random identifier existed only in memory and rotated after inactivity to estimate sessions, not people. No cross-day new/returning measurement is active. Global Privacy Control and Do Not Track stop collection. Region and city results are hidden whenever a filtered cohort has fewer than five estimated sessions.
Retention and owner access
Detailed sanitized events default to 90 days and daily aggregates to 24 months. The owner can shorten retention and delete analytics data. Synthetic verification is excluded from reports and targeted for deletion after 24 hours at the next maintenance run. The private console exposes aggregate results only.
Policy review
This data dictionary 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 it as final policy language.
Questions: info@precisionpeaks.com