Site-owner controlled
Dayo is designed for WordPress sites where your organisation controls its event, venue, speaker, attendee, RSVP, and ticketing data.
Privacy Policy
Clear data handling for serious event teams.
Dayo is a WordPress events plugin built for fast calendars, accessible event discovery, large datasets, and developer-friendly implementation. This policy explains how privacy should be understood when Dayo is used on a WordPress website.
Last updated: 10 August 2026
Minimal by design
We build for performance and clarity, so the plugin avoids unnecessary tracking, front-end payload, and hidden third-party behaviour.
Built for responsible teams
Higher education, public engagement, agencies, and event teams need predictable tools that support accessibility, consent, and governance.
Information Dayo may process
Depending on how a site owner configures Dayo, event records may include titles, descriptions, dates, times, locations, venues, maps, organisers, speakers, sponsors, categories, media, ticketing settings, and RSVP settings.
If ticketing or RSVP features are enabled, Dayo may process attendee information entered by visitors, such as names, email addresses, ticket choices, attendance status, and accessibility or dietary notes where the site owner chooses to collect them.
How information is used
Dayo uses event and attendee information to publish calendars, show event detail pages, support booking and RSVP workflows, manage event capacity, and help administrators maintain accurate event records.
The plugin is not built around advertising profiles or unnecessary visitor tracking. Any analytics, payment, email, map, or CRM integrations should be reviewed and configured by the site owner.
Where information is stored
Dayo runs inside WordPress. Event data and plugin configuration are stored in the WordPress environment controlled by the site owner, unless the site owner connects external services.
External services may include payment processors, email platforms, analytics providers, map providers, hosting services, or CRM tools. Their privacy terms apply where they are used.
Retention and deletion
Site owners are responsible for setting retention rules that match their organisation, legal basis, and operational needs.
Dayo is intended to support clean data management workflows so old event records, RSVP data, and ticketing records can be reviewed, exported, or removed according to the site owner policy.
Accessibility and sensitive information
Event teams may collect accessibility requirements or other sensitive notes to support visitors. Site owners should collect only what they need, explain why it is needed, and limit who can access it.
Dayo prioritises accessible front-end experiences, but privacy notices, consent wording, and internal governance remain the responsibility of the organisation operating the website.
Your rights
If you are an attendee or visitor, contact the organisation running the website where you submitted your information. They are the best point of contact for access, correction, export, deletion, or consent questions.
If you are a Dayo customer and need help understanding how the plugin handles data, contact support with details of your configuration and the integrations you use.
Responsible implementation