Privacy Policy
Last updated: 14/10/2026. Written with reference to UK GDPR and the Data Protection Act 2018 — confirm and amend if you operate elsewhere.
Two different kinds of personal data, covered two different ways
-
This Policy explains how we handle personal data about YOU as our client (or a visitor/prospect) — your name, business details, email, and payment information.
-
It also explains — separately, in Section 6 — how our automations handle personal data belonging to YOUR OWN customers, callers, or contacts, which we process only as your processor, on your instructions. Full processor obligations are in the Data Processing Schedule attached to our Terms & Conditions.
1. Who we are
D(Ai)LY Automations ("we," "us," "our") is the data controller for the personal data described in Sections 2–5 of this Policy — that is, data about you as our client, prospect, or website visitor. Contact us about privacy matters at hello@dailyautomation.co.uk
Section 6 explains a different role we sometimes play: processing personal data that belongs to your own customers, on your behalf, when you use one of our automations. In that role, we act as a processor, not a controller — your own privacy notice to your customers governs that data, not this Policy.
2. What personal data we collect about you
Category
Examples
Identity and contact details
Your name, business name, role, email address, phone number
Business and billing details
Business address, VAT/registration details, selected payment plan, invoices, payment amounts and dates, transaction references, payment status, and account balances.
Communications
Emails, messages, and call notes between us relating to onboarding, support, or account management
Technical/account access data
Records of which platforms and credentials you have connected for your automation (not the credential secrets themselves, which are stored by the relevant platform, e.g. n8n or Google), and configuration choices you make (e.g. chase intervals, chat IDs)
Website data (if applicable)
Standard analytics/cookie data if you visit our website — see Section 9
3. How and why we use your personal data
Purpose
Lawful basis (UK GDPR)
Providing, configuring, and supporting your automation(s)
Performance of a contract with you
Invoicing, collecting upfront and recurring payments, managing the 12-month commitment and cancellation notices
Performance of a contract; legal obligation (accounting/tax records)
Responding to your enquiries and providing customer support
Performance of a contract; our legitimate interest in supporting our clients
Improving our automations and service offering
Our legitimate interest in running and improving our business
Complying with law (e.g. tax, accounting, or a legal request)
Legal obligation
4. Who we share your data with
We may share your personal data (as our client) with:
-
Our own service providers who support our business operations — for example, accounting or invoicing tools, and cloud storage/email providers we use to run our business.
-
The third-party platforms your automation runs on (Vonage, n8n, Google/Gmail, Telegram, or Meta/WhatsApp, as applicable), to the extent needed to set up and operate your account with them.
-
Professional advisers (accountant, solicitor) where reasonably necessary.
-
Any party we are legally required to share it with (for example, HMRC, or in response to a valid legal request).
We do not sell your personal data.
5. How long we keep your data
We keep your client account and billing records for as long as our contract with you continues, and for [6 years] afterwards to meet UK accounting and tax record-keeping obligations. We keep general enquiry/prospect correspondence for as long as reasonably useful for following up, or until you ask us to delete it, whichever is sooner.
For either payment option, we may record your selected plan, payment history, outstanding amounts, renewal and cancellation dates, and communications about billing or support. Where a payment processor is used, it may process payment details under its own privacy terms; we should identify the actual provider in our published notices. We do not need to retain full card details to manage the agreement.
6. Data we process on your behalf (about your customers)
⚠ This is the part that matters most for your own customers, not you
• When you use one of our automations, it necessarily reads, stores, or acts on personal data belonging to your own customers, callers, or contacts — not just data about you.
• For that data, you are the controller and we are your processor, acting only on your instructions, as set out in the Data Processing Schedule attached to our Terms & Conditions. This Policy does not create rights for your customers directly against us — they should look to your own privacy notice, and you should ensure you have one that covers this.
6.1 — Missed Call Follow-Up Automation
-
Caller phone numbers of anyone who calls your business number and is not already a known contact, stored in a "known contacts" table so they are not messaged more than once.
-
The content of the automated SMS follow-up sent to unknown callers.
-
Phone numbers of anyone who messages your WhatsApp number or texts your business number back, logged for the same "already known" purpose.
-
A record of missed-call follow-ups sent, shared with you via Telegram so you can see what happened.
6.2 — Invoice & Quote Chaser Automation
-
The email addresses, subject lines, and relevant message metadata of people you have sent invoices or quotes to, read from your sent mail to determine whether a chase-up is due.
-
Drafted chase-up email content, created inside Gmail as a draft for your review — not sent without your action.
-
A record of chase status per client/thread (e.g. reference numbers, whether they have replied or been told to stop), shared with you via Telegram.
6.3 — Future automations
Any automation we add in future will process personal data belonging to your customers only as needed to deliver that automation, and only as your processor under the same Data Processing Schedule — we will describe the specific data involved in the Schedule or configuration document for that automation when it is added.
6.4 — Where this data lives
This data is stored within the workflow platform running your automation (typically n8n, either our shared cloud instance or your own), and passes through the third-party platforms listed in Section 4 as needed to operate (for example, Vonage for SMS, Google for email, Telegram for notifications). We do not copy this data out for our own separate use.
7. International transfers
Some of the third-party platforms involved (for example, Telegram, or Meta/WhatsApp) may process data outside the UK/EEA. Where this happens, we rely on the safeguards those providers put in place (such as standard contractual clauses) as part of their own compliance obligations. We recommend checking the current data-transfer terms of any platform your automation connects to, as these can change.
8. Your rights
If you are our client (i.e. the data in Sections 2–5 is about you), UK GDPR gives you rights including: access to your data, correction of inaccurate data, erasure in some circumstances, restriction of processing, data portability, and objection to certain processing. To exercise any of these, contact us using the details in Section 1.
If you are a customer of one of our clients (i.e. your data falls under Section 6), please contact that business directly, as they are the controller of your data — we will assist them in responding to you where needed.
You also have the right to complain to the UK Information Commissioner’s Office (ICO) at ico.org.uk if you believe your data has been mishandled.
9. Cookies and website data
Our website, dailyautomation.co.uk, is built on Wix.com. Like all Wix-hosted sites, it uses a set of essential cookies for core functions such as security, load balancing, and session handling — these do not require visitor consent.
We use Wix’s own built-in site analytics to understand visitor traffic and behaviour on dailyautomation.co.uk. As of this Policy’s last update, we have not added separate third-party trackers such as Google Analytics or a Meta/Facebook Pixel.
Booking a call through our site takes you to Cal.com, a separate website with its own cookie and privacy practices that we do not control — see Cal.com’s own privacy policy for details before booking.
You can control or block cookies at any time through your browser’s own settings; blocking essential cookies may affect how the site functions.
10. Children
Our services are provided business-to-business and are not directed at, or knowingly used by, children. We do not knowingly collect personal data from children.
11. Security
We take reasonable technical and organisational steps to protect personal data, including scoping third-party credentials (for example, Gmail API access) to the minimum permissions needed for each automation, restricting who receives operational notifications, and relying on the security measures of the reputable third-party platforms listed in Section 4. No system is completely secure, and we cannot guarantee absolute security.
12. Changes to this Policy
We may update this Policy from time to time, including to reflect new automations or third-party platforms. We will note the "last updated" date at the top, and for material changes, will make reasonable efforts to let existing clients know.
13. Contact us
Questions or requests about this Policy: D(Ai)LY Automations | tommy@dailyautomation.co.uk