Privacy Policy
The short version: PageLens is a website analytics service. We don't use cookies on the websites we measure, we don't store visitors' IP addresses, and we never sell data or use it for advertising. For the people who sign up to use PageLens, we keep only what we need to run your account.
This policy explains what information PageLens ("PageLens", "we", "us") collects, why, and what choices you have. It covers two groups of people:
- Customers — people who create a PageLens account and use the dashboard at
app.pagelens.io. - Visitors — people who browse a website that has installed the PageLens tracking script.
1. Visitors of websites that use PageLens
When a website owner adds the PageLens script, we process limited, non-identifying information about visits on their behalf. For this data the website owner is the controller and PageLens acts as a processor.
What we collect
| Data | Purpose | Stored? |
|---|---|---|
| Page URL path, page title, hostname | Which pages are viewed | Yes |
| Referring website and UTM campaign parameters | Where traffic comes from | Yes |
| Browser, operating system and device type (derived from the user agent) | Device statistics | Yes, as categories only |
| Country, city and the city's approximate coordinates (derived from the IP address, rounded to about 10 km) | Location statistics and the live globe | Yes, at city level only |
| Screen size and browser language | Device and language statistics | Yes |
| Custom events sent by the website (e.g. "signup") | Goals and funnels | Yes |
| JavaScript error messages and Web Vitals timings | Site health reports | Yes |
| IP address | Location lookup and daily visitor hash | No — discarded after processing |
| Full user agent string | Device lookup and daily visitor hash | No |
How visitors are counted without cookies
PageLens does not set cookies or use local storage, fingerprinting or any other identifier stored on the visitor's device. To count unique visitors, we combine the IP address, user agent, website ID and a random salt into a one-way hash. The salt is replaced every 24 hours and the old one is deleted, so the same person cannot be recognised from one day to the next or across different websites. The IP address itself is never written to our database.
Optional features a website owner can turn on
- User identification. A website may call
pagelens.identify()to attach its own user ID (and optional attributes such as a name, email address or plan) to visits made while a person is signed in to that website. This data is supplied by the website owner, who is responsible for having a legal basis for it. It is used only to show that website's owner per-user activity and retention, and is deleted with the website or on the owner's request. - Autocapture. If enabled, the script records clicks on buttons (by their visible label), form submissions (by the form's name) and copy actions (by the kind of content and its length). Values typed into forms and the copied text itself are never sent.
- Session replay. If enabled, the script records changes to the page (layout, clicks, scrolling and navigation) so the website owner can play the visit back. The contents of all form fields are always masked in the visitor's browser before anything is sent, and owners can mask all text or hide elements entirely. Recordings are automatically deleted after 30 days.
What we don't do
- We don't track visitors across websites. Unless a website owner uses user identification, we don't build profiles of individual visitors.
- We don't sell, rent or share visitor data with advertisers or data brokers.
- We don't collect form contents. Names or email addresses are only stored when a website owner deliberately sends them through user identification.
Requests from known bots and crawlers are kept out of visitor statistics. For them we store only the bot's name and category, the page requested, the country and the time.
2. PageLens customers
Account information
- Email and password sign-up: your name, email address and a securely hashed password (we never store your password in plain text).
- Sign in with Google or GitHub: your name, email address and profile picture as provided by that service. We request only basic profile and email access and do not access any other data in your Google or GitHub account.
- Sessions: when you sign in we store a session record with your IP address and browser user agent to keep you signed in and to help detect suspicious activity.
- Your configuration: the websites you add, goals, funnels, and the email addresses of teammates you invite.
- Billing: if you subscribe to a paid plan, payment is handled by Paddle (see below). We receive and store only your subscription status, plan, billing period and Paddle customer and subscription IDs — never your card details.
How we use it
We use account information only to provide and secure the service: to sign you in, show you your dashboards, let you collaborate with teammates, and contact you about your account or important changes to PageLens. We don't use your data for advertising.
The PageLens website
Our own marketing site, pagelens.io, is measured with PageLens itself, under the same cookieless approach described above.
If you arrive at PageLens from one of our own ads, the ad's click identifier (for example gclid) is passed in the sign-up link and stored with your new account, so we can report sign-ups back to the ad platform. We don't use cookies for this.
The PageLens Analytics app for Shopify
When a merchant installs our Shopify app, we store the store's myshopify.com domain and the PageLens site it's linked to. We don't store Shopify access tokens: each time the merchant saves settings, a short-lived token is used to set up the app's theme embed and web pixel, then discarded. The app doesn't read or store customers, products or orders from the Shopify Admin.
On the storefront, the app loads the same cookieless tracker described in section 1. From checkout pages, the app's web pixel sends two events: that a checkout started, and that it was completed, with the order total, currency, number of items and Shopify's order ID. No names, email addresses, addresses or payment details are sent. The pixel runs only when the store's customer privacy settings allow analytics. When the app is uninstalled we mark the store as disconnected, and we delete the store's record when Shopify asks us to (the shop/redact webhook). Because we hold no personal data about a store's customers, customer data requests and redaction requests from Shopify have nothing to return or delete.
Free AI crawler check by email
If you ask for the report of our free AI crawler check by email, we store your email address and the domain you checked. We use them to send you that report, to re-check the domain once a week and write to you only if AI assistants can no longer reach it, and the founder may write to you personally about the result. Every email has a link that stops them; you can also write to us to have the address deleted.
3. Service providers
We rely on a small number of providers to run PageLens:
- Railway — application hosting and database. Our servers and database run in Railway's EU region in Amsterdam, the Netherlands, so analytics data and account data are stored in the EU.
- Paddle — our reseller and Merchant of Record for paid plans. Paddle processes your payment details, billing address and tax information under its own privacy policy.
- Cloudflare — domain name (DNS) services and forwarding of email sent to our
@pagelens.ioaddresses. - Google and GitHub — optional sign-in, only if you choose to use them.
- Resend — delivery of account and product emails (sign-up confirmation, password reset, trial notices); it receives your email address and the message content.
- DuckDuckGo icon service — used by the dashboard to display small favicons of referring websites.
Location data is derived using a GeoLite2 database by MaxMind that runs on our own servers; IP addresses are not sent to MaxMind.
4. Data retention
Analytics data is kept for as long as the website remains in a customer's account. When a customer deletes a website, all of its analytics data is permanently deleted. Account information is kept until the account is deleted. Expired sign-in sessions are removed automatically. Session replay recordings are deleted 30 days after they are made.
5. Your rights
Depending on where you live (for example under the GDPR or CCPA), you may have the right to access, correct, export or delete your personal data, and to object to or restrict certain processing. Customers can delete websites directly in the dashboard. To exercise any other right, or to delete your account, email us at the address below and we will respond within 30 days.
Because we don't store IP addresses or persistent identifiers for website visitors, we usually cannot link analytics data to a specific person. Visitors with questions about a particular website should contact that website's owner.
6. Security
All traffic to PageLens is encrypted with HTTPS. Passwords are hashed, access to customer data is restricted by account and role, and we keep the amount of data we collect to a minimum.
7. Children
PageLens is a business tool and is not directed at children under 16. We do not knowingly collect personal data from children.
8. Changes to this policy
If we make material changes, we'll update the date at the top of this page and, where appropriate, notify customers by email before the changes take effect.
9. Contact
Questions about privacy or this policy: hello@pagelens.io