Does your website use third-party services? Get GDPR compliant in minutes.
Try FlowConsentFree plan · 10-min setup
How Reservio handles cookies and personal data, and what European websites must do to use it in a GDPR and ePrivacy compliant way.
Reservio is a online booking and scheduling service. It is an online booking system from the Czech Republic that lets businesses take appointments and reservations through a widget. When it runs on a website it operates as a third party processor whose scripts, cookies and network requests are loaded into the browsers of your European visitors.
In a typical deployment Reservio processes appointment details, contact data, session identifiers and analytics on booking funnels. Most of this information qualifies as personal data under the GDPR because it can be linked to an identifiable person, directly or through online identifiers stored on the device.
Any storage of or access to information on a visitor device is governed by Article 5(3) of the ePrivacy Directive, transposed into national law across the EU. The GDPR then governs the subsequent processing, so Reservio must have a valid legal basis, a clear retention period and transparent information for the data subject.
Get GDPR compliant in 10 minutes
Free plan available · No credit card required
Because Reservio sets cookies or identifiers that are not strictly necessary to deliver a service the visitor explicitly requested, prior, freely given, specific and informed consent is required before it loads. Scripts must stay blocked until the visitor accepts, and refusal must be as easy as acceptance.
Reservio reports hosting in Czech Republic (European Union), which keeps the core processing inside the European Economic Area. You should still confirm the location of any subprocessors and content delivery nodes, because a single non European endpoint can still trigger a transfer.
List Reservio in your records of processing and your cookie policy, load it only through a consent management platform, document the consent you collect and review the vendor data processing agreement at least once a year. Test the site with consent refused to make sure no identifier is set before a choice is made.
Websites using Reservio must obtain user consent under GDPR regulations.
DPIA considerations
Assess the volume and sensitivity of data processed through Reservio, whether visitors are profiled or tracked across sites, and any transfer outside the EEA. A formal DPIA is advisable where Reservio enables large scale monitoring or combines data from several sources.
Sample consent text
We use Reservio to power parts of this site. It may store cookies and identifiers on your device and process related data. With your consent we activate Reservio. You can withdraw your consent at any time from the cookie settings.
Third-party domains contacted
reservio.comCookies placed
| Name | Type | Duration | Purpose |
|---|---|---|---|
| reservio_session | necessary | Session | Maintains the booking session |
| reservio_locale | preferences | 1 year | Stores the chosen language |
| _ga | analytics | 2 years | Booking funnel measurement |
Reservio uses cookies for user preferences — inform visitors with a consent banner.
Reservio typically stores session identifiers and, depending on configuration, analytics or marketing cookies. The exact names and lifetimes appear in the cookie table on this page, and you should scan your own site because deployments differ.
Yes. Reservio sets cookies or identifiers that are not strictly necessary, so under Article 5(3) ePrivacy you must obtain prior consent before it loads.
The non essential cookies rely on consent under Article 6(1)(a) GDPR combined with Article 5(3) ePrivacy. Strictly necessary processing can rely on contract under Article 6(1)(b) or legitimate interest under Article 6(1)(f).
Reservio reports hosting in Czech Republic (European Union), so by default data stays in the EEA. Verify subprocessors and CDN nodes, since one non European endpoint can still create a transfer to a third country.
A DPIA is required when processing is likely to result in a high risk, for example large scale tracking or profiling. Where Reservio monitors behaviour at scale or combines data sources, run a DPIA before going live.
Load Reservio only after consent through a consent management platform, keep it blocked by default, document each consent, list it in your records and cookie policy, and sign a data processing agreement with the vendor.
Yes. Depending on your goal you can choose privacy first or cookieless tools, or self hosted options that keep data in the EEA. Whichever you pick, the same consent and transparency duties apply.
Add Reservio to the cookie policy with its purpose, the cookies it sets, their duration and the recipient, note any third country transfer and the safeguard used, and refresh the entry whenever you change configuration or after a new cookie scan.