AI browser extensions and meeting note-takers on hotel computers: a data checklist

An AI browser extension is a small add-on that reads the pages you open, including the PMS and guest email, and can send what it reads to a third party. A meeting note-taker joins calls and stores recordings. Check five things: what it can read, where the data goes, who installed it, how it is removed, and who agreed to the recording.

Someone at the front desk finds a small add-on that summarizes a long guest email in one click. They install it in ten seconds and keep it. It now sits in the same browser window as the PMS, the agency extranet and the reservation inbox, and nobody in the building knows it is there. This article gives you the AI browser extension security questions to ask for each tool on your computers: what it can read, where it sends data, who installed it, how to remove it, and the rules for recording calls.

Why are browser add-ons different from the AI chat tools staff open on purpose?#

A chat tool only sees what a person chooses to paste into it; an add-on sits inside the browser and can read every page that is already open, without anyone copying anything. The chat tool is a destination: a staff member decides to go there and decides what to paste. The add-on is a passenger: it travels with every page, in every tab, all shift.

The pages a hotel browser holds are the sensitive ones: guest names and identity details, room rates, agency contracts, payment pages, invoice drafts. In Türkiye every stay involves a payment, a fiscal document (an invoice or e-document), a guest identity notification (KBS) and personal data (KVKK), so a browser that reads pages is a browser that reads regulated data.

Installation takes two clicks and leaves no ticket. A person solving a small problem, such as translating a guest message or shortening a long email, installs it and forgets it. Add-ons also update themselves: the version the hotel approved is not necessarily the version running next month, and the new version may ask for more.

Some add-ons can act on the page, not just read it: clicking buttons and submitting forms as the signed-in user, inside a session the hotel already trusts. The permission is granted once, at install, and is almost never looked at again, which is why the check has to be scheduled rather than remembered.

For the chat side of the policy, see our guides on what staff may share with AI chat tools and choosing an AI chat tool for hotel staff.

Which AI add-ons and note-takers are installed on our computers, and who put them there?#

You cannot govern what you have not listed, so the first step is a written inventory of every add-on on every work computer, with a name against each entry. Check browser profiles, not just computers. One desk machine often carries a work profile and a personal one, and staff sign personal accounts into the work browser to reach the same pages.

The browser's own extension or add-on manager lists everything installed, with a version and usually the account that installed it. Show staff where that page is; it is two clicks from the menu. Walk the roles rather than the building: front desk, reservations, sales and marketing, accounting, the general manager's laptop, and the back-office machine that runs the agency extranet.

Note-takers will not appear in that list. They arrive as a calendar invitation or a button inside a meeting, and they are often attached to one person's own account rather than to a hotel account. Ask openly and without blame: people install these tools to do their job faster, and a punishment-first inventory gets you a false list.

For each entry record: name, publisher, version, who installed it, what job it does, whether the hotel pays for it, and the date it was last checked. A broader starting point is our hotel cybersecurity checklist for owners and general managers.

What does "read and change all your data on all websites" actually allow?#

It allows the add-on to see and alter the contents of every page in every tab while you are signed in, which in a hotel browser means the PMS, the extranet and guest email. Read means the add-on sees the page as rendered: guest name, room, rate, notes, the reservation list, the message thread, the invoice draft. Change means it can insert, hide or submit; a form filled in wrongly by an add-on looks exactly like a form filled in correctly by a person.

Narrower is better. An add-on that works on one site can be limited to that site; the combination to question hardest is access to all sites plus permission to keep running in the background. Clipboard and file access matter on a hotel PC, where identity scans, invoices and rate sheets pass through copy and download all day.

Ask the publisher three questions in writing: what do you collect, where is it stored and for how long, and can we have that answer on paper. A publisher who cannot answer is the answer. A free tool still costs someone money to run; the checklist question is who pays for it and what they get in return.

Can we let a note-taker record a meeting with staff, a guest or an agency?#

Only with the knowledge and agreement of everyone in the call, a stated purpose and a deletion date, and a legal view on the recording itself; a note-taker is a recording device with an AI summary attached. The note-taker joins as a participant, records the audio, produces a transcript and a summary, and stores all three somewhere the hotel does not control.

Consent is not one act. Staff, guests and agency contacts stand in different relationships to the hotel, and a guest or an agency contact may not expect a recording at all. The content is commercially sensitive as well as personal: negotiated rates, contract terms, complaints, staff performance, arrival and departure details.

Ask where the recording is stored, in which country, who at the vendor can read it, how long it is kept, and how deletion is proven rather than promised. The summary is derived personal data, not a neutral note: errors in it get forwarded to people who never heard the call.

Put these to your legal adviser rather than settling them from an article: whether a transcript is personal data, whether consent or another basis applies, how a withdrawal is handled, and whether storage abroad needs a transfer mechanism. Penalties and dates belong in that conversation too. For the personal data side, our reading of KVKK's generative AI guide for hotels sets out what to take to that adviser.

What rules should apply on a shared front-desk computer?#

An approved list, installs by the IT provider only, one profile per person, and a monthly check that produces a dated record. The approved list names what is allowed, who owns it and when it is reviewed. Anything not on the list is removed at the desk, not debated there.

The IT provider sets the browser so that only an administrator can add an extension, and staff request additions through a short form that asks what job the tool does. One profile per person on a shared machine, or no personal accounts in the work browser at all: a personal profile carries personal add-ons onto the hotel's pages.

The monthly check uses the same inventory list, is dated, and is kept by the IT provider; a check nobody can show is not a check. Run the list at onboarding and at leaving, and remove the profile and its add-ons on the last day, not the following month.

Keep it proportionate. An add-on that reads one site and does one job is not the same risk as one with access to everything, and the list should say which is which so the review stays short. Access inside the systems themselves is a separate question: see our checklist on PMS user roles and permissions.

How do we remove an add-on, and what has to change afterwards?#

Remove it from every profile and every computer, close its account, then treat every credential and every page it could see as exposed and change those, starting with the PMS and the extranet. Uninstalling in one browser leaves the others, so work through the inventory list line by line and tick each machine off.

If the add-on had an account, revoke its access at the publisher and ask in writing for deletion of what it already holds; removal stops future access, it does not recall what was sent. Change the passwords that were open in that browser: PMS and front-desk logins, the agency extranet, shared inboxes, agency portals, anything the session could reach.

Read the audit trail for actions nobody remembers taking and for sign-ins from places you do not recognize; that is where an add-on that acted on a page shows up. If the add-on could see bank details or payment instructions, confirm recent payment requests through a second channel, by a phone number you already had, before anything is paid. Our piece on AI voice clones and fake payment requests at hotels covers that verification step in detail.

Finally, tell the person who installed it why it went, or the same tool returns next month under a different name.

What to do next#

This week, open the extension manager on the front-desk computer and write down what you find. Then repeat it on every work machine and date the list. That list is the policy, because it turns an invisible habit into something an owner, a general manager and the IT provider can all see, review and remove.