On this page
Privacy Policy
OnwardHop.com
Effective date: 5 October 2026
Version: 1.0
1. Controller and contact
The controller of personal data processed by OnwardHop is Administrator of OnwardHop.com.
For privacy questions, rights requests and general enquiries, contact support@onwardhop.com or use our contact form.
This Policy explains how we handle information about website visitors, customers, passengers and people who contact us. It is an information notice, not a request for blanket consent. Necessary order processing is not made dependent on accepting advertising or analytics cookies.
2. Information we collect and its sources
Order and passenger information. We receive contact email, passenger names, age categories, and, where required for the reservation, dates of birth or gender, together with airports, travel dates, journey type, delivery choices and other details needed to arrange the order. We receive these from the purchaser, who may be booking for someone else. We do not routinely require passport scans or precise device location for the standard service.
Reservation information. Our reservation provider and the airline booking systems return itinerary details, booking references, reservation status, available validity information and PDF confirmations. These records can include information about multiple passengers on the same order.
Payment and transaction information. We receive the amount, currency, payment status, transaction references, refunds, discount information and, where applicable, billing details and limited payment-method information from Stripe. Our checkout is designed so that full card numbers and security codes are handled by the payment provider rather than stored by OnwardHop.
Messages and delivery records. We process contact-form submissions, support correspondence, complaint information and transactional email events, such as delivery failures. Do not send sensitive information or identity documents unless specifically necessary and requested through an appropriate channel.
Technical information. Website requests can produce IP addresses, browser and device information, language settings, timestamps, session and security identifiers, error information and relevant page activity. We keep previously recorded privacy choices while they remain valid. Optional analytics and advertising collect additional event and device information only as described below.
Providing information necessary for an order is voluntary, but we cannot arrange a reservation without the required passenger, journey, contact and payment details. Optional analytics and advertising consent is not needed to purchase.
We also record limited order source information: the referring domain, landing path, campaign source/medium/name and whether a Google advertising click parameter was present. These order source records do not contain the click identifier or the full referring URL. This information stays in the current page navigation until associated with a checkout; no extra attribution cookie or browser storage is used. Where trusted Cloudflare headers are available, we record the country estimated from the visitor IP, without adding the raw IP to the order. This helps us understand order sources and operate the service.
3. Purposes and legal bases
Where the GDPR applies, we use the following bases:
| Purpose | Information involved | Legal basis |
|---|---|---|
| Prepare, accept and fulfil your order; provide private access and transactional messages | Purchaser details, itinerary, transaction and reservation records | Performance of a contract or steps requested before a contract, Article 6(1)(b) |
| Arrange travel reservations for passengers who are not themselves contracting parties | Required passenger details and itinerary | Our and the passengers' legitimate interests in arranging the authorised booking, Article 6(1)(f), subject to necessity and a balancing assessment; Article 6(1)(b) where a passenger is validly represented as a contracting party |
| Maintain legally required tax, accounting and other records | Necessary transaction and billing records | Legal obligation, Article 6(1)(c) |
| Resolve enquiries, complaints, refunds and disputes | Correspondence and relevant order records | Article 6(1)(b), Article 6(1)(c) where required, and Article 6(1)(f) for establishing, exercising or defending claims |
| Protect the service, investigate errors and prevent misuse | Limited technical, security and transaction information | Legitimate interests in operating a secure, reliable service, Article 6(1)(f) |
| Optional checkout reminder with a discount | Contact email, consent record and unfinished checkout | Consent, Article 6(1)(a), and applicable electronic-communications requirements |
| Basic audience measurement without analytics cookies | Public page and checkout-start signals with technical request data | Our legitimate interest in understanding how visitors use the website, Article 6(1)(f) |
We assess legitimate interests against individuals' rights, with particular care for children's information. Information needed for one purpose is not automatically required or retained for every other purpose.
4. Passengers booked by someone else and children
A purchaser may provide information about other adults or children. In that case, the source of the passenger information is the person arranging the order. The booking provider and airlines may subsequently supply status and itinerary information.
Our service is purchased by adults, but reservations may include children. We process the necessary child information to arrange that booking; we do not treat all passengers as adults or deliberately target children with advertising.
Purchasers should provide this Policy to affected passengers or guardians. We remain responsible for meeting our own transparency duties, including providing information directly or through an appropriate documented notice process where required.
The purchaser receives the reservation confirmation and private order access. Other passengers' names and itinerary information may therefore be visible to that purchaser. Let us know if you need to exercise rights for yourself or, with authority, for a child included in an order.
5. Who receives information
We disclose relevant information only where needed for the purpose described. Recipients may act as processors following our instructions, independent controllers for their own legal purposes, or, for particular advertising functions, joint controllers under an applicable arrangement.
Reservation fulfilment — Safeonward. We transmit required passenger, contact and journey information to Safeonward, the reservation service available at safeonward.com, to create the reservation and obtain its confirmation. Relevant data can pass to the airline, reservation systems and fulfilment partners involved in the itinerary. The roles and processing locations depend on the itinerary and providers involved. Contact support@onwardhop.com for information about a specific reservation and see Safeonward's published privacy notice.
Payments — Stripe. Stripe processes payments and related fraud prevention, authentication, refunds and legal compliance. The relevant Stripe group entities are identified in the applicable merchant agreement and Stripe Privacy Center. Some Stripe activities are performed as an independent controller; other activities may be performed on our behalf under the applicable agreement. See Stripe's Privacy Policy.
Email — Resend. We use Resend, operated by Plus Five Five, Inc., to send transactional messages. Relevant information can include the recipient address, message content, order links and reservation attachments. Its processing can involve the United States. See Resend's Privacy Policy.
Hosting and infrastructure. The website, database, document storage and related infrastructure are provided by OVHcloud, with reservation documents stored privately on the server. Cloudflare Turnstile, when activated, processes information needed to protect contact and login forms. See Cloudflare's Privacy Policy.
Optional analytics. Google Analytics 4 receives the measurement signals described in Section 6. Google may also process information for its own purposes as described in Google's Privacy Policy. OnwardHop also uses a Google Ads purchase tag to report confirmed transaction values without advertising cookies. A temporary measurement identifier links a checkout to its server-confirmed payment. It is kept in browser memory during the visit and with the order for conversion reporting. Advertising storage, advertising user data and ad personalisation remain denied unless a separate permission is recorded.
Optional advertising conversion measurement. With your checkout permission, OnwardHop can send Google Ads the advertising click identifier, a transaction reference, payment time, amount and currency to measure the campaign, including after a return through a discount email. We do not send email addresses, names, itinerary or payment card details for this purpose. The click identifier is encrypted on our server for up to 30 days. The checkout control is optional and we do not use this data for personalised advertising. To withdraw, use the measurement opt-out on this page in the original checkout browser or contact support@onwardhop.com with your booking reference.
Other recipients. Relevant information may be shared with authorised professional advisers, accountants, competent authorities or parties to a legal claim where necessary and lawful. We do not publish passenger lists or make reservation PDFs publicly accessible.
6. Cookies and analytics
Essential technologies support checkout, security and private order access. The table below lists the technologies, their purposes and how long they last.
Basic analytics without cookies. OnwardHop counts public page views and checkout opens in live and daily totals without adding an analytics identifier or storing browsing histories. Google Analytics 4 also receives public page views, campaign labels, checkout activity, and a limited purchase event when the browser returns after a confirmed payment, without reading or writing analytics cookies. Checkout activity can include product, amount, currency, step and payment method type. The purchase event includes a random transaction reference to prevent duplicate counts. These signals may contain technical request information such as your IP address, browser information and screen size. Google may use the signals for estimates in its reports. OnwardHop leaves advertising storage, advertising user data and ad personalisation disabled in its Google tag.
OnwardHop runs Google Analytics without cookies. To report a public page view in Google Analytics in real time, OnwardHop sends the public page address and a random visit identifier generated in browser memory. It is discarded when the document closes or replaced after 30 minutes. We do not send the visitor's IP address with this server event or link the identifier to a booking. You can turn off Google Analytics in this browser below. Confirmed payments remain in our order records regardless of analytics settings.
We do not intentionally transmit passenger names, dates of birth, PNRs, PDF contents, full card data or secret order-access URLs as analytics or advertising event data. The purchase event reports the public checkout address and excludes the booking page URL, contact information and passenger details.
Transactional emails are used to fulfil and support the order. They are not an automatic subscription to unrelated marketing. If you separately opt in, we may send up to two reminders with a one-time discount for an unpaid checkout. You can unsubscribe using the link in that email; this does not affect essential booking messages or an offer already received. We keep the consent version, time and source, recipient, offer expiry and email delivery records to operate this feature and respect your choice. No email open or click tracking is added by this feature. Email open or click tracking, enhanced conversion matching and server-side advertising are not covered merely by naming GA4 or Meta Pixel here; they must be disclosed and configured appropriately before use.
Browser language may suggest a supported interface language or currency. You can override available choices. Only the currency and total expressly shown at checkout determine the amount charged by us.
Cookie and storage disclosure
| Technology | Purpose | Lifetime or scope |
|---|---|---|
| OnwardHop session cookies | Checkout security, private order access and administrator authentication | Limited to the configured session; private order access expires separately from the airline reservation |
| OnwardHop language cookie | Keep the chosen language between checkout and booking pages | Up to one year |
| Pending checkout identifier in session storage | Resume a prepared checkout without storing passenger or card details in browser storage | Browser tab session; removed when the pending checkout is cleared |
| Currency preference in local storage | Remember the selected currency | Until cleared or changed in the browser |
| Google Analytics opt-out (local storage) | Remember when you turn off Google Analytics | Until you clear site data. Previously recorded refusals remain valid for up to 180 days. |
| Stripe payment technologies | Payment authentication, security and fraud prevention | Governed by Stripe's Cookies Policy and the payment method used |
| Cloudflare Turnstile, when activated | Verify requests and reduce automated abuse | Governed by Cloudflare's notice and the widget configuration |
7. International transfers
Some recipients or their support and infrastructure providers may process data outside the European Economic Area. An international airline itinerary can also involve reservation infrastructure in other countries. We do not claim that every reservation, payment or email stays in Poland or the EEA.
Where the GDPR requires transfer safeguards, we must establish the relevant basis before the transfer. Depending on the actual recipient, this can include an adequacy decision or Standard Contractual Clauses with a transfer assessment and supplementary safeguards where necessary. A US recipient's use of the EU–US Data Privacy Framework is relevant only if its current certification covers the recipient and processing concerned. Accepting these Terms or this Policy is not blanket permission for unrestricted international transfers.
Stripe and Resend describe their processing arrangements and transfer mechanisms in their Data Processing Agreement and Data Processing Addendum, respectively. Hosting uses OVHcloud infrastructure; airline reservation processing can involve countries on the requested itinerary and global reservation networks. The applicable mechanism depends on the provider, destination and processing concerned. Contact our privacy address for information or a copy of applicable safeguards, subject to necessary redactions protecting others and legitimate confidential information.
8. Retention and deletion
We keep information for the purposes stated and use the following retention criteria. The period depends on the service, applicable legal duties and any specific dispute; we do not claim that all records have the same fixed lifetime. Different copies or fields may have different justified retention periods; a tax record does not automatically justify retaining every passenger's full PDF or birth date.
| Records | Retention criteria |
|---|---|
| Incomplete or unpaid checkout drafts | For as long as needed to complete or resolve the attempted checkout, then subject to deletion or anonymisation unless required for security or a specific claim |
| Reservation PDFs and passenger/itinerary details needed to deliver and support the reservation | For the time needed to deliver the reservation, provide order access and resolve related support or disputes; unnecessary passenger fields and PDFs are considered separately from transaction evidence |
| Necessary payment, tax and accounting records | For the statutory period required by applicable tax and accounting law, using the starting point required by that law |
| Support and complaint correspondence | For the time needed to handle the enquiry and document its resolution or a related legal claim |
| Routine technical and security logs | For the period needed for security, incident investigation and diagnostics; relevant incident extracts may require longer retention |
| Consent and notice-version evidence | For the time needed to demonstrate the applicable notice or choice and respond to a related complaint or legal claim |
| Optional analytics and advertising information | GA4 cookie lifetime is described in Section 6. Event-data retention is controlled by the GA4 property settings. OnwardHop does not load Google Ads or Meta Pixel tags through its analytics integration |
| Deleted information remaining in rotating backups | Deleted information is removed through the applicable backup rotation; if a backup is restored, relevant deletion requests must be reapplied before ordinary use |
Limited records may be kept longer where a legal duty or a specific claim requires it. We restrict that information to the relevant purpose and review it when the obligation or dispute ends. Otherwise, we delete information or irreversibly anonymise it. Keeping a private link active is not a promise that a flight reservation remains active.
9. Security and automated processing
We use access restrictions, protected connections and controls appropriate to the information handled. Private order links function as access credentials and should not be shared publicly. There is no guarantee that any internet service can eliminate every security risk. Contact us promptly if you believe your order access or information has been compromised.
Software validates forms, initiates payment and reservation requests, receives status updates and sends messages. A provider response, such as lack of availability or a payment verification failure, can prevent automated completion. Contact us to query an error and request appropriate review; independent payment or airline decisions may need to be addressed with the relevant provider as well.
If processing could amount to a solely automated decision with legal or similarly significant effects, we must provide the information and safeguards required by applicable law. You can contact support@onwardhop.com to ask about the processing of your order and request review.
10. Your rights
Subject to the conditions and exceptions in applicable law, you may request access to your information, correction, deletion, restriction of processing and portability of information processed automatically on consent or contract grounds.
You can object to processing based on legitimate interests for reasons relating to your situation. Where information is used for direct marketing, you can object to that use at any time. You may withdraw consent without affecting the lawfulness of processing before withdrawal.
Send requests to support@onwardhop.com. We may ask for information reasonably necessary to verify identity or authority for a child, but will not routinely demand a full passport copy. We normally respond within one month. Where the law permits an extension for complexity or the number of requests, we notify you within that first month, explain the reason and extend by no more than two further months. Requests are normally free; any exception must satisfy the law.
Some information cannot be deleted immediately where it is still necessary for a legal obligation or a legitimate claim. We explain relevant limits rather than treating them as a reason to retain everything.
You may complain to the Polish supervisory authority, the President of the Personal Data Protection Office (UODO), or another competent supervisory authority, including in your place of habitual residence or work, or the place of the alleged infringement. See UODO. You do not have to contact us first to exercise that right.
11. Updates
We publish updates with an effective date and provide additional notice of material changes where required. A revised notice does not retrospectively authorise incompatible uses of information or replace consent where consent is needed.
