Cookie Policy

This page lists every cookie and every piece of browser storage PlanWatch uses, what each one is for and how long it lasts. It also explains the anonymous visit counting we do without asking, and how to stop it. For everything else we do with personal data, see our Privacy Policy.

When you first visit, a banner offers three equal choices: Essential only, Manage and Accept all. Nothing optional is switched on, and nothing is pre-ticked, until you choose it.

These are strictly necessary to provide a service you ask for, so they do not need consent. Several are only set when you use the feature they belong to.

If you have not accepted analytics cookies, including if you chose Essential only, we still count visits for our own statistics. UK law allows this without consent when it is only used to improve our own site and you are told about it and can object easily (the Privacy and Electronic Communications Regulations, regulation 6 and Schedule A1, statistical purposes, as amended by the Data (Use and Access) Act 2025).

What we record for each page you view in this tier:

• the page and its title, and the address of the site that sent you (without any query string);
• the kind of source (search engine, AI assistant, social site, direct), and any campaign name in the link;
• clicks on buttons and links, form submissions (never what you typed), scroll depth and time-on-page markers;
• your screen size, your browser's user-agent string and a one-way scrambled (hashed) form of your IP address, used to tell visitors apart in our totals and to spot automated traffic (we never store the IP address itself);
• a random visit id, pw_stats_session, kept in your browser's session storage. It is deleted when you close the tab, so we cannot link one visit to the next.

In this tier there is no persistent visitor id and no advertising click id (such as fbclid or gclid). Our server removes them even if a browser sends them. Nothing is sent to Google, Microsoft, Meta or anyone else, and none of it is used for advertising. A session-storage note of where this visit came from (pw_source) keeps later pages of the same visit attributed correctly; it is also deleted when you close the tab. Visit records are deleted after 90 days.

One link we do make: if, during the same visit, you look at our pages for trade businesses and then sign up or start a checkout, we note on that sign-up that it came from a business visit, so our team can offer the right help. The visit id itself is not stored with your account, and we forget the visit after 24 hours.

With analytics accepted, our own visit records also carry a visitor id kept on this browser, so we can see how people come back and which visits lead to a sign-up. We also load Google Analytics 4 and Microsoft Clarity (Clarity records how pages are used, such as clicks, scrolling and mouse movement, with form fields masked).

With marketing accepted, we load the Meta (Facebook and Instagram) pixel and tell Meta when someone views a page, signs up or starts a paid plan, so we can measure our adverts. Our server also sends those events to Meta through its Conversions API, with your email address and postcode hashed, your IP address and browser user agent, and the Meta ids below. If you arrive from a Meta advert, we keep its click id (fbclid). None of this happens unless you accept marketing; a choice you make at checkout also decides whether the later trial and payment events are sent.

If we add or change a cookie, we update this page and the date at the top, and we ask again where the change needs your consent. Questions: hello@planwatch.co.uk.