Privacy Policy

Last Updated: November 8, 2026

This Privacy Policy explains what personal data M-TIME processes, why we process it, who we may share it with and what rights you have. It applies to the website, PWA, mobile web interfaces, profiles, calendars, bookings, payments, notifications and other M-TIME features ("Platform"). The Ukrainian version prevails over any translation.

1. Data Controller

The controller of personal data is Individual Entrepreneur Rudenko Mykhailo Ihorovych ("Operator", "we", "us"), Ukrainian tax ID 3521802553, operating under the M-TIME trade name.

• Request email: find.slot.ua@gmail.com
• Correspondence address: Ukraine, Pavlohrad, Pryvitna St, 21

2. Data We Process

2.1. Account data: first name, last name or public name, email, phone number, language, user role, account settings, activation statuses, legal-document acceptance version and time, account creation and update dates.

2.2. Master or Company Profile data: public name or business name, photo or logo, description, education and experience, categories, attributes, services, prices, duration, website and social links, address or working area, precise geolocation coordinates, schedule, time off, contact channels, portfolio, Company membership, ratings, reviews, subscription status and billing history. Fields marked as public by the interface are shown to Platform visitors.

2.3. Business verification data: subject type, legal name, registration identifier in raw, normalized and masked forms, representative name and role, email, phone, applicant note, accuracy-attestation version and time, status, decision reason, review metadata and resubmission history. The current form does not accept document scans or biometric images. The full identifier and internal review data are not published.

2.4. Booking and communication data: Master, Client, Company, service, date, time, duration, price, booking status, party name/photo/contact snapshots, notes, chat messages, change history, cancellation reasons, proposals, notifications and service records needed for booking performance, support and disputes.

2.5. Payment and recurring billing data: amount, currency, selected plan and cadence, paid-through and next-renewal dates, recurring agreement and cancellation status, payment description, order_id, payment status, transaction identifier, payment date, LiqPay status, failure reason and limited technical payment attributes. Where recurring billing is authorized, this also includes the opaque LiqPay card token and payment-specific payer IP supplied in LiqPay's signed successful initial callback. M-TIME does not store full card numbers, CVV/CVC, PIN codes or full payment instrument credentials.

2.6. Technical, search and analytics data: IP address, device and browser type, operating system, language, time zone, session and device identifiers, Firebase/Auth data, push tokens and web-push keys, Telegram identifiers, search queries and embeddings, error and performance logs, security events, App Check data, Meta _fbp/_fbc, cookies or similar technologies used to operate, secure, analyze and promote the Platform.

2.7. Requests, safety and leads: support requests, emails, messages, attachments, request history, complaints, blocks, M-TIME team replies, internal support notes, and voluntarily submitted prospective-Master contact, city, work-format/message, marketing source/UTM and landing path.

2.8. Sensitive data in free text: M-TIME does not request and prohibits special categories of personal data in free-text fields, including diagnoses, symptoms, medical history, test results, medical documents, prescriptions, treatment information, biometric data, political opinions, religion or intimate-life information. Do not add them to a profile, chat, support request, complaint or another free-text field. If you nevertheless disclose such data on your own initiative, that does not mean M-TIME requested it or that the channel is suitable for medical information.

2.9. Medical services are not supported: M-TIME no longer has medical categories and is not intended for offering medical services or arranging appointments with doctors. Disclosing medical information through free-text fields is prohibited (section 2.8). M-TIME does not create a medical record.

2.10. Reviews imported from Google: at the request of a Master or Company Profile owner, M-TIME imports the Profile's public reviews from Google Places (Google Maps). The source of this data is Google Places: the quoted authors do not provide it to M-TIME directly. For each review we store and show on the Profile the author's public name, the link to the author's public Google profile photo, the review text, rating and date. We process this data on the basis of legitimate interest - to show Clients a Master's existing public reputation. If you are the author of an imported review and want your name, photo or text removed from M-TIME, email find.slot.ua@gmail.com with a link to the Profile and the review; after a proportionate check we will remove the review from M-TIME. This does not change the review on Google itself.

2.11. Booking for another person: a Client may book for another person (the "Visitor") and enter that person's name and phone. The Client is the source of this data and, before every such booking, confirms that the Visitor agreed to share it with the Master for this booking; we store the version of that confirmation and the server-recorded time. The purpose is performing that booking at the Client's request: only the Client, the assigned Master, the Company owner or the manager of its place, and M-TIME administrators see the Visitor's name and phone; they are not published and do not reach search, notifications or analytics. M-TIME sends the Visitor no messages and does not link the phone to any account. The Visitor's phone is deleted 30 days after the booking is completed, cancelled or rejected; the name stays in the booking history. A Visitor may ask for their data to be deleted by writing to find.slot.ua@gmail.com.

2.12. Booking created by a Master: a Master may create a booking for their own client, arranged outside M-TIME, without entering the client's name, phone or other data. Such a booking is not published and has no client until the client opens the Master's personal link and signs in to their account or registers (no phone number is needed): the booking is then linked to that account, and the Master sees the account's name, photo and, if present, phone - as in a booking the client made themselves. The Master may add an optional private label of up to 40 characters that only they see; we delete it when the booking is linked to a Client account or 30 days after the visit ends. The label does not appear in notifications, analytics or to M-TIME administrators.

2.13. Recognizing booking text: at the Master's request, M-TIME uses Google Cloud Vertex AI (Gemini) to prepare booking proposals from pasted text. The browser and server automatically remove recognized phone numbers and email addresses before sending the text to Google. This does not guarantee that all other personal data is absent: submit only text you are entitled to use for this purpose, without the medical or other sensitive data listed in section 2.8.

For recognition, Google receives a cleaned copy of the text, the names, technical identifiers and duration information for the Master's current Personal Services, and the current date and local time in the Master's time zone. The original text and proposal draft are used only for the current recognition and review in the browser; M-TIME does not keep them as import history in databases or include them in logs, analytics or error reports. After you confirm, the selected proposals become ordinary bookings with their applicable retention periods. An AI-suggested private label is saved only if the Master keeps it; the limits and retention in section 2.12 apply.

M-TIME does not use this text to train models. Under the Google Cloud terms, using customer data to train or fine-tune models requires the Google Cloud customer's prior permission or instruction. Google may nevertheless temporarily retain data for caching, security and abuse monitoring under its data-processing rules. Having no import history in M-TIME does not mean that Google retains no data. International processing is described in section 6.

2.14. A Master's private client notes: a Master may keep, about each of their clients, one private note of up to 2,000 characters and tags chosen from a fixed list that is the same for every Master. Only that Master sees them: they are not shown to the client, Company administrators or reception, or in M-TIME emails, bookings or public pages. The rules of section 2.8 apply to the note. The note and tags are deleted when the Master removes them, or when the client's or the Master's account is deleted.

3. Legal Bases

We process personal data on these bases:

• contract performance or pre-contract steps - account creation, bookings, Master or Company Profile, business verification requested by the Profile owner, subscription, authorized recurring payments, cancellation and support;
• consent - marketing emails to Clients, push notification permission on your device or in your browser and optional settings where applicable;
• legal obligation - accounting, tax, payment and consumer records, responses to lawful requests;
• legitimate interest - security, fraud prevention, Platform improvement, rights protection, service analytics, handling requests and disputes, showing a Master's existing public reputation through reviews imported from Google Places, M-TIME promotional emails to Masters, and promotional pushes from Masters and Companies to Clients and weekly summary pushes to Masters (section 10), where such interest is not overridden by your rights; you can object to promotional emails at any time by turning them off in Settings or with the link in every email, and to promotional pushes and weekly summary pushes with the matching switch in Settings (section 10).

4. How We Use Data

We use personal data to:

• create, authenticate and maintain accounts;
• show Master profiles and help Clients create bookings;
• manage calendars, services, schedules, booking statuses and notifications;
• check business registration information and representative authority, keep decision history and permit resubmission after rejection or revocation;
• process the Master Subscription, keep paid-through access separate from recurring billing, securely store and use the LiqPay token and signed-callback payer IP required for authorized unattended renewals, stop future charges and clear both values after cancellation or terminal renewal failure, confirm payment, keep billing history and process refunds;
• send administrative messages about accounts, bookings, subscriptions, payments, security or document changes;
• send Clients promotional pushes from Masters and Companies, and send Masters weekly summary pushes about their profile, which can be turned off in Settings (section 10);
• provide support and review complaints;
• prevent fraud, unauthorized access, Terms breaches and security threats;
• comply with legal, tax, accounting and payment obligations;
• improve Platform stability, quality and usability.

5. Who We Share Data With

5.1. Masters: when a Client creates a booking, we share with the relevant Master the data needed to organize the service: name, contact, booking details, selected service, date, time and notes if added.

5.2. Clients: if a Master has a public profile, we show Clients Master profile data, including name, photo, description, services, prices, schedule, location or working area, rating and reviews.

5.3. Authorized M-TIME personnel and reviewers: only as needed for support, moderation, security, checking business registration and representative authority. Verification data is not shared with other users except for the public successful-verification status and date.

5.4. LiqPay and JSC CB "PrivatBank": for hosted card entry, issuing and using an opaque card token, returning the signed initial payer IP and receiving that IP on an authorized unattended token charge, accepting payments, confirming status, refunds, fraud prevention, chargebacks, financial monitoring and compliance with payment system rules.

5.5. Infrastructure and delivery providers: Google/Firebase/Google Cloud, Vercel, Sentry, Resend, FCM/APNs, Telegram and other hosting, authentication, database, file, push/email, support, error-monitoring and analytics providers receive only data needed for the relevant function. Sentry Session Replay is disabled; M-TIME may send Sentry scrubbed error reports, technical logs and performance data without intentionally recording user-session content.

5.6. Search, maps, sign-in, review and media providers: including Google/Apple, Google Places, Vertex AI, Nominatim/OpenStreetMap, CARTO and external media providers when you use the relevant function. They may receive a search or location request, coordinates, public Profile content, URL or request technical data. For booking-text recognition, Google Cloud Vertex AI (Gemini) also receives the data described in section 2.13.

5.7. Authorities, courts, banks and advisers: where required by law, to protect rights, respond to lawful requests, investigate fraud, handle payment disputes, tax or accounting records.

5.8. Business transfer: if M-TIME is merged, sold, transferred or reorganized, data may be transferred to a successor in compliance with this Policy and the law.

6. International Transfers

Some infrastructure providers may process data outside Ukraine. In that case, we use contractual, technical and organizational safeguards and transfer only data necessary for the relevant purpose.

Booking recognition uses Google Cloud Vertex AI (Gemini) in global mode (global): the request and related data may be processed in different countries, rather than only in Ukraine or one specified country.

M-TIME sends promotional emails through Resend (Resend, Inc., USA), which stores marketing contact data in the United States. For accounts that agreed to promotional emails, Resend receives the email address, first name, role (Master or Client), email language, their public booking link and Master referral link (when available), mailing topic subscriptions and the events that start an email (for example, finishing Profile setup or a first booking). If you turned promotional emails off, unsubscribed in an email, or the address is blocked after a bounce or complaint, Resend keeps only the email address marked as unsubscribed, so that no mailing reaches you. When an account is deleted, its contact is deleted from Resend.

7. Retention

7.1. Account data is kept while the account is active or while needed to provide the Platform. The record of a profile's promotional push that was sent to you, or that we decided not to send, is deleted 13 months after that decision if that promotion's send-out has finished (it was sent, simulated without sending or cancelled), and otherwise once it finishes. In-app notifications are kept for 180 days after they are created and then deleted, or for less if you delete them or your account. For Masters: the record of the decision whether to send you a weekly summary or reminder push is deleted 8 weeks after that decision; the log of an email campaign the M-TIME team sends to Masters, together with its recipient list, 6 months after the campaign ends; and the sending history of an automated email series 13 months after the series ends. The record that you were already enrolled in an email series is kept while the account exists, so the same series never starts again; unsubscribe links in emails you received keep working.

7.2. Booking data is kept in the working database as both parties' booking history for support and disputes for 1 year after the booking ends. Once 12 months have passed since a booking ended, the booking (whether it took place, was cancelled or was rejected), together with its change history, service records and chat, is copied to an archive and, after the copy is verified, deleted from the working database. The archive is private Google Cloud Storage with no public access in the EU region europe-central2 (Warsaw, Poland), Coldline storage class; data in it is encrypted and is not shown in the app. Each archive copy is deleted automatically 5 years after it is created. If the Master deletes their account, the bookings with them are deleted from the working database together with their profile. The exact address of a visit at the Client's place is deleted 30 days after the booking is completed, cancelled or rejected, and so is the Visitor's phone (section 2.11). Booking chat messages, including the Master's automatic out-of-hours replies, are kept while both participants' accounts exist, but no longer than the booking itself stays in the working database. Data of an unfinished booking is deleted 30 days after your last time pick (section 10).

Deleting a booking does not delete its review: the review stays on the Master's or Company's page while their profile exists or until the review is removed. For each pair of a Client and a Master or Company we keep a short summary - the dates of the first and last visit and the number of visits - while the Client's account and the Master's or Company's profile exist. It keeps the first-visit discount and the new or returning client label working after old bookings are deleted. Likewise, while the Client's account and the Master's or Company's profile exist, we keep a marker that the Client has already used that Master's or Company's new-customer discount, so it can be received only once; the marker is deleted together with either account. After old bookings are deleted we also keep, for each pair of a Client and a Master (and, where the Client booked that Master within a Company, separately for that Company), the creation date of the very first booking, the source the Client came from, where it was made (with the Master or in a Company) and its technical identifier. This lets us correctly tell how the Client came to the Master or Company and whether a new booking is a repeat booking; it is kept while the Client's account and the Master's and Company's profiles exist and is deleted together with any of them.

7.3. Business-verification applications and decision history are retained while the Profile exists, for resubmission, audit, security or a dispute, and are deleted together with the Profile. A prior rejected or revoked application is not overwritten by a new one. The raw and normalized forms of the registration identifier are deleted 30 days after the decision on the application; only the masked form stays in the application.

7.4. Payment, accounting, tax and legally significant records are kept for the periods required by law, LiqPay/bank/payment system rules or limitation periods, including after account deletion (section 7.5). The usable LiqPay card token and payment-specific payer IP from the signed initial callback are retained together only while the Recurring Billing Agreement is active. After cancellation or a terminal renewal failure, M-TIME clears both values, while retaining non-token and non-IP billing records where required. If either value is missing or invalid at initial payment, M-TIME grants the paid period without retaining renewal credentials or activating recurring billing.

7.5. Self-service deletion is available in Settings after active bookings have finished or been cancelled. It closes the Firebase Auth account and deletes your account, profiles, services, schedule, photos, settings, notifications, push devices, your booking chats (including the other party's messages), support requests and unfinished booking data. After deletion we keep the following records for other people, accounting, security or service improvement:

• we keep a server-only deletion record with the technical account identifier, source, time and processing state to prevent deleted data from being recreated. It also retains the deletion reason you choose and an optional Other comment (up to 500 characters), accessible to administrators to understand why people leave and improve the service. You can choose not to provide a reason. These records have no automatic deletion period; do not include personal or sensitive information in the comment;

• bookings in which you were the Client stay in the Master's or Company's history without your data for the period in section 7.2: your name is replaced with "Former client", and your photo, phone, note, exact visit address and your cancellation reason are deleted. The service, date, time, price, status, the discount terms stay without your name, as does the name of a Visitor you booked for (section 2.11);

• your reviews stay on the Master's or Company's page signed "Former client" without a photo;

• account deletion does not change copies of bookings and chats already moved to the archive (section 7.2): they are deleted at the end of their 5-year period. So that a deleted account's bookings are never restored from the archive to the working database, we keep in the archive the technical identifier of the deleted account and of its profiles and the deletion date, also for up to 5 years;

• billing history stays under a technical identifier of the former account, without a link to a profile, for the period in section 7.4;

• an open complaint that you filed, or that was filed about your Master profile, stays until an administrator reviews it. After the review such a complaint is not deleted automatically: an administrator deletes it manually. Complaints reviewed before you delete your account are deleted with it;

• if the account was blocked on the Platform, the block record and its history are kept, and the protected email, phone and sign-in identifiers are kept while the block is in force, to prevent registering again.

Account deletion does not change an application you submitted as a prospective Master. If you never registered as a Master, the application is deleted 12 months after you last submitted it. Technical logs, provider copies and backups may be kept longer under their own periods. For a comprehensive access or deletion request, including data in secondary systems, email find.slot.ua@gmail.com.

8. Security

We use reasonable technical and organizational measures: authentication, access control, Firebase/App Check, server-side payment signature and merchant validation, server-only access to renewal credentials, database access restrictions, security event logging and payment data minimization. Card tokens, payment-specific payer IPs and private keys are not exposed to clients or intentionally written to routine logs. No transmission or storage method is completely secure, so we cannot guarantee 100% protection.

9. Your Rights

Under personal data protection law, you may have the right to:

• know the sources of collection, location of your personal data, purpose of processing and persons to whom it is disclosed;
• receive information about access conditions for personal data;
• receive confirmation whether your personal data is processed and access it;
• request correction, update, blocking or deletion of data if it is processed unlawfully or is inaccurate;
• withdraw consent where processing is based only on consent;
• object to processing in cases provided by law;
• complain to the Ukrainian Parliament Commissioner for Human Rights or to a court.

To exercise your rights, email find.slot.ua@gmail.com. We may ask you to verify your identity proportionately so we do not disclose data to someone else. We will state within 10 business days whether the request will be fulfilled and provide processing/access information within 30 calendar days after receiving a valid request unless the law requires another period.

10. Cookies, Local Storage and Push Notifications

M-TIME may use cookies, localStorage, sessionStorage, push tokens and similar technologies for login, settings, language, city, session, security, PWA operation and notifications. You can restrict these technologies in browser or device settings, but some features may not work correctly.

M-TIME automatically uses a configured Meta Pixel integration in the background to measure marketing campaigns, without a separate marketing consent prompt or setting. Tracking is limited to an explicit list of public discovery, Profile, Company and master-setup pages. It is disabled on private/auth pages and URLs containing credentials, unknown parameters or precise coordinates. A browser event may include the allowed public page URL, event name, browser/device data, the browser's IP address and the Meta _fbp/_fbc identifiers. For a signed-in user, the browser Meta Pixel receives SHA-256 hashes of the normalized account email, the phone (if provided, including the phone a Master supplies during registration) and an account identifier, to measure advertising and match it to that user's events. Plain email, phone and identifier are not sent to Meta; the hashes remain pseudonymous personal data. When available, these hashes accompany that user's allowed public events. After signing out or switching accounts, matching data is cleared and browser events continue without these hashes until a fresh document loads. Users who are not signed in send no such hashes, and Client or Visitor details and free-text form content are not used for this matching.

Push notifications are sent only after permission on your device or in your browser. You may revoke permission in device or browser settings.

Promotional pushes are push notifications about offers from Masters and Companies you have already dealt with through M-TIME. If you allowed push notifications for your account on at least one device or browser, we may send you these promotional pushes:

• about a new discount from a Master or Company where you had a completed visit in the last 12 months;
• about a new service from such a Master or Company, or from a Master or Company you added to your favourites;
• about new free windows in the next 14 days from a Master you added to your favourites;
• about a last-minute window: when a Client cancels a booking less than 24 hours before it starts, at most 20 Clients who had a completed visit with that Master or Company in the last 12 months hear about the freed time (never the Client who cancelled);
• "Time to book again?": a reminder after a completed visit once your usual gap between visits to that Master or Company has passed (7 to 120 days), or, while there is no such gap yet, the typical gap for that service or 30 days; no reminder is sent if you have already booked again;
• one invitation to come back to the Master or Company of your last completed visit if 60 days have passed since it with no booking at all in that time.

For this we use the dates and services of your visits and bookings, your favourites, your account language and your devices' push tokens. A promotional push contains no personal data of yours, and the Master or Company receives no data about whom it was sent to. We send at most one promotional push from one Master or Company in 7 days and at most two from all of them together in 24 hours. Between 21:00 and 09:00 Kyiv time promotional pushes are not sent: such a push waits until 09:00 or, if by then it no longer makes sense (for example, the freed window has passed), is not sent. Promotional pushes do not go to members of the Master's or Company's team, to Clients who blocked them or were blocked by them, or to accounts banned on the Platform.

We send promotional pushes on the basis of legitimate interest - to tell Clients who have already used a Master's or Company's services or added them to favourites about their offers (section 3). They are on by default, and you can object to them at any time: turn off the "Offers from Masters and Companies" switch in Settings, under "Notifications" → "Push Notifications". The same switch turns off the unfinished booking reminder (below), but not notifications about your bookings, including the request to rate a completed visit. To receive no push notifications at all on a device, turn off "Push Notifications Permission" there or revoke the permission in device or browser settings. Records of promotional pushes sent or not sent are kept for the period in section 7.1, or less if you delete your account.

M-TIME sends Masters a weekly push about their profile: once a week, starting on Monday at 10:00 Kyiv time, a summary of last week's bookings and free days, or, if the profile takes bookings but has no free time in the next 7 days, a reminder to open the schedule instead of the summary, at most once every 14 days. Like promotional pushes, it is not sent between 21:00 and 09:00 Kyiv time. The basis is legitimate interest (section 3); you can turn these pushes off with the "Weekly summary for your profile" switch in the same Settings section. The morning plan with your bookings for today is a service notification, not a promotional push; its own "Morning plan" switch turns it off. The retention of decisions about weekly pushes is in section 7.1.

If you are signed in and pick a booking time but do not send the booking, M-TIME stores the profile, the service and the chosen time on its server (no free text) to remind you once by push notification an hour later, at most once every 7 days per profile. No reminder is sent if you turned promotional push notifications off in settings. This data is deleted 30 days after your last time pick. Nothing is stored for visitors who are not signed in.

11. Children's Data

M-TIME is not intended for independent use by children. If we learn that an account was created by a child without proper consent of a legal representative, we may restrict or delete that account.

12. Policy Changes

We may update this Policy. A new version becomes effective upon publication unless it states otherwise or the law requires otherwise. If changes materially affect your rights or paid features, we may ask you to reconfirm consent.

13. Contacts

If you have questions, requests or complaints about personal data, contact us:

• Email: find.slot.ua@gmail.com
• Correspondence address: Ukraine, Pavlohrad, Pryvitna St, 21