TICKETGENIUS / LEGAL
Privacy
An overview of the information involved in running TicketGenius and supporting your community.
Draft prepared 22 October 2026
1. Who is responsible
The operator’s full legal identity, postal address, and applicable privacy contact must be confirmed in the final notice. Server operators determine how their communities use support tickets; TicketGenius’s controller and processor responsibilities must be documented for each processing activity.
2. Information the service processes
Depending on the features you use, the application processes Discord account identifiers and profile details, server identifiers and permissions, administrative settings, ticket messages and associated metadata, knowledge entries, model configuration, and training status. Paid subscriptions also involve subscription identifiers and billing status. The final notice must confirm the complete data inventory, including hosting logs and attachments.
3. Why information is processed
Information is used to authenticate users, check server access, manage support conversations, retrieve knowledge, generate AI-assisted replies, and administer subscriptions. The operator must confirm and disclose the legal basis for each purpose, including any contractual necessity, legal obligations, legitimate interests, or consent that applies.
4. Connected providers and recipients
The application integrates with Discord for authentication and support delivery, OpenAI for AI features when configured, and Stripe for paid billing when configured. Relevant messages and knowledge may be sent to the configured AI provider to generate answers and search representations. Hosting, database providers, recipients, provider contracts, processing regions, and any international-transfer safeguards must be verified for the deployed service.
5. Cookies and authentication
The application uses a session cookie to keep authenticated dashboard users signed in and checks server-side sessions for access. Any additional cookies or tracking used by the deployed hosting and connected services must be audited and disclosed before final publication, including cookie lifetimes and any consent requirements.
6. Retention and deletion
Ticket content, knowledge, account records, and billing data have different operational purposes. The final policy must give verified retention periods or criteria for each category, including backups and provider copies, and explain how deletion requests are implemented. This draft does not promise an automatic deletion schedule.
7. Access and security
The application checks account and server permissions to control access to support data. Server administrators should limit access to authorised team members and avoid placing unnecessary sensitive information in tickets or knowledge entries. The final notice must reflect the security measures and incident processes actually used in production.
8. Your privacy rights
Depending on applicable law, you may have rights to access, correct, erase, restrict, object to, or receive a portable copy of your personal data, and to withdraw consent where processing relies on consent. You may also have the right to complain to a competent data-protection authority. Contact us about account data; for a community’s ticket content, its server operator may also need to handle your request.
9. AI and automated processing
AI features process selected knowledge and conversation content to assist with support replies. The final notice must explain the deployed provider’s data handling, any use for provider training, and whether any automated decisions with legal or similarly significant effects occur. Do not assume that this draft establishes provider training or retention commitments.
10. Updates to this notice
This draft will need to be updated when the operator identity and production data-processing arrangements are confirmed. The final notice should state its effective date and explain how material changes are communicated.
Contact
For questions about TicketGenius or this draft, email hello@ticketgenius.ai.