Privacy and security for AI clients
Who is responsible for what your AI client receives, what TixFin sees and logs, and how a connection is held to you and your projects
You decide what goes to your AI provider
TixFin does not run a language model and is not a party to your conversation. The AI client you chose, and the provider behind it, receives every answer the client reads from TixFin and processes it under your agreement with that provider. For that processing you are the controller under the GDPR, as for any other tool you pass your data to.
Before you connect:
- check where your AI provider processes data and whether it may use your conversations for training;
- remember that even without personal data, some details can reach the provider (what is masked);
- allow See buyers' personal data only if you need it and your agreement with the provider covers your buyers' data;
- tell your team which AI clients they may connect to your projects.
What TixFin sees
TixFin receives only the tool calls your client makes and their arguments, for example "sales of event X in March". It never sees your messages to the client or the model's replies. TixFin keeps no copy of the answers it sends: every answer is read live and passed on. Of a proposal it stores only a random number and its expiry, to apply it once; the proposal itself travels sealed inside its handle.
How a connection is held to you
- Your permissions, no more. Every tool call runs as you, with your role in the project, as if you clicked in the dashboard. A tool your role may not use is refused.
- Only what you allowed. The connection carries the permissions and projects you ticked on the consent page. A project you did not tick is refused, even if you are a member there.
- Only for TixFin's MCP server. The client's tokens are issued for TixFin's MCP server alone. Another service cannot use them, and the client cannot use them to call the TixFin API directly.
- Changes only by proposal. No tool changes anything directly. Each change is a proposal that applies once, and anything that moves money, lowers what buyers pay, issues or admits tickets, or reaches your buyers also needs a second factor confirmed on the connection in the last ten minutes.
- A fresh sign-in to approve. You approve a client only after signing in or confirming your second factor within the last 15 minutes.
The project's AI access setting
Owners and admins of a project, and roles allowed to update it, find AI access under Project settings. Its switch Let AI clients see buyers' personal data is off by default. Switching it on needs a second factor confirmed in the last ten minutes; switching it off does not. Every change is recorded with the member who made it.
No AI client can read or change this setting, not even with every permission.
Personal data reaches an AI client only when all three hold:
- the member who connected it allowed See buyers' personal data on the consent page;
- the project's switch is on;
- that member belongs to the project.
Otherwise TixFin refuses the tools that answer with personal data in that project, and masks personal fields in every other answer from it. A client connected to several projects sees personal data only in those where the switch is on.
Switching it off reaches a connected client within about a minute. Switching it on reaches it within at most ten minutes, when the client next renews its access. If TixFin cannot check the setting at that moment, the client's calls fail until it can; it never shares personal data on a guess.
Switch it on only if your privacy notice and your agreements with buyers cover passing their data to AI providers.
What is masked
Unless personal data is allowed for the project, as above:
- tools marked as personal data in the tool reference, such as orders, attendance, guest lists, campaign recipients, reports and the project's details, are refused, and so are proposals that change such data;
- in every other answer, in event summaries, proposal previews and the report after a proposal is applied, TixFin
replaces with
[masked]:- contact details: e-mail addresses, phone, mobile and fax numbers, by field name and also wherever an e-mail address or phone number appears, inside free text such as notes included;
- names: first, last, display, legal, nick and user names, and names and lists of names under fields for people such as buyers, holders, attendees, customers, guests, contacts, recipients, members, owners, staff, artists or speakers;
- addresses and locators: address lines, streets, cities, ZIP and postal codes, licence plates, IP addresses and browser user agents;
- birth dates, bank details and VAT and tax numbers;
- numbers under such fields, for example a phone number stored as a number.
IDs are kept, including those that point to a person (a user, patron or ticket ID), so tools can look things up.
Masking works by field names and patterns, so it cannot catch everything. A person's details under a field name none of
these rules covers reach the client unmasked, and so does a phone number written without a leading + or 0, or one
that looks like an order or ticket number. For the operations that answer with personal data by design, the refusal
above is the safeguard, not the masking.
Tokens
Your AI client holds two tokens: a short-lived access token and a refresh token it uses to get a new one. Each refresh token works once. If one is used a second time, for example because someone copied it from your computer, TixFin treats the connection as stolen and ends it at once: the client disappears from Account → Security → Sessions and you have to approve it again.
Revoking the client under Devices ends the connection at once. Signing out everywhere ends it too.
What is logged
- The grant: which client you approved, when, with which permissions and for which projects. The client is listed under Devices with its last activity until you revoke it.
- Refusals: a tool call TixFin refuses (a project or permission the connection lacks, a revoked connection) is logged with the client, the operation and the reason, for security.
- A reused refresh token is logged as such when TixFin ends the connection.
Reading through an AI client does not add entries to the audit log. A change made through an AI client is recorded as yours, with the client's ID beside it, wherever the same change made in the dashboard is recorded.
Buyers' words are data
Order notes, names and other text your buyers wrote reach the client marked as buyers' words. A buyer cannot make your AI client act by writing instructions into an order: no tool changes anything without a proposal, so an instruction hidden in a buyer's text can at most lead to a proposal you see. Read proposals before you confirm them, especially after the client has read buyers' messages.