Last updated: 2026-09-21
This service (group reservations) is a business tool: travel agencies send group bookings to restaurants in advance, and restaurants receive, prepare and settle them. Below is the personal data the service actually handles, and why.
Operator: Flowlabs (플로우랩스) · Address: 103-1202, 50 Deokpunggongwon-ro, Hanam-si, Gyeonggi-do, Republic of Korea · Contact: leaderbin@naver.com
Restaurants and travel agencies are the organisations that enter and view their own bookings.
| Data | When | Why |
|---|---|---|
| Email · name · phone · sign-in ID · organisation (agency/restaurant) · display language | When you apply, are invited, or use your account | Signing in, confirming who you are, and showing only your own organisation's bookings |
| Password | When you choose one | Stored only as a hash (PBKDF2). The original is never stored and the operator cannot see it |
| Booking details — tour number · tour leader's name · contact phone · number of guests · menu · notes · amounts · payments · change history | When an agency or restaurant enters them | Passing the booking on, kitchen preparation, invoicing and settlement |
| Inquiry messages | When you write one | Communication between agency and restaurant |
| Sign-in records — the ID typed, IP address, success or failure | On each sign-in attempt | Limiting repeated attempts to stop password guessing (10-minute window) |
| Sign-in session — browser type (User-Agent), time last used | While signed in | Keeping you signed in |
| Google account email · the calendar you chose · access tokens issued by Google | Only if a restaurant approves the Google Calendar connection | Putting confirmed bookings into that restaurant's Google Calendar, updating them, and marking cancellations |
The connection is optional. It happens only when a restaurant administrator approves it with their own Google account.
Permissions requested: view and edit calendar events (calendar.events), see the list of calendars (calendar.readonly), confirm the account's email address (openid · email).
What the service does: it creates booking events in the one calendar the restaurant chose, and updates or marks those events as cancelled. It reads the list of calendars so the restaurant can choose where bookings go.
What it does not do: it does not read or store the content of events it did not create. Data received from Google is not used for advertising, not sold or transferred to third parties, and not read by humans (except at the restaurant's request to resolve an error).
The use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
Disconnecting: a restaurant administrator can disconnect at any time on the “My organisation” screen; the stored tokens are deleted immediately. Access can also be revoked in the Google Account under “Third-party apps & services”.
Cloudflare, Inc. — where the service runs and the database is stored (Cloudflare Workers · D1).
Google LLC — only when a restaurant has approved the calendar connection: that restaurant's booking events are sent to that restaurant's Google Calendar.
We do not otherwise share or sell data to third parties. We use no advertising or tracking tools.
Only strictly necessary cookies, for four purposes: keeping you signed in, remembering the display language, protecting the Google connection step against forgery, and not showing a notice again. There are no tracking or advertising cookies.
Accounts and booking/settlement records are kept while the business relationship lasts and for as long as accounting and tax law requires.
Sign-in sessions lose effect when they expire; sign-in attempt records are used only for limiting attempts.
Google tokens are deleted as soon as the connection is removed.
You may request access to, correction, deletion, restriction or portability of your data, and you may object to processing. Please use the contact below.
If you live in the EU you have the right to lodge a complaint with your local data protection authority.
For details written into a booking (such as a tour leader's name), you may also ask the agency that entered it or the restaurant that received it.
Flowlabs (플로우랩스) · leaderbin@naver.com