Williams, Stanley & Co.

WS Operations Platform: privacy notice

How the firm's internal operations platform (WSOP) uses personal data. Last updated 20 November 2026.

Who we are

The WS Operations Platform (WSOP) at operations.williamsstanley.co is the internal system Williams, Stanley & Co. uses to run its work for hospitality clients: compliance deadlines, statutory and tax filings, company secretarial work, proposals, billing and client onboarding. The firm decides how and why the personal data in it is used, and is the controller of that data. The firm is Williams, Stanley and Co. Limited, a company registered in England and Wales with number 05860058, and is registered with the Information Commissioner's Office as a data controller.

This notice covers the platform. The firm's public website has its own notice at williamsstanley.co/privacy-policy.

Questions about this notice or your data: info@williamsstanley.co, or +44 (0)20 7097 6703.

Whose data we hold

  • Our own staff, who sign in to the platform, and everybody who works for the firm, whether or not they sign in.
  • People who apply to work for the firm.
  • Our clients, and the people at our clients we work with: owners, directors, finance contacts.
  • People we send a link to: a proposal to accept, an onboarding or offboarding form to complete, questions to answer before a company's confirmation statement, a company document to sign, or a procedure to read.
  • People named on the public register at Companies House for the companies we act for.

What we hold

  • Staff: name, work email address, the access granted, sign-in records, and a log of the changes each person makes.
  • A team record of everybody who works for the firm: work details (name, job, team, line manager, location, work email and phone, start and leaving dates, working pattern), and, held separately, personal details (date of birth, personal email and phone, home address and emergency contacts). Personal details are seen only by the person and People & Development; a line manager sees their team's emergency contacts. Each person can correct their own on My details, and a member of People & Development reading somebody else's is recorded. National Insurance numbers and bank details are not kept in the platform.
  • Holidays and other leave: the dates, the days, who decided and why a request was declined. Sickness: the dates, whether a fit note was given, a short note and the return-to-work talk. Sickness is health information; it is seen only by the person, their manager and People & Development, and colleagues see only that somebody is off. Whoever runs the firm's payroll is given, each month, the days of unpaid leave, sickness and parental leave, who joined and left, and a leaver's holiday left, because these change what is paid; never a note or why somebody was off. That who is off also tells the platform not to ring them on the phone system and to plan less work for them that week.
  • Goals, check-ins, self-assessments, managers' assessments and performance ratings, read only by the person, their line manager and People & Development, and kept with the team record.
  • 1-2-1 meetings between a member of staff and their line manager: the agenda, shared notes, actions and how the person said they were feeling, read only by the two of them and People & Development; and each one's private notes, read only by the person who wrote them.
  • Staff surveys: your answers to staff surveys. Where a survey is anonymous, your answers are stored with nothing that identifies you, apart from the record that you took part, and results are shown only once at least five people have answered; while a survey runs they move only in steps of five answers. People & Development may send a reminder email to colleagues who have not yet answered an open survey, without anybody being shown who has. After a survey closes, its anonymous comments may be sent to Anthropic to write a short summary, which is told never to quote or identify anybody and is kept with the survey. A thank you you give or receive on the thanks wall, and who gave it, is shown to everybody at the firm.
  • Each person's acknowledgement of the firm's policies (which version, when, and the name they typed), and the benefits each person is enrolled in with what the firm and the person pay for them, read only by the person and People & Development, and kept as the firm's employment record.
  • Each member of staff's employment documents (contract, right to work and identity checks, P45 and P60, certificates, signed policies and letters) and the notes and outcomes of their probation, one-to-one and annual reviews. They are read by the person and by People & Development, and by the person's line manager only where People & Development have shared a document with them or the review is theirs to hold. Who opened a person's document is recorded.
  • When somebody applies to work for the firm: their name, contact details, where they heard of the role, the salary they asked for, their CV and covering letter, and our interview notes and scores, to decide whether to offer them the role.
  • Emails sent to the firm's shared mailboxes peopleteam@williamsstanley.co and wsop@williamsstanley.co, handed into the platform to be answered: the sender's name and email address, the subject, the text, and the names (never the contents) of any attachments, which stay in the mailbox.
  • Clients: company and contact details, the services we provide and our fees, filing deadlines and progress, compliance and service records, and notes our team writes about the work.
  • Records a client sends us through the upload link in our reminder emails (bank statements, invoices and the like for their accounts or VAT return): the files themselves, their names and when they arrived. The link names one piece of work and lasts 60 days; it shows nothing back to whoever opens it.
  • From Timely, the time-recording system our staff use: each person's time logged in the week and their weekly capacity, so they are reminded when their timesheet is short.
  • Client due diligence under the Money Laundering Regulations 2017: identity documents, proof of address, date of birth, home address, and the directors and owners of the business.
  • When somebody accepts a proposal, completes a form or signs a company document through a link: the name they type, the email address a verification code was sent to, the internet address they signed from, and when they did it. A signature is kept with a fingerprint of the document's text, so the two can be shown to match.
  • For the directors and persons with significant control of the companies whose company secretarial work we do: whether they have verified their identity with Companies House, when, and the personal code Companies House gave them, as they tell us. And how to reach them, the email address and phone number they or the company give us, with which of them we ask about each company, so our questions go to the right person.
  • From Companies House: the public company profile of each company we act for, looked up by its company number, and of a company a member of staff adds to a fee proposal, found by its name or number. This is the company's status, its accounting reference date, its registered office, and the dates its accounts and confirmation statement were last made up to and are next due. For every client company whose number we hold, we also read the directors, secretaries and persons with significant control that Companies House publishes: their names, roles, the dates they were appointed or notified and left, nationality, occupation, country of residence, service address, the month and year of birth, and the nature of their control. We read it every night so that a change made at Companies House is noticed. Each week we also read the company's filing history and the charges registered against it. When a client's proposal is won we read the same profile and charges once more as a credit check, to decide whether to ask for a Direct Debit or payment in advance; the result is advice to the person billing them, never a refusal. For our anti-money laundering checks, a director or person with significant control who appears on a client company's reading for the first time is put on a list for the AML team to check and screen against the UK Sanctions List. And where a person with significant control over a client is itself a company, we trace the client's owners through Companies House: we read that company's own persons with significant control, and theirs, up to five companies up, until we reach the people at the end of the chain. An owner registered outside the UK, or one Companies House does not hold, is not followed further; our MLRO looks at it.
  • The statutory registers we keep for those companies under the Companies Act 2006: the members and their shareholdings, the directors and secretaries, the persons with significant control, and charges, with the history of every entry.
  • A company's Companies House authentication code, where the company has given it to us so that we can file on its behalf. It is held encrypted, is never shown on screen again, and is used only inside a filing.

Why we use it, and the lawful basis

  • To provide the services our clients engage us for, and to manage our relationship with them: performance of a contract.
  • To meet our legal and regulatory obligations, including the Money Laundering Regulations 2017 and the record-keeping that tax and company law require: legal obligation.
  • To run the firm well: making sure deadlines are met, checking quality, keeping the system secure and knowing who did what. These are our legitimate interests, and we have considered that they do not override yours.
  • To send a weekly email about our own software products (WS Insights, TeamPay, Signal, AutoAP and OpsDesk) to people who use them, people who have asked about them, and our own staff. The addresses come from lists we keep in HubSpot, our CRM, from the products themselves, or are added by a member of staff. Each night we read, from each product's own database, the email address, name, role, company and account status of the people who use it, so a product's customer email goes to whoever has a live account; our own staff and a client's employees on TeamPay's self-service are left out. We hold the email address, the name and company it was given with, HubSpot's record of the lawful basis and of any opt-out, which lists it is on, and who unsubscribed and when. Customers are emailed in our legitimate interest in telling them about a product they use. Prospective customers are emailed at a company address in our legitimate interest, as the Privacy and Electronic Communications Regulations allow; at a personal address, which may belong to a sole trader or a partnership, only where they have consented. Every email carries an unsubscribe link to a page on our website, where a person can stop one kind of email or everything we send, and a mail app's own Unsubscribe button works too; we record each unsubscribe, when and how it came. People who sign up for our newsletter on our website, and confirm it by email, are added the same way with their consent, and an unsubscribe on the website is an unsubscribe here too. Every Sunday night WSOP checks the lists against each other, so an unsubscribe or an opt-out is never missed. An address that has used it or opted out in HubSpot is never emailed, and an address that leaves a HubSpot list leaves ours. Once a month one email brings every product together; it goes to the people on any product's list who may still be emailed there, and an unsubscribe from it holds for it alone. A person reads and approves each email before it is sent. Every hour WSOP also reads the contacts held in HubSpot, and the people who have raised a ticket with us through OpsDesk, and files each one onto the monthly email's list for customers or for prospective customers, from what the Client Register records about whose contact they are: a client's contact is a customer, a former client's or anybody else's in HubSpot a prospective customer, and a ticket raised by somebody who is no client's contact (usually a supplier) is left out. The same rules about consent, opt-outs and unsubscribing apply to them as to anybody on a list.

Apart from those product emails, the platform is not used for marketing, and we do not sell personal data.

Who we share it with

Only the firm's staff can sign in, and each person sees only the parts of the platform their role needs. To run the platform we use these service providers, who act on our instructions:

  • Vercel, which hosts the platform.
  • Neon, which provides the database.
  • Microsoft, for staff sign-in and email.
  • Resend, which sends the platform's emails.
  • Anthropic, whose AI models draft summaries and suggested text inside the platform. Only the text needed for that request is sent, and a person checks what comes back before it is relied on or sent anywhere.
  • On a new client's fact find, Anthropic also reads the documents a client uploads as identity documents, proof of address, accounts or HMRC letters: to tell the client at once if an ID has expired or a proof of address is too old, and to offer the references printed on them for the client to check. Nothing it reads is kept as an answer until the client saves it, and a person makes every identity decision.
  • Four published sanctions lists: the UK Sanctions List (the Foreign, Commonwealth & Development Office), the US Treasury's OFAC Specially Designated Nationals list, the European Union's consolidated financial sanctions list and the United Nations Security Council consolidated list. The platform downloads each once a day and checks against them the names of a new client's directors and owners and, every night, the serving directors and individual persons with significant control of every current client company, as Companies House lists them. A possible match goes to the firm's money laundering reporting officer, who decides; nothing is decided by itself. Nothing is sent to any of the lists' publishers.
  • Make, which runs some of our internal workflows, and HubSpot, where client support tickets are logged.
  • Timely, where team record the time they spend on each client. The platform reads the hours by client and by member of staff to work out what each client costs to serve; it keeps the totals, never the notes on an entry.
  • Employment Hero, which has held the firm's own employee records. The platform reads the work facts (name, work email, job title, team, start and leaving dates, line manager) to keep staff accounts in step. Because the firm is moving off it, the platform copies each person's personal details and emergency contacts, their past leave and leave balances, their employment documents, and the people who applied for roles from it once, so that the platform holds them instead. It never takes bank details, National Insurance numbers or tax references.
  • Companies House, to which we send a company number to read that company's public profile, officers and persons with significant control, and a client's company name to search the public register for that company's number. When we file for a company we send Companies House the form through its software filing gateway: the company's number, name and authentication code, and the details the form asks for. Appointing a director or notifying a person with significant control includes their date of birth and home address, which Companies House keeps off the public register.
  • Fireflies and Plaud, which record and summarise meetings with clients when a member of staff uses them. The platform reads each one directly, Fireflies with the firm's key and Plaud signed in as the member of staff whose recorder it is. It takes the summary, the action items, the meeting's title, time and length and, from Fireflies, the attendees' email addresses; it never takes the transcript, which stays with the provider. A summary becomes part of the client's record when it can be matched exactly to that client (an attendee who is the client's contact with us, the client's own email domain, or the client's name in the meeting), and otherwise only when a member of staff has read it and filed it. A summary nobody files is cleared after 30 days. We tell you before a meeting is recorded.
  • Recall.ai, which runs the firm's own meeting notetaker, a bot named WS&Co Notetaker that joins a meeting on Teams, Zoom, Google Meet or Webex for a member of staff who has switched it on, and is visible to everybody on the call. To book it, the platform reads that member of staff's Outlook calendar through Microsoft: each meeting's title, time, join link and invitees. Recall records the meeting in its EU region and transcribes it; the platform reads the transcript once, has Anthropic's Claude write a summary and the action items, and then tells Recall to delete the recording, which Recall deletes after three days at most in any case. The transcript is never kept. The summary is handled exactly as a Fireflies summary is, above. A meeting marked private is never recorded. We tell you before a meeting is recorded.
  • Xero, which keeps the firm's own accounts. We send it a client's name, company number and contact email to set them up as a customer, and the lines of the invoices we raise to them.
  • GoCardless, which takes the direct debit a client sets up after accepting a proposal. We send it the signer's name and email and the company's name so its page is filled in for them; the client types their bank details on GoCardless's own page, and we keep only the reference of the mandate and whether it is active. A client already with us may be sent a request to set one up from their account page, on the same terms. Where their mandate is active, we ask GoCardless to collect their invoices against it on or after the due date, under our terms of business; GoCardless tells the payer before it is taken, and we send it the amount and the invoice numbers. A client may also pay what they owe from their bank on their account page (GoCardless's Instant Bank Pay); they choose their bank on GoCardless's page and we send it only the amount, their email and the invoice numbers. GoCardless tells us when a payment or a mandate changes, and we record a payment it has paid to us in Xero against the invoice. Each working day we also read from GoCardless every mandate on our account and the name and email of the customer it belongs to, including those set up through GoCardless's own connection to Xero, so that we can tell which of our clients pay by Direct Debit and do not send them reminders for invoices GoCardless is about to collect. Nothing is changed in GoCardless by this read.
  • Twilio, which texts the six-digit code a person enters before signing a document we send them, where they are given the choice of a code by text. We send it their mobile number, the code and the document's title, and nothing else. Twilio also carries the firm's telephone calls: when you call us, your number, the keys you press and any voicemail you leave pass through Twilio, and we keep a record of the call (the numbers, the time, how long it lasted and who took it). Where your number is one you have given us as a contact, we note the call against your record so the right person can help. A voicemail may be written out by Twilio's transcription so it reaches the right person quickly. We record conversations only if the firm has switched recording on, and then you are told at the start of the call, before anybody answers. A voicemail and a recorded call are each kept for 90 days and then deleted. If you ask to be called back instead of leaving a message, we keep that you asked. Our people may write a short note about a call, which is kept with the call and on your record. Where the firm has switched them on, we may text you, or message you on WhatsApp, from the firm's number about work we are doing for you; the message, your reply, your number and when are kept with your record, and so are any photos, documents, videos or voice notes you send us that way. A voice note may be written out as words by Twilio's transcription service so the right person can read it quickly. We record whether you agreed to hear from us on WhatsApp, and replying STOP ends it. WhatsApp messages pass through Twilio and WhatsApp, which is run by Meta Platforms Ireland. We only message a mobile number you have given us, and you can ask us to stop at any time. Where the firm has switched it on, after a call with us we may text you one question asking how we did, no more than once a month; if you reply with a number we keep it against the call. If you book a call with one of our people through a link we send you, we keep your name, email, phone number, the time and what you say you want to talk about, and put the call in their Microsoft Outlook calendar with you invited. Where the firm records calls, a manager may listen to a few to help our people improve; nothing else is done with them. Where a client's invoices are overdue and we hold a mobile number for their accounts contact, we also text a reminder at 14 and 30 days: our name, the amount overdue and the link to their payment page, and nothing about the invoices themselves.

We also share information with HMRC, Companies House, the National Crime Agency, our professional body or a regulator where the law requires us to.

Where it is stored

Some of these providers store or process data outside the United Kingdom, including in the United States. Where personal data leaves the UK, we rely on the safeguards UK data protection law requires for that transfer. You can ask us for details.

How long we keep it

  • Identity documents and the other due diligence answers clients give us are deleted five years after the business relationship ends, as regulation 40 of the Money Laundering Regulations 2017 requires, unless the law or legal proceedings require us to keep them longer. The platform does this automatically.
  • Records of the work we do for clients are kept for as long as we act for them and for as long afterwards as tax, company and professional rules require.
  • A closed staff account is kept, so that the record of who did each piece of work stays accurate.
  • Somebody who applied to work for the firm and was not hired has their details cleared six months after the role is filled or closed: their name is cut to initials, and their contact details, CV, the salary they asked for and our interview notes are removed, keeping only the record that they applied.
  • A member of staff's record, leave, documents and reviews are kept while they work for the firm and for as long afterwards as employment, tax and pension rules require.

Security

Staff sign in with their Microsoft work account. Access is granted to each person by name, area by area, and every change is logged with who made it. The platform is served only over encrypted connections.

Cookies and browser storage

The platform uses no advertising or analytics cookies. When a member of staff signs in, the browser keeps a sign-in token and a few screen preferences, such as whether the sidebar is folded. Two short-lived cookies are set during Microsoft sign-in and expire within minutes. The pages reached through a client link store nothing in the browser.

Your rights

You can ask for a copy of the personal data we hold about you, and ask us to correct it, delete it, restrict how we use it, or object to our using it. Some of these rights are limited where the law requires us to keep a record, for example due diligence records under the Money Laundering Regulations. Email info@williamsstanley.co and we will reply within one month.

If you are unhappy with how we have handled your data, you can complain to the Information Commissioner's Office at ico.org.uk or on 0303 123 1113. We would appreciate the chance to put things right first.

Changes

We will update this notice when the platform changes how it uses personal data. The date at the top says when it last changed.

Terms of use · Sign in to WSOP · Williams, Stanley & Co.