Edinburgh RoofingSpecialists
Request assessment

Privacy for roofing enquiries

The enquiry is designed to collect only the contact and property context needed for review. Final controller details and retention terms must be approved when a real operator adopts the site.

Close view of overlapping pitched-roof tiles and junctions
Roofing workers positioned on a large commercial roof
Commercial planning

Data collected

The form asks for issue, property and contact information

A live submission would include the concern selected, observed signs, postcode, property type, access notes, description, name, email, optional phone number and contact preference. A technical timestamp and source label may accompany the form. The first form does not request payment information, identity documents or roof photographs.

  • Required fields are identified before submission.
  • Phone information is optional.
  • Do not include unrelated sensitive personal information in the description.

Purpose

Enquiry data is intended for review and response

Once a verified operator is connected, the submitted details are intended to help understand the property concern, choose an appropriate contact route and decide what further information may be needed. They should not be repurposed for unrelated marketing without an appropriate basis and clear information for the person submitting.

  • Use is limited to the stated enquiry purpose.
  • Access should be limited to approved recipients.
  • Any analytics or marketing tools require separate review and disclosure.
Worker examining a roof from secured access equipment
Safe access
Close view of overlapping pitched-roof tiles and junctions
Roof covering

Storage and sharing

Recipient, retention and deletion rules are launch requirements

The production operator must identify the data controller, approved email or case-management recipient, service providers, retention period and request contact before enabling submissions. Delivery secrets must be stored in the platform environment rather than site code. Test submissions should use non-personal data and be removed after verification.

  • No recipient address is published in the site code.
  • Delivery credentials remain outside the public website.
  • Retention and deletion procedures must be defined before submissions are enabled.

Your choices

A live policy must explain access, correction and objection routes

When the site is adopted, this page must be updated with the operator's legal identity, contact channel, applicable lawful bases and the ways a person can exercise relevant data rights. The current noindex version documents the intended minimum-data design but is not presented as a final operator-specific privacy notice.

  • Controller identity is an explicit launch blocker.
  • The final notice must match the actual data flow.
  • Material changes require content and technical review together.
Edinburgh Old Town roofscape viewed across the city
Edinburgh roofs

Practical answers

Questions before an assessment

Is the form currently connected to a data recipient?

No. Live delivery is disabled until a verified operator and approved recipient are configured and tested.

Does the first enquiry collect photographs?

No. It collects written property and contact context. Files may only be requested later through an approved route.

Who is the data controller?

That information must be added when a real operator adopts the site. The absence of a verified controller is a launch blocker, not a fact to invent.

Next step

Ready to prepare the roof enquiry?

Request assessment

Tell us what you have noticed

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

Step 1 of 1