Privacy Policy

Last updated: 30 October 2026. See also our terms, the data processing addendum and our cookie policy.

1. Who we are (data controller)

LocalPulse (localpulse.digitalizer.uk) is a product of Digitalizer Ltd, registered in England and Wales, company no. 15267581. Registered office: 2nd Floor, Unicorn House, Station Close, Potters Bar, Hertfordshire, EN6 1TL. Not VAT registered. ICO data protection registration ZC253283. Digitalizer Ltd is the data controller for the personal data described in this policy, except where noted in section 3.

If you have questions about this policy or your personal data, contact us at support@digitalizer.uk.

2. What we collect

Account data - agency name, email address, and password for the account owner and any team members the owner invites, and the time and version of the terms the owner accepted at signup. Authentication is handled by Supabase; passwords are stored in hashed form and are never visible to us.

Signup attribution - when you create an agency we record the campaign parameters (utm_*), the referring site and the landing page of your first visit, if your browser still holds them. This tells us which marketing brought you here. It is stored once on your agency record and is not used to profile you. The country your signup request came from is not stored on your record; it appears only in the internal signup notice we email to our own mailbox (section 5, Google Workspace).

Client business data entered by agencies - business name (which the agency can take from the Google listing and change at any time), address or location, website URL, keywords, and Google Business Profile identity for each tracked property, plus the contact name and email address an agency nominates to receive the monthly client report.

Scan and result data - rank check results, Google Maps grid scan results, AI search visibility results, website audit scores, the personalised fix plan, and client reports.

Report share links - when someone opens a client report share link we record the time and the browser identifier (user agent) of the visit against the property, so the agency can see whether its client opened the report. We do not store the viewer's IP address with the open record; it appears only in short-lived server logs. Share pages carry no LocalPulse analytics or advertising tags.

Demo requests - if you ask for a demo account through the demo form on our marketing pages we store your agency name, agency website and work email, the page you asked from, the client business name and town, the search you name, and the Google Maps listing we matched for that business. We use it to decide on the request and to follow up about LocalPulse. If we approve the request we create an agency account and the client's property from those details and email the owner an invitation to set a password; we also email the owner five days before the 30-day demo ends and when it ends, unless a card has been added. If we decline it we send you a short email to say so.

Free Google Maps rank checker - the business name, address, Google Place ID and keyword you check, and the results. To enforce the daily limit we keep a counter keyed on your IP address for 26 hours. Finished checks are kept for 30 days; they contain no visitor identity. So that each business gets one free check, ever, we keep a permanent record that a business was checked, holding only Google's place identifier for it, the date of the check and the keyword, and nothing about the visitor.

Your email for the free rank checker - before a new check starts we ask for your email address and whether you run an agency or the business. We store the address (as you typed it, and in a standard form so the same inbox is recognised), that choice, the business and search you typed, the business we matched on Google, how far the check got and its headline numbers, which of our emails we sent and when, and whether you unsubscribed or an email to you bounced or was reported as spam. We use it to send the link that starts the check, the result, and two short follow-up emails about what the result means, and to hold the free-check limit per address (one check for a business owner, up to three for an agency). The link and the result are what you asked for. The two follow-up emails are sent only with your agreement: you give it when you request the check, where the form says you will receive them, and confirm it by opening the start link. You can withdraw it at any time with the unsubscribe link in any of the emails; using it stops all further emails to that address. We do not send a reminder if you never open the link. We also keep a coded fingerprint of the address, which cannot be turned back into it, so that the free-check limit and any unsubscribe, bounce or spam report still apply after these details are deleted (section 7).

Email link clicks - links in some older emails, from the former consumer product, go through a redirect on our site that records the time of the click, your IP address and your browser identifier against the report the email was about. The IP address and browser identifier are deleted 24 months after the click; the click itself is kept as a count.

Google account connection - if an agency connects Google (section 10), the email address of the connected Google account and an encrypted refresh token.

Payment metadata - Stripe customer and subscription identifiers and invoice history. Payments are processed by Stripe; we never store card numbers.

Usage data - server logs, request metadata used for security and rate limiting, and (with consent) marketing-site analytics data.

3. Agencies and their clients' data

Where an agency enters data about its clients into LocalPulse, or nominates a client contact to receive reports, the agency is the controller of that data and Digitalizer Ltd is its processor. We process that data solely to provide the reporting service to the agency, on the terms of the data processing addendum in section 14 of our terms. Individuals whose data has been entered by an agency should direct requests to that agency in the first instance; we will assist as required and forward any request we receive to the agency within five business days.

4. Lawful bases (UK GDPR)

Contract - providing the service you signed up for (accounts, scans, reports, billing, transactional email), and taking the steps you ask for before a contract (a demo request or a free rank check, including the email with the link that starts it and the result).

Legitimate interests - securing the platform, preventing fraud and abuse, rate limiting, recording which marketing brought a signup, following up demo requests, telling UK marketing and SEO agencies about LocalPulse by email (section 11), sending up to two reminders about finishing setup to an agency that added a property but did not complete checkout (you can opt out on the signup form or with the link in each reminder), sending one reminder five days before a demo account ends unless a card has been added (with the same opt-out link), and improving the service.

Consent - marketing and analytics cookies on the marketing site (see section 6), and the two short follow-up emails after a free rank check (section 2), which you agree to when you request the check and confirm by opening the start link we email you. You can withdraw it at any time with the unsubscribe link in any of the emails.

Legal obligation - keeping payment records for tax and accounting purposes.

5. Subprocessors and third-party services

Supabase - Postgres database and authentication. Hosted in London, UK.

Vercel - web application hosting, London region.

DigitalOcean - hosts the scanning worker that runs the monthly scans, the website audits and the PDF rendering. Frankfurt, Germany (EU).

Stripe - payment processing. We store only Stripe customer and subscription IDs.

Resend - transactional email, including the monthly client report email and the free rank checker's emails.

Upstash - Redis, rate limiting and the free rank checker's job store.

Cloudflare - the Turnstile bot check on the free rank checker, the demo request form, the agency signup form and the agency console sign-in form. When you submit one of those forms your browser sends Cloudflare your IP address, browser details (user agent and TLS fingerprint) and our widget's key. Cloudflare processes this on our behalf to tell a person from a script, and also as a controller to improve its bot detection (see its Turnstile Privacy Addendum); we do not enable its pre-clearance cookie.

Google Workspace - our support and operations mailboxes (support@digitalizer.uk and the admin inbox). Email you send us lands there, as do the internal notices we send ourselves about demo requests (your agency name, agency website and work email, the client business name and town, the search you name and the Google Maps listing we matched for that business), new agency signups (agency name, owner email and the country the request came from) and billing events (Stripe identifiers, never card details).

Zoho Mail (EU) - the mailbox we send outreach emails from and receive replies in (section 11). Zoho stores those emails on servers in the EU.

Google - Analytics 4 (marketing site, consent only); Maps JavaScript API and Static Maps API (map imagery in the agency console, on report share links and in the free rank checker's result); Places API (business listing lookups and Business Profile checks); PageSpeed Insights API (each audited website URL is submitted to it for the website health scores); and the Business Profile API for agencies that connect Google (section 10). Map and business listing data is provided by Google and is subject to the Google Privacy Policy. Business listing details we get from Google Places (address, map coordinates, listing name, website, rating and review count) are kept for at most 30 days after we fetch them, including in past monthly scans; after that only the Google place identifier is kept, so tracking can resume and the listing can be fetched again. For a property that is still tracked the details are fetched again before the 30 days are up. Each monthly scan keeps its map grid (the positions around the business that the rankings were checked from), which is what past reports draw their maps from. Listing data shown in the product carries Google Maps attribution. PDF reports never show Google map imagery: their map grid sits on a street map from OpenFreeMap (below), or on a plain background.

OpenFreeMap - the street map under the map grid in PDF client reports, drawn from OpenStreetMap data. For each scan our scanning worker (DigitalOcean, above) asks OpenFreeMap's servers for the map tiles of the area around the tracked business and draws the map once; the scan's PDFs use that image. The request carries only that map area, our server's IP address and standard browser request headers: no business name, listing details, agency or client details, and nothing about anyone who views a report.

Meta - Meta Pixel on the marketing site, and the Meta Conversions API, both only after you accept advertising cookies on the banner. The Pixel sets the _fbp and _fbc cookies on the .digitalizer.uk domain and sends Meta the pages you view. With the same consent, our server sends Meta two events so that a sign-up can be matched to the Facebook or Instagram ad that led to it: when you create an agency, your email address (hashed), your IP address and your browser identifier; and when you complete checkout, your email address (hashed) and the amount paid. Meta uses this data for its own purposes as well, so for the Pixel and these events Meta and Digitalizer Ltd are joint controllers under the Meta Controller Addendum; Meta's own processing is described in the Meta Privacy Policy. Nothing is sent to Meta if you decline, and nothing is ever sent from the agency console, client reports or share links.

DataForSEO - live Google results used for rank data, and for the business's Google star rating and review count, at scan time.

OpenAI - AI search visibility checks (ChatGPT).

Anthropic - AI search visibility checks (Claude), business categorisation when a property is added, and automated analysis of crawled website data.

Perplexity - AI search visibility checks.

We share with these providers only what each needs to perform its function. We do not sell personal data. Fonts on our public pages are served from our own domain, with no font requests to Google. The map view in the agency console loads the Google Maps JavaScript API, which makes requests to Google (including for fonts).

6. Cookies and analytics

The marketing site uses Google Analytics 4 and the Meta Pixel. Neither loads until you click Accept on the cookie banner; the choice is stored in your browser and implemented with Google Consent Mode v2. Accepting grants all four Consent Mode signals to Google's tag (analytics storage, ad storage, ad user data and ad personalisation), so Google may use the visit for measurement and to show our ads to people who visited; declining leaves all four denied. Accepting also allows the Meta Pixel and the server-side Meta events described in section 5. Declining consent does not affect use of the product. Strictly necessary cookies (for example authentication session cookies in the agency console) do not require consent. Client report share pages carry none of these tags. For full details, see our cookie policy.

7. Retention, cancellation and account closure

Account data, client business data, scan history and reports - kept while your account is active. Data for archived properties is kept so you can restore them. Google business listing details are the exception, for live, archived and past data alike: they are kept for at most 30 days after they were fetched (section 5) and fetched again from Google when tracking resumes. PDF copies of client reports are deleted from our storage 30 days after they are made; the report itself is kept and a new PDF can be made at any time. Each user can change their own login email and password in the console (Settings, then Login).

Team members who are removed - when the account owner removes a team member, that person loses access straight away. Their login (email address and password, which is stored hashed) is deleted 30 days after the removal, unless by then they belong to another agency on LocalPulse.

After you cancel - cancel your subscription in the billing portal in your console (Settings, then Billing). Your account and its properties are kept for 60 days so you can reactivate or export reports, and the properties are archived after 60 days. If billing has not been restarted 90 days after the subscription ended, the account is closed automatically and we email the account owner; as with an account the owner closes (below), all of its data is then deleted 60 days after closing, that is 150 days after the subscription ended, except payment records. An agency whose demo ended without a card is closed 90 days after the demo ended and its data deleted on the same schedule as a cancelled agency. You can ask us to delete it sooner at support@digitalizer.uk (we confirm within 30 days).

Exporting and closing your account - the account owner can download all of the agency's data as a single file (Settings, then Export your data) and close the agency (Settings, then Close agency). Closing cancels billing straight away, stops scans, client report emails and share links, and removes access for every user of the agency. All of the agency's data, including its users' logins, is deleted automatically 60 days after closing, except payment records (below); until then we can reopen the account if the owner asks. You can also email support@digitalizer.uk from the account owner's address to close your account, request an export or have your data deleted sooner; we confirm within 30 days.

Demo requests and other leads - 12 months from the request.

Business contacts we email (section 11) - deleted six months after the last email if they do not reply. An address that asks us to stop is kept on a do-not-email list for as long as we send marketing email, so we never write to it again.

Your email for the free rank checker - kept for 12 months after the last email we sent you or the last time you used the checker, whichever is later, then deleted. We then keep only a coded fingerprint of the address (a keyed hash: it cannot be turned back into the address, but lets us recognise the same address if it is used again), with one entry for each free check it started and, if you unsubscribed or an email to you bounced or was marked as spam, one entry saying not to email it again. It holds no name, business, search or date, is used only to keep the free-check limit per address and to stop emails you did not want, and is kept with no end date. If you ask us to delete your data we delete its check entries too and keep only the entry that stops our emails. The business name and address we matched on Google are removed from your email record 30 days after the lookup, like all business listing data from Google. Unsubscribe with the link in any of the emails, or email support@digitalizer.uk to have your email record deleted sooner.

Free rank checker - IP rate-limit counters expire after 26 hours. Finished checks contain the business and keyword only, no visitor identity, and are kept for 30 days (the longest we keep any business listing data from Google), during which the share link works. A record that a business was checked, holding only Google's place identifier, the date and the keyword, is kept permanently so the one-check-per-business rule can be enforced; it holds no business listing data and no visitor identity.

Report opens and email link clicks - 24 months. For email link clicks the IP address and browser identifier are removed at 24 months and the click is kept as a count only.

Our mailboxes - email you send to support and the internal notices about demo requests, signups and billing (section 5, Google Workspace) are not deleted automatically. We delete notices about demo requests and signups by hand once they are older than 12 months, in line with the lead retention above; support threads are kept while they are needed to help you and deleted by hand after that.

Data from the former consumer product - LocalPulse sold reports and subscriptions directly to businesses until 3 July 2026. Those records are kept as history for accounting and to answer questions about past orders, but the records themselves no longer identify anyone: email addresses, IP addresses, browser identifiers, advertising identifiers and any names or phone numbers have been removed from the audit, trial, subscription, lead, click and view records, leaving dates, counts, scores and the business listing identifiers. Payment records for those orders are held by Stripe and kept for 6 years (below).

Google account connection - until you disconnect Google or the account owner closes the agency (closing revokes our access and deletes the stored token straight away).

Payment records - 6 years, as required by UK tax and accounting law.

Backups - database backups are encrypted and kept for 30 days on our server in Frankfurt (EU) and for 60 days on an encrypted company device in the UK; deleted data can persist in a backup until it ages out.

Server logs - kept by our hosting providers for a short period for security and debugging.

8. Your rights

Under UK GDPR you have the right to access, rectify, erase, restrict, and port your personal data, and to object to certain processing. Contact support@digitalizer.uk to exercise any of these rights. We respond within one month, or tell you within that month if a complex request needs longer. You also have the right to complain to the Information Commissioner's Office (ICO): ico.org.uk.

9. International transfers

Our database and web application are hosted in London, UK (Supabase and Vercel). The scanning worker that runs the monthly scans, audits and PDF rendering is hosted by DigitalOcean in Frankfurt, Germany, in the EU, which the UK treats as providing adequate protection. The mailbox we send outreach emails from and receive replies in (Zoho Mail, sections 5 and 11) is hosted in the EU as well, with the same adequate protection. Nightly encrypted database backups are kept there for 30 days and for 60 days on an encrypted company device in the UK. Some subprocessors listed in section 5 (for example Stripe, Resend, Google, Meta, DataForSEO, OpenAI, Anthropic, Perplexity, Upstash, Cloudflare, OpenFreeMap) may process data outside the UK, including in the United States. Where that happens, transfers are protected by appropriate safeguards such as the UK-US Data Bridge, the UK International Data Transfer Agreement or Addendum, or adequacy regulations.

10. Google user data (Connect Google)

LocalPulse offers a "Connect Google" feature that lets an agency authorise LocalPulse, via Google OAuth, to read data on the agency's behalf for the client locations it manages.

What we access. With the agency's authorisation, LocalPulse reads Google Business Profile Performance data: calls, website clicks, direction requests, impressions, bookings made through the listing (where Google reports them), and monthly search keyword impressions. For an agency that has connected Google, LocalPulse also reads each mapped listing's categories, description and posts and whether the owner replied to its latest reviews, and keeps only the category names and counts (the length of the description, the date of the latest post and the number of recent posts, how many of the latest reviews have an owner reply), never the text of a description, post or review or a reviewer's name. Later phases will add read-only access to Google Search Console and Google Analytics 4 data.

Scopes requested.

openid and email - used only to identify which Google account is connected, so we can show it in the agency's settings. The email address of the connected account is stored with the connection and deleted when the agency disconnects.

https://www.googleapis.com/auth/business.manage - used in a read-only manner to list the locations the agency manages and to fetch Business Profile Performance metrics and the listing details described above for those locations.

https://www.googleapis.com/auth/webmasters.readonly - future: read-only Google Search Console data.

https://www.googleapis.com/auth/analytics.readonly - future: read-only Google Analytics 4 data.

How we use it. Google user data is used only to render the agency's own client reports inside LocalPulse. It is never sold, never used for advertising, never used to build profiles unrelated to the reporting feature, and never shared with third parties beyond the subprocessors listed in section 5 that are necessary to operate the service (for example our database host). Humans do not read this data except with the agency's permission for support, for security purposes, or where required by law.

Limited Use. LocalPulse's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Storage and security. One OAuth grant is made per agency. Refresh tokens are stored encrypted. The connected account's email address and any cached Google metrics are stored in our London-hosted database alongside the related agency and property.

Disconnect and deletion. An agency can disconnect Google at any time from its settings, which deletes the stored token and the connected account email. Cached Google metrics are deleted when the related property's data is deleted, or with the rest of the agency's data 60 days after the agency account is closed (section 7). Agencies can also revoke LocalPulse's access from their Google Account at myaccount.google.com/permissions.

11. Business contacts we email about LocalPulse

We sometimes email the owners and directors of UK marketing and SEO agencies to tell them about LocalPulse. We find the name, role and work email address on the agency's own website or in the Companies House register, and we only email limited companies and LLPs. Our lawful basis is legitimate interests: telling agencies about a service made for agencies.

We hold the name, role, agency, work email address, where we found it, and the date and outcome of each email, and nothing else. We do not share it and we use no open or click tracking. We send at most one email and one follow-up.

You can object at any time by replying "stop" to the email or by writing to support@digitalizer.uk. We stop the same working day and keep your address only on a do-not-email list so we never write again. Contacts who do not reply are deleted six months after the last email.

12. Changes to this policy

We will post updates to this page and, for material changes, notify agencies by email or an in-console notice. The list below records every change to this page since 27 September 2026, newest first.