Skip to main content
Parlour

Privacy notice

What Parlour keeps about you, why, for how long, and what you can do about it. Last updated 2026-11-21.

Who we are

Parlour is booking and business software used by salons. This installation is run by Automation Bureau.

When you book with a salon, that salon decides how your details are used; Parlour holds them on the salon's behalf.

Contact about your data: info@automationbureau.co.uk

Clients of a salon

Who
People who book with, or are added as clients by, a salon that uses Parlour
Where it comes from
Typed in by you when you book online or join a waiting list, or by the salon's team when they add or update your record. The team may add notes about your preferences and the colour formulas used on your hair. If you tick the box when booking, that you agreed to marketing emails is recorded with its date. A salon may also bring its existing client list in by uploading a spreadsheet exported from the system it used before.
Why
To book and manage your appointments, recognise you when you return, contact you about an appointment, and give you a consistent service. Marketing is only ever sent if you said yes.
Lawful basis
Performance of a contract with you (your booking) and the salon's legitimate interests in running its business and keeping its client records. Consent for marketing.
How long it is kept
Kept for as long as the salon keeps you as a client. The salon can erase your personal details from your card at any time, and must do so if you ask and it has no legal reason to keep them; your name, phone number, email, date of birth, notes and formulas are then removed for good. A waiting-list request stops being used once its last date has passed. An uploaded spreadsheet is deleted as soon as it has been imported, and after 1 day if it was uploaded but never imported; the short list of rows that needed attention is kept with the record of the import.
Where it is held
The SQLite database on the installation's server.
Who else handles it
The hosting provider that runs this installation's server (Amazon Web Services, London region) stores the database.
Our role
Processor. The salon you book with decides why and how your details are used (it is the controller); Parlour processes them on the salon's behalf.

Allergies, medical alerts and patch tests

Who
Clients of a salon whose team has recorded an allergy, a medical alert or a patch test
Where it comes from
Recorded by the salon's team from what you tell them, and from the result of a patch test they carry out. An allergy or medical alert can only be saved after the team member confirms you agreed to it being kept; that agreement is recorded with its date.
Why
To keep you safe: so that a stylist or therapist sees an allergy or a reason not to carry out a treatment before they start, and so that colour and lash services are only carried out with a patch test that is in date.
Lawful basis
Your explicit consent (this is health information). You can withdraw it by asking the salon to remove the alert.
How long it is kept
Kept until you or the salon remove it. The salon's team can remove an alert from your card at any time, and it is removed with the rest of your details if your record is erased. Each time a card with alerts is opened by the team, that it was opened, by whom and when is written to the audit log.
Where it is held
The SQLite database on the installation's server.
Who else handles it
The hosting provider that runs this installation's server (Amazon Web Services, London region) stores the database.
Our role
Processor. The salon is the controller; Parlour processes this on its behalf and shows it only to the salon's signed-in team.

Appointments

Who
Clients of a salon, and the team members who carry out their appointments
Where it comes from
Created when you book online, or by the salon's team. Later changes (moved, checked in, done, cancelled, no-show) are recorded by you from your booking link or by the team.
Why
To hold your time in the salon's diary, make sure nobody is double-booked, and keep the history of your visits. Your booking link contains a long random code so that only someone with the link can see or change the booking.
Lawful basis
Performance of a contract with you (your booking) and the salon's legitimate interests in keeping records of the work it has done.
How long it is kept
Kept as part of the salon's business records. If your personal details are erased, your past appointments remain but no longer carry your name or contact details. A time that was held while a deposit was not paid is deleted 30 days later by the daily retention job.
Where it is held
The SQLite database on the installation's server.
Who else handles it
The hosting provider that runs this installation's server (Amazon Web Services, London region) stores the database.
Our role
Processor. The salon is the controller; Parlour processes this on its behalf.

Sales and payments

Who
Clients who pay a salon or one of its chair renters, and the salon and renters who are paid
Where it comes from
Created when you pay a deposit online or pay at the salon, and when a chair renter's rent or commission falls due. Card details are typed only into Stripe's own pages and never reach Parlour: we receive the amount, whether it was paid, and Stripe's reference for it. A salon or chair renter who connects a Stripe account does so on Stripe's pages; we keep only the account's reference and whether it can take payments.
Why
To take and record payment for appointments and products, refund when a booking is cancelled in time, show the salon its takings, and keep an accurate record of what chair renters owe the salon.
Lawful basis
Performance of a contract with you (paying for a service) and the salon's legal obligation to keep accounting records.
How long it is kept
Kept as the salon's accounting records, which UK tax law requires a business to keep for at least six years. They are deleted when the salon's account is deleted. Erasing a client's personal details removes their name from these records but not the amounts.
Where it is held
The SQLite database on the installation's server.
Who else handles it
The hosting provider that runs this installation's server (Amazon Web Services, London region) stores the database. Stripe Payments UK Ltd takes card payments. It holds the card details and pays the money to the salon's or the chair renter's own Stripe account.
Our role
Processor. The salon (or the chair renter you paid) is the controller; Parlour processes this on their behalf. Stripe is an independent controller for the card payment itself.

Messages sent to clients

Who
Clients of a salon who have an email address or mobile number on their record
Where it comes from
Written by Parlour when you book, when a booking is moved or cancelled, and the day before an appointment. The salon may enter the details of its own mail server and of a webhook that sends WhatsApp messages for it; the mail password and webhook secret are stored encrypted.
Why
To confirm your booking, tell you if it changes, and remind you of it. Each message, where it was sent, and whether it was really sent is kept so the salon can see what you were told.
Lawful basis
Performance of a contract with you (telling you about your booking).
How long it is kept
The text of a message and the address it went to are removed 365 days after it was written, by the daily retention job; the record that a message of that kind was sent is kept with the appointment.
Where it is held
The SQLite database on the installation's server.
Who else handles it
The hosting provider that runs this installation's server (Amazon Web Services, London region) stores the database. The mail server that carries the email: the salon's own email provider if it has connected one, otherwise the mail server of the operator of this installation. If the salon has connected a WhatsApp webhook, the message text and your mobile number are sent to the service the salon chose to deliver it.
Our role
Processor. The salon is the controller and chooses which services carry its messages; Parlour processes this on its behalf.

The salon's team and chair renters

Who
Owners, managers, reception, team members and chair renters who sign in to a salon on Parlour
Where it comes from
Entered by the business owner when they set up the team, and by each person when they sign in, set a password or ask for time off.
Why
To let each person sign in and see what their role allows, show clients who they can book with, work out when each person can be booked, and record who took a payment or changed a record. A chair renter's clients and takings are shown only to that renter and to nobody else on the team.
Lawful basis
Performance of a contract (the business's use of Parlour) and the business's legitimate interests in running its team.
How long it is kept
Kept while the person is on the team. When someone leaves, their sign-in to that salon is ended at once; their name stays on the appointments and payments they handled, as part of the salon's records, until the salon's account is deleted.
Where it is held
The SQLite database on the installation's server. Passwords are stored only as salted hashes.
Who else handles it
The hosting provider that runs this installation's server (Amazon Web Services, London region) stores the database.
Our role
Processor. The business is the controller for its team's details; for the sign-in account itself (email and password) the operator of this installation is the controller.

The business and its settings

Who
The owner of a salon that uses Parlour
Where it comes from
Entered by the owner when the salon's account is created and when they change its settings.
Why
To run the salon's account, show its name to its clients, and contact the owner about the service.
Lawful basis
Performance of a contract with the business.
How long it is kept
Kept while the business has an account. Deleted, with everything the business holds, when the account is deleted.
Where it is held
The SQLite database on the installation's server.
Who else handles it
The hosting provider that runs this installation's server (Amazon Web Services, London region) stores the database.
Our role
Controller. The operator of this installation decides how the business's own account details are used.

The audit log

Who
Team members whose actions are recorded, and clients whose records they acted on
Where it comes from
Written by Parlour when a member of the team changes something that matters: a booking, a payment, a client's card, a price, a rota; and each time a client card that holds allergy or medical alerts is opened.
Why
So that the business can see who did what and when, and so that access to health information is accountable.
Lawful basis
Legitimate interests of the business in the security and integrity of its records.
How long it is kept
Entries are deleted 730 days after they were written, by the daily retention job.
Where it is held
The SQLite database on the installation's server.
Who else handles it
The hosting provider that runs this installation's server (Amazon Web Services, London region) stores the database.
Our role
Processor. The business is the controller; Parlour keeps this log on its behalf.

Sign-in sessions and abuse protection

Who
Everyone who uses the site
Where it comes from
Created by the site when you sign in (a session cookie) or submit a form (a cookie that protects the form against forgery), and from your connection's IP address when you sign in, book or pay.
Why
To keep the team signed in, protect forms against forgery, and stop password guessing and floods of bookings. These are the only cookies Parlour sets; there are no advertising or tracking cookies and no analytics.
Lawful basis
Legitimate interests: keeping the service working and secure. The cookies are strictly necessary, so no consent banner is shown.
How long it is kept
Sessions expire after 2 days and are removed by the daily retention job. IP addresses and counts of failed sign-ins are held only in memory for at most 1 hour and are never written to disk.
Where it is held
The SQLite database on the installation's server; rate-limit counts in the server's memory only.
Who else handles it
The hosting provider that runs this installation's server (Amazon Web Services, London region) stores the database.
Our role
Controller. The operator of this installation decides how these are used.

Cookies

Parlour sets only the cookies it needs to work: one that keeps the team signed in, and one that protects forms against forgery. There are no advertising or tracking cookies and no analytics, so there is no cookie banner.

Your rights

  • See the personal data held about you (access).
  • Have it corrected (rectification).
  • Have it deleted (erasure).
  • Receive it in a portable form (portability).
  • Object to it being used, or ask for its use to be restricted.
  • Withdraw a consent you gave, such as for marketing or for keeping an allergy on your record.

To use any of them, ask the salon you booked with: it can give you a copy of your record or erase your details from your client card. You can also contact us as above.

How to complain

Please tell us first so we can put it right. You can also complain to the Information Commissioner's Office (ICO): https://ico.org.uk/make-a-complaint/

Privacy Terms Help

Parlour: booking and business software for salons.