Privacy Policy
Last updated: November 6, 2026
1. Introduction
TicketerBot is operated by Evolve Orbit FZC ("we", "us", "our"). This Privacy Policy explains how we collect, use, store, and protect your information when you use the TicketerBot Discord bot, web dashboard, and related services (collectively, the "Service").
This policy explains the service's data flows. Optional public-website advertising measurement requires a separate explicit marketing choice; using the Discord bot, signing in or continuing to browse does not grant that consent.
2. What Data We Collect
We collect the following categories of data:
- •Discord account information: Your Discord user ID, username, avatar, and email address (provided via Discord OAuth2 during login).
- •Server information: Discord server (guild) ID, name, icon, member count, and channel information for servers where TicketerBot is installed.
- •Message content: Messages sent within ticket channels, including text content, attachments, and embeds, for the purpose of providing support transcripts and the inbox feature. If a server owner separately enables TicketerBot's moderation rules, messages in that server may also be processed transiently to detect configured blocked terms, unsafe links, excessive mentions, or repeated-message spam.
- •Limited server-member data: Discord user IDs, display names, roles, and member join, leave, or role-update events when needed to identify ticket participants, enforce the support-team permissions configured by a server owner, and safely close or restrict tickets when a participant leaves.
- •Usage data: Interaction data such as tickets opened, closed, response times, and feature usage for analytics purposes.
- •Optional public-website marketing measurement: Only after you accept marketing measurement, Whop may process cookies, browser storage, advertising identifiers, IP address, public page and campaign information, and browser/device characteristics to derive a device fingerprint for advertising attribution. This is separate from Discord account, member, server, ticket, message and transcript data.
- •Payment information: If you subscribe to a paid plan, payment details are processed by Stripe. We do not store your full credit card number.
Scope of Discord message access: TicketerBot persistently stores message content only inside channels created or designated as support-ticket channels by the server owner. Outside ticket channels, content is processed only when that server's owner has explicitly enabled a moderation rule; this processing is transient and the message body is not stored. Message edit and deletion audit entries contain identifiers and one-way content hashes or lengths, not the message body.
Scope of Discord member access: TicketerBot does not build marketing profiles or scrape complete member lists. Member data is used only for ticket participation, server-configured staff permissions, and the join, leave, or role changes needed to operate the support workflow.
3. How We Use Your Data
We use your data to:
- •Provide, maintain, and improve the TicketerBot service
- •Authenticate your identity and manage your account
- •Display ticket messages in the web dashboard inbox
- •Generate analytics and performance reports
- •Process payments and manage subscriptions
- •Send service-related communications (e.g., billing receipts, critical updates)
We do not sell your data to third parties. We do not use Discord account, server, member, ticket, message or transcript data for advertising purposes, and we do not use Discord message content or other Discord API data to train machine-learning or artificial-intelligence models. Optional public-website advertising measurement uses only the separate consented website activity described here.
4. Data Storage & Security
Your data is stored securely on Supabase (PostgreSQL) with encryption at rest and in transit. All connections to our servers use TLS 1.2 or higher. Access to production databases is restricted to authorized personnel only.
We implement industry-standard security measures including parameterized queries, role-based access control, audit logging, and regular security reviews. However, no method of transmission or storage is 100% secure, and we cannot guarantee absolute security.
Ticket content is available only to the ticket participant, server members whom the server owner has authorized as support staff, and the minimum authorized TicketerBot personnel required to operate or secure the Service. Access checks are applied per Discord server so one server cannot access another server's tickets or member data.
When optional repeated-message protection is enabled, TicketerBot holds a user's recent message text in application memory for no more than 15 seconds to compare repeats. This transient cache is not written to the database and is discarded automatically.
5. Third-Party Services
We use the following third-party services:
- •Discord API: To authenticate users and interact with Discord servers.
- •Stripe: To process payments and manage subscriptions. Stripe's privacy policy applies to payment data.
- •Supabase: For database hosting and authentication services.
- •Vercel: For web application hosting and serverless functions.
- •Whop: Only after explicit marketing consent, for optional advertising attribution on selected public marketing, blog and policy pages. See Whop's Privacy Policy.
Whop is not enabled on dashboard, admin, onboarding, authentication, API or transcript routes, or on development and preview hosts. Form capture, link tracking, iframe tracking and URL-based identity collection are disabled. We do not send Whop Discord identities, guild/member information, ticket content, transcripts, account or payment details, or Discord bot activity.
Marketing measurement defaults off. Choose Decline or reopen Privacy choices on public pages to reject it or withdraw consent. Global Privacy Control and Do Not Track keep it off. We remember the marketing choice in first-party browser storage for up to 180 days; it does not affect essential account or Discord bot functions. Further browser-storage details appear in our Cookie Policy.
6. Data Retention & Deletion
We retain account and server configuration data while the relevant account or Discord server uses the Service. Ticket messages and transcripts are retained so authorized participants and support staff can review the support history, until the server owner requests their deletion or the data is no longer needed to provide the Service or meet legal, security, or billing obligations.
You may request deletion of your data at any time by contacting us at privacy@ticketerbot.com. Upon receiving a valid deletion request, we will remove or irreversibly anonymize the relevant personal data within 30 days, except where limited retention is legally required. Removing TicketerBot from a server immediately stops new collection for that server; an authorized server owner may request deletion of the server's existing ticket history using the same address.
7. Children's Privacy
TicketerBot is not intended for use by individuals under the age of 13 (or the minimum age required by Discord in your jurisdiction). We do not knowingly collect personal information from children. If you believe a child has provided us with personal data, please contact us immediately.
8. Your Rights
Depending on your jurisdiction, you may have the right to:
- •Access the personal data we hold about you
- •Request correction of inaccurate data
- •Request deletion of your data
- •Object to or restrict processing of your data
- •Data portability (receive your data in a structured format)
9. Changes to This Policy
We may update this Privacy Policy from time to time. We will notify you of significant changes by posting a notice on our website or through the Discord bot. Your continued use of the Service after changes are posted constitutes your acceptance of the updated policy.
10. Contact Us
If you have any questions about this Privacy Policy or our data practices, please contact us at:
Evolve Orbit FZC
Email: privacy@ticketerbot.com