Privacy notice

Last updated: 14 November 2026

This notice says what pivitlab collects, why, and what you can ask us to do. It is written in plain English for people in the UK.

Who we are

pivitlab is a UK service for running A/B tests on a website. pivitlab is a service run by Go2Media. You can email us at info@pivitlab.com.

For visitor data collected on a customer’s own website, pivitlab is the processor and the customer is the controller. For account data (the people who sign in to pivitlab), pivitlab is the controller.

What we collect

Account data. When you ask for access, sign up, or are invited, we keep the details you give us, such as your name, work email, and website. We also keep a record of sign-in, your role (Owner, Member, or Viewer), and the tests you set up.

Site visitor data. The snippet a customer pastes into their site can store a random visitor id, which variant that visitor was shown, page views, and goal events such as a click. It does not collect visitors’ names. A visit marked as a test (with ?pivit_qa=1) is labelled so it can be left out of the results.

We do not ask the snippet to read the contents of a form, a payment page that belongs to someone else, or anything inside a closed-off part of the page.

Why we use it

  • To run the account: sign-in, invites, and keeping each agency’s tests separate.
  • To run a test and show the results to the customer who set it up.
  • To keep the service reliable, including backups and a record of important account actions.
  • On pivitlab.com itself, to see how the public pages are used, and only after you click Accept.

Legal bases under UK GDPR

  • Contract. We use account data to provide the service you signed up for.
  • Legitimate interests. We use account and security records to keep the service safe, to answer a support email, and to understand whether the product is working. You can object.
  • Consent. On a customer’s site, storing a visitor id and sending test results generally needs consent under PECR, unless the customer has a lawful reason not to ask. The customer’s own cookie banner is what collects that choice. On pivitlab.com, analytics cookies run only after Accept.

The customer decides the lawful basis for testing on their site, and must say so in their own privacy notice. pivitlab does not put a consent banner on the customer’s site.

Cookies and local storage

On a customer’s site, the snippet may use:

  • _ab_visitor_id in local storage: a random id, not a name.
  • _ab_assign_… in local storage: which variant that visitor was shown.
  • _ab_click_…, _ab_element_…, _ab_custom_… and _ab_converted_… in local storage: so the same goal is counted once.
  • pivit_qa in local storage and as a first-party cookie: only when the address includes ?pivit_qa=1, to mark a test visit. ?pivit_qa=0 clears it.

The snippet does not set an expiry on those local storage keys. They stay until the browser clears site data. If analytics consent is refused, or is withdrawn during the visit, the snippet does not write these and does not send results.

In the pivitlab app:

  • A sign-in cookie, pivit.sid (in production, __Host-pivit.sid). It keeps you signed in. An Owner or Member session ends after 30 days without use, and never lasts more than 90 days from sign-in. A platform admin session lasts 12 hours.

On the public pivitlab pages (this site, not a customer’s site): before you choose, analytics and advertising storage are denied. Nothing is sent until you click Accept. Reject loads nothing. The choice is stored in local storage as pivitlab_analytics_consent (granted or denied). That is not a cookie, and the code sets no expiry. Accept then loads Google Tag Manager, container GTM-KZCDC3HJ, which contains Google Analytics 4 (G-NT78JHVHGY) and Microsoft Clarity. Google Analytics 4 can set _ga and _ga_*. Microsoft Clarity can set _clck and _clsk, and Microsoft can also set CLID, MUID, ANONCHK, MR and SM. Choosing Reject after Accept sets consent back to denied and deletes the first-party cookies where the browser allows. Cookie settings on this page lets you choose again.

Who else handles the data

We use these suppliers:

  • Railway provides application hosting and the database.
  • Postmark sends transactional email.
  • PostHog provides product analytics.
  • Hostinger provides domain and email hosting.
  • Google Analytics 4, only where a customer turns on Send to GA4. The snippet sends one event through the Google tag already on that customer’s site. pivitlab does not receive a copy of that Google hit.

How long we keep it

We keep account data and test results while the account is open, so you can sign in and read a test. Sign-in sessions end on the times above. Test results and account data are deleted 30 days after an account closes, unless the law requires us to keep them longer. Local storage on a visitor’s browser stays until that browser clears it.

International transfers

Some suppliers (Railway, Postmark and PostHog) are based in, or process data in, the United States. Where a supplier is certified under the UK Extension to the EU-US Data Privacy Framework (the UK-US data bridge), we rely on UK adequacy regulations. Otherwise we rely on the ICO’s International Data Transfer Addendum to the EU Standard Contractual Clauses, as included in each supplier’s data processing agreement.

Your rights

You can ask to see the personal data we hold about you, to correct it, to delete it, to limit how it is used, to object, and, where it applies, to receive a copy you can move. Email info@pivitlab.com. If the data is about a visit to a customer’s site, the customer is the controller and may be the right place to start. We will help them answer.

You can complain to the Information Commissioner’s Office (ICO) at ico.org.uk. We would like the chance to put things right first.

Changes

If this notice changes, we will update the date at the top. If a change is important, we will also say so by email to account holders.

Back to pivitlab · Terms of use ·