Privacy Policy
This policy explains how SlotSmile (the “Application”: the Android app, the Windows and web versions, and the online booking pages at slotsmile.app/m/…) handles personal data. The Application is provided by NBSerG, Ukraine (“we”, the “Service Provider”).
1. Who is responsible for your data
- Your account and subscription data: NBSerG is the data controller. Contact: slotsmile.app@gmail.com.
- The data about your clients that you enter into the Application: you (the master) are the controller. We process it on your behalf only to provide the Application’s features (storage, synchronisation, online booking) and do not use it for our own purposes.
- If you are a client who submitted a booking request: the master you booked with is responsible for your request. You can also contact us (see below) and we will help.
2. Data we process
The Application works offline: without an account your data stays on your device. We process the data below only to the extent you use the related feature.
- Account: if you sign in with Google, your name, email address and a unique account ID (Firebase Authentication).
- Data you enter: clients (name, phone number, notes, preferred message language), appointments (date, time, service, price, expenses, prepayment, notes), services and settings. It is stored on your device in encrypted form and, with Pro/VIP cloud synchronisation, also in Cloud Firestore.
- Photos (VIP): photos you add to a client are stored on your device and, if you enable photo sync, in a folder that the app creates in your own Google Drive.
- Google Calendar (Pro/VIP, optional): if you enable calendar sync, the app creates a calendar in your Google Calendar and writes your appointments to it. Access is requested only when you enable this feature.
- Purchases: subscriptions are handled by Google Play and RevenueCat. We receive the subscription status and an app user ID; we never receive your payment card details.
- Push notifications (optional): a device token, platform and language are stored when online booking or enabled Telegram notifications need them. Notifications cover booking requests and client replies; Telegram reply notifications contain the action and appointment time, without the client’s name or phone. Turning one feature off does not remove a token still needed by the other. Tokens are removed or disabled through sign-out, disabling the relevant features and account deletion; system notification settings also apply.
- Technical records: trial dates, monthly counters and delivery/deduplication records are linked to an account ID, even when they contain no name, email or phone. They support entitlement checks, limits, security and reliable delivery. Account-linked app records are included in server-side account deletion.
- Crash reports and diagnostics (release builds only): crash logs, device model, operating system and app version, and an installation identifier (Firebase Crashlytics).
We do not show advertising, do not use analytics or advertising SDKs, do not collect precise location, and do not use artificial intelligence to process your data.
Telegram (optional): we process the linked Telegram user/chat ID, the client’s international phone number, preferred language, connection status, appointment details and replies. For waiting lists we also process the selected service, date range, hours and weekdays. For return invitations we store consent, service opt-outs, intervals and delivery records to avoid duplicate invitations. Local seen markers are saved per account on the device.
3. Online booking pages
- A master can enable a public booking page (slotsmile.app/m/…). Visitors see the master’s display name, the services offered with their duration, and which days and times are free. No client names or other client data are published.
- When a visitor sends a booking request, we collect the name, phone number, optional comment, and the chosen service, date and time. The request is stored in the master’s account and shown only to the master, who can accept it (this creates an appointment and a client record) or decline it. We do not use these details for marketing and do not sell them.
- To accept the request the page sends it to our server (a Cloud Function in the EU), which checks it and stores it in the master’s account; no sign-in or email is needed. Your IP address is processed by Google’s and Cloudflare’s infrastructure to deliver and protect the page. The page uses no advertising or analytics cookies; it stores only the time of your last request in your browser to limit repeated submissions.
- To block automated abuse the form is protected by Cloudflare Turnstile, which processes your IP address and browser signals and may use strictly necessary technical storage. We also keep short-lived technical records (counters with a hashed form of your IP address) to limit the number of requests; they are deleted automatically, normally within a few days.
- If the master has turned on email confirmation, the page also asks for your email address. We use it once, to send you a one-time confirmation link through our email provider, and we do not store it with your request. Until you press the link, your name, phone number, comment and chosen time are kept in a temporary record that is deleted when you confirm or after the link expires (normally within a few days). The email provider keeps delivery logs for a limited period.
- By ticking the consent box you agree that the master receives and processes your details to arrange the appointment. To have your request deleted, email us with the address of the master’s page, your name and phone number.
3a. Telegram bot and booking inside Telegram
Telegram features are enabled by the professional and require the client to connect through an invitation. We use the connection to send appointment reminders and confirmations of accepted online bookings, and to deliver the client’s replies. A reschedule or cancellation reply is a request to the professional; it does not automatically change the visit. In My appointments we show future visits belonging to the verified connection. The Mini App uses Telegram-signed launch data to verify the user and may prefill the name and phone from the linked client card. The ordinary booking-page rules still apply.
Waiting-list participation is voluntary. The client chooses their service and acceptable dates and times and can withdraw the request. Return invitations require separate consent to the selected professional; the client can withdraw it or opt out of a service without disabling normal appointment reminders. Consent is not inferred from merely starting the bot. /stop stops bot messages but does not by itself delete records held by the professional. To request deletion, contact the professional or slotsmile.app@gmail.com.
Telegram appointment messages and waiting-list requests are used to provide the chosen scheduling service. Repeat-procedure invitations use the client’s separate opt-in consent, which can be withdrawn.
Telegram replies are automatically removed from our database according to the professional’s selected period (1, 7, 30 or 90 days), or can be deleted earlier. Waiting entries are removed on withdrawal/account deletion or after their expiry by the daily cleanup. Consent, opt-outs and the latest return-invitation cycle can remain while the linked professional’s account exists to honour preferences and prevent repeats. Short-lived bot links and delivery markers expire separately. Older unlinked technical push markers may remain until their existing expiry, up to about 31 days. Deleting a reply does not delete the underlying appointment.
3b. Client portal
The client portal uses Firebase Authentication in a regular browser or Telegram-signed launch data in the Mini App. A public master link may be saved without revealing private history. Visit history becomes available only through an existing verified Telegram connection or a short-lived, single-use invitation issued by the professional for one client card. We store the portal profile, saved masters, verified links, language, consent and waitlist preferences. The server returns only appointment time, service, status and professional details; it does not return internal notes, finances, photos or other clients’ data.
“I’ll come”, reschedule and cancellation are requests recorded separately from the appointment status. Removing a saved master or deleting portal access does not cancel a visit and does not delete the professional’s lawful business record. Portal deletion removes the portal profile, saved/verified links and portal access data; contact the professional regarding their own client card and visit records.
4. Why we use data and legal bases (GDPR)
- Providing the Application — account, synchronisation, online booking, subscriptions (performance of a contract).
- Optional features — Google Calendar, Drive photos, the consent box on the booking page (consent, which you can withdraw at any time by switching the feature off or contacting us).
- Security, preventing abuse of the free tier and of the booking pages, and fixing crashes (legitimate interests).
- Legal obligations, for example accounting records of purchases.
5. Google user data
SlotSmile accesses Google Calendar and Google Drive only when you turn on calendar or photo synchronisation, and only the calendar and the folder that the app itself creates. This data is used solely to provide those features.
SlotSmile’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. We do not use Google user data for advertising, do not sell it, and do not allow people to read it except with your consent, for security purposes, or to comply with the law.
6. Who else processes data
We use the providers below, who process data on our behalf under their own terms. We do not sell personal data and do not share it for advertising.
- Google (Firebase Authentication, Cloud Firestore, Firebase Hosting, Firebase Crashlytics, Firebase Cloud Messaging, Google Drive, Google Calendar, Google Play): Firebase privacy, Google Privacy Policy.
- RevenueCat (subscription management): Privacy Policy.
- Cloudflare (DNS for slotsmile.app and the Turnstile anti-bot check on booking pages): Privacy Policy, Turnstile Privacy Addendum.
- Resend (sending booking confirmation emails): Privacy Policy.
We may disclose data where the law requires it or where necessary to protect rights and safety.
Telegram is a separate messaging provider, not a private archive controlled solely by SlotSmile. Appointment details and replies pass through Telegram’s infrastructure and appear in the chat. Telegram handles its own account and message data under its Privacy Policy, including processing outside the EU where applicable. Only use this channel with clients who choose to connect; do not include unnecessary sensitive details in service names or messages.
7. Where data is stored
Our Cloud Firestore database is located in the European Union (Google multi-region eur3). Google and RevenueCat may process data in other countries, including the United States. Where data leaves the EEA, transfers rely on the mechanisms required by GDPR Chapter V, such as adequacy decisions or Standard Contractual Clauses. Our server functions run in Belgium (Google Cloud region europe-west1).
8. Retention and deletion
- Data on your device stays until you delete it or uninstall the Application.
- Cloud data stays until you delete it or delete your account. In the Application choose Account & Sync → “Delete account and all data”: your clients, appointments, services, settings, online booking page and all booking requests, the Drive photo folder and the calendar created by the app are deleted. See Delete your account and data. You can also request deletion by email; we complete it within 30 days.
- Online booking requests are also deleted automatically: about 30 days after the master accepts or declines a request, and about 14 days after the requested time if it was never answered. An appointment or client record that the master creates from a request is the master’s own record and stays until the master deletes it.
- Technical records: trial dates, monthly counters and delivery/deduplication records are linked to an account ID, even when they contain no name, email or phone. They support entitlement checks, limits, security and reliable delivery. Account-linked app records are included in server-side account deletion.
- Purchase records are kept by Google Play and RevenueCat as required by law. Backups are removed by Google on its own schedule. Crash data is kept for up to 90 days.
9. Your rights
Depending on where you live (including under the GDPR and the California CCPA/CPRA) you may have the right to access, correct, delete, restrict or object to the processing of your data, to receive a copy of it, and to withdraw consent. We do not sell personal information or share it for cross-context advertising.
Write to slotsmile.app@gmail.com; we respond within one month. For data about a master’s clients, please contact that master first; we will help the master to respond. You may also complain to your data protection authority (EDPB members; in the UK, the ICO).
10. Children
The Application is not intended for children under 16 (or a higher age of digital consent where applicable). We do not knowingly collect their data. If you believe a child has provided data, contact us and we will delete it.
11. Security
Your clients, appointments and services on the device are stored encrypted (AES-256), with the key kept in the system’s secure storage. Data is sent over encrypted connections and is encrypted at rest in the cloud by Google. Our database rules allow only the account owner to read their data (the public booking page contains no client data). No system is completely secure; in case of a data breach we will notify the authorities and affected users as required by law.
12. Changes
We may update this policy. The effective date above will change and, where required, we will ask for your consent.
13. Contact
NBSerG, Ukraine · slotsmile.app@gmail.com