Privacy policy

Effective date: 10 November 2026

This policy explains how PlanProof handles personal information when you visit our website, use the builder workspace or Your Project Journey, take part in a project, or contact us. It covers project photographs and documents, including material sent to an external artificial intelligence service when an AI feature is used.

1 Who we are and how to contact us

PlanProof is operated by JJW Renovations Ltd, trading as PlanProof, a private limited company registered in England and Wales (company number 17243878). Our registered office is 1 Wallisdean Avenue, Portsmouth, Hampshire, PO3 6HA. We pay the data protection fee to the Information Commissioner’s Office (registration reference ZC280462).

For privacy questions, requests or complaints, email hello@planproof.co.uk or write to the address above. Please describe your concern and, where relevant, identify the project or account. You do not have to use a particular form.

2 Our role and the role of your builder

A data controller decides why and how personal information is used. A data processor handles information on a controller’s instructions.

PlanProof is a controller for its own account administration, business enquiries, subscription and billing administration, service security, and management of privacy requests and legal obligations.

When a builder or other business customer uses PlanProof to manage information about its customers, workers and projects, that business normally controls those project records and PlanProof processes them on its instructions. The business is responsible for its lawful basis, the information it uploads, its invitations and its instructions to use AI. Its own privacy notice may also apply.

Where PlanProof determines a separate purpose for using information, we remain responsible for that use. We do not transfer all responsibility to the builder simply because information was uploaded through a builder account. If you contact us about project information controlled by a business customer, we will help identify the responsible organisation and assist it with your request.

3 Information we collect and where it comes from

Depending on the features you use and your role in a project, we handle the following information.

  • Account and contact information: your name, email address, telephone number, business details, account role, sign-in information and communication preferences.
  • Project information: property addresses, customer and contractor details, agreed scope, quotations, drawings, planning documents, Project Agreements, variations, invoices, payment-status records, correspondence and diary entries.
  • Evidence and approvals: photographs, uploaded files, comments, approval or signing records, dates, timestamps and records of relevant actions. Photos and files can contain faces, possessions, personal documents, addresses, filenames and embedded metadata. A signed Project Agreement’s acceptance record can include the IP address it was accepted from.
  • AI information: material submitted to an AI feature, instructions or requests, generated illustrations, extracted information, suggested wording, review results where available, and records needed to connect an AI request or result to its project.
  • Technical and support information: IP address, device and browser details, access and security logs, errors, support messages and permitted information about feature use.

We receive information directly from you; from the builder, homeowner or other authorised participants in your project; and from the service providers needed to operate PlanProof. We also create records of actions taken in the service and receive outputs from AI processing. A builder may provide your details before you create an account, for example to invite you to Your Project Journey.

Information needed to create an account, identify the correct project or provide a requested feature must be supplied for that function to work. If it is not supplied, we may be unable to provide the relevant service. An AI feature cannot process material that has not been submitted to it.

4 Photos, documents and artificial intelligence

What is sent to AI and why

PlanProof uses OpenAI’s business API for supported AI features. The information sent depends on the feature being used. These features can involve photographs, documents or text, not just the words typed into a message.

For an AI picture in Visual Variation, selecting Make an AI picture sends the selected source photograph and the written description of the proposed work to OpenAI, together with instructions to create an illustration. This picture-generation step is initiated by that action; uploading a photograph alone does not trigger this particular feature. The image and description may still identify a person or a home, even when a separate customer name or address is not added to the request.

For supported document-reading and planning checks, PlanProof sends the relevant document, document image or extracted text, and its filename, to OpenAI so information can be read and organised. This material may contain the property address, planning reference, names, drawing details and other information printed in the document. For text-assistance features, the relevant project wording is sent to produce the requested draft or suggestion. Before a quotation is read, PlanProof removes the project’s known names and addresses and anything that looks like an email address, phone number, postcode, street address or bank detail. The same removal applies to text sent for wording help. It works by recognising patterns, so it can miss something. Planning documents are sent as they are.

Voice dictation works differently. When you tap Dictate, your phone or browser turns your speech into text using its own speech service: in Chrome and on Android phones this is normally Google’s, and on iPhone and in Safari it is Apple’s. PlanProof receives only the resulting text, never the recording. The phone or browser maker’s own privacy terms apply to the recording.

Protecting people shown in photos

Please choose images that show the relevant work. Before submitting material, remove or obscure unnecessary faces, children, personal papers, medical information, bank details, access codes and other private or security information. Where redaction would remove evidence needed for the project, use a separate copy for AI processing and preserve the original evidence appropriately.

Only upload or submit information that you have a lawful basis and authority to share. Tell affected people how their information will be used where required. Pressing an AI button does not give consent on behalf of everyone shown in a photograph. Do not assume that PlanProof automatically removes faces, addresses or location metadata.

If sensitive personal information is genuinely necessary for a project, contact us before sending it to AI so the appropriate handling can be assessed. An ordinary project upload is not a request to analyse someone’s health, identity or other sensitive personal characteristics.

Training provider retention and access

OpenAI states that business API inputs and outputs are not used to train its models by default, unless the customer opts in to sharing that data. This is separate from retaining information to operate the service or prevent abuse.

OpenAI’s published default is to retain abuse-monitoring logs for up to 30 days, with longer retention possible for legal or safety reasons. Certain image and file safety checks can result in additional retention and review. Different API features and account arrangements can have different storage rules. These provider arrangements are separate from the project records kept by PlanProof.

Authorised provider personnel and contracted reviewers may access relevant content for limited operational, security or legal purposes under the applicable service terms.

OpenAI’s current data controls are described at https://developers.openai.com/api/docs/guides/your-data.

AI results and project decisions

An AI-generated picture illustrates a possible change. It may be inaccurate and is not a photograph of completed work. AI-generated wording and document readings also need checking against the original information.

AI assistance does not automatically approve a variation, certify workmanship or release payment. The builder and homeowner remain responsible for reviewing the information and following the agreed approval process. Generated illustrations and review records may form part of the relevant project record and be shared with the authorised participants for that purpose.

If you believe an AI result contains inaccurate personal information or exposes information that should not have been shared, contact us. The rights in section 12 apply to personal information in AI inputs and outputs as well as other project records.

5 Why we use information and our legal bases

Where PlanProof is the controller, we use the following legal bases under UK data protection law. Where we act as a processor, the business customer determines the lawful basis for the project processing and instructs us through the service and our processing agreement.

  • Providing a service to you: we use information necessary to create and administer your account, carry out your requests and provide our contracted service on the basis of our contract with you, or steps you request before entering that contract. This basis applies only where the contract is with the individual whose information is used and the processing is necessary.
  • Business account contacts and support: we use staff and representative contact details to administer a business customer’s account and answer enquiries in our legitimate interests in operating the service and communicating with the appropriate people.
  • Security and reliability: we use relevant technical information and activity records in our legitimate interests in protecting accounts and projects, preventing misuse, identifying faults and maintaining a reliable service.
  • Project records and requested AI assistance: where we determine a controller purpose for these activities, we rely on legitimate interests in helping authorised participants document, understand and manage their project. The business customer remains responsible for its own basis when we process project content on its instructions.
  • Legal obligations and claims: we use information needed to meet applicable tax, accounting and data protection obligations because the law requires it. Where necessary to establish, exercise or defend legal claims, we rely on the relevant legitimate interests in resolving those claims.
  • Optional marketing and device tracking: where consent is required, we ask separately and provide a way to withdraw it. The actual uses and controls are described in sections 10 and 11.

Legitimate interests do not give us an unrestricted right to use information. We must consider necessity, reasonable expectations and the effect on the people concerned. You can object to processing based on legitimate interests. If special category information is needed, an additional legal condition must also apply.

Providing information for a project or AI request does not grant general permission for unrelated advertising, public case studies or model training. Any new purpose must have its own lawful justification and appropriate privacy information.

6 Who information is shared with

Project information is shared with the builder, homeowner and other participants according to their role, project access and the actions taken within the service. A photograph or comment shared into a project may therefore be visible to other authorised participants. Project exports and documents can also be shared by those participants under their own responsibilities.

We use suppliers to provide the service. These include Supabase for relevant database, authentication and storage services; Vercel for application hosting; Resend for service emails; and OpenAI for the AI processing described above. Suppliers receive the information needed for their functions, subject to the applicable contracts and their defined roles. We use postcodes.io to find addresses from a postcode you type, and Ideal Postcodes where house-level address lookup is switched on. Phone alerts are delivered through the push service of the phone or browser maker (Apple, Google or Mozilla). The alert’s content is encrypted so that service cannot read it, and an alert never includes an amount.

Within PlanProof, the owner can see account and company details on an internal administration page, to give support, keep the service secure and suspend an account where necessary. Each view or change made there is recorded before it happens.

We do not currently use analytics, advertising or error-monitoring services, and PlanProof does not process card payments.

We may also disclose relevant information to professional advisers, insurers, courts, regulators or law-enforcement bodies where necessary and lawful. If the business is sold or reorganised, relevant information may be transferred subject to appropriate confidentiality, legal safeguards and notice where required.

7 Processing outside the United Kingdom

Some suppliers and their authorised support providers may process information outside the UK, including in the United States. The location of a database alone does not determine every place from which information can be processed or accessed. PlanProof’s database and stored files (Supabase) and its server code (Vercel) are hosted in Stockholm, Sweden.

Where personal information is transferred outside the UK, we rely on UK adequacy regulations or on the safeguards in our suppliers’ data processing terms, such as the UK International Data Transfer Addendum.

You can contact us for details of the safeguards that apply to your information and how to obtain a copy. We may redact confidential commercial information while explaining the protection provided.

8 How long we keep information

Retention depends on the type of record and the reason it is needed. We do not treat a project’s history as permission to keep every item of personal information indefinitely.

  • Account and contact information is needed while an account or relationship is active, followed by the period necessary to complete closure, deal with outstanding issues and satisfy applicable obligations.
  • Project agreements, variations, relevant photographs, approvals and correspondence are kept for the project and any justified period afterwards needed for contractual obligations, warranties or legal claims. Relevance, the applicable claim period and any actual dispute determine what must be retained. Unrelated information should not be retained merely because a claim is possible.
  • Billing and accounting records are kept for the applicable statutory record-keeping period and any outstanding accounting issue or claim.
  • Technical logs and support records are kept for the period needed to investigate faults, security incidents and support matters. They do not automatically need the same retention period as the project agreement.
  • AI-provider copies follow the applicable provider terms and settings described in section 4. PlanProof’s stored prompts, illustrations and results follow the purpose and retention rules for the corresponding project records.

Archiving a project, ending a subscription or removing someone’s access does not necessarily erase records needed for the project or a legal obligation. Records protected against ordinary editing can still be assessed for correction, restriction or lawful erasure. A privacy request is considered on its circumstances; preserving evidence does not remove your data protection rights.

Where we must retain part of a record, we will explain the reason and consider whether unnecessary personal details can be removed or access restricted.

9 Security and access

We use proportionate technical and organisational measures to protect personal information, including controls over account and project access. Only people and suppliers with an authorised reason should access the relevant information. Builders’ bank details are stored encrypted. Records of sign-in attempts keep email addresses and IP addresses only in a scrambled (hashed) form. Views and changes on PlanProof’s internal administration page are recorded.

Keep your login details and project invitation links secure. Tell us promptly if you believe an account, link or project record has been accessed without permission. We assess suspected incidents and make any notifications required by law.

10 Cookies and similar technologies

PlanProof uses cookies or similar device storage where needed for sign-in, account security and other essential service functions. Blocking essential technologies may prevent the relevant functions from working.

We do not use analytics or advertising cookies. PlanProof’s cookies keep you signed in and protect sign-in, and the service stores some information on your device, such as work in progress, so that its features work.

If we add an optional technology, such as analytics, it will stay off until you choose to turn it on, and you will be able to change that choice.

11 Service messages and marketing

We send messages needed to operate an account or project, such as invitations, approval requests, security messages and responses to support enquiries. These are separate from promotional messages.

We do not currently send marketing messages. If we start, we will do so only where the rules allow it, ask for consent where it is needed, and stop whenever you ask. Being invited to a builder’s project does not sign you up for PlanProof marketing.

12 Your rights

Depending on the circumstances and the legal basis, you can ask to access your personal information, correct inaccurate information, erase information, restrict its use, or receive and transfer eligible information in a usable electronic format.

Your right to object

You can object to our use of your personal information where we rely on legitimate interests. We will assess your objection and explain our decision. You can object to direct marketing at any time, and we will stop using your information for that purpose.

Withdrawing consent and making a request

Where we rely on consent, you can withdraw it at any time, and we will stop the processing that depends on that consent. Withdrawal does not affect the lawfulness of processing carried out before withdrawal. If we need to retain limited information for a separate legal obligation or to establish, exercise or defend a legal claim, we will explain that reason.

Other rights and exceptions may also apply, including safeguards for any solely automated decision that has a legal or similarly significant effect.

Contact hello@planproof.co.uk to make a request. We may need reasonable information to verify your identity or understand which records you mean. We normally respond within one month. If the law allows an extension or a pause to obtain necessary clarification, we will explain the reason and applicable timing. Requests are normally free of charge.

If we cannot fully comply, we will explain why and how to complain. Where a business customer controls the relevant project information, we will assist it in responding; you do not lose your rights because the information is held in a shared project.

13 Privacy complaints

You can complain about our handling of personal information by emailing hello@planproof.co.uk or writing to our address in section 1. We will acknowledge your complaint within 30 days, investigate without undue delay, keep you informed and explain the outcome.

You also have the right to complain to the Information Commissioner’s Office, the UK data protection regulator. Information about making a complaint is available at https://ico.org.uk/make-a-complaint/. You do not need our permission to contact the regulator.

14 Children and other people in project records

PlanProof is intended for adults managing building projects. Please avoid including children or unrelated visitors in project photographs and do not send their information to AI unless there is a necessary, lawful and appropriately assessed reason. Contact us if you believe a child’s or another person’s information has been included unnecessarily.

15 Changes to this policy

We update this policy when our processing changes and show the current effective date. Where a change materially affects how we use your information, we will draw it to your attention before the new use begins and obtain any consent required.