How Durward handles your information
What we collect on this site, what our keyword research tool reads from Google, and how to ask us about your information.
Last updated 14 November 2026.
Who this notice covers
Durward runs this website. The company is not registered yet, so there is no company number, registered office or ICO registration to show here. The about page explains this, and the security and data page shows the current status of each commitment. To reach us about anything in this notice, use the contact form.
What we collect on this website
Enquiries
If you send the contact form, we receive what you type: your name, your business, your sector and what you tell us about the problem. Please do not put customer, employee, patient, driver or case-level personal data in it. We use your details to reply and, if you ask for work, to scope it. The enquiry is stored on Cloudflare and passed to our CRM. The security and data page lists the providers involved and says which are live. We have not yet set an automatic deletion period for website enquiries.
Analytics
Google Analytics runs only after you accept analytics cookies. You can change your choice at any time with Cookie settings in the footer. If you decline, the analytics script does not load.
Hosting
Cloudflare serves this site and processes the technical data needed to deliver its pages.
Google user data and the keyword research tool
Durward uses a small internal tool to look up how often people in the United Kingdom search for a phrase on Google. It calls the Google Ads API for the Durward team member who signs in. Visitors to this website cannot use it, and it does not read the Google data of anyone who visits the site.
What the tool asks Google for
Access to the Google Ads API, through the scope https://www.googleapis.com/auth/adwords. The tool uses it only to request search volume figures for phrases we type in. It does not read, change or create campaigns, ads, billing details or customer lists. Google offers this API through one permission that is wider than what the tool uses, so the limit is in how the tool is built, not in the permission itself.
What we keep
A sign-in token, held in the secure storage of the signed-in team member’s computer, and the search volume figures Google sends back. Those figures describe phrases, not people. We do not store the contents of any Google Ads account.
What we do not do
We do not sell this data, use it for advertising or pass it to anyone else. Nobody reads it except the team member running the tool. We do not use it to train AI models. Durward’s use of information received from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements.
Withdrawing access
The signed-in person can withdraw access at any time at myaccount.google.com/permissions. We can also delete the stored token on request.
Your rights
Under UK data protection law you can ask us for a copy of the personal information we hold about you, ask us to correct or delete it, or object to how we use it. Use the contact form to ask. If you are unhappy with how we handle a request, you can complain to the Information Commissioner’s Office at ico.org.uk.
Changes to this notice
If we change what we collect or how we use it, we will update this page and its date. For how Google handles data in its own products, see the Google Privacy Policy.