2 min read
MyBookaro integrates with WordPress’s built-in privacy tools and follows GDPR-style data handling principles.
What MyBookaro stores #
- Bookings: customer name, email, phone (if provided), notes, dates, status, links to listing/provider/service.
- Provider availability rules, time slot templates, exceptions.
- Notification logs for delivery diagnostics.
- Pro: chat messages, custom profile data, payment metadata, calendar sync tokens (in user meta).
- Pro: export audit log entries.
What it does NOT store #
- Payment card data — handled by WooCommerce + your gateway.
- Calendar event content beyond the booking summary.
- SMS message content beyond the immediate send (logged on failure only).
Personal data export #
Use WordPress’s built-in tool: Tools → Export Personal Data. Enter the user’s email; MyBookaro adds a “MyBookaro Bookings” group and a “MyBookaro Profile” group to the export.
Personal data erasure #
WordPress’s built-in Tools → Erase Personal Data. MyBookaro responds by anonymizing booking records (removing PII) rather than deleting them — this preserves business integrity (revenue, audit trails) while honoring the erasure request.
Filters for advanced cases #
bookaro_privacy_user_meta_keys— list of meta keys to export.bookaro_privacy_export_masked_meta_keys— meta keys to mask (last 4 digits, etc.).bookaro_privacy_export_sensitive_meta_keys— meta keys to exclude entirely.bookaro_privacy_on_user_delete— custom behavior on user deletion.bookaro_privacy_cleanup— post-deletion hook.bookaro_privacy_policy_content— privacy policy text suggested by the plugin.
Pro: third-party data flows #
- WooCommerce orders are stored in WooCommerce.
- Google Calendar OAuth tokens stored in WP user meta; calendar IDs and event IDs are sent to Google.
- Twilio: phone numbers + message bodies sent to Twilio at send time.
- Webhooks: payloads sent to your configured endpoints.
Public endpoints #
Public REST endpoints (booking submit, availability query) are rate-limited. Excessive abuse returns HTTP 429 with a Retry-After header.