Terms of Use

Last updated 12 September 2026

These terms govern access to PlanningLeads. By using the service you agree to them. They’re written plainly; email hello@planningleads.ie with any questions.

The service

PlanningLeads aggregates construction-lead intelligence from public records and presents it for business use. We work to keep it accurate but the data originates from third-party public sources and is provided “as is”, without warranty of completeness or fitness for a particular purpose. Indicative values (e.g. estimated construction value) are estimates, not valuations.

Who may use this service

You must be at least 16 to hold an account or to use TNDR. PlanningLeads is a service for businesses and for people dealing with their own building work, and nothing here is directed at children. If you believe someone under 16 holds an account, or you have any other concern about a person using these services, tell us at privacy@planningleads.ie and we will close the account and delete what we hold.

Acceptable use

Access is for your own organisation’s business use. You may not resell, redistribute, sublicense or publish the data in bulk; build or train a competing product or dataset from it; bypass tier limits, export caps or security controls; or use the service unlawfully. Accounts are per-organisation - don’t share credentials. Resale or redistribution rights are available only under a separate Enterprise data licence.

The underlying public records are provided under their own open licences (e.g. CC-BY); these terms govern PlanningLeads’ compiled, enriched and scored dataset, our software and your access - not the raw public records themselves.

API access and fair use

API access is authenticated with a personal Bearer key and governed by the scope on that key, which sets the request rate, the fields returned and whether feeds and bulk export are reachable. Feed and bulk scopes are granted under an Enterprise agreement after basic due diligence, not at checkout. A licence has a fixed term and a number of keys (seats). Keys created under it expire when the licence does, and ending a licence ends every key issued under it. That is a normal expiry of the entitlement, not a suspension for breach.

Paid plans below Enterprise carry a daily row budget. It applies to everything a key reads over the wire - bulk exports, keyset pages and ordinary searches alike - because a paginated search walked by a script is a bulk pull by another name. The budget exists to stop wholesale copying of the dataset, not to ration ordinary work, so it does not apply when you are signed in and using the application in a browser. Current budgets are on the pricing page. A licence is issued to an organisation and the keys under it are created by you, shown once and never held by us in a form we can read or re-send. They must not be shared outside your organisation, and may be revoked for use outside the scope granted.

Data protection - your responsibilities

PlanningLeads and you are independent data controllers. We are the controller for the lead database we compile (see our Privacy Notice); you become the controller for any personal data once you retrieve and act on it. We are not your processor.

When you contact a developer or company using information from PlanningLeads, you are responsible for complying with the GDPR and Ireland’s ePrivacy Regulations (S.I. 336/2011) - including the rules on electronic direct marketing, consent and opt-outs, and for having your own lawful basis. You must honour any objection or opt-out a contact gives you, and you must not use the data to market to private individuals in breach of those rules. We provide data; we do not authorise or carry out your outreach.

Exports and redistribution

Bulk exports and API responses are licensed to you under the scope of your key and are not for redistribution or resale unless your agreement says so. To make that enforceable, every bulk export includes a very small number of traceable marker records unique to your account (currently one). They correspond to no real planning application and contain no personal data, and they exist only so that we can identify the source if licensed data appears somewhere it should not. They are stable per account, so they do not read as new activity, and they are not counted against your row budget. If you need them identified for a data-quality process, ask us and we will tell you which records they are.

We also keep an audit record of data retrieved through an API key: the account, the key, the row count and the filters applied - never the row contents. We keep it so that we can answer a data-subject enquiry, evidence a licence, and investigate misuse. Alongside it we keep an append-only record of privileged actions taken by us on an account - issuing or ending a data licence, changing a plan, deleting an account - naming the administrator responsible. That record is retained after an account closes, because it evidences what we authorised and on what terms; it holds account identifiers only, never planning-record data.

TNDR ranking

The main parameters that determine the order of jobs in your TNDR deck and of firms on a job, and their relative importance, are described at planningleads.ie/how-ranking-works, which forms part of these Terms. Sending a tender is a paid action that improves your position on that job. We will give at least 15 days' notice of changes to these parameters, and a statement of reasons if we restrict, suspend or remove your filings.

Availability & changes

Basic, Pro and Max are provided on a reasonable-endeavours basis with no committed service level. Customers on an Enterprise agreement are covered by the published Service Level Agreement, which sets out availability, support response targets, data-refresh commitments and service credits.

We may update the service and these terms; material changes will be dated here. We may suspend access for breach of these terms. Either side may end the arrangement; paid plans are handled per your subscription.

Liability

To the extent permitted by law, PlanningLeads is not liable for indirect or consequential loss, or for decisions made in reliance on the data. Nothing here limits liability that cannot be limited by law.

See also our Privacy Notice, the Service Level Agreement and the Enterprise licence scope.