Skip to content

This website

How we handle enquiries you send us

This describes what happens to information sent through the forms on this website. If Quarrymoor Tiling collects information in other ways — in person, by phone, or through other services — that isn't described here.

Who this is for

People who submit a form on this website — typically to make an enquiry, booking request, or similar.

Who receives what you send

The business named on this site, Quarrymoor Tiling, receives your enquiry and decides how to use it. They are the organisation the enquiry is for.

This website is hosted by ThemeSmith. When you submit a form, ThemeSmith stores the submission so Quarrymoor Tiling can read it. ThemeSmith does not use your enquiry to market to you.

What the form asks for

The visible questions on this website’s forms, today:

  • Form 1: Your name; Email; Phone — only if you'd rather talk; Where the house is; What the floor is doing.

What is stored with the enquiry

The form system stores more than the answers you can see. The list below is taken from the storage record itself, so a field we collect cannot go unnamed here.

  • The answers you type into the form. Every field on the form is stored as you sent it — name, email, phone, message, and any other questions on that form.
  • Your name. A copy of the name field, stored separately so the business can find the enquiry.
  • Your email address. A copy of the email field, stored separately so the business can reply.
  • Your telephone number. A copy of the telephone field, when the form asks for one.
  • Internet address (IP address). The IP address of the device that submitted the form. This is personal data. It is used to detect spam and abuse.
  • Browser and device details. The browser’s user-agent string (browser name, version, and a description of the device). Used to detect spam and diagnose failed submissions.
  • The page you came from. The referring URL, when the browser sends one.
  • The page you submitted from. The URL of the page that contained the form.
  • Spam and behaviour notes. Technical notes stored with the enquiry: a hashed copy of the IP address, spam-detection reasons, and any behavioural signals the form script sent (for example time-to-submit). These are used to detect spam.
  • Whether you ticked the consent box. A yes/no record of the consent checkbox on the form, when the form shows one.
  • How you found this page. Campaign and click identifiers the browser sent with the form (for example utm_source, gclid). Used to tell the business which page or campaign the enquiry came from.
  • Files you attach. If the form accepts uploads, the files themselves are stored separately and deleted on a shorter timetable than the enquiry record.

Operational records kept with the same enquiry

  • Whether the business has read the enquiry. Internal status (new, read, replied, archived, spam) so the business can manage their inbox.
  • When the enquiry was opened. A timestamp recorded when the business first opens the enquiry.
  • When the enquiry was archived. A timestamp recorded if the business archives the enquiry.
  • Whether the business was emailed. A flag recording that a notification email was sent to the business.
  • When the business was emailed. The time the notification email was sent.
  • Whether an automatic reply was sent. A flag recording that this site sent you an automatic acknowledgement, if that is switched on.
  • When the automatic reply was sent. The time an automatic acknowledgement was handed to the email provider.
  • Automatic-reply delivery record. An internal key that stops the same acknowledgement being sent twice.
  • Automatic-reply delivery status. Whether the acknowledgement was accepted by the email provider.
  • When an automatic reply was attempted. The time the site tried to send an automatic acknowledgement.
  • Email-provider message id. The email provider’s id for the automatic acknowledgement, if one was accepted.
  • Automatic-reply failure code. An internal code if the automatic acknowledgement could not be sent.
  • Spam score. A number the platform computes to decide whether the submission looks like spam.
  • Spam flag. Whether the platform marked the submission as spam.
  • Platform health-check flag. Marks ThemeSmith’s own form-liveness probes so they are not shown as customer enquiries.
  • Simulator flag. Marks enquiries created by ThemeSmith’s Growth simulator, not by a real visitor.
  • How long this enquiry will be kept. The retention period that applied when the enquiry arrived, stamped on the record so a later policy change does not silently re-age it.
  • A snapshot of the site’s growth work at the time. An internal snapshot of the site’s growth-engine state when the enquiry arrived. It is not something you type; it is stored so the business can see when enquiries landed relative to work on the site.
  • When you sent the enquiry. The time the form was submitted. Deletion is counted from this moment.

How long we keep it

Enquiries are kept for 180 days from the day they arrive, then deleted automatically. The period that applied when you submitted is stamped on the record, so a later change of policy does not quietly keep an older enquiry longer.

Files attached to a form are deleted after 90 days, even if the enquiry itself is kept until 180 days. The written record can remain after the files are gone.

If you want a copy, a correction, or deletion

Ask Quarrymoor Tiling at the contact details published on this website. Say which enquiry you mean if you can — the email address you used is usually enough. You can also complain to the Information Commissioner’s Office if you are in the United Kingdom.