Privacy: what happens to your roof enquiry data

Before you send the six-step form, understand which personal data it collects, why it is needed, where it goes and how to exercise your rights. This notice also identifies the legal details that are still missing.

Roofing work on a property

What the form collects

The form sends the selected roof-problem category, including flat-roof, chimney, flashing or leadwork concerns; signs you have observed; your written description; postcode; town or city; property type, including tenement or flat; access notes; name; email address; optional phone number; and preferred contact method. It also adds the submission time, a derived roof-type label and a priority score.

Name, email, postcode, roof problem, observed signs, description and the final confirmation are required. The message asks when the problem happened and for relevant weather conditions. Phone, access notes and contact preference are optional; name a factor or landlord only when relevant to access or shared-building arrangements. Do not put payment details, identity documents, health data or unrelated personal details about other people in the description.

Why the data is used

The data is used to deliver and answer the roofing request, understand the property and visible problem, contact you through the route you chose, prevent misuse and investigate delivery faults. The final checkbox records that you asked to be contacted about this request; it is not consent to a newsletter or unrelated marketing.

No lawful basis is yet published for each purpose. Until the legal controller and basis are named, do not treat this notice as complete or assume that the final contact checkbox supplies every basis required for later or unrelated use.

Where the form sends your data

Your browser sends the form to the website's roof-inspection endpoint. The server checks the allowed origin, request size and required fields, rejects invalid email syntax and can use Cloudflare Turnstile when that security control is enabled. Responses are marked no-store.

The application has no customer database. A valid request is delivered to a configured email inbox or webhook. Copies may therefore exist in Cloudflare service logs, the chosen email or webhook service, and the receiving mailbox. This notice does not yet name the exact processors, processing locations or any international-transfer safeguards.

How the priority indicator works

Fixed points are added for an active leak, dripping after rain, debris at ground level and a commercial, managed or shared property. The total becomes Standard, Medium, High or Urgent. This label helps sort the reported circumstances; it does not inspect the roof, select a repair, provide a diagnosis, make a safety assessment or guarantee a response time.

The score does not make a legal or similarly significant decision about you. Do not use its priority label to judge safety or expect a particular response. If there is immediate danger, keep clear and use the relevant emergency, utility or building-safety service.

How long copies should be kept

The application keeps no database copy. An email or webhook copy should remain only while it is needed to answer the request, manage relevant follow-up, resolve a complaint or delivery fault, protect the service from misuse, or meet a documented legal requirement. A priority label does not justify keeping it for longer.

When the request and relevant follow-up are closed, the copy should be deleted or anonymised unless a recorded reason requires continued retention. Security and delivery logs may follow separate periods. No normal retention period for the receiving copies is currently published, so you cannot yet know how long they may be kept.

Your rights, objection and complaint route

Depending on the lawful basis and circumstances, you may have rights to access, correction, erasure, restriction, portability or an explanation of how your personal data was used. You may also have a right to object. The rights that apply can depend on the basis used.

To raise a privacy request, call 01383 252038, identify the roof request and say that it concerns personal data. Proportionate details may be needed to locate the copy and verify the requester. You can complain to the Information Commissioner's Office if the concern is not resolved.

Browser storage and security

Form answers are held in page memory while the modal is open and are reset when a new form session starts. The form code does not write those answers to localStorage or sessionStorage. Transport uses HTTPS on the production site, the Worker rejects disallowed origins, and request-size, validation, spam-trap and optional Turnstile controls reduce misuse; no internet transmission can be described as risk-free.

If the form fields, recipients, delivery route, security controls, retention rules or uses change, this notice may no longer describe the processing. Check the current notice before sending new details. No internet transmission can be described as risk-free.

Controller details are still missing

The public trading name is The Roofing Specialists, but the legal controller identity must be published together with a contact address. This notice is incomplete. Do not send personal data through the form until you can identify who controls it and how to contact them.

The notice also does not yet name the lawful basis for each purpose, exact processors, international-transfer position, retention periods or a complete rights contact. Without those facts, you cannot make a fully informed decision about sending personal data.

Tell us what you have noticed

Six short steps collect the details needed to route your enquiry. Stay at ground level and never climb onto a roof to gather information.

Step 1 of 6