Privacy policy
Effective 27 September 2026. Applies to the Navbat Telegram bots, the Navbat Mini Apps and the website at this domain (together, «Navbat»).
1. Who we are
Navbat is an appointment and reminder service for independent specialists («masters») and their clients, operated by the Navbat developer. Contact: akbarpulatov7@gmail.com.
2. What we collect and why
| Data | Source | Purpose |
|---|---|---|
| Master profile: Telegram user ID, display name, language, working hours, services and prices | Entered by the master in the Master Bot / Mini App | Running the master's appointment book |
| Client records: name, phone number, language, reminder preferences and, once connected, Telegram user ID | Entered by the master, shared by the client in the Client Bot, or found in a connected Google Calendar event | Booking visits, sending notifications and reminders, letting the client see their visits |
| Appointments: service, date and time, status, notes, who created them | Created by masters, clients or the Google Calendar import | The core service |
| Technical event log: timestamps of bookings, notifications, sync runs and errors | Generated by the service | Reliability, support and abuse prevention |
3. Google Calendar data
A master may connect a Google account. Navbat then requests read-only access to that calendar
(calendar.readonly) and the account's email address (userinfo.email, shown in the settings so the master knows which account is connected).
- Navbat reads events from the connected calendar from the current moment up to 60 days ahead: title, description, location, attendee names and e-mails, start and end times, status.
- This data is used for one purpose only: to mirror the calendar into Navbat. Events containing a phone number become appointments for that client (the client may be notified in Telegram); events without a phone number become blocked time. Google edits move or cancel the corresponding appointment.
- Navbat never creates, edits or deletes anything in your Google Calendar.
- OAuth tokens are stored encrypted at rest and are used only to perform this synchronisation. They are deleted immediately when the master disconnects the calendar (Settings → Google Calendar → Disconnect) or revokes access in their Google Account.
- Navbat's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. Google user data is not used for advertising, is not sold, and is not shared with third parties except as needed to provide the service described here; humans do not read it except with the master's explicit consent for support or as required by law.
4. Sharing
We do not sell personal data. Data is shared only with the parties needed to run Navbat: Telegram (delivering bot messages), Google (only when a master connects a calendar), and our hosting provider Fly.io (servers located in the European Union, Frankfurt), and when required by law. A master sees the data of their own clients; a client sees only their own appointments.
5. Retention and deletion
Data is kept while the master's account is active. Disconnecting Google Calendar deletes the stored tokens at once; appointments created from it remain in the master's book. A master or client may ask for their data to be corrected or deleted by contacting akbarpulatov7@gmail.com; we answer within 30 days.
6. Security
All traffic uses HTTPS. Mini App requests are authenticated with Telegram's signed init data. The database lives on an encrypted volume. Access to the operator dashboard is password-protected.
7. Children
Navbat is not directed at children under 13 and does not knowingly collect their data.
8. Changes
We may update this policy; the effective date above changes when we do. Material changes are announced in the bots.