Check the spelling or try a shorter, more general word.
Try one of these
Search is unavailable right now. Please try again.
Search is not available for this device.
This happens after inappropriate or unsafe queries.
Search settings
When a query is in another language, the results come in that language. You can switch back in one click, and this setting remembers what you choose.
Your searches are linked to this device only. When the period ends, or if you delete them, the link to you is removed and only anonymous statistics remain.
Also deletes your AI assistant data — search and the assistant share one identity.
Enter — open · Esc — closeSpace or → completesnakordoni.eu
Privacy Policy
Last updated: 2026-09-12
Introduction
This website (“we”, “us”, “our”) respects your privacy and is committed to protecting it.
This Policy explains what information we may collect when you visit our site, how we use cookies and similar technologies,
and how you can control them. It also outlines your privacy rights and how to contact us.
Who is responsible (Data Controller)
The controller of your personal data is Andrii Kurhanskyi, operating Nakordoni.
For any privacy question or to exercise your rights, contact us at
privacy@nakordoni.eu or via the contact form.
A postal address is available on request.
What data we collect
When you simply browse the public website, we do not intentionally collect information that identifies you personally.
If you create a developer (API) account or contact us, we process the personal data described in those sections below.
When browsing, we may process technical and usage data generated by your device and browser, such as:
IP address (which may be truncated or anonymized where supported), user-agent, device and browser type/version;
pages visited, referring URLs, time on page, interactions with features (e.g., search);
basic error and performance metrics needed to keep the service reliable and secure.
If you voluntarily contact us (e.g., via the contact form), we will process the data you provide (such as your email)
solely to respond to your request.
Developer (API) accounts
If you register for an API key in our developer portal, we process the account information you provide together with limited technical data:
Data we process: your name and surname, company name, email address, website and usage-page URLs, the IP address used at sign-up, your hashed password, your API keys and API usage statistics, and any support tickets you send us.
API call records: for every call made with your keys we record the time, the key and account, the product and parameters requested, the calling IP address, the HTTP response code and the size and duration of the answer. We use these to meter your plan, bill paid plans, investigate faults and abuse, and check compliance with the Developer API Terms — including, where an integration is public, retrieving the page you declared in order to verify the attribution link. Legal basis: performance of our agreement with you, and our legitimate interest in protecting the service and our licensed data. Section 10 of the Developer API Terms describes the same processing from the contractual side.
Accounts closed for abuse: if we terminate a developer account for a serious or repeated breach, we keep a one-way hash of its email address, and the date and reason, so the same address cannot simply register again. We keep no other content of the closed account for that purpose. Legal basis: our legitimate interest in preventing repeat abuse of a free service.
Purpose: to create and secure your account, verify your email, issue API keys, enforce usage quotas, send essential service notices, and answer your support requests. We never sell or share this data.
Product news: if your account is active, we may also send you occasional email about our own developer services that are similar to those you already use — new API endpoints, feature changes and comparable offers. This is separate from the essential service notices above, is never sent on behalf of a third party, and your address is never shared. Legal basis: our legitimate interest in informing existing customers about closely related services of our own. How to stop: untick “Email preferences” in your developer dashboard, or use the unsubscribe link in any such message — it takes effect immediately, is permanent, and never affects your account or API access. We do not send these to accounts that are not active.
Legal basis: performance of our agreement with you (provision of the API service) and our legitimate interest in keeping the service secure and preventing abuse.
Retention: account data is kept while your account is active and for up to 24 months after it becomes inactive (your last login); the sign-up IP address for up to 12 months; aggregated usage statistics for up to 24 months; support tickets for up to 24 months.
You can access, export, or delete your developer-account data yourself at any time from the "Account and data" tab in your developer dashboard, or by emailing
privacy@nakordoni.eu.
Media Generator (images for publishers)
Our Media Generator page lets anyone create images of current border-queue data for use in articles and posts. When you use it:
What we record: for every image request we log the image settings (card type, crossing or corridor, language, size, theme), the time, the address of the page that requested the image, your browser's user-agent string, and an identifier computed from your IP address with a one-way hash. We do not store the IP address itself, but whoever knows an address can recompute its identifier, so we treat it as personal (pseudonymised) data.
Licence acceptance: when you download an image or copy its link, we record that you ticked the box accepting the licence terms, as evidence that those terms applied to that image.
Hourly free quota: to keep the free service available, visitors can download or copy links to a limited number of images per hour. The counter is stored under the same hashed identifier and deletes itself after one hour.
Invisible image identifier: each newly generated image carries an invisible identifier in its pixels. We record which identifier belongs to which image request (settings, time, hashed identifier), so that an image found in a publication can be traced to our generator and the terms it was issued under. The identifier contains no personal data by itself and may not survive cropping or heavy editing.
Purpose: running and protecting a free service, preventing automated bulk use, enforcing the image licence terms, and understanding which publications use our images.
Legal basis: our legitimate interest in providing and protecting the service and our licensed data.
Retention: the image request log is deleted after 90 days, image-identifier records after 12 months, and the quota counter after one hour.
Cookies and similar technologies
Cookies are small text files stored on your device by your browser. We use cookies and similar technologies to operate the site,
remember preferences, analyze traffic, and (where applicable) show ads.
Cookie lifetimes vary by category and provider (from the end of the session to several months).
Analytics data may be retained for up to 26 months unless configured otherwise.
Legal bases
Depending on your region, we may rely on legitimate interest (e.g., security, basic analytics) and/or consent (e.g., advertising cookies).
Your rights
Subject to applicable law, you may have the right to access, correct, delete, export (data portability), or restrict the processing of your personal data, and to object to or withdraw consent for certain processing. To exercise any of these, email privacy@nakordoni.eu or use the contact form.
If you are in the EU/EEA, you also have the right to lodge a complaint with a data protection supervisory authority. In Poland this is the President of the Personal Data Protection Office (Prezes Urzędu Ochrony Danych Osobowych, UODO), ul. Stawki 2, 00-193 Warszawa.
AI Assistant
Our website and our mobile apps include an optional AI Assistant that answers questions about
border crossings, queues and truck driving bans. The assistant runs on our own servers: they retrieve
the relevant facts from our own database and then call a third-party large language model (LLM) API to
phrase the answer in your language. Answers are labelled as AI-generated and may contain mistakes.
What is sent to the LLM provider: the text of your question, the checkpoint or country already
mentioned in the conversation, your interface language, and factual context taken from our own database
(queue counts, wait times, ban calendars, our published page text).
Location: only if your question is explicitly about the "nearest" place (nearest checkpoint,
parking, shower) and you grant the browser or app location permission at that moment are your
approximate coordinates included, so that the assistant can pick the closest one. If you decline, the
assistant simply asks you to name the place instead.
What is never sent to the LLM provider: your name, e-mail, account credentials, phone number,
device or advertising identifiers, your IP address (the request is made by our server, not by your
device), push tokens, contacts, photos or payment data.
LLM providers we use: Groq, Inc. (api.groq.com — llama-3.1-8b-instant, openai/gpt-oss-120b), and, as fallbacks, Mistral AI SAS
(api.mistral.ai — mistral-large-latest) and Google (Gemini API — gemini-2.5-flash); as a last resort a model hosted on our own servers. They
process the prompt only in order to return the answer, under their API terms, and we have not enabled
any option that would let them use it for model training.
What we store: on our own servers we keep the question, the answer, a random per-install
identifier and a timestamp, in order to monitor answer quality and prevent abuse. This is not linked to
a real-world identity, is never sold, and is not used for advertising or profiling. To have your
assistant history deleted, write to privacy@nakordoni.eu.
Your consent in the mobile apps: in our mobile apps the assistant sends nothing at all until you have read this notice inside the app and tapped “Agree and continue”. You can withdraw that consent at any time from the app menu (“Withdraw AI assistant consent”); the next question then asks you again.
Equivalent protection: we use these providers under API terms that require them to protect the data they receive to a standard equivalent to this Policy, to process it solely in order to return the answer, and not to use it for training.
Contact
If you have questions about this Policy or wish to exercise your rights, please use the form:
/en/contactus.
