Privacy Policy
This document explains what data the platform processes, for what purpose and on what legal basis, who receives it, and what rights you have.
Who processes your data
Maydanchyk (the "Platform") is a service for car dealers: a dealer maintains its vehicle catalogue in the dashboard, and the Platform displays it on the dealer's branded website and publishes listings to Telegram, Instagram, Facebook and TikTok on the dealer's behalf, and places listings on OLX from the OLX account the dealer connected.
The controller of personal data relating to the operation of the Platform itself is Individual entrepreneur Dmytro Bondarchuk (registration number 3608503538), Kyiv, Ukraine.
Data requests go to dmytro.bondarchuk.wm@gmail.com. We reply within 30 calendar days and charge nothing for it.
On Meta for Developers the Platform is registered as the app Maydanchyk; on Telegram it operates through the bot @car_dieller_publisher_bot; with OLX, through the OLX partner API.
Who is responsible for what
The same data passes through different responsible parties on the Platform, and that determines whom you should contact.
- For dealer staff accounts, sessions, technical logs and cookies, the Platform is the controller: we decide what is collected and why.
- For listing content, photographs, contact details and opening hours, and for buyers' callback requests from the dealer website, the dealer is the controller. Here the Platform is only a processor: we store and publish this data on the dealer's instructions and do not use it for our own purposes.
- Once a listing is published to a social network or placed on OLX, that network or OLX processes the data as well, under its own policy, which we do not control.
If your data appears on a dealer website as the seller or author of a listing, contact that dealer first. If they do not respond, write to us: we will either pass the request on or apply the technical means ourselves.
What data we process, for what purpose and on what legal basis
The table covers all data the Platform stores in its own database and object storage. We do not collect special categories of data — health, political opinions, biometrics — and we ask that they are not entered into listing descriptions.
| Category | Specifically | Purpose | Legal basis | Retention |
|---|---|---|---|---|
| Account | Name, email address, password hash, creation date, sign-in times; a one-time password reset link, if you requested one (valid for an hour); if you sign in with Google or Facebook, the identifier of your account there (we keep neither the network access tokens nor the profile photo) | Access to the dashboard, identifying a staff member; service communications: confirming a place in the programme for the first 10 dealerships, invoices, requests for feedback | Performance of the contract with the dealer | While the account exists (up to 30 more days in database backups) |
| Sessions | Session token, IP address, user agent, timestamps | Keeping you signed in, detecting session hijacking | Performance of the contract; legitimate interest in security | Until sign-out or session expiry |
| Team invitations | Invitee email address, role, invitation state | Adding a staff member to the dealer dashboard | Performance of the contract on the dealer's instructions | Until accepted or declined, then kept in the dealer's history |
| Dealer profile | Name, phone numbers, address and map pin coordinates, opening hours, timezone, logo, subdomain | The dealer website; service communications by phone | Performance of the contract; publication is the dealer's instruction | While the account exists |
| Listings and photographs | Vehicle specifications, price, description, VIN, photographs: the uploaded original and a 4:3 frame for the website and posts | The dealer website, posts to social networks | Performance of the contract on the dealer's instructions | Until the dealer deletes them (up to 30 more days in database backups) |
| Social network access | Access tokens (encrypted), channel, page or Instagram account identifier, Meta or Instagram user identifier, TikTok user identifier (open_id), Instagram and TikTok account names | Publishing on the dealer's behalf; handling data deletion requests from Meta (through Facebook or Instagram) and Facebook's, Instagram's and TikTok's notices that access was revoked; revoking TikTok access when the channel is disconnected | Consent given by the dealer when connecting the channel | Tokens — until the channel is disconnected in the dashboard or the network tells us access was revoked; identifiers and the account name — while the dealer account exists, since the publication history refers to them |
| OLX access | Access tokens (encrypted), the OLX user identifier, name and email address, the account type (private or business), the city and district of the listings and, when they were found from the map pin, its coordinates | Placing, updating and taking down listings on OLX on the dealer's behalf; showing in the dashboard which OLX account is connected | Consent given by the dealer when connecting the OLX account | Tokens — until OLX is disconnected in the dashboard or another OLX account is connected; the account identifier, name and email, the city and district — while the dealer account exists, since the listings on OLX refer to them |
| Listings on OLX | The OLX listing identifier, its state and the moderation rejection reason, the title and description if the dealer edited them for OLX, the values of the fields OLX requires beyond the vehicle card, error text, timestamps | Keeping the OLX listing in line with the vehicle: updating it, taking it down once sold, deleting it with the vehicle | Performance of the contract on the dealer's instructions | While the vehicle exists; for a deleted vehicle — until OLX confirms the listing is deleted or the dealer connects another OLX account |
| Publications | Post text, message identifiers in the network, state, error text, timestamps | Showing publication state, retrying a failed post, deleting a post | Performance of the contract | While the listing the publication belongs to exists |
| Callback requests | The buyer's name and phone number, an optional comment ('what car are you looking for'), the catalogue filters the request was left with, timestamp; the dealer's mark that the buyer was called back, and which team member set it | Calling the buyer back and finding a car for the request | The buyer's own request — steps taken at their request | 12 months, then deleted automatically; earlier when the dealer deletes the request or the account |
| Technical logs | IP address, user agent, request path, response code, timestamp | Security, fault diagnosis, investigating abuse | Legitimate interest in a reliable and secure service | Up to 90 days |
| Email enquiries | The address you wrote from, the message body and attachments | Replying, fulfilling a data request, evidencing that it was fulfilled | Fulfilment of a data subject request; legitimate interest | 12 months after the enquiry is closed |
| Support activity log | Which platform staff member performed an action, what the action was, which account it concerned and when; for a deleted dealer — its name, subdomain and owner email | Accountability of support access to dealer dashboards; evidence that a deletion request was fulfilled | Legitimate interest | 12 months |
We do not sell data, do not pass it to advertising networks and do not use it to display advertising.
The legitimate interest we rely on for sessions, logs, enquiries and the support activity log is keeping the service running, protecting dealer accounts from takeover, keeping support access to dealer dashboards accountable, and being able to evidence that a deletion request was carried out. We have balanced it against your interests and keep the minimum this requires.
Visitors to the platform website and dealer websites
The public pages — the platform website and the dealer websites on subdomains — require no registration. Their only form is «Call me back» at the bottom of a dealer catalogue (see «Callback requests from dealer websites»); there are no subscriptions or mailing lists. We ask a visitor for no other personal data.
Opening a page leaves a technical record on the server: IP address, user agent, page path, response code and timestamp. It is needed to keep the service running and to investigate a fault or an attack, and it is kept for up to 90 days.
There is no web analytics, no advertising pixels and no third-party trackers on the public pages, and no cookies are set there at all. Vehicle photographs are fetched by the Platform server from Cloudflare object storage and served by the Platform itself; the browser loads only the dealer website icon directly from Cloudflare, when the dealer has added a logo. Cloudflare sees the technical details of such a request but does not link them to your identity or profile you for advertising.
When a dealer has marked their location, the contacts block of their website carries a map. The browser loads its tiles directly from OpenFreeMap (Hyperknot Software Kft., Hungary) — only as the block nears the screen. OpenFreeMap sees the IP address and the request address, sets no cookies and does not write IP addresses to its regular logs (only to an error log kept for up to 7 days). The get-directions button is a plain link to Google Maps: Google receives data only once you press it.
If you call a dealer on the number shown on the website, or message them on a social network, that is direct communication with the dealer — the Platform neither sees nor stores it.
Callback requests from dealer websites
At the bottom of the catalogue on a dealer website there is a «Call me back» form: your name, your phone number and, if you wish, what car you are looking for. The catalogue filters you left the request with are stored with it, so that the dealer sees at once what to offer you.
- The controller of this data is the dealer on whose website you left the request. The Platform stores the request on their instructions and does not use it for its own purposes.
- Only the owner and the staff of that dealer see the request, in their dashboard; it is not passed to other dealers or third parties.
- The legal basis is your own request: you ask to be called back.
- A request is kept for 12 months and then deleted automatically; earlier as soon as the dealer deletes it or the dealer account is deleted.
- To keep the form free of spam we count attempts from one address and for one phone number. The counter holds only a SHA-256 hash, not the IP address or the number itself, and it disappears once the limit window passes (up to one day).
To change or delete a request, contact the dealer; if they do not respond, write to us.
Cookies and similar technologies
We use strictly necessary cookies only — the dashboard does not work without them. There are no advertising, analytics or tracking cookies, which is why we show no consent banner for them.
- "better-auth.session_token" (over HTTPS — "__Secure-better-auth.session_token") — the httpOnly dashboard session cookie. Signing in is impossible without it. It lives until sign-out or session expiry.
- "meta_oauth_nonce" — an httpOnly cookie holding a one-time value that proves the Facebook dialog was opened by this browser. It lives about 10 minutes and only while a channel is being connected.
- "meta_oauth_session" — an encrypted httpOnly cookie that carries the Meta user token between the return from Facebook and the page selection step. It lives 15 minutes and is erased as soon as a page is chosen.
- "tiktok_oauth_nonce" — an httpOnly cookie holding a one-time value that proves the TikTok sign-in was opened by this browser. It lives about 10 minutes and only while a channel is being connected.
- "instagram_oauth_nonce" — an httpOnly cookie holding a one-time value that proves the Instagram sign-in was opened by this browser. It lives about 10 minutes and only while a channel is being connected.
- "olx_oauth_nonce" — an httpOnly cookie holding a one-time value that proves the OLX sign-in was opened by this browser. It lives about 10 minutes and only while an OLX account is being connected.
- "better-auth.state" ("__Secure-better-auth.state" over HTTPS) — a signed httpOnly cookie that proves the Google or Facebook sign-in was opened by this browser. It lives 5 minutes and only during such a sign-in.
All seven are set on the dashboard domain. You can delete them through your browser — that is equivalent to signing out.
On the «Location» page of the dashboard the map and the address suggestions come from Google Maps. While it is in use, Google may use its own cookies and similar technologies under its own privacy policy. Dealer websites do not load Google Maps — the map there is OpenStreetMap, without cookies.
Transfers to social networks
Publishing happens only to accounts the dealer connected themselves, and only to the extent of the listing: the post text, the link to the vehicle page and the selected photographs.
- Telegram: the post is sent by the bot @car_dieller_publisher_bot, which the dealer adds as an administrator to their own channel. We receive no data about channel readers — the Bot API does not expose it. We store only the channel identifier and the message identifiers of what we sent, so that a post can later be updated or deleted.
- Instagram: publishing goes through the Instagram API on behalf of the professional Instagram account the dealer connected by signing in with Instagram; no Facebook page is needed. We store the encrypted access token (it is valid for 60 days, and we extend it while the channel stays connected), the account identifier and name, and the Instagram user identifier within our app.
- Facebook: publishing goes through the Graph API on behalf of a Facebook page. We store the encrypted page access token, the page identifier and the identifier of the Meta user who performed the connection.
- TikTok: the post is published through the Content Posting API to the account the dealer connected by signing in with TikTok. For every post the dealer chooses who can see it, whether comments are allowed and whether it is promotional. We store encrypted access tokens, the TikTok user identifier (open_id) in plain text, the account name and the post identifier.
The Meta and TikTok user identifiers are stored in plain text, unlike the tokens. This is deliberate: Meta's data deletion request and Meta's and TikTok's notices that access was revoked identify the person by that identifier alone, and an encrypted value would make it impossible to find whose tokens to erase. The Instagram user identifier is kept in plain text for the same reason: Instagram's data deletion requests and notices that access was revoked name it alone. The identifiers are not secrets and are meaningful only within our app.
Once published, a post lives by the rules of the network itself. We do not control how Meta Platforms, Telegram and TikTok further process published content, and we cannot remove a post that the dealer deleted with us but left in the network by hand. TikTok does not allow deleting a post through its API at all — it can only be removed in the TikTok app.
Placing listings on OLX
OLX is a classifieds marketplace operated by EMARKET UKRAINE LLC. A listing is placed there only from the OLX account the dealer connected themselves by signing in with OLX, and only for a vehicle the dealer chose in the "Publish" form. We work through the OLX partner API.
- What we send to OLX: the listing title and description, the vehicle details (including the VIN if one is given), the price, the photographs (OLX downloads them by link from our storage), the dealer's name and main phone number as the listing contact, the city and district and, when they were found from the map pin, its coordinates.
- When an account is connected, and when the dealer asks to find the place from the «Location» page, we send OLX the coordinates of the pin on the map so that OLX names the city and district for the listings. Without a pin, we look up the dealer's city and address on the map (through Nominatim) and send OLX the coordinates of the point found; we neither store those coordinates nor put them in the listings.
- What we store: encrypted access tokens, the OLX user identifier, name and email address, the account type, the listing identifiers and their state on OLX. Without them a listing cannot be updated with the vehicle or taken down once it is sold.
OLX decides on moderation, how long a listing is shown and what placement costs, and the dealer pays OLX for placement directly. We take down or delete a sold, withdrawn or deleted vehicle from OLX ourselves while OLX is connected. While OLX is disconnected we cannot change or take down listings already placed: they stay on OLX until the dealer connects the same account again or removes them on OLX. Listings placed on OLX other than through the Platform we neither see nor change.
Processors and transfers abroad
The Platform runs on third-party infrastructure. Each provider receives only the data its function requires.
| Provider | Country | What it processes | Why | Role |
|---|---|---|---|---|
| Hetzner Online GmbH | Germany (EU) | Application servers and the database | Hosting the service | Processor on our instructions |
| Cloudflare, Inc. | United States | Listing photographs, dealer logos and database backups | Object storage and image delivery; storing backups | Processor on our instructions |
| Hyperknot Software Kft. (OpenFreeMap) | Hungary (EU) | The visitor's IP address and request address when a dealer website shows a map | OpenStreetMap map tiles for the contacts block | Independent controller once the data is received |
| Google LLC / Google Ireland Ltd (Google Maps Platform) | United States, Ireland | The dealer's browser IP address, the address the dealer types on the «Location» page and the pin coordinates | The map, address suggestions and the address under the pin in the dashboard; dealer websites do not load Google Maps | Processor on our instructions |
| OpenStreetMap Foundation (Nominatim) | United Kingdom | The address or pin coordinates a dealer looks up in the dashboard, and the dealer's city and address when we find the place of the OLX listings; our server sends the request, not the browser | Finding a pin by address, an address by pin, and the city of the OLX listings | Independent controller once the data is received |
| Meta Platforms, Inc. / Meta Platforms Ireland Ltd | United States, Ireland | Post text and photographs, the page or Instagram account access token; on sign-in with Facebook, the fact that you sign in to the Platform | Publishing to Instagram and Facebook at the dealer's request; signing in to the dashboard with Facebook, if you choose it | Independent controller once the data is received |
| Google LLC / Google Ireland Ltd | United States, Ireland | The fact that you sign in to the Platform with your Google account; we receive your name, email address and account identifier from Google | Signing in to the dashboard with Google, if you choose it | Independent controller once the data is received |
| Telegram Messenger Inc. | Outside the EU | Post text and photographs | Publishing to the dealer's channel | Independent controller once the data is received |
| TikTok Pte. Ltd. | Singapore and other countries outside the EU | Post text, title and photos; account access tokens | Publishing to TikTok at the dealer's request | Independent controller once the data is received |
| EMARKET UKRAINE LLC (OLX) | Ukraine | Listing data and photographs, the dealer's name and phone number, the city, district and pin coordinates, the OLX account access tokens | Placing listings on OLX at the dealer's request | Independent controller once the data is received |
Transfers to the United States and other countries outside the EU take place on the terms the providers themselves offer (standard contractual clauses and participation in the applicable frameworks). Publishing to Instagram, Facebook, Telegram and TikTok and placing listings on OLX are transfers initiated by the dealer: without them the service does not perform its primary function.
No email provider is connected yet: in the current version transactional email, including team invitations, is not handed to an external service. As soon as a provider is in place we will add it to this table and update the revision date.
How long data is kept
The general rule: data lives while the dealer uses the service. Platform support deletes a dealer account on request (see "How to delete your data"): the data leaves the database at once and for good — the deletion cannot be postponed or undone — a background job removes the files from storage, and the data ages out of backups within 30 days as they are overwritten.
- Social network access tokens are erased immediately when the dealer disconnects the channel in the dashboard, and likewise as soon as Facebook, Instagram or TikTok tells us that access was revoked: the person who connected the page or the Instagram account removed the app in their Facebook or Instagram settings, or the TikTok account was disconnected from the app, deleted or banned. Scheduled posts for such a channel are cancelled.
- OLX access tokens are erased immediately when the dealer disconnects OLX in the dashboard. A partner app cannot revoke access on the OLX side, so the access OLX issued, once nobody uses it, expires by itself within a month at the latest.
- The listing of a deleted vehicle is deleted from OLX — at once if OLX is connected, or as soon as the same account is connected again. The record of such a listing is kept until OLX confirms the deletion or the dealer connects another OLX account.
- Listings and photographs are deleted together with the listing; a background job removes the files from storage.
- Publication history remains while the listing it belongs to exists: without it there is no record of what went where. Only a draft or an archived listing can be deleted, and its publication history goes with it; disconnecting a channel does not touch the history.
- Buyers' callback requests — 12 months; older ones are removed by a background job.
- Technical logs — up to 90 days.
- The support activity log — 12 months; a background job removes older entries.
- Database backups are rotated and are not kept longer than 30 days.
Deleting data with us does not automatically remove a post already published to a social network. It can be removed in the dashboard with "Delete post", or by hand in the network itself. The same goes for OLX: deleting the dealer account entirely does not take its listings off OLX — take the vehicles off sale before the deletion, or remove the listings on OLX.
How we protect data
- Passwords are stored only as a hash — the password cannot be recovered from it.
- Social network and OLX access tokens are encrypted with AES-256-GCM, and the encryption key is stored separately from the database.
- Dealer data is isolated at the database level: row-level security policies prevent one dealer's query from seeing another dealer's rows even if the application code has a bug.
- All traffic to the Platform goes over HTTPS.
- Only the service owner has access to the infrastructure; the application itself uses a database role that cannot bypass the access policies.
Absolute security does not exist. If a breach occurs that puts your rights at risk, we will notify you and, where the law requires it, the competent authority.
Platform support may sign in to a dealer dashboard on behalf of one of its staff members to help or to fix a fault. Such a session lasts no longer than an hour and does not change the staff member's password. Every support sign-in to a dashboard is recorded in the support activity log, and its end is recorded when support leaves the session itself. At a dealer's request, support may also add a staff member to the team, change their role or remove them from the team — together with their account and sessions if they belong to no other dealer; every such action is recorded in the support activity log.
Your rights
In respect of data for which the Platform is the controller, you have the right to:
- know what data we process and receive a copy of it;
- correct inaccurate data or complete incomplete data;
- have data erased once there is no longer a basis for keeping it;
- restrict processing while we consider your objection;
- object to processing that relies on legitimate interest;
- withdraw consent — for example, by disconnecting a social network channel or OLX; withdrawal does not undo processing that already took place;
- receive your data in a machine-readable format in order to move it to another service;
- lodge a complaint about us with the competent data protection authority.
Send your request to dmytro.bondarchuk.wm@gmail.com from the address the account is registered to. We reply within 30 calendar days; if a request is complex, we will tell you the deadline is extended and explain why.
Rights in respect of data for which the dealer is the controller — listing content, the dealer's own contact details — are exercised by that dealer. We will help technically and pass the request on if the dealer does not respond.
How to delete your data
The right to deletion is available to every user of the Platform. Step-by-step instructions, and a status check by confirmation code, are on the "Data deletion" page: maydanchyk.com/data-deletion.
- Disconnect a channel: in the dashboard open Integrations, pick the network and press "Disconnect" — access tokens are erased immediately.
- Through Facebook: Settings → Apps and Websites → find Maydanchyk → "Remove". Facebook notifies us automatically and we erase the stored access tokens for your pages.
- Through Instagram: in the Instagram settings open "Apps and websites", find Maydanchyk and remove it. Instagram notifies us automatically and we erase the stored access tokens for that account.
- Through TikTok: in the TikTok app, remove the access of Maydanchyk in the security settings, among the permissions of apps and services. TikTok notifies us and we erase the stored access tokens for that account.
- Disconnect OLX: in the dashboard open Integrations → OLX and press "Disconnect" — access tokens are erased immediately. Listings already placed stay on OLX afterwards: take the vehicles off sale before disconnecting, or remove the listings on OLX.
- Delete the account entirely: write to dmytro.bondarchuk.wm@gmail.com from the registered address. We will delete the account, the dealer profile, the listings and the photographs within 30 days and send you confirmation. The deletion is final — the data cannot be restored afterwards. It does not take listings off OLX — do that before the request.
Children
The Platform is a business tool and is not intended for anyone under 18. We do not knowingly collect children's data. If you believe an account was created by a child, write to us and we will delete it.
Automated decisions and profiling
We make no decisions about you by solely automated means and build no profiles. The only automated processes are publishing scheduled posts, processing uploaded photographs and keeping OLX listings in sync with the vehicles — they carry out the dealer's instruction and decide nothing about you.
Changes to this policy
We may change this policy: a provider is added, the set of data changes. The current edition is always published at maydanchyk.com/privacy, and the date in the header shows when it was last updated.
We will notify dealers of changes that materially affect them at the account email address at least 14 days before they take effect. Continuing to use the service after that date means the new edition is accepted.