Knotless

Privacy Policy

Last updated: 13 November 2026

1. Introduction

Knotless ("we", "our", "us") is a booking management platform for beauty and event professionals. This Privacy Policy explains how we collect, use, store, and protect personal data when you use our platform at knotless.co.uk (the "Service").

Email: hello@knotless.co.uk.

If the business moves to a company we control, or is sold, the personal data we hold moves with it and continues to be handled under this Privacy Policy. We'll tell you before it happens, and you can close your account if you don't want to continue.

We are committed to protecting your privacy in accordance with the UK General Data Protection Regulation (UK GDPR) and the Data Protection Act 2018.

2. Data Controller & Processor

For Providers (service professionals): You are the data controller for your clients' personal data. Knotless acts as a data processor, processing client data on your behalf in accordance with our Terms of Service and Data Processing Agreement.

For Clients (couples and other clients of a provider): The provider you contact or book with is the data controller for your enquiry and booking details, and Knotless processes them on that provider's behalf. Knotless is the data controller for your client portal account and for the single contact record (your email address) we keep so that, when you sign in, you can see your bookings with every provider who uses Knotless. Providers never see each other's records about you.

For Team members: If you work in a provider's team, that provider is the data controller for the work records about you in their account, such as bookings assigned to you and messages you wrote. When you leave a team, your access to the team is removed, but your name stays on messages and records you created, so the provider keeps an accurate record of their bookings. Knotless is the data controller for your Knotless login, which leaving a team does not remove.

For platform data: Knotless is the data controller for data relating to provider accounts, billing, and platform usage.

3. Data We Collect

Provider Account Data

  • Name, email address, phone number
  • Business name and website
  • Profile and company images
  • Business location
  • Payment and subscription information (processed by Stripe)
  • Push-notification tokens for the devices you use the Knotless app on

Client Booking Data

  • Full name, email address, phone number
  • Event date and time
  • Venue name, address and country as typed, and the Google Maps place reference it was matched to
  • Party size and booking preferences
  • Allergy and patch-test notes, where a provider records them
  • Wedding contacts a provider records for the day, such as the planner, maid of honour or venue coordinator: their name, role, phone number, email address, company and notes
  • Communications with the provider
  • Invoice and payment records
  • Document uploads and checklist responses
  • When you accept a provider's terms on a Knotless page: the date and time, and the IP address you accepted from

Run sheets. A provider can print a run sheet of the wedding day and send links to it. The client's name, phone number and email address, and the wedding contacts' names, roles, phone numbers, email addresses and companies, are on the provider's printed run sheet and on each team member's own run sheet link. They are on a run sheet link the provider shares with someone else, such as a photographer or venue, only if the provider turns that on for the booking. Run sheets never include prices, allergy or patch-test notes, or the provider's notes about a wedding contact.

Flight Passenger Data

For flights a provider books through Knotless, we collect each passenger's title, name, gender, date of birth, email address and phone number. Passengers can be the provider or other people travelling with them.

Usage & Technical Data

  • IP address, browser type, device information
  • Pages visited, features used, where on a page the pointer clicks or moves, and which form fields fail a check, never what was typed in them (via PostHog analytics, on by default; you can opt out). This is counted without linking it to your name or account, except where you first came from, described below
  • A pseudonymous code for your business (not your name or email) on records of key actions, such as creating a booking, so we can see how businesses use Knotless. To stop the records that carry this code, turn off "Help improve Knotless" in Settings › Your data on the Knotless website. We still count trials and plan changes, but without this code or anything else that links them to your business
  • The promotion you signed up under, if any, so we can honour the offer and see which campaigns work
  • Where you found us, stored with your account when you sign up as a provider: the campaign tags in the link you first arrived by (for example "instagram"), the website that sent you there (its name only, not the page), the Knotless page you landed on, and your answer to "How did you hear about Knotless?" if you give one. We use this to see which channels bring providers to Knotless. Our analytics record of your sign-up carries the campaign tags, your answer and whether another website referred you (not which one). Our sign-in provider, Clerk, also keeps a copy of the campaign tags, referring site and landing page with your login, from the moment you sign up
  • Counts of how many times the QR codes on our printed marketing are scanned. We don't record who scanned them
  • Session recordings of the provider dashboard (only if you allow them, via PostHog), kept for up to 30 days. A recording shows how you moved around and what you clicked. Text is hidden apart from menus and page titles, so clients' names and details are not recorded, and pictures, previews, typed entries and the contents of network requests are left out
  • Authentication data (managed by Clerk)
  • Error logs and performance data

Marketing list

If you join our waitlist or newsletter, we keep your email address, your type of business if you tell us, and where you signed up (held by Resend) until you unsubscribe.

4. How We Use Your Data

  • To provide and maintain the booking management Service
  • To process bookings, send emails, and manage workflows on behalf of providers
  • To process subscription payments and billing
  • To send transactional emails (booking confirmations, notifications)
  • To provide customer support
  • To improve the Service through analytics and usage patterns
  • To detect and prevent fraud or security issues

5. Legal Basis for Processing

We process personal data under the following legal bases:

  • Contract: Processing necessary to provide the Service to providers and facilitate bookings
  • Legitimate interest: understanding how Knotless is used so we can improve it (analytics, including the pseudonymous business code above); finding and fixing errors; security and fraud prevention; running the client portal. You can object to any of these by emailing hello@knotless.co.uk, or, for the records of your business's key actions, by turning off "Help improve Knotless" in Settings › Your data on the Knotless website.
  • Consent: Marketing communications and session recordings
  • Legal obligation: Tax records, compliance requirements

6. Sub-processors and Third-Party Services

We use third-party services to run the Service, including hosting, file storage and the database (Cloudflare and PlanetScale), sign-in (Clerk), payments and invoicing (Stripe and Square), email (Resend), analytics and error reporting (PostHog), background jobs (Inngest), the AI features (Anthropic), finding venues, maps, venue photos and travel times (Google Maps Platform), and flight booking (Duffel).

The full list, with what each service does, the personal data it receives, where it is processed and how transfers out of the UK are protected, is on our sub-processors page. That page is the list referred to in section 8.2 of our Terms of Service. It also lists the services that are not our processors, such as Google Maps, which acts as an independent controller under its own terms.

We require data processing terms with each processor.

A provider can also choose to connect their own Google Calendar. Section 6b explains what that involves.

6a. The AI Assistant

Knotless includes AI features for providers: an assistant that answers questions about their own business, an assistant that helps build workflows, and a trip planner.

What it can read. The question-answering assistant answers by running a fixed set of read-only queries against the asking provider's own data. Those queries can return client names, email addresses and phone numbers; booking dates, times, party sizes, prices, venues and cancellation notes; invoice amounts and status; flight bookings; and the recipient, subject and delivery status of emails the provider has sent. It is restricted at the database level to the data of the provider who is asking. The trip planner reads the provider's bookings from the past year onwards and every existing trip with its bookings, whatever their date: dates, status, client names, and the venue's city and country. The workflow builder assistant reads the provider's workflow, template names and checklist names.

Where it is sent. The provider's request and the data each feature reads are sent to the Claude API of Anthropic, PBC. Anthropic is the only AI model provider Knotless uses. Anthropic, PBC is based in the United States, and this data may be processed in the United States and other countries; section 9 explains how international transfers are protected. Under Anthropic's commercial terms, Anthropic does not use data sent through its API to train its models, and deletes it within 30 days, except where it must keep it longer to enforce its usage policies or comply with the law.

What is kept. Assistant conversations are saved in the provider's account so they can see their history, and are deleted on the schedule in section 7. We send technical diagnostics (model, timings, token counts and an account identifier) to Langfuse. Langfuse does not record the content of questions or answers.

For couples. If you are a client of a provider who uses Knotless, your name, contact details and booking details may be included in what is sent to Anthropic when that provider uses the AI features. Your provider is the data controller for that processing.

6b. Google Calendar

A provider can connect the calendar in their own Google account. Google's own permission screen asks the provider to allow each use below when they turn it on.

  • Busy times. Knotless reads when the provider's calendar is busy, so it can warn them about a clash when they book. It reads start and end times only, never event titles, descriptions or guests. They are shown to that provider and not stored on our servers (the Knotless app may keep a copy on the provider's device).
  • Calendar invites. If a solo provider or a team lead turns calendar invites on, Knotless adds an event to their Google calendar for each booking that's accepted or booked (and any other booking they choose to send). It keeps upcoming events up to date as the booking changes. Cancelling a booking removes its upcoming events, and turning invites off removes upcoming events unless the provider chooses to keep them; in both cases events for days that have passed are left as they are. Deleting a booking removes all of its events. On a team there is one event for each team member working the day. Each event contains the couple's name, the business name and, on a team, the team member's name; the venue name and address, including the client's address when that is where the team is going; that person's start and finish times, which allow for travel each way (worked out from the business address or the team member's home, which is never itself included) and an hour after; a link to their run sheet when there is one; and, as the only guest, the email address of the team member, when the provider has chosen to invite them. Google emails those team members the invitations. Events never contain clients' phone numbers or email addresses, prices, payment details, allergy or patch-test notes, or the provider's notes. Knotless never changes any other event in the calendar.

What is kept, and for how long. The provider's Google sign-in, and the access it grants, is held by our sign-in provider, Clerk, not in our database. For each event it added, Knotless keeps only what it needs to update and remove it: Google's event id and link, a fingerprint of what it last wrote, and the guests it added — not a copy of the event's content. These records are deleted when Knotless removes the event, and with the provider's account. If the provider deletes an event in Google Calendar themselves, Knotless keeps only its event id, so that it doesn't add the event back. When a couple's data is erased, Knotless removes their events from the calendar, past ones included. When a provider deletes their Knotless account, Knotless first removes the upcoming events it added; if it can't (for example because Google access was already removed), those events stay in the provider's own Google calendar for them to delete.

Google Calendar is a service the provider chooses and holds an account with: what Knotless adds to it is held by Google under the provider's own agreement with Google. A provider can turn calendar invites off in Settings › Calendar, and can remove Knotless's access at any time from their Google Account permissions page.

Knotless's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. We use it only to provide the features above: we don't sell it, use it for advertising, let our staff read it except with the provider's permission or where security or the law requires it, or use it to develop, improve or train generalised AI or machine learning models. Nothing Knotless reads from or adds to Google Calendar is given to the AI assistant described in section 6a.

7. Data Retention

We keep personal data only as long as we need it. A daily automated job enforces the periods for data in our own database; the service that holds the rest deletes it on its own schedule:

  • Provider accounts, and the client records, bookings, documents and files in them: until the provider deletes their account. Deletion is immediate and permanent, with no recovery period, so download your clients and bookings first (Settings › Your data).
  • Couples' details held by a provider: until that provider deletes them or deletes their account, or until a couple's erasure request is carried out. Copies kept in records of sent emails, in form submissions and in providers' notifications are cleared or deleted on the schedules below. A couple's contact record is removed automatically once no provider holds a record of them, unless they have signed in to the client portal.
  • Email content sent through Knotless (the message and the details merged into it): deleted 90 days after sending. The send record (recipient, subject, delivery status) is deleted 24 months after sending.
  • In-app notifications to providers, which can name a couple: deleted 90 days after they are created.
  • Enquiry and booking-form answers: cleared 12 months after submission.
  • AI assistant conversations: each message is deleted 12 months after it was sent, and a conversation's title is removed 12 months after the conversation started.
  • The IP address recorded when a couple accepts a provider's terms: deleted 6 years after acceptance.
  • Payment records are held by Stripe, our payment processor, not by Knotless. Stripe keeps them for at least 6 years for tax and accounting purposes.
  • Booking messages between a provider and a couple: kept with the booking, and deleted when the booking, the client record or the provider's account is deleted.
  • Client portal accounts: until the couple asks us to delete it.
  • Google Calendar invites: Knotless's records of the events it added (Google's event ids and the guests it added) are deleted when Knotless removes the event, and with the provider's account; for an event the provider deleted in Google Calendar, only its event id is kept. The events themselves are in the provider's own Google calendar; section 6b says when Knotless removes them.
  • Analytics events: deleted automatically at the end of the retention period set in our analytics account. Session recordings: up to 30 days.
  • Server logs: 7 days.
  • Background job records (Inngest): kept by Inngest for a limited period, then deleted automatically.
  • Backups: deleted data can remain in encrypted database backups for a limited time, until those backups expire.
  • Marketing list: until you unsubscribe.

8. Cookies and analytics

  • Essential cookies: Required for signing in (Clerk) and for the Service to work. These cannot be switched off.
  • Analytics: We use PostHog, through our own domain, to count visits, see which features are used and where people click or move the pointer on a page, and record errors, so we can fix problems and improve the Service. This is on by default. UK law allows this kind of statistical analysis as long as we explain it and make it easy to opt out (the Privacy and Electronic Communications Regulations, as amended by the Data (Use and Access) Act 2025). It stores an identifier in your browser. It counts how the Service is used; apart from where you first came from (below), it doesn't link that to your name or account, and isn't used for advertising or shared with advertisers. To opt out, use Cookie Settings. Once you opt out, our analytics stops collecting anything from your browser, including error reports.
  • Where you first came from: while analytics is on, when you first arrive from another website or by a link with campaign tags, we keep a note in your browser of where from, for up to 30 days. Nothing is sent anywhere unless you sign up as a provider, when it is stored with your new account (see "Usage & Technical Data" above). Opting out of analytics deletes it.
  • Session recordings: Only if you allow them, in the cookie notice, on the dashboard or in Cookie Settings. Only the provider dashboard is recorded, with clients' details hidden. Kept for up to 30 days. Pages opened from a link sent to you, such as a proposal, a team invite or a calendar link, are never recorded.

You can change these choices at any time in Cookie Settings, linked in the site footer.

9. International Data Transfers

Some of our service providers are outside the UK, mainly in the United States. Where personal data goes to them we rely on: UK adequacy regulations (for the EU and EEA, for example PostHog's and PlanetScale's EU hosting); the UK Extension to the EU-US Data Privacy Framework (for example Cloudflare, Clerk, Stripe, PlanetScale, PostHog, Resend, Mux and Expo); or the UK Addendum to the EU Standard Contractual Clauses (Anthropic). Our sub-processors page shows which applies to each.

10. Your Rights

Under UK GDPR, you have the right to:

  • Access your personal data
  • Rectify inaccurate personal data
  • Erase your personal data ("right to be forgotten")
  • Restrict processing of your personal data
  • Data portability — receive your data in a structured format
  • Object to processing based on legitimate interest
  • Withdraw consent where processing is based on consent

To exercise any of these rights, email us at hello@knotless.co.uk. We handle every request ourselves and will respond within one month of receiving it.

Couples can correct the phone number their providers hold for them from the client portal. Providers can download their clients and bookings (on a team, the team lead can), and delete their account, from Settings › Your data.

If you are a client of a provider who uses Knotless, that provider is the data controller for your booking data, and you can also contact them directly. If you ask us directly to see, correct or delete your booking details, the providers who hold them have authorised us to act on that request, and we will let them know.

Complaints. If you're unhappy with how we've handled your data, email hello@knotless.co.uk with "Complaint" in the subject. We'll acknowledge it within 30 days and tell you the outcome without undue delay. You can also complain to the Information Commissioner's Office (see section 14).

11. Data Security

We implement appropriate technical and organisational measures to protect personal data, including:

  • Encryption in transit (TLS/HTTPS) and at rest
  • Access controls and authentication
  • Regular security assessments
  • Secure hosting on Cloudflare, with the database on PlanetScale
  • Presigned URLs for file access (no public storage)

12. Children's Privacy

The Service is not directed at individuals under the age of 18. We do not knowingly collect personal data from children.

13. Changes to This Policy

We may update this Privacy Policy from time to time. We will notify you of significant changes by email or by posting a notice on the Service.

14. Contact Us

For any questions about this Privacy Policy or to exercise your data rights, contact us at:

Email: hello@knotless.co.uk

You also have the right to lodge a complaint with the Information Commissioner's Office (ICO) at ico.org.uk.