Skip to content
Warp Calendar

Warp Calendar Events: External Services and Privacy

Updated

This page explains what the free Warp Calendar Events plugin stores on your WordPress site and when it shares data with external services. It covers version 0.4.0 of the plugin distributed through WordPress.org.

The free plugin does not send telemetry or contact an activation, licensing, or external update server. WordPress.org handles updates for the directory version.

External services

  • ICS calendar imports. When an administrator previews a public HTTPS calendar feed, the WordPress server requests the feed. The feed provider receives the request and the server’s IP address. The free plugin does not fetch feeds on a schedule. Use feeds you have permission to import and review the provider’s policies.
  • Google Calendar. When a visitor clicks the Google Calendar link, their browser opens Google Calendar with the event title, dates, description, public event link, and venue location. This is a one-time action initiated by the visitor. Google Calendar · Privacy · Terms
  • Venue directions and event maps. Clicking an enabled venue directions link sends the venue address to Google Maps. The events map starts as a list. If the site administrator enables Google Maps or OpenStreetMap, map images load only after the visitor selects Show map. The map provider receives the visitor’s IP address and venue coordinates. Google Maps uses the site’s own API key. Google Maps · Google Privacy · Google Terms · OpenStreetMap · Tile Usage Policy · OpenStreetMap Privacy
  • PayPal. When an organizer enables paid tickets through PayPal, buyers complete payment on PayPal’s hosted checkout. The WordPress server uses PayPal’s API to create, capture, verify, and refund payments and to verify webhook signatures. PayPal receives the booking reference, amount, currency, event description, and any information the buyer enters at checkout. PayPal · Privacy · Terms
  • WooCommerce. If the site owner enables WooCommerce checkout, Warp Calendar creates an order in WooCommerce on the same WordPress site. The store’s configured payment gateway then handles the payment under its own terms and privacy policy.
  • MailPoet. If the integration is enabled, Warp Calendar passes sign-up details to MailPoet on the same WordPress site only when a guest selects the separate newsletter checkbox. MailPoet may send a confirmation email according to the site’s settings.
  • Online event links. Organizers can add links to meeting providers such as Zoom or Google Meet. Visitors who have access to the link contact the provider when they open it in their browser.
  • Calendars embedded on other websites. Visitors’ browsers request public calendar data and assets from the WordPress site that hosts the calendar. That server receives standard HTTP request information. The optional automatic resizing script shares the public calendar frame’s height with the page that embeds it.

For AppSumo purchases, we exchange authorization information with AppSumo to verify and connect your purchase. We store the AppSumo license identifier and its status alongside your WordPress account and license handler so we can provide access, updates, and support. License and activation records are retained for licensing administration and are not automatically deleted when the bridge is deactivated.

Data stored on your WordPress site

Venue and organizer details, including names, addresses, websites, phone numbers, and email addresses, are stored in WordPress. Published contact details can appear on event pages. Displaying an email address requires an explicit setting.

When registration is enabled, booking records can include purchaser names and email addresses, attendee names, optional attendee email addresses and answers, booking dates, and payment status. These records are stored privately and are available to staff with booking permissions. Waitlist and newsletter sign-up records are also stored privately. Public calendar responses and feeds exclude these records.

WordPress’s personal data export and erasure tools cover booking data. Waitlist and newsletter sign-up records are also covered by the erasure tool. Payment amounts and PayPal transaction IDs are retained for accounting. Deactivating or deleting the plugin leaves booking data in place. Site administrators control backups, retention, and deletion.

Waitlist backups and recovery

Warp Calendar stores waitlist entries in your WordPress database. These include the guest’s name and email address, the event and date, the number of places requested, and the entry’s status.

Site administrators can download an encrypted backup of verified closed waitlist entries with no linked booking. Keep the backup file and its recovery key separately. Both are required to restore the entries on the original site.

Administrators can erase eligible entries after a separate confirmation. Older or unverified entries are kept, and uninstalling the plugin keeps the stored data. Warp Calendar sends no data to external services for this feature.