Who we are
ReceptionOS is a visitor management system made and run by Fluid IT Services Limited, a company registered in England and Wales (company number 10214593). Our registered office is Bute House, Lakeview Business Park, Lamby Way, Rumney, Cardiff, CF3 2EP. In this policy, “we”, “us” and “ReceptionOS” mean Fluid IT Services Limited.
You can reach us about anything in this policy at hello@receptionos.co.uk.
When we are a controller, and when we are a processor
This matters for your rights, so we say it first.
- For visitor and booking records, we are a processor. An organisation that uses ReceptionOS to run its front desk is the controller of the personal data of the people who sign in, book or are pre-registered for a visit at its sites, including visits booked on its public booking page. The same goes for the details of its staff and hosts that it gives us, such as a host’s mobile number for arrival alerts and what its directory sends us. We process that data only on the organisation’s documented instructions, to provide the service. If you have visited, booked with or been pre-registered by such an organisation, it, not us, decides why and how your data is used, so your first point of contact is that organisation.
- For our own accounts, enquiries, website and billing, we are a controller. When an administrator creates an account, when you ask us for a demo or write to us, when you browse this website, or when an organisation pays for the service, we decide how that data is handled, and this policy applies to us directly.
What we collect
Visitor and front-desk data (as a processor, on a customer’s instructions)
- names, the company a person represents, and contact details (email address, phone number) where a site asks for them;
- sign-in and sign-out times, the host being visited, and the site and reception used;
- a photo, where a site’s sign-in journey asks for one (a visitor can always skip it);
- a vehicle registration, where a site asks for one, and a record of each car park exemption, where a site passes its visitors’ registrations to its car park operator;
- answers to any questions a site adds to its sign-in journeys, and acknowledgements of NDAs, health and safety documents, inductions and permits, with the version of the document accepted;
- booking and pre-registration details for expected visits, including those made on a public booking page;
- for employees who sign in at the kiosk with a PIN, the PIN itself, which is stored only as a salted hash and never in readable form.
Staff and host data your organisation provides (as a processor, on a customer’s instructions)
- the names, email addresses, departments, job titles and phone numbers of staff that an organisation’s directory sends us through Stytch when directory sync is on, for organisations on Enterprise identity;
- a host’s mobile number, where the host or an administrator switches on arrival alerts to it, and what those alerts carry: the visitor’s name, company and site.
Account and platform data (as a controller)
- the name, work email address and role of each administrator, host and other person who uses the admin portal, and the organisation, sites and tenant companies they belong to;
- sign-in details handled by our identity providers: WorkOS for standard sign-in, and Stytch for single sign-on for organisations on Enterprise identity;
- billing contact details for organisations that pay for the service, and our correspondence with customers;
- a tamper-evident audit log of visits and administrator changes, and the security logs we need to keep the service safe.
Demo requests, enquiries and website data (as a controller)
- when you ask for a demo: your name, work email address, organisation, number of sites, type of building, what prompted the request and an optional message. We also record which page of this website you sent the form from and, if a campaign link carried one, the name of the campaign. We do not ask for a phone number. We do not store your IP address with a demo request: we use it only to limit repeated submissions;
- when you write to us: your email address and whatever you tell us;
- when you visit this website: Cloudflare, which hosts it, processes your IP address and request details to deliver the pages and keep the site secure.
Why we use it, and our lawful bases
As a controller, we rely on these lawful bases under UK GDPR:
- Legitimate interests (Article 6(1)(f)): to create and run the accounts of the people who use the admin portal, provide the service and invoice customers, answer enquiries and demo requests, keep the platform secure, prevent abuse, keep audit logs and improve the product, balanced against your interests and rights;
- Performance of a contract (Article 6(1)(b)): where a customer is itself an individual, such as a sole trader, to provide the service to them and invoice them;
- Legal obligation (Article 6(1)(c)): where we must keep records to meet accounting or other legal duties.
When we act as a processor for visitor, booking, staff and host data, the lawful basis is the controller organisation’s responsibility, including for a host’s arrival alerts. We process that data only to deliver the service on its behalf.
Sub-processors
We use a small set of providers to run the service. Each is bound by data processing terms and processes personal data only to provide its part of it. This list was last checked on 13 October 2026.
| Provider | What it does | What it handles |
|---|---|---|
| Cloudflare | Hosting, the database, file storage and email delivery | Visit records, visitor photos, documents and logos, and your organisation’s accounts and settings |
| WorkOS | Standard sign-in to the admin portal | The name and email address of each person who signs in to the portal |
| Stytch | Single sign-on and SCIM directory sync, for organisations with Enterprise identity | Staff names, email addresses, departments, job titles and phone numbers from your directory, and their single sign-on sign-ins |
| Twilio | Text messages, and WhatsApp messages through Meta, to hosts whose alerts are switched on by the host or their administrator | The host’s mobile number, and the visitor’s name, company and site in the message |
Card billing through Stripe is built but switched off, so Stripe receives nothing from us today.
If your organisation connects another service to ReceptionOS, such as its own identity provider for single sign-on, or a system that uses our API or webhooks, data goes to that service on your organisation’s instruction, and that service is your supplier, not our sub-processor.
We will give customers reasonable notice of any change to this list. We do not sell personal data, and we do not share it with anyone for their own marketing.
International transfers
Your records and files are stored in Cloudflare’s Western European data centres. We do not offer a UK-only or EU-only residency guarantee.
Our providers are international companies, and some of their processing may take place outside the UK, including in the United States. Where a provider handles personal data outside the UK, we rely on a safeguard that UK GDPR allows: the UK’s adequacy regulations, or the International Data Transfer Agreement or the UK Addendum to the EU Standard Contractual Clauses, as set out in that provider’s data processing terms.
How long we keep it
How long we keep data depends on what it is.
- Visits. Each site sets how long it keeps visits, from 1 to 3,650 days (395 by default), counted from sign-out. Every night we delete the visits past that period, together with their document acceptances, permit records, photos and permit files. A visit with no sign-out is never deleted by this schedule.
- Bookings and pre-registrations. Cancelled bookings, and pre-registrations that were used, have expired or were cancelled, are deleted on the same schedule, counted from the end of the booking or the expected arrival. Other bookings are not yet deleted by the schedule, even once the booked time has passed, because nothing yet marks a booking as completed or missed: we delete them on request. A pre-registration that is still pending is never deleted by it.
- Car park exemptions. Where a site passes its visitors’ registrations to its car park operator, we keep a record of each exemption: the vehicle registration, the visit and host it belongs to, and the times it is valid. The schedule above doesn’t delete these records yet: erasing the visit deletes them, and we delete them by hand on request.
- Webhook delivery logs. A webhook delivery log can hold a visitor’s name, company and email address, so we delete its entries after 30 days.
- Fire roll-call. While a roll-call is running, its list of people signed in is held on Cloudflare’s network. The list is wiped an hour after it ends, and a roll-call left open for 24 hours is ended automatically. What we keep afterwards is a summary with no names: the mode, the times and the counts.
- Each reception’s recent sign-ins. Each reception keeps a log of its latest 500 sign-ins and sign-outs, with visitor names, so that a kiosk that was offline can catch up. Older entries drop off as new ones arrive. This log is not covered by the schedule above or by erasure.
- The audit log. Entries are chained to the one before, so they are not edited or deleted one by one. An erasure is recorded in the log without the erased details, and an entry that records a correction to a name keeps the name as it was and as corrected.
- Demo requests. We keep demo requests for 24 months and then delete them, and we keep the email copy we receive for the same time.
- Account and billing data. We keep it for as long as the account exists, and for any period we are legally required to keep it afterwards.
Erasing a person’s records
An owner can erase a person’s records from the admin portal, in Organisation settings under “Erase a person’s data”. An owner or a site manager searches by name or email address, and the search lists the records it finds. Exact email matches, and the records linked to them, start ticked; name matches start unticked, as a name can belong to someone else. The owner reviews the list and erases the records they tick. A visit can’t be erased while the person is still signed in. If you are the person concerned, ask the organisation you visited. A customer can also ask us to action a request, at hello@receptionos.co.uk.
An erasure takes:
- the visits, pre-registrations and bookings ticked after the search
- each visit’s document acceptances, permit records and car park exemption records
- its photo and any permit files
- the webhook delivery log’s copies of the erased visits’ and pre-registrations’ events
The audit log records that an erasure happened, by whom, with a reference and the number of records erased, without the erased details. If a stored file cannot be removed when a record is erased, the failure is recorded so that it can be removed by hand.
An erasure does not reach:
- webhook delivery-log entries for any other event, which are deleted after 30 days
- audit log entries that record a correction to a name
- watchlist entries
- space bookings and staff accounts
- each reception’s log of its latest 500 sign-ins and sign-outs
There is no subject access export tool yet. The same search lists the records held about a person, and when a person asks an organisation for a copy of their data, we help the organisation to collect it by hand.
Security
Every record is kept separate for its organisation and, inside a building, for the right site or tenant. API keys are stored only as hashes and shown once, and employee PINs are stored only as salted hashes. We keep a tamper-evident audit log of visits and administrator changes that an organisation’s owners can verify and export. Traffic is encrypted in transit and data is encrypted at rest, and every part of the service sends strict security headers and a content security policy.
We do not hold a security certification yet. Our security page says plainly what that means. To report a vulnerability, email security@receptionos.co.uk.
Cookies
This website sets no tracking cookies, loads no advertising or analytics scripts, and serves its fonts from our own domain, so visiting it does not send your IP address to a third-party font or analytics provider.
The admin portal uses essential cookies, such as a signed session cookie that keeps an administrator signed in. The kiosk keeps its pairing and the language a visitor chose on the tablet, not in a cookie.
Your rights
Under UK GDPR you have the right to ask for a copy of your data, to have it corrected or erased, to restrict or object to its use, to receive it in a portable form, and to withdraw any consent you have given.
To use these rights over a visitor, booking or pre-registration record, contact the organisation whose site you visited. For the details your employer gave us about you as a member of its staff or a host, contact your employer. That organisation is the controller, and we will support its request as its processor. For data we hold as a controller (your account, an enquiry or a demo request), email hello@receptionos.co.uk. We will reply within one month, as UK GDPR requires.
UK GDPR and data processing terms
We build ReceptionOS for UK GDPR: retention you set for each site, erasure from the admin portal, records kept separate for each organisation and an audit log are part of the product.
UK GDPR requires a written contract between a controller and its processor. We don’t publish a standalone data processing agreement yet. If your organisation needs one, or wants to propose its own terms, email hello@receptionos.co.uk and we will agree the terms with you in writing. Where a signed agreement covers the same ground as this policy, the agreement takes precedence.
Children
ReceptionOS is a workplace tool and is not directed at children. Whether to collect data from anyone under 18 at a site is a decision for the controller organisation, under its own lawful basis.
Changes to this policy
We update this policy as the product changes, and revise the date at the top when we do. The box at the top of the page says what changed. For changes that materially affect how we handle personal data, we will give customers reasonable notice.
Complaints
We would always like the chance to put things right first, so please contact us. You also have the right to complain to the UK Information Commissioner’s Office (ICO) at ico.org.uk or on 0303 123 1113.