Privacy notice

Updated 5 November 2026

1. Controller and contact

Phoenix GmbH operates the Parklumo booking platform and is the controller for Parklumo's platform processing.
Kappeler Straße 199
40599 Düsseldorf
Germany
Email: info@phoenix-biz.de

2. Booking, service coordination and accounts

We process the information needed to arrange and administer your booking: booking reference and status, name and necessary contact details, selected airport and Parking Service, arrival and return times, price, required vehicle identification or suitability details, and essential service milestones. We also process the account and access information needed by customers and authorized partner staff. Booking and service information necessary to perform the selected service is provided to that Parking Service. This includes your name, e-mail address and phone number as well as the travel and vehicle details and the price paid for your booking. They are passed on by e-mail, in the partner area or automatically through an interface (API) to the parking service's booking system. The parking service processes this data under its own responsibility to provide the booked service.

The purposes are booking/intermediation, communication about the booking, service coordination, payment/refund administration and customer support. Processing needed to perform a contract or take requested pre-contractual steps is based on Article 6(1)(b) GDPR; applicable legal obligations are based on Article 6(1)(c). Necessary security, abuse prevention and the establishment, exercise or defence of legal claims are based on Article 6(1)(f), subject to the required balancing of interests.

Reviews: After your stay has ended, we send you one e-mail asking for a review (legitimate interest, Article 6(1)(f) GDPR). You can object to this use at any time, using the link in the e-mail or by replying. If you write a review, we publish it after checking it, with your first name, the first letter of your last name, the month of your stay and the service type (Article 6(1)(b) GDPR). The parking service sees your review together with your name and the booking number.

3. Parking Service responsibility and complaints

The selected Parking Service performs the physical parking, valet or shuttle service. It keeps its own vehicle-condition photos, damage or inspection records, mileage evidence, handover/return signature images and physical-service CCTV in its own systems under its applicable responsibilities. Parklumo does not routinely collect, upload, store, display or require that customer-vehicle evidence.

Parklumo may keep a complaint case, its booking link, communications and request metadata, the operator's response, necessary factual resolution and the payment/refund outcome. Complaint coordination does not routinely involve copying the Parking Service's raw vehicle evidence into Parklumo. Please do not upload vehicle photos, inspection records or signature images to Parklumo. Public service-listing photos describe an offering and are separate from customer-vehicle evidence.

4. Payment and refund administration

We process the minimum payment/refund transaction references, amounts and statuses needed to administer your booking and resolve claims. Parklumo does not store raw card numbers or CVC. Payment details required for a payment are handled through the payment components presented during checkout; this notice does not assign additional data-protection roles to those services.

If you choose PayPal, you are redirected to PayPal (Europe) S.à r.l. et Cie, S.C.A., 22–24 Boulevard Royal, L-2449 Luxembourg, to sign in and approve the payment; for this, PayPal receives through Stripe the details needed for the payment (in particular amount and currency). PayPal's privacy notice applies there. Through Stripe, we receive from PayPal the status of the payment and the name, e-mail address, PayPal customer ID and country of the PayPal account; we use these details only to process and refund the payment. We never receive the login details of your PayPal account.

5. Technical logs and necessary technologies

Technically necessary access data is processed to keep the platform available and secure and to detect faults and abuse. The minimised routine access log contains source IP address, timestamp, HTTP method, normalised path without query string, response status, transferred data volume and request ID. Referrer, user agent, request body and query string are not stored in that routine log.

Routine access and error logs have a 14-day retention period by default. Longer retention requires a documented security incident, legal dispute or statutory need. The legal basis is Article 6(1)(f) GDPR; our legitimate interests are platform security, availability and integrity. Hosting and IT infrastructure service providers may process the necessary technical data to provide, maintain and secure the platform.

Necessary session and access technologies support protected platform functions and security. Non-essential storage or access on your device is not permitted without the required consent.

6. Optional analytics and consent

Optional first-party behavioral analytics is disabled by default and is not active. If separately lawfully activated, it requires your explicit, optional consent under Article 6(1)(a) GDPR and, where applicable, consent for non-essential device access. The approved retention target for those behavioral events is 30 days. Refusal does not prevent booking. You may withdraw consent for the future without affecting the lawfulness of earlier consent-based processing.

Only minimal proof of a consent or withdrawal decision is retained as needed to demonstrate that decision, with a policy target of three years after the end of the calendar year of withdrawal or last reliance, subject to review. Behavioral event detail is not retained as consent proof.

7. How long we retain other data

Our default operational retention target for Booking Core and payment/refund metadata is through the end of the third calendar year after the relevant booking/stay year. These records are needed independently of analytics consent. Complaint cases are kept while open and through the applicable claim-defense period after closure. A documented active dispute or claim can require restricted retention of the records actually needed for that case.

Records that qualify as accounting vouchers are retained for eight years under the applicable statutory calculation; qualifying commercial correspondence is retained for six years. These periods normally run from the end of the calendar year in which the voucher arose or the correspondence was received or sent. Other statutory accounting categories can require longer retention. We do not treat every booking field as an accounting document or every support message as commercial correspondence.

Partner/operator relationship and account information is kept while needed for the active relationship. After closure, only information required for claims, accounting, qualifying correspondence, security or other documented obligations is retained under the relevant category.

Truly anonymised statistics may be kept separately only if re-identification is not reasonably possible. A 24-month business-analysis target does not mean that existing completed-booking aggregates have already been approved as anonymous or that their separate lawful-basis question is resolved. Optional collection remains disabled.

8. Your rights and complaints

Subject to the GDPR requirements, you have rights of access, rectification, erasure, restriction, portability and objection. In particular, you may object to processing based on Article 6(1)(f) for reasons relating to your situation. Statutory retention and necessary legal-claim restrictions may limit erasure. Contact info@phoenix-biz.de. We respond without undue delay and generally within one month.

You may complain to a data protection supervisory authority. For Phoenix GmbH in North Rhine-Westphalia, the relevant authority is in particular the State Commissioner for Data Protection and Freedom of Information of North Rhine-Westphalia (LDI NRW), Kavalleriestraße 2–4, 40213 Düsseldorf, Germany.

9. Changes

We update this notice when relevant platform processing changes, before activating additional processing that requires new information or consent.