Reception

Privacy policy

Last updated 19 October 2026

Reception is an AI receptionist for small service shops. A shop owner makes a page where guests chat and book. This page says what Reception stores, who else handles it, and how to ask for deletion. It also covers the page where people book a call with the Reception team.

Who is responsible

Reception is run by Fulin Labs, a trade name. Fulin Labs is not a registered company.

Contact for every privacy question: giovannifulin@gmail.com.

Shop owners

Reception has no user accounts. When an owner makes a shop, Reception creates a secret owner link and a staff link. We store only a hash of the owner link, so we cannot show it again. The owner's phone can keep the link in its browser storage so the owner can come back. During setup, the current tab keeps a draft of the menu text, services, shop name and settings so Back and reload do not erase the work. The draft is removed when setup succeeds or the tab closes.

We store what the owner enters or teaches the helper: shop name, city, country, language, time zone, currency, opening hours, services with minutes and prices, how many guests fit at once, and optional address, phone number, map link and Telegram chat. We also store the notes and facts the owner teaches, the questions the helper could not answer, and the first names staff enter when they finish the staff training.

When the owner sends a menu photo, the photo goes to our AI provider to read it. We keep the services and facts it finds. We do not keep the photo.

Guests

For guests chatting on the shop page, Reception stores messages and replies, random chat and request identifiers, and booking receipts so it can continue the conversation and recover a retry without creating another booking. The current browser tab also keeps recent messages and any pending request in session storage to recover after a reload. Reception passes the recent chat to the AI provider to write a reply. Questions the helper could not answer are also shown to the owner. On a chat channel the shop has connected, such as Telegram or Messenger, Reception stores the conversation: the messages the guest and the helper wrote, the channel, an id for the chat, and the helper's tool calls.

A guest who books creates a booking with the name, the phone number, email or chat handle the guest gave, the service, the time, the number of guests, the language and the status. A guest on a waiting list is stored the same way. We also store the notices Reception sends to the guest and to the owner, with the recipient handle, the text and whether it was delivered.

The shop owner and staff can see the bookings of their own shop. Reception does not show one shop's guests to another shop.

The microphone button uses the speech recognition of the guest's browser. The audio goes to the browser's vendor. Reception receives only the text.

AI assistants and agents

An owner can let an AI assistant, such as ChatGPT or Claude, book for guests. The owner connects it with a sign-in page, or makes a key on the owner page. For each connection we store a hash of the token or key, the name the app gave itself, the shop it belongs to, when it was made and when it was last used. An app that is connected can list the shop's services, find open times and book a slot. It cannot read guest lists, chats or the owner link. Anything the assistant sends us to make a booking, such as a guest name and contact, is stored as a booking. What the assistant does with its own conversation is covered by its own provider's policy, not by this one.

Who else handles the data

We do not sell personal data and we do not use it for advertising.

The call booking page

Reception lets people book sales and customer calls with the Reception team. We store the name and email address you enter, the time you choose, your time zone and any note you add. We use them to schedule, confirm, change or cancel that call and to follow up on it. We create an event, including a Google Meet link, on the host's Google Calendar and Google invites you by email.

If a booking submission needs checking, your details and a retry identifier are kept in your browser tab's session storage so a reload can recover it safely. They are removed when confirmation or a definite rejection arrives.

Google user data

The host connects their own Google account so Reception can read their free and busy times and create, change and delete the calendar events for bookings. Reception requests the Calendar events and free/busy permissions plus the account email address. The refresh token is stored encrypted and is used only to run the booking page.

Reception's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Calendar data is not used for advertising, is not sold, and is not used to train AI models.

Abuse limits

To limit automated requests, we store a hash of the client IP address, made with a server secret, together with short-lived request counters. The counters do not hold raw IP addresses or booking details. Expired counters are removed in batches.

Retention and deletion

We keep shop, booking and chat data until the shop or the person asks us to delete it. We delete it within 30 days of a request. Reception has no payment feature and stores no payment data.

To have your data deleted, or to ask any privacy question, email giovannifulin@gmail.com. A shop owner can cut off any connected AI app, and revoke any key, on the owner page at any time. A host can remove Reception's Google access at myaccount.google.com/permissions.

Contact

Fulin Labs has no postal address. Email giovannifulin@gmail.com for deletion requests and any other privacy question.

Changes

When the product changes in a way that changes what we store or who handles it, we change this page and its date.