Privacy Policy
Last updated · 30 August 2026
Who is responsible
Broadhurst Digital Limited (Company No. 12503471) operates planningconstraints.com and is the data controller for personal data described here. Contact: support@planningconstraints.com.
What we collect and why
Searches. When you search, we log the coordinates, postcode (if entered), result count, referrer and browser user-agent. Where you search signed out, this is product analytics and is not linked to an account or identity. Where you search signed in, it is associated with your account so we can show you your own history and saved sites. Legal basis: legitimate interests (improving the Service) or, for signed-in use, performance of a contract.
Accounts. Creating an account stores your name, email address, whether it is verified, and (if you turn it on) that two-factor authentication is enabled — never the authenticator secret or backup codes in the clear. We keep a record of your sessions (a token, when it was created, its expiry, and the IP address and browser user-agent it was created from) so you can stay signed in and so we can show you where you are signed in; a session is deleted when it expires or you sign out. Signing in with a one-time link or a six-digit code creates a short-lived token that is deleted once it is used or expires. Legal basis: performance of a contract.
Purchases and licences.When you buy a Site Report Pass or Pro, our payment provider Stripe collects your payment details; we never see card numbers. We store your email address, licence key, plan, Stripe customer/subscription identifiers and (for Site Passes) the purchased location, to deliver and support what you bought. If you buy a Team or Practice licence for an organisation, we also store the organisation's name, branding, billing details and the list of members and their roles (owner/member/guest), plus any email addresses you invite. Legal basis: performance of a contract.
Saved sites, organisations and client portals. If you save a site, we store its location, label, notes, tags, score and any files or boundary you attach to it, against your account or organisation. An organisation owner can generate a client portal link (a token naming a set of sites) to share a read-only view with someone outside the organisation — we log when that link was created and last viewed, but not who viewed it if they are not signed in. An organisation owner can also create API keys (we store a hash of the key, never the key itself) and set up watches (saved searches that re-run on a schedule and email an alert when something changes). Legal basis: performance of a contract.
Land-ownership features.Where you use features built on HM Land Registry corporate-ownership data (CCOD/OCOD), HM Land Registry's licence requires us to keep a record of end users — the contact details you provide when you purchase (such as your email address) and technical logs such as IP address — and we may have to disclose those records to HM Land Registry if it audits our use of the data. Legal basis: legitimate interests (meeting the conditions of our HM Land Registry data licence and demonstrating compliance with it). We keep these records for the life of that licence and for 12 months afterwards.
Site report PDFs. When you generate a Full Report, we store a copy of the PDF for 90 days so you can re-download it if your browser loses the original download; it is then deleted.
Enquiries and founding-member requests. If you submit a form we store what you give us (email, name, role, company, message) to respond and follow up. Legal basis: legitimate interests / pre-contract steps.
Cookies and analytics. A strictly functional cookie records paid access on your device. A second strictly-necessary signed cookie (pc_vid) holds a random identifier used only to enforce free-tier daily search limits on this device — it carries no personal data, is never used for cross-site tracking or advertising, and expires after 1 year. Google Tag Manager loads on every visit, but its tags — Google Analytics among them — only fire after you accept the cookie banner. Microsoft Clarity (session analytics) is loaded separately, directly by its own SDK, and is likewise only started after you accept the cookie banner. No analytics data is collected before that. Legal basis: consent.
Who we share data with
Service providers acting as processors, and what each receives:
- Vercel — hosts the application and, for Team/Practice branding and site file uploads, may store the files you upload.
- Neon — hosts our Postgres database: accounts, licences, saved sites and the other records described above.
- Cloudflare (R2) — stores organisation branding assets and site files you upload, and the map tile data the app serves; it does not receive your account details.
- Stripe — processes payments. We never see your card number.
- Emailit — sends transactional email (purchase receipts, magic links, sign-in codes, report links, alert emails) on our behalf.
- Anthropic — generates AI digests and narrative summaries. We send it council document text (conservation area, Article 4 and TPO documents) and survey facts about a location — never your account details, email address or payment information.
- Exa — web search we use to find local plan documents for a council when our own registers have not been populated yet; the council name is sent, not anything about you.
- Nominatim / OpenStreetMap — address search: what you type into the search box is sent to their API to resolve it to a location.
- postcodes.io — resolves postcodes to coordinates and local authority information.
- Microsoft Clarity and Google Analytics (via Google Tag Manager) — session analytics, consent-based, as described above.
- Better Auth (better-auth.com) — our authentication provider's hosted dashboard receives sign-in events, including IP address, city and country, so we can monitor for abuse and support account problems.
If you submit an enquiry or founding-member request, those details are also forwarded to an external CRM/automation webhook (e.g. Zapier, Make or HubSpot) so we can follow up. We do not sell personal data. Some providers process data outside the UK/EEA under appropriate safeguards (e.g. UK IDTA / EU SCCs).
Public ownership and company pages
Our /ownership/<postcode district> and /company/<company number>pages draw on HM Land Registry's CCOD/OCOD data, which covers companies and other corporate bodies only — never natural persons. If you are named on one of these pages as a proprietor, that means a company or corporate body you are associated with owns a registered title, not that you personally are named. Legal basis: legitimate interests (the data is published by HM Land Registry for exactly this kind of due-diligence use). We do not use this data for direct marketing. If you have a concern about how a proprietor is described, email us and we will respond within one month.
Retention
Purchase and licence records are kept while your licence is active and for up to 6 years afterwards (tax and accounting). Account records (name, email, sign-in history) are kept while your account is open; you can delete your account yourself at any time from your account page, subject to the HM Land Registry retention above where it applies, or email us and we will action it. Site report PDFs are kept for 90 days. Leads are kept for up to 2 years after last contact. Anonymous search logs are kept for product analytics. End-user records required by our HM Land Registry licence (see above) are kept for the life of that licence and 12 months afterwards. Consent-based analytics retention is governed by the providers' documented periods.
Your rights
Under UK GDPR you can request access to, correction or deletion of your personal data, object to or restrict processing, withdraw consent (e.g. decline cookies), and request portability. If you have an account you can delete it yourself at any time, immediately, from your account page — we keep your purchase record for tax and accounting, and a stripped account record with no name or email address for as long as our HM Land Registry licence requires it. Otherwise email support@planningconstraints.com and we will respond within one month.
Complaining to us. If you are unhappy with how we have handled your personal data, you can complain to us directly at support@planningconstraints.com. We will acknowledge your complaint within 30 days, respond without undue delay, and keep you informed of progress. You do not have to complain to us first, and doing so does not affect your right to go to the regulator. You can also complain to the Information Commissioner's Office (ico.org.uk).
See also: Terms of Use & Sale