EventBookings AI Connector — Privacy Policy

Last updated: 20 August 2026

This policy covers the EventBookings AI Connector: the service that lets an AI assistant such as Claude or ChatGPT work with your EventBookings data on your behalf. It does not replace the EventBookings privacy policy that covers your account and the EventBookings website; it describes what this connector specifically does with data.

In short. The connector is a pass-through. It holds no database and keeps no copy of your events, orders, tickets or contacts. It signs you in to EventBookings, forwards each request under your own credentials, and returns the answer to the assistant you asked. It keeps operational logs that record which action ran, not the contents of your data, and it never reads your conversations, chat history or files.

Who controls the data

EventBookings operates this connector. The data it reaches is the data already in your EventBookings account, and EventBookings remains its controller. The AI assistant you use is operated by a separate company you have your own relationship with — see the assistant you choose.

What the connector processes

Your identity, to sign you in

You sign in through the EventBookings identity service using the standard OAuth 2.1 authorisation-code flow. Your password is never sent to this connector and never seen by it. What the connector receives and holds is an access token, and a refresh token where you granted one, so your session can continue without asking you to sign in for every request. These are stored encrypted on the server and are removed when you disconnect the connector or the grant is revoked.

Your EventBookings data, in transit only

When you ask the assistant to do something, the connector calls the EventBookings API with your token and passes the result back. Depending on what you asked, that may include your organisation profile, events, ticket types, orders, tickets, attendees, contacts and contact lists, coupons, merchandise, bookable resources, and team members. None of it is written to storage by this connector — it is held in memory only for as long as the request takes.

Your token limits what can be reached to exactly what your EventBookings permissions already allow. The connector cannot see another organisation's data, and it does not widen your access.

Images you choose to upload

If you use the connector to set an event banner or add an image or PDF, the file is stored in EventBookings' own cloud storage and served from the EventBookings content network, exactly as if you had uploaded it in the dashboard. It becomes part of that event's content and is retained with it.

Operational logs

The connector writes two log files, to run the service and to investigate faults:

Both are held on EventBookings-controlled infrastructure, rotate at a fixed size, and the oldest file is discarded as new ones are written — so they are retained on a rolling basis rather than indefinitely.

Short-lived items held in memory

Confirmation tokens for actions awaiting your approval, single-use upload links (valid 15 minutes), and per-user rate-limit counters. None is written to disk and all are lost on restart.

What the connector does not do

The assistant you choose

The connector answers the AI assistant you connected it to. Anything you ask for is therefore returned into that conversation and handled under that provider's terms and privacy policy — Anthropic's for Claude, OpenAI's for ChatGPT. EventBookings does not control what that provider does with a conversation, so it is worth reading their policy alongside this one, and worth asking only for what you want in the conversation.

Others who process data for this service

There are no analytics, advertising or tracking services on this connector.

Legal basis and retention

Processing is to perform the service you asked for, and it starts only when you connect the connector and sign in. Retention: access and refresh tokens until you disconnect or revoke them; logs on a rolling basis as described above; uploaded images for as long as the event content they belong to exists. Your EventBookings data itself is retained under the EventBookings account policy, not this one.

Your choices

Security

All traffic is over HTTPS. Tokens are stored encrypted. Every request is authorised by the EventBookings API against your own token, so the connector cannot exceed your permissions. Access to log files is limited to EventBookings operations staff.

Children

The connector is a tool for event organisers and is not directed at children.

Changes to this policy

If this changes, the date at the top changes with it. Material changes will be communicated through the EventBookings account channels.

Contact

Questions about this policy, or about data handled by the connector: contact@eventbookings.com.


Connector documentation