Your data
Who holds what, and how to ask us about it.
Most of what TicketQuill touches belongs to the Discord server that installed it, not to us. That distinction decides who can answer a request, so it is the first thing on this page rather than a footnote.
Controller and processor
The server administrator controls the conversations.
They decide what is collected and why. We hold and transmit it on their instructions. For our own security, consent, and support records, we decide — and we answer for those directly.
- Ticket conversations and member-submitted form answers
- Controlled by: The Discord server administrator
TicketQuill is Processor — we hold and transmit it on the administrator’s instructions - Security and access logs, consent evidence, support correspondence, and minimal billing references
- Controlled by: TicketQuill
TicketQuill is Controller — we decide why and how this is processed
Subprocessors
Every provider that touches this, and why.
We use providers only where necessary and limit what each one receives. This list is updated when a new provider materially processes personal information, with notice and an opportunity to object under the DPA.
| Provider | Purpose | Location and role |
|---|---|---|
| Hetzner Online GmbH | Application and database hosting | Helsinki, Finland · hosting infrastructure |
| Porkbun LLC | Domain registration and email forwarding | United States · domain and mail infrastructure |
| Stripe, Inc. and affiliates | Payment processing, subscription management, fraud prevention, and tax calculation | United States and other locations · payment infrastructure |
Discord is not on this list. It is a platform provider and payment intermediary that independently decides its own processing under its own terms — calling it our subprocessor would misdescribe the relationship. There are no advertisers or data brokers, and the database is self-hosted rather than a separate managed service.
Making a request
Access, correction, deletion, and the rest.
Send it to privacy@ticketquill.com. Here is what happens next, including the parts people are not usually told until they are waiting.
- Send it
- Email privacy@ticketquill.com and say which Discord server it concerns. Rights may include access, correction, deletion, portability, restriction, objection, and withdrawal of consent where consent is the basis.
- We verify
- We confirm identity and authority before acting. A request that would expose one person’s data to another is refused, which is the point of the check rather than an obstacle to it.
- We route it
- Where a server administrator controls the data, we refer the request to them or help them answer it. We do not quietly act on their data without them.
- We respond
- Within 30 days. We may extend or decline only where the law allows, and we explain why when we are required to.
- You can appeal
- If you disagree with the outcome, reply and say so — appeals go to the same address and are reviewed again. In the EEA or UK you may also complain to your supervisory authority.
- Transcripts and attachments already stored in the customer’s own Discord are controlled by that server, not by us. We cannot erase a copy that lives there.
- Deletion can complete asynchronously as backups expire, within a maximum of 30 days.
- Billing, consent, and other legally required records are kept for their required period even after a deletion request.
The binding version is the Privacy Policy, and the processing relationship for customers is set out in the Data Processing Addendum.
What we do not do
Two commitments, stated plainly.
- We do not sell personal information
- Not to data brokers, not to advertisers, not for their own purposes — no sale, rental, or brokering. There are no advertising pixels on this site and no third-party analytics.
- We do not train AI models on private customer content
- Ticket conversations and form answers are not training data. Any future dataset would be limited to synthetic data, data we own, or data covered by a separate explicit opt-in and a legal and product review first.
Both are commitments in the Privacy Policy, which is the binding version.
Security reports
Found something? Tell us first.
Vulnerability reports go to the security address and are read before anything else in the queue.
TicketQuill accepts no caller-provided return address.