Privacy Policy

Cookieless analytics

This website sends aggregate page-view events through its Vercel-hosted endpoint to PostHog EU Cloud. When someone selects a Chrome Web Store or Firefox Add-ons link, it also sends oneextension_cta_clickevent before opening the store.

Page-view events can include the page path and title, the referring site, and general browser or device properties. Query strings and URL fragments are removed before a page-view event is sent. The store-intent event contains only the product, destination store, link placement, page kind, and a controlled content slug, plus the minimum cookieless session and SDK fields needed for delivery and aggregate measurement.

The optional Screenshot Capture Studio post-uninstall page is excluded from website page-view analytics. Its voluntary Tally form does not send a landing, submission, or free-text event to PostHog, so it is not an uninstall metric.

No persistent analytics identifier

PostHog is configured in always-on cookieless mode. It does not store PostHog cookies or analytics identifiers in browser local storage or session storage. PostHog uses a privacy-preserving server-side hash for aggregate visitor measurement instead of a persistent browser identifier. A random in-memory session ID joins page views to a store-intent event only while the current page session is open; it is not persisted in the browser.

Analytics exclusions

This website does not identify analytics visitors, create identified person profiles, record sessions, capture JavaScript exceptions, or use PostHog autocapture. The store-intent event excludes inspected extension data, destination and page URLs, paths, referrers, query strings, campaign/search values, element metadata, page titles, pasted content, form values, and other free text. Checkout and embedded form providers process information submitted directly to their own interfaces under their respective privacy terms.

Contact

For questions about this website privacy policy, emailgevorg@glechyan.com.