Confidentiality and what not to upload to a drafting tool

Confidentiality in AI planning documents work comes down to one habit: decide what a document actually needs before you upload it, rather than uploading the whole file because it is to hand. A planning consultant handling an option agreement, a viability model and a client's correspondence file is holding material that does real commercial damage if it moves, and the drafting tool is only one of several places it can move to. The answer is not avoidance. It is a short, boring routine applied every time.

PlanScope has no published privacy policy or terms of service at present, so the only safe statement about how any provider handles uploads is that you should read their current published policies before you upload anything confidential. That applies to us as much as to anyone.

Why the question arises at all

Planning work is unusual in how much of it becomes public. The application, the drawings and most supporting documents go onto a public register and stay there. So practitioners get used to treating planning material as non-sensitive, and then handle the pre-application phase the same way.

The pre-application phase is where the confidential material lives. Site assembly is not public. The identity of a purchaser is often protected. A viability appraisal submitted later may be redacted, but the version circulating in month three is not. And an objector's letter containing a neighbour's medical circumstances is personal data whether or not the council publishes a redacted copy.

Two distinct risks sit behind the same question. Commercial confidentiality, which is contractual and reputational. And personal data, which is regulated, and where the obligations sit on your firm as controller regardless of which tool you used.

Categories of sensitive planning material

It helps to sort the file before the project starts rather than case by case under time pressure.

• Land interests: option and promotion agreements, heads of terms, overage provisions, seller identities
• Commercial models: viability appraisals, build cost plans, land value benchmarks, funder correspondence
• Third party personal data: objection letters, consultation responses, neighbour correspondence, occupier details
• Client personal data: names, addresses, contact details, financial circumstances
• Legal material: counsel's advice, litigation correspondence, anything privileged
• Security-sensitive information: detailed plans of certain premises, security arrangements

Against that, the material a planning document genuinely needs is usually thin: a site address and boundary, planning history references, constraint data, dimensions and areas, policy references and a description of the proposal. Almost none of that is confidential.

Option agreements and land assembly

The most common unforced error is uploading a full option agreement to extract a site boundary and a red line description. The document also contains the price mechanism, the trigger events, the minimum land value and the identity of the promoter, and none of that belongs in a planning statement.

Extract what you need. A site area, a boundary reference to a title plan, and the ownership certificate position under the application forms. Where the applicant is not the freeholder, the planning submission needs the correct ownership certificate and the notice served on the owner, and the terms of the option are irrelevant to both.

Land assembly also creates a timing risk. If a drafting tool's output is shared within a wider team, a document naming an unacquired parcel can reach a landowner's agent and change the price. Keep the draft's circulation as narrow as the underlying deal.

Personal data in objection correspondence

Objection letters are the material practitioners handle most carelessly, partly because the council has already received them. A letter may contain health information, details of a child's school journey, or a description of a family dispute, and all of it is personal data. Where it concerns health it is special category data and the bar for processing it is higher.

The practical approach is to summarise rather than to upload. A planning response needs the planning substance of the objections, which is almost never the identity of the objector. "Twelve representations raised overlooking from the first floor windows" is more useful in a statement than a list of names, and it is what the officer's report will say.

Where you do need to work with the correspondence itself, redact identifying detail first. And note that your firm's own privacy notice to clients and third parties should already describe the categories of processor you use. If it does not, that is a document to update, and it is independent of which tool you choose. The related question of how you describe authorship of a draft to the council is dealt with in when a council asks who wrote your report.

Checking a provider's current policies

Every provider's position changes, so this is a recurring check rather than a one-off. What to look for, in order of how much it matters:

1. Whether uploaded content is used to train models, and whether that can be switched off.
2. Where data is stored and processed, and whether any transfer mechanism is described.
3. The retention period for uploads and outputs, and whether deletion is available on request.
4. Whether the provider will sign a data processing agreement, and what its terms say about sub-processors.
5. What the provider publishes about access controls and staff access to customer content.
6. Whether there is a published security page at all, because absence of one is itself information.

PlanScope's current position is that no terms of service, privacy policy or disclaimer page is published, so treat the absence as a reason to keep confidential material out of uploads rather than as a reassurance. Pricing and account information sits on the pricing page, and the account required for the guided flow is created at registration.

Practical redaction before upload

Redaction does not need to be elaborate. It needs to be habitual.

Work from a clean extract rather than the source file. For a site description, that means a plan with the red line and a north point, not the full title pack. For planning history, the reference numbers and decisions, not the officer's internal notes. For a viability discussion, the structure of the argument, not the appraisal.

Where a PDF must go up, flatten it after redacting, because a black rectangle drawn over text in some editors leaves the text underneath. Check metadata too: author names, tracked changes and comment threads travel inside Word files and are easy to forget.

One test that catches most problems. Before uploading, ask whether you would be comfortable if this file appeared on the planning register tomorrow. If the answer is no, extract instead of uploading. The same discipline belongs in the internal review checklist the firm applies to every submission.

Client engagement terms worth updating

Two clauses make this straightforward. A statement in the engagement letter that the firm uses software tools, including AI-assisted drafting tools, in the preparation of documents, with the firm retaining professional responsibility for the output. And a clause setting out what the client must tell you about confidentiality restrictions on material they send.

The second one is the more useful. Clients send option agreements unprompted, and a line in the engagement letter asking them to flag restricted material shifts the conversation to the start of the job rather than after the event.

None of this is a reason to keep drafting by hand. It is the same care you already apply to email distribution lists and shared folders, applied to one more channel.

This is general guidance, not legal advice, and it does not address data protection compliance, which is a matter for your own advisers. Check the position with your local planning authority or a qualified professional before relying on it. PlanScope provides AI-assisted draft reports for planning applications. Reports should be reviewed before submission. We do not guarantee planning approval.