Contact
info@reisenpartner.com
Use this address for privacy questions, correction requests, or anything that feels unclear about how your information is handled.
Privacy overview
How privacy works across ReisenPartner and booking partners
ReisenPartner is built around travel discovery and partner handoff. That means some information is handled on this site, while booking-specific responsibility moves to the partner you choose.
Scope
Browsing and support only
ReisenPartner focuses on discovery, comparison, and outbound partner handoff. We are not processing full booking payments on this site.
Review window
Handled manually
Privacy-related requests are reviewed directly so the response can reflect the actual issue rather than a canned support reply.
Privacy questions
What kind of information does ReisenPartner collect?
That can include standard browsing information, search inputs you enter on the site, device or session signals used to keep the experience working, and details you send directly through support contact.
Why is this information used?
It is mainly used to improve discovery, understand what parts of the site are being used, respond to support requests, and make outbound partner handoff more consistent when you move toward booking.
Does ReisenPartner store payment details?
No full booking payment flow is being completed here. When you move to a partner site to finish a reservation, that transaction and its payment handling are controlled by the partner.
What happens when I click through to a booking partner?
Once you leave ReisenPartner and continue on a partner site, that partner applies its own privacy terms, cookies, and reservation handling. Their policy governs what happens next on that destination.
Can I ask for my message history or submitted details to be reviewed?
Yes. If you contacted support, you can request a review or correction of the information shared in that thread by writing to the privacy contact email.
Are cookies or analytics involved?
Basic site analytics and session-related tools may be used to keep the product functional and understand usage patterns. The exact implementation may change as the product evolves.