Skedify

What Skedify is and how it works

Skedify is a SaaS appointment scheduling platform developed by the Belgian company Skedify NV (skedify.co). It targets sectors with omnichannel customer interactions: retail banks, insurers, telcos, government agencies, and healthcare networks. The product is delivered as an embeddable booking widget that merchants drop on their website, plus a backend used by employees to manage availability, locations, services and appointment types.

Bookings can be conducted in-branch, by video conference, or by phone. Skedify synchronises with Microsoft 365 and Google Calendar so that appointments appear directly in the agent calendar, and it supports SAML single sign-on for enterprise deployments.

Data and cookies collected

The Skedify widget sets a small number of first-party functional cookies: a session identifier used by the booking flow, a CSRF protection token, a locale preference cookie, and a cookie that remembers an in-progress booking so the visitor can resume it. These cookies are strictly necessary for the widget to function.

Skedify also offers optional analytics cookies that aggregate widget usage statistics (success rate, drop-off step, average completion time). These are off by default and require consent. Personal data processed includes the visitor's name, e-mail, phone number, the chosen appointment topic and time slot, and sometimes free-form notes added by the customer.

GDPR and ePrivacy framework

Functional cookies needed to make a booking are exempt from prior consent under Article 5(3) of the ePrivacy Directive. The analytics cookies are not exempt and must be gated by the consent banner. The legal basis is contract performance (Article 6(1)(b) GDPR) for the appointment itself, and consent (Article 6(1)(a)) for the analytics layer.

Hosting and data transfers

Skedify hosts customer data on EU infrastructure located in Belgium. There is no systematic transfer outside the EEA. Subprocessors such as cloud providers and e-mail delivery services operate in EU regions. This makes Skedify a strong fit for organisations that need to limit third-country exposure, including public sector entities subject to additional Schrems II constraints.

Consent, DPIA and processor obligations

Sign a data processing agreement with Skedify as a processor. A DPIA is recommended whenever the appointment topic can imply sensitive information (financial advice, healthcare visits, social services). Configure the widget to collect only the minimum required fields, avoid free-text notes for diagnostic content, and enable role-based access for staff calendars.

Practical implementation steps

Add Skedify to your privacy policy as a processor, document the data flow in your record of processing, classify functional cookies as strictly necessary and analytics cookies as subject to consent, set a clear retention policy for booking records (typically twelve months after the appointment), and use the Skedify API rather than embedding sensitive context in free-text fields.