
Eventotron is a festival and season management service used by arts festivals, fringes and venues. This plugin connects a WordPress site to a season in your Eventotron account and publishes it on the site.
What it does
[etron_account] shortcode, so they can see their orders. Sign-in happens inside Eventotron’s window too.You need an Eventotron account. The plugin does nothing until it is connected to a season with an API key from your Eventotron dashboard. Eventotron is a paid service; see https://eventotron.com for plans and terms.
Third-party code
assets/lib/leaflet.This plugin relies on the services below. Nothing is sent to anyone else, and no usage data is collected by the plugin itself.
Eventotron (https://eventotron.com) — the service this plugin exists to publish. It is used for three things:
https://eventotron.com/api/wp-bridge/) using the season API key you enter in the settings. This happens when you connect or refresh a season, and every 15 minutes if background sync is switched on. Only the API key is sent.https://eventotron.com/embed/v1/embed.js. Ticket selection, buyer sign-in and payment all happen inside Eventotron’s own window; this plugin never sees payment details or buyer accounts.Terms: https://eventotron.com/terms. Privacy: https://eventotron.com/privacy. You need an Eventotron account for any of this to work.
Eventotron’s image store — when you import an event, venue or merchandise item, its main image is downloaded from Eventotron’s content delivery network (d1vlmco8ur52ud.cloudfront.net) into your media library, and built-in listings, maps and social-image metadata use that media-library copy. If the image import fails, these views omit the image rather than loading the original remote URL. Custom template fields styled as images, custom HTML and theme overrides may still load URLs supplied by the site owner or the imported data directly; those image hosts then receive the visitor’s IP address and normal browser request headers. Covered by the Eventotron terms and privacy policy above.
OpenStreetMap (https://www.openstreetmap.org) — map tiles are loaded from OpenStreetMap’s public tile servers when a page shows a map, which means those servers receive the visitor’s IP address as part of the request. Tile usage policy: https://operations.osmfoundation.org/policies/tiles/. Privacy: https://wiki.osmfoundation.org/wiki/Privacy_Policy. Busy sites should use the etron_map_tile_url and etron_map_tile_attribution filters to point at a hosted tile provider of their choice.
YouTube and Vimeo — if an event or venue in your season has a YouTube or Vimeo video, its page embeds that video with the provider’s own player (youtube.com, player.vimeo.com), which loads only when that page is viewed. YouTube terms: https://www.youtube.com/t/terms, privacy: https://policies.google.com/privacy. Vimeo terms: https://vimeo.com/terms, privacy: https://vimeo.com/privacy.
The visitor’s browser location — the departure board’s “Nearest” option asks the browser for the visitor’s location. The browser asks the visitor for permission first, and the coordinates are used only to order results on that page; they are not stored.