Privacy Policy

Data collection

Snapxel captures screenshots and recordings locally on the device. Step metadata is stored locally so the current guide can be edited and exported. Typed values are excluded by default and are included only when a user explicitly enables that behavior in privacy settings.

• Screenshots and recordings are processed locally.
• Typed text is off by default in step metadata.
• No names, email addresses, or browsing history are collected as part of the capture flow.
• Snapxel does not use cookies or browser tracking for the public site or the extension workflow.

Anonymous analytics

Snapxel collects limited anonymous usage data to improve the product. This data is sent to PostHog and can be disabled by the user at any time in the extension settings. Snapxel sends only explicit product events; it does not use PostHog autocapture or session replay.

• Feature usage events such as recording started or export completed.
• Counts and durations such as number of steps or recording length.
• Extension version information.
• A random anonymous identifier that is not linked to personal identity.

Analytics do not include page content, screenshot media, video media, typed text, page titles, hostnames, or URLs visited by the user. Analytics properties are filtered before they leave the browser so URL-like values, email-like values, identifiers, raw text, labels, selectors, and similar fields are dropped.

How Snapxel works

When the user starts a recording, Snapxel watches the visible tab for actions such as clicks, input steps, and shortcuts. The extension captures screenshots, stores the working session locally, and lets the user export the guide in the format they choose.

• Guide media is stored locally during the session.
• Preferences and working metadata use Chrome storage and IndexedDB.
• Exports are written directly to the user’s machine.
• Starting a new session or clearing browser data removes local session state.

Permissions explained

• activeTab: capture the visible tab when a step occurs.
• scripting: detect events and draw indicators on the active page.
• downloads: save exports such as GIF, PDF, images, and video.
• storage: persist user settings and local guide metadata.
• <all_urls>: allow user-initiated workflow capture on the website the user chooses to document. Snapxel supports arbitrary browser workflows, so the permission is broad instead of tied to a fixed domain list. The content script is active for interaction detection only while recording is running.

Data storage and security

Snapxel relies on local browser storage for the current product. The safety of captured content therefore depends on the security of the device it runs on.

• Use device encryption when possible.
• Review screenshots before sharing exported guides.
• Disable analytics if the environment requires a stricter privacy posture.

Third-party services

Snapxel uses PostHog for anonymous analytics only. Screenshot content, recording media, page URLs, hostnames, page titles, typed values, and browsing history are not sent to PostHog or another third-party service as part of the extension workflow.

Limited Use disclosure

Snapxel’s use of information received from Google APIs adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements.

Children’s privacy

Snapxel does not knowingly collect personal information from children under the age of 13. The product is intended for general audiences and does not require account creation for its core local-first workflow.

Changes and contact

If this policy changes, Snapxel will update the revision date on this page and communicate significant changes through the product or public release materials.

Questions about privacy can be sent to support@snapxel.com.