Privacy

The short version: we run analytics on this page so we can see what helps and what doesn't. If analytics is allowed for you, we also load Meta’s pixel and send Meta a few events (that you visited, which buttons you pressed, and that you asked for or booked a call) so we can measure our Facebook and Instagram ads. Our analytics events are also passed from our server to Mixpanel, a service that helps us read them. We don't sell your data. If you're in the EU, UK or Switzerland we ask first. Everywhere else we tell you and you can opt out. If your browser sends a Global Privacy Control or Do Not Track signal, none of it runs.

Last updated 29 October 2026.

What we collect

Only what your browser shares with any website by default, plus what you do on the page. We group it here so you can see all of it.

• A random ID and your visit history. A random visitor ID and session ID (not derived from your device), how many times you've visited, when you first came, and whether you're coming back.
• Pages and where you came from. The page, its title, how it loaded, and the referring page (without its query string).
• Campaign details in the link you used. If you arrived from an ad or an email, the tags in that link (such as UTM tags and ad or click IDs), kept so we know which campaign worked. If our email link carried a personal token (pid or rid), we keep it so we can connect your visit to the email we sent you.
• How you read. How long the page was visible, how much of that you were active versus idle (no input for 15 seconds), how often you switched tabs, how long until your first click or scroll, how far you scrolled, and which sections you saw and for how long.
• What you click and look at. Whether you saw each “Book a 15-minute call” button, hovered over it or clicked it (and which one). Clicks on links that leave the site, on email and phone links. Which FAQ questions you opened and for how long. How long you hovered over cards and footer links. When you copy text from the page, we record that you copied and how much (and the text itself only if it is short and it is our own copy). If you select our email address or phone number, we record that.
• Signs you were weighing the offer. Whether, and for how long, you looked at the price and at our worked example, proof and evidence sections, which FAQ answers you opened, and, if you started the booking form or saw the calendar but didn't finish, that you stopped, which field (by name, never what you typed) you were on last and for how long. If you read most of the page for a while and left without pressing a booking button, we record that, with the last section you saw.
• One optional question. Once, if you seem to be leaving without booking, a small box may ask “What would have made you book?” with five choices, and a short free-text box (up to 140 characters) if you pick “Something else”. It is shown only if analytics is allowed for you, and you can close it. Your choice is stored with your random visitor ID; the free text is stored only in our own analytics store, never passed to Meta or Mixpanel, so please don't put names or contact details in it. The booking form also has an optional “Biggest worry about booking?” question, kept with your other answers.
• Signs the page frustrated you. Rapid repeated clicks in one spot, clicks on things that aren't interactive and didn't respond, fast scrolling up and down, and your mouse leaving through the top of the window (a sign you might be leaving).
• Whether the page worked. Loading speed and stability numbers (Core Web Vitals), slow-task counts, JavaScript errors and failed file loads (message, file and line number only).
• Your device and browser, roughly. Window and screen size in ranges, pixel density, orientation, whether it's a touch device, your language settings, time zone and local time, connection type when your browser reports it, your light/dark, reduced-motion and contrast preferences, whether you're online, and the browser, operating system and device type read from your browser's user-agent text.
• Where you are, roughly. Country, region and city, worked out from your IP address by our host, Vercel. We never store the IP address. To count unique visitors per day we store a one-way hash of your IP address and browser, mixed with a secret that changes every day, so it can't be linked across days or turned back into an IP address.
• Details you choose to give us. If you use the booking form: your company name, your role, the size of your engineering team, what you most need tested and, if you choose to give it, your work email. We use these to prepare for the call. Then you pick a time on a calendar from Cal.com, shown on this page, which gets your name and email and the answers above (as notes on the booking). We read the answers in the booking notification Cal.com sends us. If you email us, we keep the thread.
• What Meta receives, if analytics is allowed for you. The events listed here (a page view, that the offer page was viewed, which booking button you pressed, that you submitted the form, that you booked a call), Meta's own browser cookie _fbp, the ad click ID _fbc if you came from a Meta ad, and what any website you load a Meta pixel from passes to Meta: your IP address and browser details. We also send the same events from our server (Meta’s Conversions API): the IP address and browser details of your visit, a one-way hash of your visitor ID, the page address without its query string, and, for a form submission or a booking, what you said your role, team size and needs are. If you gave an email address, only its SHA-256 hash goes to Meta, never the address. We never send Meta your company name.
• What Mixpanel receives, if analytics is allowed for you. The analytics events described above, sent from our server, labelled with your random visitor ID, your country, region and city (from our host, never from Mixpanel looking up your IP address), device and browser type, and the campaign tags in your link. If you use the booking form, also a profile with your role, team size, what you need tested and your company name. Never your email address.

What we don't collect

• Anything you type, except what you send us by pressing the form’s button. Our analytics never reads fields, we don’t record keystrokes, and there is no session replay or screen recording.
• Device fingerprints: no canvas, audio, WebGL, font, battery, memory, CPU or plugin probing.
• Your IP address (see above), your history, your other tabs, or anything from other sites.
• No session replay, social widgets or analytics SDKs from other companies in your browser. The one other company’s script is Meta’s pixel, and it loads only after analytics is allowed for you. If you reach the booking step, the calendar is Cal.com’s and loads from their server then, not before. Mixpanel gets its data from our server, nothing from Mixpanel loads in your browser.
• We don't look up the company behind an IP address, buy enrichment data about you, or try to work out who you are from this data.

What we use it for

To see how people read this page and where they drop off, which button placement works, what's broken or slow, and which campaigns bring people who engage. If you came from a personal link in an email from us, we also use it to understand your interest in what we sent. We don't make automated decisions about you.

When we ask first

• EU, EEA, UK and Switzerland (and when we can't tell where you are): nothing is collected or stored until you press “Allow analytics”. Closing the notice counts as no.
• Everywhere else: analytics is on, you see a notice, and “Opt out” turns it off.
• Browser privacy signals: if your browser sends Global Privacy Control or Do Not Track, analytics stays off, Meta’s pixel is never loaded, and nothing is sent to Meta or Mixpanel, whatever else you've chosen.
• The booking form itself works whatever you chose above. Sending it is you asking us for a call. Only the optional extras described here (Meta, Mixpanel) depend on your choice.

Change your mind any time: Change cookie preference. Turning analytics off stops collection straight away, stops the Meta pixel, deletes Meta’s cookies from this site, and clears the IDs we stored in your browser. Meta also lets you manage how ads use your activity in your Facebook and Instagram ad settings.

Cookies and browser storage

Everything above is first-party except _fbp, which Meta’s script sets, and what Meta’s pixel and Cal.com’s calendar store themselves when they load. Meta’s and Cal.com’s cookies are theirs and follow their policies.

How long we keep it

Analytics events we hold are kept for 13 months and then deleted. Emails and booking details are kept for as long as we're talking to you, or until you ask us to delete them. What Meta holds is governed by Meta’s policies, not ours; we can stop sending it, but deleting it on Meta’s side is something you can do in your Meta account settings or ask us to request. What Mixpanel holds stays there until we delete it; we will delete a person’s events and profile from Mixpanel when asked.

Who sees it

Us, and the services that run the site for us. This site is hosted by Vercel, which handles requests, keeps ordinary server logs (IP address, browser, pages requested) for security and operations, and may hold our analytics events in its logs. Scheduling is done by Cal.com, which receives your name, email, the booking details and the answers you gave us, and follows its own privacy policy.

Meta Platforms is a recipient, when analytics is allowed for you. It receives the events and identifiers described above so we can measure and improve our Facebook and Instagram advertising. That is sharing data with an advertising company, and Meta may use it under its own terms, including to match it with its own accounts. We do not give Meta your company name or your email address in clear text. If you don't want that, choose “No analytics” or “No thanks”, or send a Global Privacy Control signal.

Mixpanel is a processor for us: it stores and analyses the analytics events described above on our behalf, in the United States. If you turn analytics off, nothing more is sent to it.

We don't sell your data. Apart from the Meta sharing described above, we don’t share it for advertising.

Your rights, and removing your details

You can ask us what we hold about you, ask us to delete it, or object to us using it. Write to yash.priyam@pilabs-ai.com. Analytics data is tied to a random ID, not a name, so to find yours it helps if you include the ID: in your browser's developer tools, open Application, then Local Storage, then this site, and copy the id inside pi_v. If you can't, tell us roughly when you visited and we'll do our best. Data we can't connect to you is also data we can't identify you from, and it is deleted after 13 months anyway. We will pass a deletion request on to the services named above. You can also complain to your local data protection authority.

PI Labs. +1 (628) 333-3970