Your data deserves care.
What this version stores
When a business registers, we store its owner's name, email, securely hashed password, business settings and services. When a client books, we store their name, email, optional phone number, answers to booking questions, appointment time and booking status. The business owner can access all appointments for their business. Active team members can access only their own assigned appointments. Employee invitations use expiring, single-use tokens. Authorized platform administrators can view business accounts and individual booking details, including customer contact information and booking answers. Business detail access, booking detail access and CSV exports are recorded in a private audit log retained for 365 days.
Why we use this information
Account information lets you sign in and manage your business. Booking information lets the selected business deliver and manage an appointment. Only provide information relevant to the service. Do not submit medical records, identity document numbers or other sensitive information in custom questions.
Essential cookies
Bookio uses session and security cookies to maintain your login and protect forms against forgery. These are required for the site to function.
Statistics, on our own servers
When you visit public pages without being signed in, we use a first-party visitor cookie (up to 180 days) and store a pseudonymous hashed visitor identifier, session identifier, public page paths, business identifier, event time, device and browser categories, referring hostname and campaign tags. Events include page views, booking starts, booking completions, signup clicks and registrations. Sessions expire after 30 minutes of inactivity. Raw referrer URLs and raw browser user-agent strings are not retained. We do not store IP addresses, browser fingerprints or advertising identifiers in the analytics table. Unique browser counts are estimates based on cookies; they do not identify unique people. Authenticated traffic and recognized bots are excluded. We do not use Google Analytics.
The analytics cleanup command deletes records older than 90 days when the scheduled task is running. Operational hosting logs may contain additional technical data and must be configured with appropriate access and retention before launch.
Booking and account data are separate from these statistics. You can delete the visitor cookie at any time in your browser settings.
Sharing, access and deletion
Your appointment details are shared with the business you select. Keep the private confirmation link secure: anyone with that link can view or cancel that appointment. This preview has no advertising partners. Email confirmations are prepared in a private owner outbox and are not sent until a provider and delivery are enabled. No WhatsApp notifications are sent. An operator contact and verified data access/deletion process must be provided before accepting real customer data.
Before public launch
The business operator must document controller/processor responsibilities, retention for account and appointment records, security measures, hosting locations, cross-border transfers and a lawful basis for each use. This development notice is not a declaration that all legal launch requirements have been met.
Optional business management modules
Business owners may store employment start dates, visa references and expiry dates, salary reference amounts, private notes and income/expense records. HR fields containing visa references, salaries and notes are encrypted in application storage. Employee accounts cannot access these modules. Owners are responsible for the employee data they enter. Provider-enabled email and WhatsApp messages transmit appointment details and recipient contact information to the configured delivery provider. WhatsApp messages require the client's opt-in. Message status and delivery receipts are retained in the business message history.