Cookie policy

Last updated: 21 October 2026

This policy explains which cookies jplistings.co.uk sets, what each one does, and how you control them. It is written to be read, not scrolled past.

1. What a cookie is

A cookie is a small text file that a website stores in your browser. When you come back, your browser sends it with the page request, which is how a site can keep you signed in or remember a choice you made. Some cookies are set by us; some are set by services we use.

2. The choice you make

The first time you visit we show a small card with three options: accept all, essential only, or choose. Essential cookies run whatever you pick, because the site cannot work without them. Everything else stays off until you say yes. You can change your mind at any time with the "Cookie settings" button in the footer of every page, and your choice is kept for 180 days.

3. Essential cookies (always on)

Cookie	Set by	What it does	How long
`jp_consent`	JP Listings	Remembers which cookie categories you agreed to	180 days
`sb-` followed by our project id (`-auth-token`, and sometimes `-auth-token-code-verifier`)	Supabase, our sign-in service	Keeps you signed in and lets you sign in with Google	Session, refreshed while you use the site
`cf_clearance` and similar	Cloudflare Turnstile	Checks that a form is being sent by a person, not a script, on sign-up, contact and the home valuation	Up to 1 year
`__vercel_live_*`	Vercel, our host	Only on preview links used during testing, never on the live site	Session

Cookie: jp_consent
Set by: JP Listings
What it does: Remembers which cookie categories you agreed to
How long: 180 days

Cookie: sb- followed by our project id (-auth-token, and sometimes -auth-token-code-verifier)
Set by: Supabase, our sign-in service
What it does: Keeps you signed in and lets you sign in with Google
How long: Session, refreshed while you use the site

Cookie: cf_clearance and similar
Set by: Cloudflare Turnstile
What it does: Checks that a form is being sent by a person, not a script, on sign-up, contact and the home valuation
How long: Up to 1 year

Cookie: __vercel_live_*
Set by: Vercel, our host
What it does: Only on preview links used during testing, never on the live site
How long: Session

4. Analytics cookies (only if you say yes)

Cookie	Set by	What it does	How long
`_ga`, `_ga_` followed by an id	Google Analytics 4	Counts visits and pages so we can see which parts of the site are used. IP addresses are truncated; Google's own use is covered by Google's privacy policy	Up to 2 years

Cookie: _ga, _ga_ followed by an id
Set by: Google Analytics 4
What it does: Counts visits and pages so we can see which parts of the site are used. IP addresses are truncated; Google's own use is covered by Google's privacy policy
How long: Up to 2 years

5. Advertising cookies (only if you say yes)

Cookie	Set by	What it does	How long
`_fbp`	Meta (Facebook and Instagram)	Lets us measure whether our adverts on Facebook and Instagram led to a listing or an enquiry, and show our adverts to people like our visitors. Meta's own use is covered by Meta's privacy policy	90 days
`_fbc`	Meta (Facebook and Instagram)	Set only if you reached us by clicking one of our adverts. It records which advert it was, so that advert can be credited if you go on to list or enquire	90 days
`_ga` and Google Tag Manager	Google	Tag Manager is the container we load our Google and advertising tags through. It sets no cookie of its own; the tags inside it are the ones listed here	See above

Cookie: _fbp
Set by: Meta (Facebook and Instagram)
What it does: Lets us measure whether our adverts on Facebook and Instagram led to a listing or an enquiry, and show our adverts to people like our visitors. Meta's own use is covered by Meta's privacy policy
How long: 90 days

Cookie: _fbc
Set by: Meta (Facebook and Instagram)
What it does: Set only if you reached us by clicking one of our adverts. It records which advert it was, so that advert can be credited if you go on to list or enquire
How long: 90 days

Cookie: _ga and Google Tag Manager
Set by: Google
What it does: Tag Manager is the container we load our Google and advertising tags through. It sets no cookie of its own; the tags inside it are the ones listed here
How long: See above

6. What we do not use

No cookies for the map (Mapbox loads without them), the mortgage calculator, the home valuation estimate, email newsletters, chat widgets or social share buttons. Our error monitoring (Sentry) sets no cookies. There are no third-party advertising networks on the site beyond the Meta pixel above, and only if you consent to it.

Two of the cookies above, _fbp and _fbc, are also read by our servers and sent to Meta along with the actions we report to it. That only happens once you have agreed to advertising cookies, and the privacy policy section Measuring our advertising sets out exactly what is sent.

7. Storage that is not a cookie

When you open a property page we note in your browser's session storage that you have seen it, so the listing's view count goes up once per visit rather than every time you scroll back to it. It holds no personal data, it is never sent anywhere, and it disappears when you close the browser.

8. Changing or removing cookies

Use "Cookie settings" in the footer to turn analytics or advertising on or off. To remove cookies entirely, use your browser's settings (usually under Privacy). If you delete jp_consent, we will ask you again on your next visit. If you delete the Supabase cookie, you will be signed out.

9. Your rights

You can ask what personal data we hold, have it corrected or deleted, withdraw consent, or object to how we use it. Email info@jplistings.co.uk. You can also complain to the Information Commissioner's Office at ico.org.uk.

10. Changes to this policy

When we add or remove a cookie we update this page and the date at the top. Material changes are shown on the cookie card again.