API & Data Licence
The terms for using the Planning Signal API, the MCP server and the data they return.
Version 2026-10-02, last updated 2 October 2026.
In short
- Use the data inside your own organisation, and show individual records to your own users.
- Don't resell it, redistribute it in bulk, or use it to build or train a competing planning dataset or model.
- Credit "Planning data from Planning Signal" where you show it publicly, and keep any licence notice a record carries.
- Agent contact details are personal data: you are responsible for using them lawfully, including the rules on marketing emails.
- Council registers can be incomplete or late. Check the council's own record before relying on anything.
- Delete stored data within 30 days of your plan ending.
The summary is for convenience. The numbered terms below are the licence.
1. About these terms
These terms are a licence between you and KK London (Designs & Fashion) Limited, trading as Planning Signal (company number 12968488, registered office 1 Davies Meadow, East Hanney, Wantage, OX12 0GG) ("we", "us"). They cover the Planning Signal API, our MCP server and the data either of them returns (together, "the API" and "API Data").
"You" means the organisation named on the account that holds the API key, or the individual if the account is held personally. If you accept on behalf of an organisation, you confirm you are authorised to bind it.
They apply alongside our website Terms of Service and Privacy Policy. If these terms and the website terms conflict on anything about the API or API Data, these terms win.
You accept these terms when you create an API key, subscribe to an API plan, or use the API. We record the version you accepted and when.
2. What you may do
While your account is in good standing we grant you a non-exclusive, non-transferable, non-sublicensable, revocable licence to use the API and API Data for:
- your own organisation's internal business purposes; and
- display to the end users of your own products and services, as described in section 3.
The licence is personal to your organisation. It does not extend to group companies, clients or contractors unless we agree in writing. Contractors may build or operate your integration for you, but only for your purposes and under your responsibility.
3. Showing data to your users
Permitted display means showing individual records, or small sets of records, to your end users inside your product as part of what your product does: for example a list of applications near a property, a lead in a CRM, or an alert about a new application.
Permitted display does not include giving your users, or anyone else, a way to export, download, query or copy API Data in bulk, publishing API Data as a dataset, feed or API, or making it available in a form that substitutes for a subscription to our API.
4. What you may not do
You must not, and must not let anyone else:
- resell, sublicense, rent, lend or redistribute API Data in bulk, or share your API keys outside your organisation;
- use the API or API Data to build, enhance, verify, benchmark or train a planning applications database, dataset or service that competes with ours, including by training, fine-tuning or evaluating machine learning or AI models on API Data;
- combine API Data with data from other accounts, or use multiple accounts or keys, to get around allowances, rate limits or plan restrictions;
- try to work out which systems, platforms or suppliers we obtain data from, or reverse-engineer identifiers, cursors or the service itself;
- use API Data to harass, discriminate against or unlawfully profile any person, or for any unlawful purpose;
- interfere with the API's security or operation, or test it for vulnerabilities without our written permission.
Fetching and storing records you are entitled to, in order to run your own product, is fine. Systematically copying the whole or a substantial part of our dataset is not.
5. Attribution
Where you show API Data to anyone outside your organisation, show the line "Planning data from Planning Signal" near the data, or in a credits or sources page your users can reach from it. A link to planningsignal.co.uk is welcome.
Some records carry an attribution field. Where it is set you must keep it with the record and show it wherever the record is shown publicly. For records that contain public sector information licensed under the Open Government Licence, it reads: "Contains public sector information licensed under the Open Government Licence v3.0."
Every record links to the council's own public page. Do not present API Data as an official council record or as your own original work.
6. Personal data
We do not return applicants' names or home addresses on any plan. Some plans include agent contact details (name, company, business address, email and telephone) as published by councils on their planning registers. These are business contact details, but some of them identify individuals and are personal data.
For personal data you receive through the API, you are an independent controller under the UK GDPR and the Data Protection Act 2018. You are responsible for having a lawful basis for what you do with it, for telling people how you use it where the law requires, and for keeping it secure.
You must comply with the Privacy and Electronic Communications Regulations 2003. In particular, you must not send unsolicited marketing emails or texts to individuals (including sole traders and partnerships) without their prior consent or another lawful basis, and you must respect any marketing objection or the Telephone Preference Service where it applies.
If we pass on a person's objection, erasure or correction request about data we supplied to you, you must act on it for the copies you hold within 30 days, and tell us if you cannot.
You must not use API Data to make decisions about individuals that have legal or similarly significant effects on them.
7. Accuracy and no advice
API Data comes from public planning registers that councils publish. Registers can be incomplete, late, inconsistent or wrong, and councils change them without notice. We read them in good faith but we do not check every record against the council's own file, and coverage varies by council and over time.
API Data is provided "as is" for information. It is not legal, planning, surveying or professional advice. Before relying on any record, for example to object, to buy, to build or to price a job, check it with the council's own record (the url field) or a qualified professional.
8. Allowances, rate limits and fair use
Your plan's record allowance, field access and rate limits are those published on our developers page at the time, and are shown in every API response. We may change them for future billing periods with at least 30 days' notice, or immediately where needed to protect the service.
Keep your keys secret and use them only from your own servers. You are responsible for all use of your keys until you revoke them. Tell us promptly if you think a key has been compromised.
We may throttle or temporarily block traffic that threatens the stability of the service, even within your allowance, and will tell you if we do.
9. Fees
Paid API plans are billed monthly in advance through Stripe, plus VAT. Unused records do not roll over. You can cancel at any time from Manage billing; access continues to the end of the period you have paid for. Fees already paid are not refundable except where the law requires.
10. When your access ends
If your API plan ends, or your free demo access is withdrawn, you may keep using API Data you already hold for 30 days. After that you must delete API Data you have cached or stored, except:
- individual records you have already shown to your end users in the normal course of your product (for example a lead already in a user's pipeline), which may remain where they are; and
- data you are required by law to keep, for as long as the law requires.
On request, confirm in writing that you have done this.
11. Checking compliance
On reasonable written request, and no more than once in any 12 months unless we have good reason to suspect a breach, you will tell us how you use API Data and give us reasonable information and cooperation to show you are complying with these terms. We will keep what you tell us confidential.
12. Suspension and termination
We may suspend or revoke your keys, or end this licence, if you materially breach these terms (including sections 4 and 6), if your payment fails and is not put right, or if we reasonably need to in order to protect people whose data is involved, our service or our sources. Where it is practical and lawful we will tell you first and give you a chance to fix the problem.
You may stop using the API at any time. Sections 4, 6, 10, 11 and 13 to 15 continue after the licence ends.
We may change or withdraw the API, its fields or its endpoints. We will give paying customers at least 30 days' notice of changes that remove fields or endpoints they use, unless a council or the law stops us providing them sooner.
13. Liability
Nothing in these terms limits liability for death or personal injury caused by negligence, for fraud, or for anything else that cannot be limited by law.
Subject to that, neither party is liable for loss of profit, revenue, business, goodwill or data, or for indirect or consequential loss, and our total liability to you arising out of or in connection with the API and these terms in any 12-month period is limited to the fees you paid us for the API in the 12 months before the event giving rise to the claim. If you use only the free demo, that amount is nil.
You are responsible for, and will compensate us for, claims by third parties arising from your use of API Data in breach of these terms, including breaches of data protection or electronic marketing law.
14. Changes to these terms
We may update these terms. The version and date are shown at the top of this page. We will tell account holders about material changes by email at least 30 days before they apply to paid plans. Creating a new key or changing your API plan after a change requires accepting the current version.
15. Law and contact
These terms are governed by the law of England and Wales, and the courts of England and Wales have exclusive jurisdiction.
Questions about these terms, or to pass on a data request: support@planningsignal.co.uk.
See also the API documentation, our Terms of Service and our Privacy Policy.