Privacy policy
Effective 12 November 2026
Ticketslayer Copilot is a helpdesk for businesses: shared email inboxes, live chat, calls, a knowledge base and an AI assistant that sorts tickets and drafts replies. This policy explains what Ticketslayer Copilot ("we", "us") collects, why, and the choices you have.
Who this policy covers
- Team members: people who have an account in a workspace.
- End customers: people who write to a business that uses Ticketslayer Copilot. For their messages the business is the controller and we process the data on its behalf. If you are an end customer, contact that business first; we will help it answer you.
- Visitors to ticketslayercopilot.com.
What we collect
- Account details: name, email address, a hashed password, two-factor and passkey settings, and sign-in history.
- Workspace content: tickets, messages, attachments, contacts, notes, knowledge base articles, settings and the records your team creates.
- Connected accounts: when you connect a mailbox or another product, the content needed to run that connection (see "Google user data" below) and the access tokens the provider issues.
- Technical data: IP address, browser and device type, and logs of requests and errors. Logs do not include message bodies, passwords or tokens.
- Cookies: only the cookies needed to keep you signed in and to protect sign-in. The landing page sets none.
How we use it
- To provide the service: receive, show, sort and send your team's support conversations.
- To run the AI features your workspace turns on, such as triage, summaries and suggested replies.
- To keep accounts secure, prevent abuse and fix faults.
- To send service email: sign-in and security notices, invitations and reports you asked for.
We do not sell personal data and we do not use it for advertising.
Google user data
When a team member connects a Google account, Ticketslayer Copilot asks Google for these permissions and uses them only as described.
- Gmail (read, modify and send): to read incoming mail in the connected mailbox so it becomes tickets, to send your team's replies from that address, to read the send-as addresses and signature set on the mailbox, and to label and mark messages it has handled.
- Email address: to show which account is connected and to match it to the mailbox.
- Google Sheets and Drive files you pick: only the files a team member chooses in Google's file picker, to read or write the rows an integration needs.
Storage. Messages become tickets in your workspace and are stored on our hosting provider's servers. Google access and refresh tokens are encrypted at rest.
Sharing. Google user data is shared only with the service providers that run Ticketslayer Copilot for us (hosting, file storage and, when your workspace uses AI features, the AI model provider that produces the draft or summary), and only to provide the features you see. It is never sold, never used for advertising, and never used to develop, improve or train generalised AI or machine learning models.
People. Our staff do not read your mail unless you ask us to for support, it is needed for security or to comply with the law, or the data has been aggregated and anonymised for internal operations.
Removal. Disconnecting the mailbox in Settings stops access at once and deletes the stored tokens. You can also remove access in your Google Account under "Third-party apps and services". Deleting the workspace deletes its tickets and messages.
Ticketslayer Copilot's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Who processes data for us
We use providers for cloud hosting and databases, file storage, sending service email, and AI models. They act on our instructions and may process data outside your country. We share personal data with others only when the law requires it or to protect the service and its users.
Security
Data is encrypted in transit. Passwords are hashed with Argon2id. Mailbox credentials, access tokens and two-factor secrets are encrypted at rest. Access inside a workspace follows the roles its admins set.
Retention and deletion
We keep workspace data while the workspace exists. A team member can delete their account and an owner can delete the workspace; the data is removed, not hidden.
Your rights
Depending on where you live, you may ask to access, correct, export or delete your personal data, or object to how it is used. Write to support@ticketslayercopilot.com. If your data sits in a business's workspace, we will pass the request to that business.
Children
Ticketslayer Copilot is a tool for businesses and is not directed at children under 16.
Changes
If this policy changes in a way that matters, we will tell workspace owners by email or in the app before it takes effect, and update the date above.
Contact
Ticketslayer Copilot · support@ticketslayercopilot.com