Privacy notice
Effective 5 November 2026. Last updated 5 November 2026.
Who processes the data
The controller is Ilya Fedorov, a natural person, Vysokoškolákov 8215/18, 010 08 Žilina, Slovakia ("we"), who runs the punkto.sk service. You can reach us by e-mail at [email protected]; more on the Operator and contact page.
This notice meets the information duty of Art. 13 of Regulation (EU) 2016/679 (GDPR) and section 19 of the Slovak Personal Data Protection Act 18/2018.
Overview: what, why, legal basis, who receives it, how long
The table lists everything we process when you use Punkto. We collect nothing else.
| Data | Purpose | Legal basis | Recipients | Retention |
|---|---|---|---|---|
| Server logs: IP address, user agent, time, requested address (URL including query, so also the text you typed into a search) and status code | Security, operation and troubleshooting | Legitimate interest, Art. 6(1)(f) GDPR | Cloudflare and Contabo GmbH, server hosting (processors); the server we operate | Up to about 5 weeks (35 days) |
| Location and coordinates: in the request address when you plan a journey, a walking or cycling route, look up departures nearby or find the address of a point | Answering your request | Consent, Art. 6(1)(a) GDPR, given through your browser's location permission; for a point picked by hand on the map, legitimate interest, point (f) | Cloudflare (processor) while it transmits the request; nobody else, except the address lookup and the taxi service you tap (below) | Not stored beyond server logs (up to about 5 weeks) |
| City from the IP address: when the app opens without your location and without a saved city (a first visit), Cloudflare tells us the approximate location of the city from the IP address (rounded to about 1 km), its name and country, and the app opens the map on your city. It is used only to choose the city the app opens on; it is not stored, not even on your device | Opening the app on the city you are in rather than on the default one | Legitimate interest, point (f) | Cloudflare (processor) | Not stored (except in server logs, up to about 5 weeks) |
| Address lookup: coordinates rounded to three decimals (about 100 m) are sent from our server to Photon (Komoot GmbH, Germany), without your IP address | Showing an address instead of coordinates | Consent (device location), point (a); point picked by hand: point (f) | Komoot GmbH | With us only in the cache below; at Komoot per its policy |
| Address cache: coordinates rounded to three decimals (about 100 m), the address label found and the time it was stored; no IP address and nothing about who asked | Faster answers and fewer requests to Photon | Legitimate interest, point (f) | Nobody | At most 30 days |
| Carrier journey search at RegioJet and FlixBus: a station or city identifier for the start and end and the travel date, sent from our server; no coordinates, no IP address of yours and no account | Showing these carriers' connections and prices | Legitimate interest, point (f) | RegioJet, FlixBus (independent controllers) | With us only in server logs; at the carriers per their policies |
| Anonymous visit counters: when the app opens, at your first touch of the screen and when you do a few things (open a stop or a line, look up a route and whether options came back, open one of them, leave a search before its answer, start guidance, set a reminder; for a route also the tab you searched in: the map, Route or Trains), one is added to a daily total together with the landing page without parameters (so without coordinates), the domain of the referring site, the country (Cloudflare works it out from the IP address), the platform (web, installed app, iOS, Android), the language and the city. No IP address, cookie or any identifier is stored. The number of different visitors per day is estimated from a one-way hash of the IP address and user agent with a random salt that changes daily, lives only in the server's memory and is discarded at midnight. If your browser sends Do Not Track or Global Privacy Control, we do not count you. If you answer "Did you find what you were looking for?" under an opened journey, one is added to the total of the tab and the answer (yes or no), and nothing else; you send that answer yourself with your tap | To know how many people use the service and which features are used | Legitimate interest, point (f); the data is aggregated and identifies no one | Nobody | Daily totals with no time limit (they hold no personal data); hashes in memory only, until midnight at most |
| Anonymous server statistics: for every answer of our server one is added to a daily total by the address template (such as /api/journeys/country, without parameters or identifiers), the response time (in bands), a server failure and a coarse kind of client from the user agent (iOS app, Android app, web on a phone or a computer); robots are not counted. When you look up a journey beyond the city, also the name of the town or village nearest to its start and end (chosen by distance, not by address), whether any journey was found, how many days ahead you searched and how (by time or price, arrive by, trains or buses only). The same pair of places from the same person is counted once a day by the same daily hash of the IP address and user agent as the visit counters, which lives only in the server's memory and is discarded at midnight. No IP address, user agent, coordinates, exact time or identifier is kept; a pair of places is shown in our overview only once at least 5 people looked it up. Nothing is read from or stored on your device for this: the server counts its own answers | To learn what people look for and where journeys or data are missing, and where the server is slow or failing | Legitimate interest, point (f); the data are aggregated and identify no one | No one | Daily totals with no time limit (they contain no personal data); hashes in memory only, until midnight at the latest |
| Usage analytics, only with consent: a random device identifier (the pk_vid cookie and browser storage), a random session identifier, IP address, user agent, country, region and city (worked out by Cloudflare from the IP address), time zone, screen size, connection type, the app version (in the iPhone and Android app, its store version), where the visit came from (the referring site's domain, utm tags), the landing page without parameters, and what you did in the app: screens and sections of the app seen and time on them, buttons pressed (their name in the interface, not their text), opening a stop (its name and identifier) or a line or train (its number and name), looking up a route, guidance, a reminder, pressing "Buy" (the seller and the place in the app), loading speed and script errors, repeated quick presses of the same element, how far you scrolled a list, failed requests to our server (the shape of the address without identifiers or parameters, the response code, the time taken), going offline and back, how many options a route search found and how long it took, or that you left before the answer and after how many seconds, opening one of them, your answer to "Did you find what you were looking for?", signing in (the prompt to sign in and its reason, the method chosen, success or the error code, whether the account is new; no e-mail or account identifier) and deleting the account, sharing a link (a route or a place, for a short link also its code), the offer to install the app and your answer to it, which taxi app you pressed, and when you look up a route, whether its start or end is your position and the station identifier where the point has one; with consent to the Trips purpose also the name of the start and the end as the app showed it (a stop, a place, an address or one of your saved places), but not a start or end that is your position. Once a session also the browser's languages, whether notifications are allowed, whether the app is installed, the number of processor cores and memory size, touch screen, dark mode, reduced motion and the number (not the content) of saved places and followed journeys. When you search in the app, also the text you typed (at most 120 characters; if it is an address or a place name, that too), the number of results and the kind and position of the result you picked. No coordinates of your position and no text of other fields | To learn how the app is used, where people drop off, whether they come back, where it is slow or failing and what people look for and do not find, and to improve it accordingly | Consent, point (a); storing the identifier on your device with consent under section 109(8) of Act 452/2021 | Nobody (Contabo and Cloudflare as processors) | Up to 2 years (the IP address and robots' records too); for consent given before 16 October 2026, up to 400 days, with the IP address cut to its network after 90 days and robots' records deleted after 180 days, as the banner then said; everything is deleted at once when you withdraw consent |
| Anonymous error and speed statistics: for a script error its text (without coordinates), file and line; after a page load the load timings (such as the server's response and the first paint), the connection type and the app version. With them the day, the platform and a coarse description of the device from the user agent (such as mobile, iOS, Safari); the user agent itself is not kept. No device or session identifier, IP address or exact time. If your browser sends Global Privacy Control or you objected in your profile, nothing is sent | To see where the app fails or is slow, and to fix it | Legitimate interest, point (f); you can object in your profile (Anonymous statistics) | Nobody (Contabo and Cloudflare as processors) | Up to 2 years |
| Anonymous search statistics: for each search in the app, the day, platform, language, where the search was, the text typed (at most 120 characters; pasted coordinates are cut out), the number of results and the kind and position of the result picked. No device or session identifier, IP address, user agent or exact time. If your browser sends Global Privacy Control or you objected in your profile, nothing is sent | To see what people look for and what the search fails to find or finds wrongly, and to fix it | Legitimate interest, point (f); you can object in your profile (Anonymous statistics) | Nobody (Contabo and Cloudflare as processors) | Records for up to 2 years; after that only daily counts of texts searched at least 5 times that day remain, with no time limit |
| Consent record: each answer to the analytics question (consent, refusal, withdrawal, change) with the time, the version and language of the text, the purposes chosen, the platform and where it was given (banner or profile); with consent also the random device identifier, with a refusal no identifier | To demonstrate what consent you gave and when, and when you withdrew it | Legal obligation, point (c), with Art. 7(1) GDPR (the duty to demonstrate consent) | Nobody (Contabo as processor) | 2 years from the answer; when you withdraw consent we remove the device identifier from it |
| Link to buy a ticket from a seller (ZSSK, RegioJet, Leo Express, FlixBus, České dráhy, Slovak Lines, MÁV, Omio, UNITED BUSES, AUTO-BEY, DOPRAVA+, Zubačka, Bileto, IDS BK, Ubian): when you press "Buy", your browser opens an address on our server that contains the stretch of the journey (names and identifiers of the departure and arrival stations, the coordinates of those stations and the departure time; not for IDS BK and Ubian), the place in the app and the language. The server builds the seller's address from them, for the IDS BK and Ubian apps picks the App Store, Google Play or the seller's website by the user agent, and immediately redirects you. One anonymous counter is written: day, seller, place in the app, language and whether it was a partner link; no IP address, user agent, stations, time or destination address | Taking you to the ticket sale with the search filled in, counting how often a link was used, and, where the seller has a partner programme, letting it pay a commission for a ticket bought | Legitimate interest, point (f) | The ticket seller (independent controller); for an app, Apple or Google (app store); where the seller has a partner programme, also its partner system; see Partner links | The counter holds no personal data: no time limit; the address in server logs at most 35 days; at the seller per its policies |
| Short link when you share a route or a point on the map (punkto.sk/r/… for a route, punkto.sk/p/… for a point): when you share a route or a point, the app sends our server the address the link stands for — for a route the coordinates and names of the start and the destination (the start may be your location), any stops, the time, the way of travel and the option chosen; for a point its coordinates and name. The server stores a short code with it (derived from the address), when it was made, how many times it was shared, when it was last opened and how many times, and, when it is made, a coarse description of the device (type, operating system and browser from the user agent) and the country and city (worked out by Cloudflare from the IP address). Every time a link of ours is opened (a short link, a stop's or a poster's QR code, a link to a place, a stop or a line) we record the time to the minute, whether a person opened it or an app drawing its preview in a chat (and which one), the same coarse description of the device, the country and city, the browser's first language, the domain of the referring page, and how far the person who opened it got in the app that day (for example, searched for a route) — by an anonymous daily fingerprint that lives only in the server's memory. If your browser sends Do Not Track or Global Privacy Control, we record only the time and the link. No IP address, user agent, device identifier or account; we do not know who made or opened the link | Keeping a shared link short and opening the same route or point for whoever receives it, and seeing how shared links and QR codes are used | Legitimate interest, point (f); you make the link yourself by tapping Share | Nobody; the link is seen by whoever you send it to | While the link is being opened; deleted 180 days after it was made or last opened; a record of an opening after 180 days |
| Delay alerts in the app (iPhone, Android): when you turn on the bell on a departure and allow notifications, the app sends our server the device's notification token (Apple Push Notification on iPhone, Google's Firebase Cloud Messaging on Android), the stop, the line, the direction, the departure time and the alert's wording in your language. Once a minute the server checks whether the trip is late or cancelled and, if so, sends you a notification through Apple or Google. No IP address, location or account | Telling you that the bus you are waiting for is late or will not run | Consent, point (a): by turning on the bell and allowing notifications; withdraw it in iOS notification settings | Apple (delivering the notification) | Until the trip has left, plus a few minutes, then the record and its token are deleted; about 4 hours at most |
| Following a train journey in the app (iPhone, Android) ("Follow this journey"): when you follow a journey and allow notifications, the app sends our server the device's notification token (Apple Push Notification on iPhone, Google's Firebase Cloud Messaging on Android) and the journey: for each part the line or train, the departure and arrival stations, the departure and arrival times, the time to change and what the journey already showed (a cancellation or a closure); also the journey's title (its start and destination as the app shows them, so possibly an address you picked) and the notification texts in your language. A journey can be followed if it starts within 2 days. Once a minute the server checks the journey's trains against ZSSK's announcements and their live delays and sends you a notification through Apple or Google when a train will not run, a closure applies, a delay costs you a change or the first train is late. It also keeps which notifications have been sent. No IP address, coordinates or account | Telling you that a train on your journey will not run or is late, or that you will miss a change | Consent, point (a): by following the journey and allowing notifications; withdraw it by unfollowing the journey or in iOS notification settings | Apple (delivering the notification) | Until about 3 hours after the last train's scheduled arrival, then the record and its token are deleted; at once if you unfollow the journey |
| Taxi: when you tap Bolt or Uber in the Taxi tab, a link opens that hands that service the pickup and drop-off coordinates (the pickup may be your current position) and, where the places have names, their names. For Uber this is m.uber.com or the Uber app; for Bolt the Bolt app and, if it does not open, Bolt's app download link (bolt.onelink.me) without the trip. The HOPIN button, and the Zoberma button where a ride cannot be ordered in the app itself, only open their app, their page in the App Store or Google Play, or their website, with nothing about the trip. Nothing is sent before you tap, and the link does not pass through our server | Ordering a taxi with the trip filled in | Legitimate interest, point (f); you start the transfer yourself by tapping the button | Uber, Bolt (independent controllers); HOPIN and Zoberma receive nothing about the trip; for an app store, Apple or Google | Not stored by us; at the service per its policy |
| Ordering a Zoberma taxi in the app itself (signed-in accounts only): for the Zoberma button we ask Zoberma for the price and how soon a car is there by sending it the pickup and the destination (coordinates and name) and the length of the drive, with nothing about you. When you order the ride, we also send it the phone number and name you entered for the driver, and a pseudonymous identifier derived from your account, from which Zoberma cannot tell your account. We store the order: these data, the state of the ride, Zoberma's identifiers of the order and the ride, the price, your rating of the driver and, if you allowed notifications, the device's notification token and the notification texts in your language. During the ride we show you the driver's first name and initial, rating, car, plate and position. You pay the driver directly; we receive no payment details. We keep the phone number and name for the driver with your account so that the next order does not ask again; if you sign in with a phone number, that one is used | Ordering and following the taxi ride you asked for; settling the commission with Zoberma for rides ordered through Punkto | Performance of a contract, point (b): you send the order yourself; settling with the partner: legitimate interest, point (f) | Zoberma s. r. o. and the driver (independent controllers; the driver receives the pickup, destination, phone and name); for a notification, Apple or Google | Places, phone, name and the notification token in the order are deleted a day after the ride ends; the record of the order without them (state, price, time, Zoberma's identifiers) and the phone and name for the driver with the account until the account is deleted |
| Data on your device (localStorage and service-worker cache): language, appearance, saved places, kept trips, the list of followed journeys, ticket and map settings, install-prompt state, city timetables downloaded for offline use, feedback waiting to be sent while offline and the e-mail address you last entered in it | Functions you asked for, including offline mode | Strictly necessary for the requested service (section 109 of the Slovak Electronic Communications Act 452/2021); it does not reach us | Nobody, the data never leaves your device | Until you delete it (browser settings) |
| Map: your browser itself fetches tiles from OpenFreeMap. Satellite imagery and the rain radar come through our server, so their providers do not see your IP address. They see your IP address, user agent and the map area you view | Displaying the map you opened | Legitimate interest, point (f): the map cannot be shown without these requests | OpenFreeMap (independent controller) | Per their policies, see below |
| Correspondence: your e-mail address and the content of a message you send us | Handling your message | Legitimate interest, point (f), or fulfilling your rights request, point (c) | E-mail provider (Google) | While handling it, then at most 12 months |
| Feedback from the app (Write to us, Report an error): the kind of message, the reason, the text you write and, if you enter it, an e-mail address for the reply. If you opened the form from a journey, line or stop card or from search, its name and address in the app are attached (for example the stretch and time of the journey or the search text); you can remove the attachment before sending. Also the language, platform and app version. We store no IP address, device identifier or analytics data with the message | Fixing errors in the data and in the app, improving the service and replying to you | Legitimate interest, point (f); you send the message yourself | Resend, Inc. (processor, delivers the notification to us by e-mail), e-mail provider (Google); the server we run | The message at most 2 years. The e-mail address is deleted once the message is handled (after our reply), at the latest 30 days after it is closed; it stays in the server's encrypted backups for at most 14 more days |
| Account (only if you create one): the e-mail address and whether it is verified, your name if Apple or Google hands it over, the ways you sign in (Apple, Google, e-mail) with the identifier Apple or Google gave you, the language, when it was created and last used, kept trips and saved places (their names, stops, times and coordinates as the app shows them) and, for Apple, an encrypted token with which we revoke Punkto's access to your Apple ID when the account is deleted | Running your account, signing you in and having your kept trips and saved places on all your devices | Performance of a contract, Art. 6(1)(b) GDPR (the account and its functions) | Apple, Google (sign-in, independent controllers); Resend, Inc. (processor, delivers the e-mail with the code); Contabo and Cloudflare (processors) | As long as you have the account; deleted at once when you delete it, and from the server's encrypted backups within at most 14 more days |
| Sign-in and abuse protection: for e-mail sign-in the address, a hash of the code and the link, the number of attempts and the network of the IP address (IPv4 /24, IPv6 /64); signed-in devices (sessions): platform, a short description of the device from the user agent, the network of the IP address, when you signed in and last used it; when you ask for a code, a Cloudflare Turnstile check (no pictures to click) that assesses browser signals and the IP address | Protecting accounts and the service from abuse (mass code requests, bots, account takeover) and showing you your signed-in devices | Legitimate interest, point (f) | Cloudflare (Turnstile, under the Turnstile Privacy Addendum); Contabo (processor) | Codes and attempts 2 days; a session until you sign out, at most 180 days after it was last used, or until the account is deleted |
| Account deletion record: a one-way hash of the account identifier, the date of deletion and the ways of signing in it had; the Apple token only until access is revoked at Apple | Showing that and when we deleted the account, and completing the revocation at Apple | Legal obligation, point (c), with Art. 5(2) and Art. 17 GDPR | Apple (revocation); Contabo (processor) | At most 2 years; it holds no e-mail address or name |
Legitimate interests: keeping the service secure and working (logs help detect abuse and faults), answering quickly (the cache) and showing the map you opened. These interests are narrow, the data is used only for the stated purpose and the impact on you is low because we build no profiles. If you have a reason why this does not hold in your case, you can object (see Your rights).
Location in more detail
Your browser asks you whether it may share your position. Without your permission we do not get it, and the app keeps working, only without nearby stops. You can withdraw the permission at any time in the browser settings.
Providing data is neither a statutory nor a contractual requirement, and you need none of it to use the service. If you do not share your position, nearby stops are not shown and planning from your position, routes from it and nearby departures will not work. You can still search for a journey, route or departures by entering a place by hand.
The position is used in the browser to show nearby stops. When you plan a journey or a route or look up nearby departures, the coordinates are sent to our server in the request address so that it can answer. We do not store the coordinates of these requests with a name or an account; the account holds only the trips and places you save yourself (see Account).
The request address, including coordinates, is written to the server log and deleted after about 5 weeks at the latest (35 days). The address cache keeps only rounded coordinates and the address label, for at most 30 days.
Usage analytics with consent
When you first open it, the app asks whether you allow us to record how you use it. You can allow everything, decline, or choose the purposes one by one in the settings: usage statistics, search text and trips (the latter two only together with the statistics). No purpose is chosen in advance. Until you answer, and if you decline, none of this is recorded and we only count the anonymous totals and the anonymous search statistics in the table above. If you decline on the banner, we ask again at the earliest in 30 days; if you decline in your profile, we do not ask again. If your browser sends Global Privacy Control, we take it as a refusal and do not ask. We record each answer so that we can demonstrate what consent you gave (see Consent record in the table).
With consent, your device gets a random identifier. We keep it in browser storage and in the pk_vid cookie (valid for 2 years, punkto.sk only) so that we recognise a returning visit, and record the data in the table above with each visit. The identifier is not linked to your name or to an account; we do not sell the data, use it for advertising or give it to anyone.
That data includes the text you type into the app's search (a stop, an address, a place, a line), at most 120 characters, together with how many results were found and which one you picked. We keep it with the visit to see what people look for and what the search fails to find or finds wrongly, and to fix it. We keep it only if you also consented to the Search text purpose. It is kept like the rest of the analytics: for up to 2 years, and it is deleted at once when you withdraw consent. We do not attach the coordinates of your position to it. If you consented before 15 October 2026, when the banner said that search text is not recorded, we do not keep the text of your searches. If you consented before 16 October 2026, when the banner said up to 400 days, we keep the data of that consent for up to 400 days and the app asks you again; if you decline, that withdraws your consent to analytics.
With the Trips purpose we also keep, with the visit, where you looked up a route from and to: the name of the start and the end as the app showed it — a stop, a place, an address or the name of one of your saved places, at most 120 characters, without coordinates. If the start or the end is your position, we keep only that it was your position, not where you were. It helps us see between which places people travel and where the planner fails to offer a good connection. An address may reveal where you live or work, so we keep it only with your consent to this purpose (added on 17 October 2026; consent given before does not cover it and the app asks you again). It is kept for up to 2 years; if you switch the Trips purpose off in your profile, we delete the names of the routes already kept, and if you withdraw consent, everything is deleted at once.
You can withdraw consent at any time in your profile (Usage analytics). We then delete every record with your device's identifier on the server, and the cookie, and record nothing further; the consent record keeps only that and when you gave and withdrew consent, without the identifier. Withdrawal does not affect the lawfulness of processing before it.
Anonymous search, error and speed statistics
To see what people look for in the app and what the search fails to find, after each search the app sends our server a summary of it: the text typed (at most 120 characters, without pasted coordinates), the number of results, the kind and position of the result picked, where the search was, the language and the platform. The server adds only the day. No device or session identifier, IP address, user agent or exact time is sent or stored, so we cannot link the record to you or to your other searches.
The text of a search may still contain an address, so we treat it as personal data. We process it on the basis of legitimate interest (Art. 6(1)(f) GDPR): improving the search you use. We keep the records for up to 2 years; after that only daily counts of texts searched at least 5 times that day remain, and those we keep with no time limit. If you rejected analytics or switched off search texts, we do not keep the text of your searches — only that a search happened and how much it found.
In the same way, without any identifier, the app sends script errors and page-load timings, so that we see where it fails or is slow for people who did not allow analytics too. We strip coordinates from an error's text; of the user agent we keep only a coarse description of the device (such as mobile, iOS, Safari), not the user agent itself. We keep this for up to 2 years.
You can object to this processing: switch off Anonymous statistics in your profile and the app stops sending your searches, errors and load timings. If your browser sends Global Privacy Control, we take it as an objection. If you rejected analytics or consented without the Search text purpose, these statistics get only that a search happened and how much it found, without its text.
Data stored on your device
Without your consent Punkto sets no cookies; with consent to analytics it sets one, pk_vid (see Usage analytics with consent). Otherwise it stores on your device only what the functions you asked for need: your chosen language and appearance, saved places (such as home), kept trips, ticket and map settings, whether we have offered you installation, downloaded city timetables for offline mode and feedback waiting for a signal. If Cloudflare were to set a technical cookie to protect against abuse, it is a strictly necessary security cookie with no tracking.
This data is not sent anywhere, except kept trips and saved places while you are signed in (see Account). You delete it in your browser settings (site data) or by uninstalling the app. Because the storage is strictly necessary, we do not ask for consent (section 109 of Act 452/2021); for the analytics identifier we do.
Account
An account is optional and you can use Punkto without one. You sign in with Apple, Google or by e-mail (we send you a link and a code). The account lets you have your kept trips and saved places on all your devices: while you are signed in, the app keeps them with the account on our server. We do not collect phone numbers at present.
What we keep: the e-mail address (with Apple it may be a relay address if you chose to hide your e-mail), your name if Apple or Google hands it to us, the ways you sign in with the identifier from Apple or Google, the language, kept trips and saved places, and signed-in devices (platform, a short description of the device, the network of the IP address cut to /24, or /64 for IPv6, and times). The legal basis for the account is performance of a contract (Art. 6(1)(b) GDPR); we keep it as long as you have it.
To protect against abuse (legitimate interest, Art. 6(1)(f) GDPR) we keep records of requests for a sign-in code: the address, a hash of the code, the number of attempts and the network of the IP address; they are deleted after 2 days. A code request is checked by Cloudflare Turnstile without pictures to click: it assesses browser signals and the IP address and tells us only whether it is a person. Cloudflare processes that data under the Turnstile Privacy Addendum.
Recipients: Apple and Google when you sign in with them (as independent controllers under their own notices; from them we receive an identifier, the e-mail address and possibly your name), Resend, Inc. (our processor, delivers the e-mail with the link and code), Cloudflare (Turnstile and delivery) and Contabo (the server).
Deletion: in the app or on punkto.sk under Profile → Delete account. The account is deleted at once and for good, together with kept trips, saved places and signed-in devices; if you signed in with Apple, we also revoke Punkto's access to your Apple ID. It stays in the server's encrypted backups for at most 14 more days and then disappears. We keep only a deletion record: a one-way hash of the identifier, the date and the ways of signing in, without the e-mail address or name. The full procedure, also without the app, is on the Delete your account page. You can also remove single kept trips and saved places without deleting the account.
Services your browser contacts
When a map is shown, your browser connects directly to the services below. We are not their processor and cannot see what they record. See their notices for details. Cloudflare may instruct your browser to send a network-error report to a.nel.cloudflare.com after a failed connection; this happens only on an error.
- OpenFreeMap (base map): openfreemap.org/privacy
- Komoot GmbH (Photon, address lookup; it receives coordinates rounded to about 100 m from our server, not your IP address): komoot.com/privacy
Fonts are served from punkto.sk itself, so we do not load them from third parties. Weather is fetched by our server from MET Norway (the Norwegian Meteorological Institute): it sends the coordinates of the centre of the city shown on screen, rounded to about 1 km (not your position or IP address), so the most the request reveals is which city you are looking at. Air quality and the rain radar are downloaded by our server from the EEA and EUMETNET for the whole of Slovakia, Czechia, Austria and Poland at once, with no coordinates at all. When you search for connections, our server sends RegioJet and FlixBus a station or city identifier for the start and end and the travel date (not coordinates, your IP address or an account). The text you type into a place search is handled by our own server and stays in its logs and, if you consented to analytics, in its records (see Usage analytics with consent).
Partner links to buy tickets
We do not sell tickets or take payments: you buy them from the seller (a carrier or a transport authority) on its site or in its app, under your own account. The "Buy" links pass through our server. The sellers are: ZSSK, RegioJet, Leo Express, FlixBus, České dráhy, Slovak Lines, MÁV, Omio, IDS BK and Ubian, and the Czech carriers whose e-shop runs on the Bileto system: UNITED BUSES, AUTO-BEY, DOPRAVA+ (POASS Technologies), Zubačka and Bileto's shared e-shop (BRISEN TRANSPORT, HEXIBUS, MP Bus, RETROBUS Line). Omio is an intermediary that sells many carriers' tickets with its own service fee. Beside the button of České dráhy long-distance trains we show a link to it, and only while we have a partner programme with it. For ÖBB, WESTbahn, PKP Intercity and Deutsche Bahn trains outside Slovakia, for which we have no other seller, Omio is the seller on the "Buy" button itself.
As of the effective date of this notice we have no partner programme with any of them: the links go straight to the seller and nobody pays us for them. If a seller joins a partner programme, its links become partner links: if you buy a ticket, the seller may pay us a commission. The price for you is the same.
The address your browser opens on our server when you click contains the stretch you are looking for a ticket for: the names and identifiers of the departure and arrival stations, the coordinates of those stations (not of your position) and the departure time, plus the place in the app and the language. For IDS BK and Ubian it contains only the place in the app and the language. This address is written to the server log like any other request (up to about 5 weeks). Beyond that we keep only a counter: how many times a link to a given seller was opened on a day, from which place in the app, in which language and whether it was a partner link. It holds no IP address, user agent, station, travel time or anything else that could be tied to you.
The address we redirect you to gives the seller what it needs to fill in its search: ZSSK the station names, the date and the departure time; Slovak Lines its own stop or town identifiers and the travel date; RegioJet, Leo Express and FlixBus their own station or city identifiers and the travel date (Leo Express also the station names); Omio its own identifiers of the start and end places and the travel date, without the time; MÁV its own codes of the start and end stations and the departure time; the Bileto e-shops their own identifiers of the stops or towns and the departure date and time. For České dráhy their sales page opens without journey details; for IDS BK and Ubian the app's page in the App Store or Google Play, or else the seller's website. As the referring page the seller learns only our service's domain, not the page you were on. To fill in the FlixBus search, our server may ask FlixBus for the city by the station's name, without your IP address or any data about you. For Omio our server first records the click with the Impact partner network (impact.com) and receives its identifier, also without your IP address, user agent or cookies; we then show you a short page that submits Omio's search from your browser (the places, the date, a random search identifier and the click identifier) so that the results open straight away. From then on the seller, Apple or Google process your visit as independent controllers under their own notices.
Where a seller has a partner programme, the redirect will pass through its partner system's tracking link, or a partner parameter will be added to the seller's address. The seller or the partner system then receives our partner identifier and a non-personal tag (the place in the app and the language, for example "bill-sk"), and the partner system also receives the seller's destination address with the journey details described above. After the redirect the partner system may set its own cookie and record that you bought a ticket; it does so as an independent controller under its own notice, and we do not see that data, only totals of what we are paid. Such cookies are set only after you click the link.
Processors and transfers outside the EU
Cloudflare, Inc. delivers punkto.sk as our processor: traffic passes through its network, so it sees visitors' IP addresses. A data processing agreement applies and, for transfers to the USA, the safeguards of Art. 46 GDPR: Cloudflare is certified under the EU-U.S. Data Privacy Framework and uses standard contractual clauses as a fallback (we will provide a copy of the safeguards on request). Cloudflare keeps its own logs under its own policy, whose periods we do not control. We run the server with the hosting provider Contabo GmbH (Munich, Germany) in its data centre in Nuremberg, that is inside the EEA; Contabo, as a processor, supplies only the infrastructure. Details: cloudflare.com/privacypolicy.
Some services from the previous section may also process data outside the EEA, in particular in the USA. Data reaches them when your browser requests the relevant map tile, and their operator sets the transfer terms. The same applies to the mailbox (Google LLC), which may process messages in the USA; Google is certified under the EU-U.S. Data Privacy Framework. The notification of feedback from the app and the e-mails with a sign-in code are sent by Resend, Inc. (USA) as our processor, from a data centre in Ireland; a data processing agreement applies and, for any access from the USA, standard contractual clauses (Art. 46 GDPR).
What we do not do
- We use no advertising. We set a cookie and record usage analytics only with your consent; without it we only keep anonymous daily visit totals (see the table above). After you click a "Buy" link, the ticket seller or its partner system may set its own cookie (see Partner links).
- We do not profile you or take automated decisions with legal effects on you.
- We do not sell your data or share it for advertising.
The project is commercial and is meant to be funded by partner links to buy tickets (see above). We use no ads yet; if we introduce them, we will first update this notice and announce it on this page, and ask for your consent where the law requires it.
Your rights
You have the right of access to your personal data, to rectification, erasure, restriction of processing and data portability. You can withdraw your location consent at any time in the browser settings without affecting earlier processing.
Right to object: you can object at any time, on grounds relating to your situation, to processing based on legitimate interest, by e-mail to the address below. We will then stop, unless we show compelling legitimate grounds that override your interests.
To exercise your rights, write to [email protected]. If you have an account, you see and delete kept trips and saved places right in the app and delete the account in your profile; if you write to us about the account, write from its e-mail address. Other records are not tied to an account, so for them we can identify you only from what you send us, such as an IP address and a time range. Without them we may not be able to find a record. We answer within one month.
Complaint to the supervisory authority
If you think we process data unlawfully, you can lodge a complaint with the Office for Personal Data Protection of the Slovak Republic (Úrad na ochranu osobných údajov Slovenskej republiky), Galvaniho 7/B, 821 04 Bratislava, dataprotection.gov.sk. You can also contact the supervisory authority of the EU state where you live or work.
Children
Punkto is not directed at children under 16 and we do not knowingly collect their data. You share your position only when you allow it in the browser.
Changes to this notice
We may change this notice, for example when a new feature is added. The current version is always on this page with its effective date. We will announce material changes on this page at least 30 days in advance, and they will not apply retroactively.