Privacy Policy

From the company owner (admin): name, email, password (stored as a hash, never in plain text), company name and address.

From clients of companies using Zabook: name, phone, email (optional), booking history, and niche-specific fields (vehicle model, pet type, device model — depends on the company) — only if the client provided them.

Technical data: admin and client session cookies, and an interface-language preference cookie. We don't use third-party ad trackers or sell data to anyone.

To make online booking and CRM work for the company: showing available slots, creating and storing bookings, maintaining client records.

Notifications: booking confirmations, status changes, and reschedules are sent by email. Reminders and Telegram delivery are still in development.

Database: PostgreSQL, hosted on Neon. The application runs on Vercel. Data for companies from Canada and Russia currently lives in a shared database; this may change as the service grows, and we'll update this page if it does.

A company's client data is visible only to that company (its admins) — Zabook is a technical infrastructure provider, not the owner of any company's client base. CSV export of a company's own client list is available to its admin at any time.

Online payments aren't wired up yet (in development — Stripe for Canada, YuKassa for Russia). Once live, payment details will be processed directly by the payment provider — Zabook will not store card numbers.

A client of a company can request deletion of their data from that company — the company admin is responsible for handling such requests. If you need help, contact us directly (see below).

The service isn't intended for children under 16.

We may update this page as the product evolves — the date at the top shows the last update.