ClickTrek
Privacy Policy
Last updated: May 14, 2026
ClickTrek has a local extension flow and an optional hosted Pro checkout and activation
flow. This policy covers both.
Local extension data
- screenshots captured for the current export
- page content visible in the captured image
- click coordinates, step labels, and redaction rectangles
- the generated PNG export
These workflow and screenshot materials stay local to the browser extension. ClickTrek does not upload them to the hosted payment and licensing backend.
Paid flow data
If you use ClickTrek Pro, ClickTrek and its providers may process:
- checkout nonce and activation code
- device identifier used for entitlement checks
- transaction reference, customer identifier, and entitlement status
- basic request metadata needed for security and service operation
Why we process data
- to deliver a one-time ClickTrek Pro activation code after payment
- to activate Pro and refresh entitlement tokens
- to enforce the 3-device active-seat limit
- to release a server-tracked device slot when you deactivate Pro on a device
Service providers
- Cloudflare for hosted pages, API execution, and D1 database storage
- Stripe for secure checkout and payment processing
What ClickTrek does not do
- it does not send screenshots, page content, click data, labels, or redaction regions to Cloudflare or Stripe
- it does not require an account login
- it does not add analytics or advertising trackers in the extension
Retention and security
Local workflow data remains on your device until you close the flow, export, clear browser data, or remove the extension. Hosted checkout and entitlement records may be retained for security, legal compliance, activation recovery, device-seat enforcement, and support. Keep activation codes private.
Contact
For privacy, billing, support, or legal notices, contact pbinder.supp@gmail.com.