Privacy

Data, purposes and legal bases for processing

When you connect to the service, the infrastructure processes your IP address and technical request data. These are used to deliver the page, limit abuse and diagnose errors. The basis is the controller's legitimate interest in maintaining a secure service (Article 6(1)(f) GDPR). We do not provide user accounts or a payment form.

If you write to us, we process your email address, any name you voluntarily provide and the correspondence to reply and handle your enquiry. The basis is a legitimate interest in handling enquiries and defending claims (Article 6(1)(f) GDPR), and, when fulfilling obligations concerning individuals' rights, a legal obligation (Article 6(1)(c) GDPR). Providing data in a message is voluntary; without a reply address, we cannot respond.

Optional analytics and the Travelpayouts Drive marketing script operate on separate consents (Article 6(1)(a) GDPR). Refusal does not restrict access to offers. We do not make decisions about you that produce legal effects solely through automated processing. Offer scoring concerns prices and routes, not your personal circumstances.

Browser storage and withdrawing consent

If email signup is available, we store your address, flight preferences, consent version, signup, confirmation and deactivation dates, and the history of offer delivery attempts. The subscription is not active until the address is confirmed. The email link lets you change settings and unsubscribe; do not share it, as it gives access to the subscription. We do not share your address with offer partners. Summaries depend on enabled delivery and new matches; the form shows the current service status.

If personal Telegram alerts are available, after your commands in a private chat we store chat and user identifiers, language, flight preferences, consent version and time, and command and delivery records. /start alone does not enable offers: a separate /confirm is required after saving preferences. Use /settings and /set to manage them, and /stop to disable the alert. We do not request your phone number or contact list.

Saved trips are stored in this browser (up to 20 plans). A sharing link contains the route, dates, number of people, saved prices and budget. Anyone with the link can read the plan. When the link is opened, the data reaches the HopTrip server as part of the address and may appear in browser history and access logs. The link is an independent copy; removing a plan from the list does not invalidate shared links. We do not include contacts or private notes in them.

When you change the budget calculator, we save its draft in this browser's storage: amounts, number of people, dates and length of stay, separately for each offer. We do not send the draft to the HopTrip server. The ‘Clear calculator’ button replaces the entered data with an empty plan; clearing site data in your browser removes all drafts. Drafts are not synchronised between devices.

With analytics consent, we also measure clicks on museum and attraction cards: city, venue identifier, guide or offer page, and link type (affiliate or official). We do not record page URL parameters in this event. A click does not mean a ticket purchase.

After a flight search or airport confirmation in the short trips section, we remember the selected airport code in the hoptrip.origin.v1 cookie for 180 days. It sets the search and homepage suggestions on this device. We do not determine your location. Choosing ‘Any airport’, searching with an empty ‘From’ field or removing the airport filter deletes this setting.

We store the necessary privacy choice hoptrip.consent.v1 in localStorage for 180 days. Privacy settings in the footer let you refuse, select purposes or withdraw consent. After that period, we ask for your choice again. Withdrawal does not affect the lawfulness of earlier processing.

After analytics consent, we store hoptrip.session.v2: a random session identifier, activity time and any source and campaign labels. After 30 minutes of inactivity, a new identifier is created on the next use; the entry does not disappear automatically after 30 minutes. Events include page views, offers, searches, filters and partner visits. These data are pseudonymous, not guaranteed to be anonymous. Withdrawing consent removes the identifier from the browser and stops new events.

After separate marketing consent, we load Drive from emrld.ltd. The script can read the page, change links and send technical data, including IP, to the provider; it may use its own cookies and identifiers. Withdrawing consent reloads the page and prevents the script from loading again. Data previously stored by third parties can be removed in browser settings. Drive is not loaded on contact, privacy or terms of use pages.

Recipients and external services

HopTrip hosting and the database run in Oracle Cloud in the Frankfurt region (Germany). Email is handled by OVHcloud Zimbra; according to the provider, this service's mailboxes are hosted in France. Infrastructure providers may process data as necessary to provide their services.

Operational Telegram notifications to the operator report the number of new messages. This notification does not include message content, subjects or sender addresses. HopTrip checking the mailbox does not mark messages as read.

When you use personal Telegram alerts, your commands and the preferences in them, as well as replies and matching flights, are also processed by Telegram. The Telegram privacy policy also applies to this channel. Disabling the alert does not automatically delete chat history in the Telegram app.

After consent to Drive, Travelpayouts provides the tool. After clicking an affiliate link, your browser may pass through tp.media to Aviasales or a seller. These entities process data under their own policies, including for commission attribution. HopTrip does not add your email or passenger data to these links.

Not all providers operate exclusively in the EEA. Providers' policies and terms describe processing locations and transfer mechanisms, including standard contractual clauses or other appropriate safeguards. You can obtain information about safeguards for services used by HopTrip by contacting the controller. Marketing consent does not replace required transfer safeguards.

How long we keep data

We retain active subscription data and delivery attempt history to operate the subscription and prevent repeated messages. When cleanup runs, it removes unconfirmed requests older than 7 days from the last request and disabled subscriptions older than 30 days from unsubscribing. Telegram command and reply records older than 7 days are removed; reply text is cleared after an attempt reaches a final outcome. Match history for active subscriptions remains to prevent repeated offers. Unsubscribing does not mean immediate deletion of every record.

We delete analytics events older than 90 days in a maintenance task. We remove links to sessions, sources and campaigns from older records of affiliate visits. Without analytics consent, a redirect stores only a technical record without the browser session identifier.

We keep technical records of visits and settlements as needed to reconcile commissions, detect abuse and establish or defend claims — until settlement is complete and the applicable limitation period expires. The basis is Article 6(1)(f) GDPR; documents subject to a statutory obligation are kept for the legally required period under Article 6(1)(c) GDPR.

We keep correspondence while handling the matter, and afterwards only as necessary to demonstrate its course, fulfil legal obligations or defend claims, until the applicable deadlines expire. Technical data are processed for as long as necessary to handle the connection and security; error logs may be kept until diagnostics are complete. We review the need for further retention when closing enquiries.

Deleted data may remain in access-restricted backups until the backup is replaced or removed in the retention cycle. We do not use these backups for ongoing analytics; after a restore, we reapply data deletion rules.

Your rights

You may request access, rectification, erasure or restriction of processing of your data. In the cases provided for by the GDPR, you have rights to data portability, to object to processing based on legitimate interest, and to withdraw consent. The scope of these rights depends on the basis and circumstances of processing.

Send your request to the email address below. As a rule, we reply within one month; where the law allows an extension, we inform you and explain the reason. You may lodge a complaint with the President of the Polish Personal Data Protection Office (uodo.gov.pl).