Cookie Policy
Last updated: 28 September 2026. See also our terms and privacy policy.
What are cookies?
Cookies are small text files stored on your device when you visit a website. Websites can also keep small amounts of data in your browser's local storage and session storage, which work like cookies but are not sent with every request. This policy covers all three on localpulse.digitalizer.uk.
How we use them
LocalPulse uses cookies and browser storage for three purposes: keeping you signed in to the agency console (strictly necessary); remembering your cookie choice; and, only if you accept, measuring how visitors use the marketing site (Google Analytics), whether our Facebook and Instagram advertising leads to sign-ups (Meta Pixel), and showing our ads to people who visited. We do not sell your data.
What Accept switches on: Google's tag is told, through Google Consent Mode v2, that all four signals are granted (analytics storage, ad storage, ad user data and ad personalisation); the Meta Pixel loads and sets its cookies; and our server may send Meta a record of your agency sign-up and of a completed checkout (your email address hashed, your IP address and browser identifier at sign-up; your email address hashed and the amount at checkout), so the sign-up can be matched to the ad. Meta is a joint controller with us for the Pixel and those events (see section 5 of our privacy policy) and processes the data under its own privacy policy. Decline leaves all four Google signals denied, loads no Meta script and sends nothing to Meta.
Google Analytics and the Meta Pixel do not load until you click Accept on the cookie banner. If you decline, neither script loads and no analytics or advertising cookie is set; the site works exactly the same. The client report share pages, served on a separate report domain, carry none of these tags.
Cookies and storage we use
| Name | Set by | Purpose | Type and duration |
|---|---|---|---|
| sb-*-auth-token (may be split into sb-*-auth-token.0, .1) | LocalPulse (Supabase Auth) | Keeps you signed in to the agency console. Strictly necessary; set only when you log in. | Cookie, up to 400 days, refreshed while you use the console; the sign-in itself ends 30 days after you log in |
| lp_agency | LocalPulse | Remembers which agency the console opens when your login belongs to more than one. Strictly necessary; set only when you switch agency or join another one. | Cookie, 1 year |
| lp_admin | LocalPulse | Set only for Digitalizer Ltd staff accounts so that our own visits are excluded from analytics. | Cookie, 30 days |
| lp_admin_view_agency | LocalPulse | Set only when a Digitalizer Ltd administrator opens an agency's console to help with a support request. | Cookie, 8 hours |
| cookie_consent | LocalPulse | Remembers whether you accepted or declined analytics and advertising cookies so we do not ask again. | Local storage, until you clear it or use the reset button below |
| lp_consent | LocalPulse | A copy of your cookie choice that our server can read, so the sign-up and checkout conversion events we send to Meta are sent only if you accepted advertising cookies. | Cookie, 1 year |
| lp_attr | LocalPulse | Records the campaign link, referrer and landing page of your first visit so that, if you create an agency, we know which marketing brought you. Nothing is stored before you accept: until then the record lives only in the page's memory. | Written only after you accept: session storage for the current tab, and local storage so a later visit still carries the original source |
| lp_skip_tracking | LocalPulse | Set manually by our own staff to exclude their visits from analytics. Never set for visitors. | Local storage, until cleared |
| _ga, _ga_* | Google Analytics | Counts visitors and which pages are viewed so we can improve the marketing site. Set only after you accept. | Cookie, up to 2 years |
| _fbp | Meta (Facebook) | Identifies your browser to Meta so it can measure whether our Facebook and Instagram ads lead to sign-ups on this site. Set only after you accept. Meta sets it on the .digitalizer.uk domain, so it is also sent to our other sites on that domain. | Cookie, 3 months |
| _fbc | Meta (Facebook) | Stores the click identifier when you arrive from a Facebook or Instagram ad. Set only after you accept, on the .digitalizer.uk domain like _fbp. | Cookie, 3 months |
| Meta browser storage (names begin with fb) | Meta (Facebook) | Meta's Pixel script can also keep its own working entries in this site's local storage and session storage. Their names are chosen by Meta and begin with fb. Written only after you accept; the reset button below removes them. | Local storage and session storage, until cleared |
Managing your preferences
You can change your cookie choice at any time by clicking the button below. This clears your stored choice, deletes the analytics and advertising cookies we can reach from this page, turns tracking off for this visit, and shows the consent banner again on your next page load.
Browser controls
Most browsers let you block or delete cookies through their settings. Keep in mind that blocking all cookies will stop you signing in to the agency console. You can find instructions for your browser at allaboutcookies.org.
Contact
If you have questions about our use of cookies, email us at support@digitalizer.uk. This policy is issued by Digitalizer Ltd; see our privacy policy for who we are and how to exercise your rights.
Changes to this page
Every change since 27 September 2026, newest first.
- 28 September 2026 - The lp_agency row added (which agency the console opens for a login in more than one); the sign-in cookie row says a sign-in ends 30 days after you log in.
- 28 September 2026 - What Accept switches on (the four Google consent signals, the Meta Pixel and the server-side Meta events) and Meta's joint-controller role; the lp_attr row corrected (nothing is stored before you accept); the _fbp and _fbc domain and Meta's browser storage listed; the reset button also clears Meta's storage entries.
- 27 September 2026 - No change to this page (the lp_consent row was added on 26 September 2026 without updating the date; corrected today).