Data and privacy
Where guest data lives, who can see it, how long it is kept, and how to answer a guest who asks.
How Phil treats guest data, in short. The full Privacy Policy is at /privacy; a signed data-processing agreement is available on request.
Roles#
- Your property is the controller of guest data; Foyer Intelligence is the processor.
- We act only on your instructions and only to run the service.
- You decide what Phil knows about the property, who on your staff can see what, and when a guest's record should be deleted.
What is stored, per guest#
| Data | Why | Kept |
|---|---|---|
| Room, reservation reference, booking phone | To send the stay link and codes to the right person | Full phone number during the stay; only the last four digits after checkout. Codes expire in minutes |
| Conversation with Phil | To answer, and so staff can read context when they take over | 12 months after checkout, then deleted (anonymised copies excepted, see below); deletable per guest on request |
| Requests, orders, reservations, offer claims | The service record your staff act on | 12 months after checkout; needed for disputes and history |
| Charge evidence: last-4 of phone, device, verification method, chat excerpt | To support a room charge if the guest questions it | 12 months after checkout |
| Voice calls: time, length, outcome, summary, links, last four digits of a phone number and a redacted transcript | To count call minutes and show your team what happened | 12 months, then deleted (anonymised copies excepted, see below). Transcribed only: Foyer never stores call audio |
| Device identifier | To recognise devices admitted to the stay | Access ends at checkout; the device record is deleted with the reservation 12 months after checkout, and the browser cookie can last 400 days |
Anonymised copies, which identify no guest and no Property, may be kept after the originals are deleted, to improve Phil, as described in the Privacy Policy.
Never asked for: payment card numbers, passport or ID scans, passwords. Card numbers, and passwords a guest labels as such, are masked before a message is stored. Anything else a guest chooses to type into the chat is kept as part of that conversation.
Where it lives#
- The database is in Frankfurt (AWS eu-central-1, operated by Supabase). Encrypted in transit and at rest.
- Every table carries the hotel identifier, and Foyer's server scopes every staff and guest request to the hotel in the signed session, so a staff key from one property cannot read another property's rows.
Who can see it#
- Your staff, according to their role, department and pages: staff see their department's queue; leads and managers see all of the property; nobody sees another property.
- The Foyer team: during your first 30 days, to review conversations and tune Phil for your property; after that, when you ask for support on a specific issue.
- Providers that run parts of the service: database (Supabase), hosting (Vercel), our automation server (Hostinger), the language model (OpenAI), usage analytics with all text masked (Microsoft Clarity), and, where used, Telegram for your staff's cards and notifications. The full list is in the Privacy Policy.
- Nobody else. We do not sell data or share it with advertisers.
AI, specifically#
- Message text is sent to the language-model provider (OpenAI) to draft each reply.
- OpenAI does not use API data to train its models by default, and may keep inputs and outputs for up to 30 days for abuse monitoring.
- Prices and saved confirmations have code checks. Emergency handling uses fixed rules with an AI fallback.
- Phil answers property questions from your knowledge base, not from the open internet.
When a guest asks#
- “What do you have on me?” Ask us and we provide the guest's requests and conversation within 30 days.
- “Delete my data.” Email support@foyerintelligence.com with the property, room and dates; we delete the guest's conversation and records within 30 days and confirm. When a guest's data is erased, anyone who shared the stay keeps their own messages and access; the guest's name, phone number and email are removed from the conversation they shared, which is kept because its messages cannot be told apart by speaker. Only what billing needs is kept, without the guest's details: the length of calls for call minutes, the record that the guest asked for a call with only the last four digits of the number, and the count of the stay's check-in.
- “Why did you text me?” The stay link and codes go only to the phone on the booking. If the number is wrong, correct it in the PMS.
When you leave#
- You can export everything for 30 days after the subscription ends.
- Then it is deleted from live systems, except the anonymised copies described in the Privacy Policy, which identify no guest and no Property; database backups roll off within 7 days after that.
Something unclear or out of date? Write to support@foyerintelligence.com.