Privacy policy
Draft pending legal review. It is not in force yet.
Who this covers
PageFriction measures landing pages for the agencies and professionals who install it. For the visitors of those pages, the site that installed the tag decides why data is collected, and PageFriction processes it on that site’s behalf. For accounts on PageFriction itself, PageFriction decides.
What the tag records
Page path, which sections were seen and for how long, clicks tied to a section, that a form was started, sent or left, load time, page errors, and classes of browser, device, time zone and connection. Campaign parameters and click identifiers in the URL are kept, because they say which ad brought the visit.
What it never records
What anyone types into a form. The name of the form field is off by default. Exact device fingerprints and any identifier across different sites. IP addresses: a salted hash is used for a few minutes to limit abuse, and the address itself is not stored.
Consent
The tag sends and stores nothing until the site signals consent. Refusing clears the identifiers it created.
Page analysis
When someone asks for a URL analysis, our server opens that public page, takes images of its sections and sends computed facts about the page to an AI model hosted by Cloudflare. Without an account, the result and the images are deleted after 30 days.
Retention
Raw events are deleted after 12 months. Daily totals stay while the account exists, and they hold no identifier of a person.
Accounts
Name, email, password in hashed form, and the organizations you belong to. Payments are handled by Stripe, and card numbers never reach us.
Where it runs
Everything runs on Cloudflare, and payments on Stripe.
Your rights
A visitor can ask the site they visited, which is responsible for that data. An account holder can ask for access, correction or deletion through the contact on this site.