Latchkey

Privacy policy

Last updated Wed 18 Nov 2026

Latchkey is software for people who run guest accommodation: check-in, stay guides, guest messages, housekeeping, direct stays and the records that go with them. This policy explains what personal data is involved, who is responsible for it, and the choices you have.

There are two kinds of data here. For our website, demos and hosts' accounts, Omnistar Ltd, trading as OMS Estates decides what's collected and why. For guests, the business you stay with decides, and Latchkey looks after the data on its behalf.

1. Who we are

Latchkey is run by Omnistar Ltd, trading as OMS Estates, a company registered in England and Wales with company number 17252744, whose registered office is at 49 Trinity Circle, High Wycombe, Buckinghamshire, HP11 1FB.

For anything about your data, email hello@omsestates.uk.

2. Who is responsible for which data

  • Visitors to this website, people trying our demos, and hosts and their team members: Omnistar Ltd, trading as OMS Estates is the controller of this data.
  • Guests of a business that uses Latchkey: that business (the "host") is the controller. Omnistar Ltd, trading as OMS Estates is its processor: we store and process guests' details only to run the service for the host, under the data processing terms in our Terms of service, and never for our own marketing.
  • Card payments from guests, and Pay by Bank payments approved in a guest's banking app, are made in the host's own Stripe account. Stripe and the host are responsible for that payment data; we only see whether a payment succeeded.
  • If a host connects their bank account or uploads a bank statement, we read the payments into it to mark direct bookings paid by bank transfer. A payment matched to a booking (date, amount, payer's name and reference) is kept for 13 months; any other payment in is deleted after 60 days. Payments out are never read or kept.

3. Website visitors and demos

  • Page views and demo steps, counted as described under Website statistics below.
  • If you start the guest tour or host demo, nothing you type in it is kept beyond the demo's daily reset, and sample ID checks never store photos.
  • To stop misuse of the demo and our sign-up, we keep a scrambled version of your IP address that changes every day, never the address itself.
  • If you arrive through a Commission Partner's link and accept cookies, we keep their referral code in a cookie for 60 days (see Cookies below), so the right partner is credited if you sign up.

4. Hosts and their team

  • Account details: name, email address, sign-in method (email, Google or Apple), and your role in the business.
  • Business details: business and property names, addresses, contact phone and email, bank details you choose to show guests, tax settings, theme and logos.
  • Billing: your plan and subscription status. Card details are collected and held by Stripe, never by us.
  • Use of the service: activity in your business (who changed what, for your own audit trail), alerts and how you've chosen to receive them (email, text message, WhatsApp, Telegram, app notifications), and feedback or support requests you send us.
  • Our support team can see your business's data to help you and to keep the service running. They can only change it if you allow it, for up to 30 days at a time, and you can turn that off in Settings.
  • If you sign up through a Commission Partner's link or code: to stop self-referral and fraud, we compare scrambled (hashed) versions of your email, phone, business and property details, card fingerprint, IP address and a random device code with the partner's and with other accounts (our legitimate interests). We never share these with the partner, who sees your business only as initials and a town. The scrambled IP address and device code are deleted after 180 days; the other scrambled details are kept while the referral can affect commission, and at most 6 years after the partner's agreement ends.

5. Guests (handled for the host)

Depending on what the host turns on, Latchkey may hold:

  • Booking details: name, dates, room, number of guests, booking site and reference, email and phone number, and notes. Some arrive from the booking sites' calendars.
  • Check-in details: who is staying (adults and children's ages), and for the UK guest register everyone 16 and over gives their full name and nationality; guests who aren't British, Irish or from a Commonwealth country also give their passport or ID number, where it was issued and their next destination (and the address there, if known), as the law requires. If they say they're going home, the home address printed on their driving licence or ID card is used for this, and nothing else is kept from it.
  • Photo ID checks: a photo of the ID document and, if the host asks, a face photo, taken at the door or added by the host on the guest card. The images are read automatically to fill in the guest's details and help the host check the document, and the host sees the result. A small copy is kept only if the host has turned this on and confirmed their ICO registration, and only for the days they've chosen. Kept copies are stored in a restricted folder for that business in our Google Drive, never shared, and shown to the host only through links that expire after 10 minutes.
  • Door tablet camera view: if a host switches it on for a tablet, live video from that tablet's camera, only while the host has the camera view open, sent straight from the tablet to the host's screen over an encrypted connection; it doesn't pass through or get stored by us. The tablet says on screen that it's being viewed. On some older tablets that can't send video, a small picture every few seconds is sent through us instead, and only the latest is held, deleted when the host closes the view. Hosts who use it are responsible for telling guests (a notice by the tablet and their privacy notice).
  • Messages between guest and host, requests (extras, breakfast, maintenance), invoices with the billing address the guest gives, and ratings.
  • Returning guests, if the host switches it on: after an ID check that matched, the name and expiry date from the ID and a scrambled copy of the guest's email and phone, so they can skip the ID photo next time. No ID photo or document number.
  • Whether a guest has stayed with the same business before, worked out from the name, email or phone on their earlier stays while the business still keeps them, and used to welcome them back. Unless the host chooses otherwise, a guest whose ID was checked on an earlier stay isn't asked for it again: the host sees the earlier check's result, and the face photo while it's still kept, on the new stay. Nothing is kept for longer because of this.
  • Direct enquiries and bookings made on the host's own page, how the guest chose to pay, and whether they agreed to hear from the host about future stays (only if they ticked that box).
  • Loyalty vouchers a host makes for a past guest: the guest's name and, if the host adds them, email and phone, the rooms, dates and price it gives, and whether it was used. The host sends the code from their own phone or email; we don't send it.
  • Stay terms for direct stays: the exact booking terms a guest agreed to, and for a longer stay the licence they signed with their permanent home address, the purpose of the stay, their typed name and drawn signature; with when they agreed, their IP address and browser. Kept as a record for the host and in case of a dispute about the stay; the signature and a PDF copy are stored in that business's restricted Google Drive folder.

6. Why we use it, and our legal basis

  • To provide the service to hosts and their guests (performing our contract with the host; for guest data, on the host's instructions).
  • To bill for subscriptions and keep accounting records (contract and legal obligation).
  • To keep the service secure, prevent fraud and misuse of trials and demos, and fix problems (our legitimate interests).
  • To understand which pages and features help, using the website statistics below, only if you agree to them (your consent, which you can withdraw at any time).
  • To answer support requests and send messages about your account and important changes (contract and legitimate interests). We don't send hosts marketing without their agreement, and we never send marketing to guests.
  • Keeping the UK guest register and tax invoices is the host's legal obligation; we keep them for the periods below to support it.

7. Services we use

We share only what each service needs to do its job:

  • Lovable Cloud (built on Supabase): hosting, database, file storage, sign-in and the email we send. Private files (ID photos, signatures) only wait here briefly if Google Drive can't be reached, and are removed once they're safely in Google Drive.
  • Lovable AI Gateway and the AI model provider behind it (currently OpenAI): reading photo ID during guests' check-in (when the host turns ID checks on), Commission Partners' identity checks, and answering guests' questions to the AI stay assistant (the question, the last few turns and the host's guide text; when an ID is read for the stay assistant's voice, only the document's sex field is used, on the screen, and never kept). Images are sent for that check only; we ask the service not to keep them, and we don't use them to train any AI model.
  • Stripe: hosts' subscriptions, and guests' card and Pay by Bank payments in the host's own Stripe account.
  • Starling Bank: when a host connects their own Starling account, we read the payments into it with the read-only token they made.
  • Twilio (text messages, and WhatsApp messages for hosts who turn them on) and Telegram (messages to hosts who link it): alerts to hosts. App notifications go through the browser maker's push service and carry no content.
  • Twilio, and Meta's WhatsApp through Twilio: messages to guests when the host turns them on, and the check-in photo link a guest asks for at the door tablet. They receive the guest's mobile number and the message. A number typed in for the photo link is used for that one message and isn't kept.
  • Google: sign-in with Google, and Google Drive, where we store files hosts attach to their guides and, in restricted folders that are never shared, kept copies of guests' ID and face photos and Commission Partners' ID photos, drawn signatures and signed agreements. Apple: sign-in with Apple.
  • ElevenLabs: the voice guide's recorded phrases (made once from fixed words), turning a guest's spoken reply into text on devices that can't do it themselves, and speaking the AI stay assistant's answers. Recordings and answers aren't kept.
  • OpenStreetMap (Overpass, Nominatim and FOSSGIS's routing service), postcodes.io, the Food Standards Agency's hygiene ratings and, when set up, Ticketmaster and Skiddle: finding places, walking and driving times, hygiene ratings and events near a property for its guide's Around here section. Only the property's location is sent, never guest data. Events are only looked up while guests are staying or arriving within a week.
  • Pictures of places and events (from Wikimedia Commons, a place's own site, Ticketmaster or Skiddle), small OpenStreetMap maps of places and the Food Standards Agency's rating badges are shown straight from those sites, so a guest's device asks them for the picture and they see its internet address. Latchkey doesn't store or pass on these pictures. Wikidata and a place's own website are read (about once a week) only to find which picture or logo belongs to the place, with no guest data.
  • Firecrawl: reading a host's public listing pages when they import them, the reviews on them for the host's door tablet, and the prices shown on them (and on other properties' public pages the host chooses) for smart pricing. No guest data is sent.
  • Voice check-in, if the host offers it and a guest chooses it: the door tablet's own browser turns what the guest says into text (on Android through Google, on an iPad through Apple) and speaks with the tablet's built-in voices. Latchkey keeps no recording or transcript; when a reply isn't understood, just those words (as text) are sent to our AI provider to work out the answer. On a tablet that can't turn speech into text itself, each short reply is sent as a recording to ElevenLabs to be turned into text, and isn't kept.
  • Reviews on the door tablet, if the host switches it on: public reviews of the property from its own listing pages, kept as a short quote with the reviewer's first name, rating and date, until the host hides them or the property is removed.
  • Samsung SmartThings or TP-Link (Tapo): when a host links smart lights to a room, switching them for the guest staying there. The service receives the commands (on, off, brightness, colour) from Latchkey's server under the host's own account; no guest's name or contact details are sent. For TP-Link, Latchkey keeps the host's TP-Link email and password, encrypted, only to sign in again when TP-Link asks, and deletes them when the host disconnects.
  • Frankfurter (exchange rates) and Cloudflare (checking a host's domain): no personal data is sent.
  • Google and Cloudflare connection servers (STUN): help a door tablet and its host's screen connect directly for the live camera view. They see the two devices' internet addresses, never the video.

8. International transfers

Some of these services store or process data outside the UK. Where they do, we rely on the UK's adequacy regulations or on the UK International Data Transfer Agreement or Addendum, so your data has the same protection.

9. How long data is kept

  • Website statistics: 13 months.
  • Guests' names and contact details on a stay: cleared 30, 90, 180 or 365 days after check-out, as the host chooses (90 days unless changed). Messages: deleted after the period the host chooses, or kept with the stay.
  • Copies of photo ID and face photos: 7, 14 or 30 days after check-out, as the host chooses, then deleted from Google Drive (deleted, not moved to the bin).
  • Door tablet photos: while a guest is on the photo step, the tablet looks at a tiny copy of the camera picture for a whole ID or a face, so it can take the photo by itself. That happens on the tablet, using Latchkey's own files, and only the photo it then takes is sent.
  • Door tablet waking on movement or sound, if a host turns on Smart Screensaver: a very small picture and a sound level are compared on the tablet itself while it rests. Nothing is kept or sent.
  • Door codes: kept with the stay, so that a code isn't given to another guest too soon.
  • Someone who gives their ID at check-in but can't be matched to a booking straight away: their details are kept for the host to place them or remove them, under the same rules as any other guest.
  • UK guest register: 12 months from arrival, as the law requires, then deleted.
  • Door tablet camera: live video isn't stored. Pictures from older tablets: only the latest, deleted as soon as the host closes the camera view.
  • Invoices: kept for the host's tax records. Direct enquiries: one year. Check-in attempts: 30 days. Team activity: one year.
  • Returning guests' remembered ID checks: 12 months, then deleted.
  • Room lights: each tap a guest makes (which light, which stay, when) is kept for 7 days to stop misuse, then deleted.
  • A host's own test check-in: until they reset it, or a week after its check-out day.
  • A host's own sample ID and selfie for trying the check-in: in a restricted Google Drive folder until the host removes them.
  • Loyalty vouchers: one year after the last date the code could be used.
  • Stay terms accepted and licences signed (direct stays): six years after check-out, the time in which a claim about the stay can usually be brought in the UK, then deleted with their files.
  • Host accounts: while the account is open. When a business closes its account, we delete or anonymise its data on request, except records we or the host must keep by law.
  • Commission Partners: see the Commission Partners section below.

10. Website statistics

With your agreement, we record visits to this website to see what's useful, how people find and use Latchkey, and to improve it. When you first visit, a banner asks whether you agree; nothing is recorded or stored for statistics until you choose Accept, and choosing Reject (or doing nothing) means it never is. You can change your choice at any time with the switch below.

  • What we record: pages opened, how long they're looked at and the page you came from; campaign tags on the link you followed (like utm_source=linkedin); browser and device type, language, time zone, country and region; and steps in our demo and free trial. Your browser keeps a random visitor number so visits from the same browser can be put together.
  • Visitor profiles: when you sign in, start a trial or give us your email, we link that browser's visits to a profile with your account and email address, and join visits from other browsers or devices where you sign in with the same account or email. Omnistar Ltd, trading as OMS Estates uses these profiles to understand which pages, campaigns and steps lead people to try and keep using Latchkey, to improve the website and service, and to help you when you ask for support (based on your consent to statistics, and our legitimate interests in supporting you). We don't sell them, share them with advertisers or use advertising networks.
  • What we don't record: no IP addresses (only a scrambled code that changes every day, to spot automated traffic), and no town or exact location.
  • Browsers that send Global Privacy Control or Do Not Track are never recorded and aren't asked. If you withdraw consent, we stop recording and delete the visitor number and referral cookies from your browser; visits already recorded are kept for the period below unless you ask us to delete them.
  • Kept for 13 months, then deleted.

Your cookie choice

This browser remembers your choice for up to 12 months. You can also add ?notrack=1 to any of our links.

11. Cookies and storage on your device

  • We don't use advertising cookies or third-party trackers. We only store what's needed for the service you asked for unless you agree to more on our cookie banner.
  • Always (needed for the service): your browser's storage keeps you signed in, remembers settings (like your chosen property or layout), and remembers your cookie choice (lk_consent) for up to 12 months, after which we ask again.
  • Only if you accept: the random visitor number for website statistics (lk_vid), the campaign you arrived from for this visit, lk_ref (if you open a Commission Partner's link, their referral code for 60 days so they're credited if you sign up; otherwise you can confirm or type their code when you sign up), and lk_dev, a random device code for 60 days used with it for the fraud checks described under Hosts.
  • On a guest's phone (needed for the service): lk_stay_ remembers their own stay until check-out, so scanning the room's QR code opens it. The cookie banner isn't shown on guests' pages or door tablets, and nothing optional is stored there.
  • Installed apps and kiosks keep an offline copy of guest pages so they still open without a connection.
  • Stripe's payment pages and Google's or Apple's sign-in pages set their own cookies under their own policies.

12. Keeping data safe

  • Data is encrypted in transit, and each business can only reach its own data; team members can be limited to particular properties.
  • Photos of ID, signatures and signed agreements are kept in restricted Google Drive folders that are never shared (or, for a short time while Drive can't be reached, in private storage) and shown only through links that expire within minutes. Viewing a Commission Partner's ID photos is logged with a reason.
  • Guest links and invoice links are long random codes, and we store only scrambled versions of guest link codes.
  • If a breach puts personal data at risk, we tell the hosts affected without undue delay so they can meet their own duties, and the ICO where we must.

13. Commission Partners

If you apply to be an independent Latchkey Commission Partner, Omnistar Ltd, trading as OMS Estates, a company registered in England and Wales with company number 17252744, whose registered office is at 49 Trinity Circle, High Wycombe, Buckinghamshire, HP11 1FB is the controller of your data. This section explains it; the Commission Partner agreement (clause 17) says the same.

  • What we collect: your application (name, business details, country, email, phone, VAT number and address); the records of your signature (the agreement's version and fingerprint, date and time, your typed name and drawn signature, the boxes you ticked, your IP address and your device and browser details); for your identity check, photos of your ID document and a selfie, and the details read from the document (name, date of birth, expiry date, issuing country, document type, the last 4 characters of the document number) with the result; scrambled (hashed) fraud-check details; and your statements, payouts and tax records.
  • Why, and our legal basis: to run the agreement with you (contract); to verify who we're paying and to prevent fraud and self-referral, and to be able to prove what was agreed (our legitimate interests); and to keep accounting and tax records (legal obligation).
  • Automated reading of your ID: an AI service (through the Lovable AI Gateway, currently OpenAI models) reads your document and checks it isn't a copy, a printout or a screen. We ask the service not to keep the images, and we don't use them to train AI models. An automatic check never refuses you on its own: after two failed attempts a person at OMS reviews it, and you can ask for a person to review any decision.
  • Where it's held: your application, the details read from your ID and your signing record are in our database (Lovable Cloud). Your ID photos, selfie, drawn signature and signed PDF are in restricted folders in our Google Drive, never shared, seen only by OMS's authorised administrators through links that expire after 10 minutes, and every view of your ID photos is logged. If Google Drive can't be reached, they wait in our private storage and are moved to Google Drive, then removed, as soon as it's back. Stripe collects its own identity and bank details from you as an independent controller when you set up payouts; we never see your bank details.
  • International transfers: some of these services process data outside the UK, under UK adequacy regulations, the UK International Data Transfer Agreement or the UK Addendum.
  • How long we keep it: ID and selfie photos are deleted 30 days after we approve or reject your identity check. The details read from your ID and the result, your application, and your signing records and signed PDF are kept while you're a Commission Partner and for 6 years after the agreement ends. Scrambled IP addresses and device codes: 180 days. Other scrambled fraud-check details: while you're a partner and up to 6 years after, reviewed at least once a year. Statements, payouts and tax records: 6 years after the end of the financial year they relate to.
  • Setting up a business for a host (agreement clause 6.9): the host's name and email address you enter are kept with the set-up so we can send them the invitation and credit you once they take it over. The host can see and change their details in their own account after that.
  • Your rights are the same as everyone's (below), and you can complain to the ICO.

14. Your rights

  • You can ask to see, correct or delete your data, to restrict or object to how it's used, to receive it in a portable form, and to withdraw consent you gave.
  • Hosts and visitors: email hello@omsestates.uk. We reply within one month.
  • Guests: please ask the business you stayed with first, as they decide about your data. If you contact us, we'll pass your request on to them and help them answer it.
  • You can complain to the Information Commissioner's Office at ico.org.uk or on 0303 123 1113. We'd appreciate the chance to help first.

15. Children

Hosts must be 18 or over. Guests' children are recorded only by their age at check-in, and children don't give ID.

16. Changes to this policy

When we change this policy, we update the date at the top and tell hosts about important changes in the app. For questions, email swapnil@omsestates.uk.