Security, spam and data retention

Built-in spam protection, the optional reCAPTCHA v3 integration and what it sends, what Schedopia does and does not contact, and what happens to your data on uninstall.

Updated 30 August 2026. Applies to Schedopia 1.3.0.

Spam protection that needs no third party

The public booking form is protected out of the box by two checks, added in version 1.2.1:

  • Honeypot field: a field humans never see. Automated submissions that fill it are rejected.
  • Minimum fill time: submissions completed faster than a person plausibly could are rejected.

Both run on your server. Nothing is sent anywhere.

Optional Google reCAPTCHA v3

If you want an extra layer, enable reCAPTCHA v3 under Settings → Booking rules and enter your own site key and secret key from Google.

When, and only when, it is enabled:

  • The booking form loads Google’s reCAPTCHA script.
  • On submit, the reCAPTCHA response token and the visitor’s IP address are sent to Google’s siteverify endpoint to obtain a score.
  • No booking or customer data is sent.

Google’s terms of service and privacy policy apply to that request. If you never enable the feature, no request to Google is ever made.

External services

Schedopia loads nothing from third-party CDNs and contacts no external service by default. The only optional external connection is reCAPTCHA as described above. Emails are sent by your WordPress install using its configured mail method.

Where your data lives

Bookings, customers, services, staff, payments, venues, seats and events are stored in wp_schedopia_ tables in your WordPress database. Backing up your database backs up Schedopia. Moving your site moves it too.

Permissions

Admin actions are guarded by per-area capabilities, so you can give a receptionist access to bookings and customers without access to settings or the seat planner. Public REST routes used by the form are rate-limited.

What happens on uninstall

Deleting the plugin preserves your business data by default. The tables and their contents stay in the database so that reinstalling brings everything back. Data is deleted only if you explicitly opt in before uninstalling.