Privacy

We are a support tool for FiveM script developers. This describes what we hold and why. It is written to be read, not to be defensible.

What we store

Your account. Discord sign-in gives us your Discord user ID, username, avatar and email. The email is used for billing receipts and service notices. It is never a login factor and never sold.

Your organisation. Its name, the plan it is on, and the settings you configure.

Your bot token. Encrypted with AES-256-GCM before it is written, and stored in a table that holds nothing else. It is never returned by any API, never written to a log, and never displayed back to you — not even masked. If you lose it, regenerate it in the Discord developer portal.

Your scripts. The archives you upload, the documentation generated from them, and the search index built from that documentation. Archives are kept so documentation can be regenerated when we improve the generator, which is the only reason they are kept.

Support conversations. Messages in ticket channels your bot handles, the replies it gave, and the solutions distilled from resolved tickets. This is the product working: a ticket the AI cannot answer today is answered tomorrow because it read yesterday's.

What we do not store

We do not store payment card details. Checkout and billing run entirely inside Stripe; we hold a customer reference and a subscription status.

We do not read messages outside ticket channels. The bot's Discord permissions are the narrowest set that lets it work, and it does not request the members intent.

Who else sees it

Anthropic — the text of a support conversation, and the documentation relevant to it, are sent to Claude to produce a reply. Voyage AI — documentation text is sent to build the search index. Stripe — billing. Tebex — only if you turn on purchase verification: when a customer gives a transaction ID to open a ticket, we ask Tebex whether that payment is real and what it was for, and we keep the transaction ID, the Discord account that presented it, and what the payment covered, so the same person is not asked again. Our infrastructure provider — hosting.

Nothing is sold, and nothing is shared with anyone else.

Tenancy

Every customer's data is isolated at the database level by row-level security, not by application code remembering to filter. A query that forgets its tenant returns nothing rather than someone else's rows.

Deleting it

Email us and we will delete your organisation. Everything above goes with it, including uploaded archives and generated documentation, and your public documentation site stops resolving straight away. Backups age out within 30 days.

There is no self-serve delete button yet, and we would rather say so than point you at one that is not there. If you have simply stopped paying, nothing is deleted: your documentation site keeps serving for 30 days, and your data stays until you ask us to remove it.

Ask us anything at support@legacytickets.net.