TailDesk logo

TailDesk

Easy bookings. Happy pets.

My Taildesk
Get Started

TailDesk Privacy Policy

Last updated: 30 May 2026

This Privacy Policy explains how EyeSeeT processes data in relation to TailDesk, TailDesk Pro, TailDesk licensing, billing, and the optional Google Calendar connection. TailDesk is a WordPress booking plugin for pet sitters, pet care providers and small-scale care services.

This policy applies to the TailDesk plugin, TailDesk Pro, the TailDesk licensing and sync services operated by EyeSeeT, and the related product pages on eyeseet.nl.

Who is responsible for the data?

EyeSeeT develops and operates TailDesk, TailDesk Pro, the licensing system and the optional TailDesk Google Calendar bridge.

When TailDesk is installed on a customer’s WordPress website, the site owner is responsible for the booking data, customer data, invoice data and plugin settings stored on that WordPress website. EyeSeeT is responsible for the data processed on EyeSeeT servers for licensing, billing and optional Google Calendar sync services.

Data stored on the customer’s WordPress website

TailDesk stores booking and configuration data locally on the customer’s own WordPress website.

Booking data

Bookings are stored in the custom post type taildesk_booking and related post meta. This may include:

  • customer name;
  • customer email address;
  • customer phone number;
  • customer note or booking note;
  • selected service;
  • start date and end date;
  • booking status;
  • internal administrator note;
  • price, invoice and booking snapshots, including amounts, days and price breakdowns.
  • Additional configured fields using the Pro version.

Plugin settings

TailDesk stores plugin settings in WordPress options. This may include:

  • services, including service name, description, price and capacity;
  • general plugin settings;
  • runtime settings;
  • notification settings.

Invoice data

TailDesk may store invoice-related data locally on the customer’s WordPress website. This may include company details such as company name, address, VAT ID and tax settings, as well as invoice snapshots or invoice documents per booking that include customer and booking data.

Temporary feedback

TailDesk may store temporary form feedback, such as form errors or success messages, as short-lived WordPress transients.

Additional data stored by TailDesk Pro on the customer’s WordPress website

TailDesk Pro may store additional local data on the customer’s WordPress website.

  • Pro settings per service, such as Google Calendar connection settings, additional rules and extra fields;
  • per-booking Google event linking, such as calendar ID, event ID, sync timestamps and conflict status;
  • custom booking field values and snapshots;
  • external calendar overlays, such as calendar ID, event ID, title, date and status;
  • local connection status cache.

In the current TailDesk architecture, Google OAuth tokens are stored primarily on the TailDesk server operated by EyeSeeT, not inside TailDesk Pro on the customer’s WordPress website.

Data stored on EyeSeeT servers

EyeSeeT may process and store data on its own servers for licensing, billing, customer account management and optional Google Calendar sync.

Licensing and tenant records

EyeSeeT may store licensing and tenant records, including:

  • license key;
  • domain or site URL;
  • user ID;
  • license status, type and expiry date;
  • tenant ID or customer site record;
  • hashed license key;
  • validation status, error status and related technical status information.

Purchases, payments and invoices

TailDesk purchases, subscriptions, invoices and license records may be processed through the payment and billing system used by EyeSeeT. This may include customer name, email address, billing details, tax details, order details, product details, payment status, invoice details and license details.

Payment card or payment account details are processed by the relevant payment provider. EyeSeeT does not use Google Calendar data for payment processing.

Google Calendar connection data

If a customer connects TailDesk Pro to Google Calendar, EyeSeeT may store Google Calendar connection data per tenant. This may include:

  • Google account email address;
  • Google OAuth access token;
  • Google OAuth refresh token;
  • token expiry time;
  • OAuth client ID and client secret where applicable for the configured connection;
  • calendar list data;
  • selected calendar IDs;
  • last sync status and last error information.

Access tokens and refresh tokens are used only to process requests required by the TailDesk plugin and TailDesk Pro Google Calendar features. These requests require the customer site URL, a valid TailDesk license key and a secret key generated during the secure handshake between the customer site and the TailDesk server.

Google OAuth access tokens and refresh tokens are deleted from EyeSeeT servers when the Google Calendar connection is disconnected. Data already stored in the customer’s Google Calendar, such as calendar events created or updated by TailDesk, remains in the customer’s Google account until the customer deletes or changes it in Google Calendar.

Temporary OAuth and bridge data

EyeSeeT may store short-lived technical transients for the Google OAuth and bridge flow, such as OAuth state, token hashes, tenant identifiers, site URL and expiry timestamps. These are used to complete the connection process and secure communication between the customer website and the TailDesk server.

How Google Calendar data is used

Google Calendar access is optional. TailDesk can be used without connecting Google Calendar.

When Google Calendar sync is enabled, TailDesk may use Google Calendar data to:

  • connect a customer’s Google account to TailDesk Pro;
  • retrieve calendar lists or selected calendar information;
  • read calendar events for availability overlays and conflict checks;
  • create, update or link Google Calendar events for TailDesk bookings, depending on the enabled sync settings;
  • store event IDs, calendar IDs and sync timestamps so that future updates can be matched to the correct booking and calendar event.

When TailDesk sends booking information to Google Calendar, the calendar event may include booking details such as customer name, customer email address, customer phone number, customer note, selected service, booking dates and booking status, depending on the customer’s configuration and the sync feature being used.

If Google Calendar is not connected, booking personal data is not sent to EyeSeeT servers through the TailDesk Google Calendar sync flow.

Google API Limited Use

TailDesk’s use and transfer of information received from Google APIs complies with the Google API Services User Data Policy, including the Limited Use requirements.

EyeSeeT uses Google user data only to provide and improve user-facing TailDesk Google Calendar functionality, such as calendar connection, availability overlays, booking conflict checks and booking event synchronization. EyeSeeT does not sell Google user data, does not use Google user data for advertising, does not use Google user data to determine creditworthiness or lending purposes, and does not allow humans to read Google user data unless this is necessary for security, support, legal compliance, abuse investigation, or when the customer has explicitly asked EyeSeeT for help.

Data sharing

EyeSeeT does not sell personal data.

EyeSeeT may share data only when needed to provide TailDesk services, comply with the law, protect security, or process payments and licensing. This may include hosting providers, payment providers, billing providers, email delivery providers, support tools and Google APIs when Google Calendar sync is enabled.

Data retention and deletion

Booking data stored on a customer’s WordPress website is controlled by the customer/site owner and remains there until the customer deletes it or changes the applicable retention settings.

License, order and invoice data may be retained for as long as needed for account management, legal, tax, accounting, security and support purposes.

Google OAuth access tokens and refresh tokens stored by EyeSeeT are deleted when the customer disconnects Google Calendar. Temporary OAuth and bridge transients expire automatically after a short period.

Security

EyeSeeT uses technical and organizational measures designed to protect data against unauthorized access, misuse, loss and alteration. Google Calendar requests require a customer site URL, a valid license key and a secret key generated during the handshake between the customer site and the TailDesk server. OAuth tokens are used server-side for TailDesk functionality and are not intended to be exposed publicly.

Customer responsibilities

Customers using TailDesk on their own WordPress website are responsible for informing their own visitors and booking customers about how they process booking data, invoice data and any data sent to Google Calendar through their configuration of TailDesk Pro.

Your rights

Depending on applicable privacy law, individuals may have the right to request access, correction, deletion, restriction or export of their personal data. For booking data stored on a customer’s WordPress website, requests should be directed to the relevant website owner. For data processed by EyeSeeT for TailDesk licensing, billing or Google Calendar sync, requests can be sent to EyeSeeT through the contact page at https://eyeseet.nl/contact/.

Changes to this policy

EyeSeeT may update this Privacy Policy when TailDesk, TailDesk Pro, the licensing system, Google Calendar sync, legal requirements or data processing practices change. The latest version will be published on this page.