Privacy policy

The operator and your professional

Vikno is provided by the sole proprietor identified below. The operator organises data processing for sign-in, service operation, security and support.

Each professional decides which services to offer and how to use client data to organise them. Vikno provides the technical processing of those bookings. Ask the professional about a particular appointment; you can also contact the operator about data held in Vikno.

Data we receive

When in-app Plus purchases are available, we verify the product and purchase identifiers supplied by Apple or Google, account binding, subscription status and period, and verification records. An unfinished purchase proof may be kept in protected device storage. Vikno does not receive a full card number or CVV from the system payment flow.

Professional profiles: name, page link, time zone, services, prices and working hours. Optional details include studio name, description, specialty, Instagram, address, entrance directions, greeting and selected photos. Photos are re-encoded without EXIF metadata.

App sign-in: an Apple or Google identifier or an operator-issued username; a random installation identifier, platform, device name and session data. For username sign-in, the password is sent for verification, is not stored by the app and is retained on the server only as a protected hash. Google may supply a basic profile and email; Vikno’s server retains the identifier rather than the email in that proof. Telegram web sign-in, when available, supplies its identifier, name and avatar URL.

Client bookings: name, service, time and one contact — phone, Instagram or Telegram. A contact is required on the public booking page and optional when the professional adds a booking. We also retain changes, cancellations and appointment outcomes. Contacts are entered manually: the app does not read your address book. A name or username does not verify identity.

When online Plus checkout is available: order, subscription and payment identifiers, amount and currency, payment status, access period and evidence of the accepted terms and renewal consent. These support payment verification, access, cancellation and refund requests. Without ordering the paid offer, viewing the site does not create a payment order.

Technical data: IP address and connection details, security identifiers, request times and results. These support service operation, access checks and abuse prevention. Cloudflare Turnstile receives an IP address and technical browser signals to protect public bookings against bots.

Support requests: sender address, message and details you provide to answer or verify the request. Do not send passwords, identity documents, medical information or unnecessary information about others.

Purposes and grounds for processing

Account and booking data is used to provide the service you request: sign-in, the professional’s page, availability, booking creation and recovery, history and statistics. Statistics describe bookings and service value rather than verified payments.

Fraud prevention, access checks and troubleshooting serve the operator’s and users’ legitimate interests in a secure service. Optional messages require your separate choice. Where data is necessary to fulfil a legal obligation, we process it on that basis.

Demo mode uses fictional data and does not create an account. Demo bookings are not sent to a professional as real appointments.

Messages and consent

You can enable optional booking push notifications in app settings. Delivery uses a device token, platform, language and notification settings. Apple Push Notification service delivers iOS alerts and Google Firebase Cloud Messaging delivers Android alerts. Delivery depends on device permissions and connectivity. Notifications show the event, such as ‘New booking’, and the date and time in the professional’s time zone. A generic ‘Schedule updated’ message may be used for compatibility. Visible text excludes client names, contacts, services and addresses. Opening a notification loads the schedule after access is checked.

The Telegram bot is connected separately when that feature is available. Messages may include the service, date and time; messages to professionals also include the client’s name. Entering a Telegram contact does not consent to bot reminders. You can disable optional messages in settings or send /stop to the Telegram bot. Delivery may be delayed or fail.

Who can access data

Server records are stored in Cloudflare D1 and uploaded photos in Cloudflare R2. Cloudflare also runs the website infrastructure and bot protection. Apple and Google participate in your selected sign-in and notification delivery; Telegram participates in selected Telegram features. Support correspondence is handled by email.

For Plus payments, when available, mono receives the amount, currency and payment-order details. Card details are entered on mono’s payment page; Vikno does not accept or store a full card number or CVV. The payment provider processes data under its own policies.

Visitors with the link can see the public profile and permitted photos. The professional chooses address visibility: hidden, public or after booking. Anyone holding a private confirmation link may open its allowed details. Client data is available to the corresponding professional through secure sign-in and is not published as a list. If an appointment is entered in a studio calendar, the studio owner, its managers and the assigned professional can see it.

Providers may process data outside Ukraine. You can ask the operator about recipients, processing locations and applicable safeguards. Links to Instagram, maps or an email app open external services with their own policies.

Device data and cookies

A protected unfinished purchase proof may remain after sign-out so only the same account can resume verification. The app removes the relevant local record after successful verification or accepted account deletion when secure storage is accessible. This does not cancel a store subscription.

For subscription management and the reminder before account deletion, the app may separately keep minimal protected information identifying the linked account, product and observed purchase state. It may remain after purchase verification and sign-out. A local pending or unclear state does not prove a payment, an active subscription or a future charge. We remove this information only after matching confirmation that the relevant purchase has ended, or during accepted account deletion when protected storage is accessible. Without reliable confirmation, it may remain for checking in the store.

The app stores a session, a local copy of working data and drafts. Signing out clears the session and ordinary local working data, except for the protected purchase information described above, but does not delete the account. Language and appearance settings may remain. An accepted deletion’s status code may be kept separately to check completion.

Necessary secure cookies support a professional’s session for up to 7 days, sign-in for up to 10 minutes and booking protection for up to 24 hours. The browser also stores the selected appearance and temporary retry data for an unfinished booking: key, service, time and time zone. The client’s name and contact are not written to that retry storage. A private confirmation link may remain in browser history.

Advertising and analytics

Vikno does not sell personal data or use advertising tracking. The apps have no analytics or crash-reporting SDKs. Firebase Messaging is used for notifications, not Firebase Analytics. Booking statistics are a professional’s working tool. The service does not send automated email campaigns.

When this feature is on, the website and booking pages count anonymous visit statistics without cookies or browser storage: the kind of page (home, sign-in, booking and so on), the booking step reached, the device type by screen width, the site the visitor came from and campaign tags. The identifier is random and lasts only until the page is reloaded. The page address, the professional’s link, names, contacts and booking details are not sent. Vikno’s server forwards these events to PostHog in the EU without the IP address and with location lookup off. Nothing is sent when the browser has Do Not Track or Global Privacy Control on. The purpose is to understand which pages and booking steps work and to improve the site (legitimate interest). The professional’s cabinet and the apps are not tracked this way.

Retention and deletion

Deleting a Vikno account does not by itself stop an Apple or Google subscription renewal or delete the store’s purchase records. If you use a store subscription, review and, if needed, cancel renewal in the store’s subscription settings. You can still request immediate deletion of your Vikno account.

Profiles and booking history remain while the account exists. There is no general automatic deletion for inactivity. Expiry of a session or private link does not delete a booking. Support correspondence is used to resolve the request, related issues and protect rights; mandatory retention is determined by law.

You can delete your account in the app: Settings → Delete account. You can also request deletion of the account or of individual data through support: after verification, we explain the next steps, the outcome and any data that needs to be retained, with the reason.

An accepted deletion request immediately blocks the page and new bookings, revokes sessions and cancels confirmed appointments starting after the request time. The profile, bookings, client records, services and photos are cleaned up in stages. The status code lasts 30 days from the request; a minimal completed-procedure record is scheduled for cleanup 90 days after completion, and reservation of the former page link after 30 days. An expired code or error does not confirm deletion.

A minimal deletion record (operation and account identifiers, time) is kept so that, if data is restored from a backup, the deletion is applied again before the service is back in use.

Cleanup of the main system does not mean immediate deletion of backups or all technical security records. There is no single verified backup-erasure deadline. Ask support about your data’s status and reasons for continued retention. We do not confirm full deletion based solely on acceptance of a request.

Your rights

You can ask about access to your data, recipients and purposes, correction, deletion or objection to processing. You can withdraw consent to optional messages without affecting the lawfulness of earlier processing. Personal-data requests are handled within applicable legal time limits, verifying only the information needed about the requester.

In Ukraine, you can complain to the Ukrainian Parliament Commissioner for Human Rights or a court. Where the GDPR applies to processing, its rights also apply, including restriction, portability and a complaint to a competent data-protection authority. Use the address below or the support page’s deletion section to contact us.