Privacy and your data
FiveUnity keeps what it needs to run your community and nothing more. This page is the plain-language version; the authoritative text is the privacy policy on fiveunity.com.
Delete everything: Dashboard → Core → Danger zone · In Discord: /factory-reset
#What the website collects about you
| What | Why we hold it |
|---|---|
| Your Discord identity (user id, username, avatar) and the list of servers you are in | To sign you in, and to re-check on every request that you still hold Administrator or Manage Server. |
| The settings you save | They are the same settings the bot reads, so the website and /setup are the same change. |
| Billing identifiers from Stripe: customer and subscription id, tier, status | To show your plan and keep it in sync. Card details stay with Stripe; FiveUnity never sees a card number. |
| A session cookie | Keeps you signed in. Sessions last 24 hours. |
| Aggregated page views | Reliability only. No advertising profiles, and nothing is sold. |
FiveUnity never asks Discord for your email address, for your messages, or for permission to act as you. Data is shared only with the services that make the product work: Discord, Stripe, and our hosting and analytics providers.
#What the bot stores for your server
Everything the bot stores is scoped to one Discord server:
- Your configuration: every setting from the dashboard and
/setup. - Tickets and their transcripts, queues, and applications.
- Moderation cases and ban evidence.
- Tebex purchase records, including the buyer's Discord id when your store collects one.
- Permission groups: which roles may use which commands.
- FiveM player statistics, only if you connect a FiveM server.
- Log events for Log Lookup, kept for 30 days by default. You can set retention anywhere from 1 to 365 days.
- Staff activity entries for the staff log finder, kept for 90 days by default (7 to 365), on Pro servers with recording switched on.
#How long records are kept
Most records stay until you delete them or remove the bot. A few are cleared automatically by a daily clean-up, because they stop being useful and would otherwise grow for ever:
| Record | Kept for |
|---|---|
| Log Lookup events | 30 days by default, adjustable from 1 to 365 |
| Staff log finder entries | 90 days by default, adjustable from 7 to 365 |
| Ticket transcript files and their links | 30 days |
| Finished giveaways, including the entrant list | 30 days after the draw. Winners are announced in the channel and stay in that message. |
| Staff duty logs and department shifts | 180 days. An open shift is never removed, however old it is. |
| Remembered roles for a member who left (sticky roles) | 180 days. Return sooner and your roles come back; return later and staff re-assign them. |
| Invite-event point transactions | 365 days. Point balances are never pruned, so a member's total stays right. |
| Stream metrics sessions (one per stream a creator did) | 90 days. The all-time stream count is a running total and is never pruned, so the dashboard's headline never falls. |
Moderation records (cases, warnings, ban evidence, staff ratings and sit logs) are not on a timer. They stay until you delete them or remove the bot, because a server's disciplinary history is exactly the thing you need to be able to look up years later.
#Secrets are write-only
The Tebex secret key and webhook URL, the FiveM bridge keys, the txAdmin password and the Gemini API key are write-only. Once saved, the dashboard only tells you whether one is set, never the value, to you or to anyone else with panel access.
FiveUnity encrypts them at rest, each tied to the server it was saved for, so a stored secret cannot be lifted and replayed elsewhere. To change one, type the new value over the old; to remove one, clear the field and save.
Keep your own copy of any key you may need again. Nobody can recover one from FiveUnity: if it is lost, generate a fresh key at the source.
#AI features, consent and redaction
The AI Assistant is off by default, needs the Pro plan, and runs on a Google Gemini key that you supply. Nothing goes to Google until an administrator turns a feature on.
Before you can enable anything that reads ticket or channel content, an administrator has to accept a notice at Dashboard → Support desk → AI Assistant → Data-use consent, or the same notice in Discord under /ai panel → Consent. It says plainly that content sent to Gemini on Google's free tier is used by Google to improve their products, and that ticket transcripts routinely contain member names, ban appeals and payment references. The acceptance is recorded with that administrator's Discord id and the date, and shown in the panel afterwards. Turning the feature on without it is refused.
When a feature runs, the message text from the relevant channel is sent to Google to produce the reply or summary. Redact personal data is on by default and replaces email addresses, IP addresses, API tokens and long digit runs (card numbers, phone numbers, order references) before anything leaves. Sheisty Development does not keep the model's input beyond the summary that comes back, and none of it is used to train models. Google's own handling is governed by the Gemini API terms.
See AI Assistant.
The dashboard Log Builder can use the same Gemini consent to group unusual log convar names. It sends convar names and section headings only; it does not send the pasted convar values or webhook tokens.
Plain-English log search (/logs find and Ask the logs) sends matching gameplay log entries to Gemini so it can
write the answer. Only entries that already matched the search are sent, at most 60 of them, each shortened to a single
line, and only from the channels you configured for Log Lookup. It is gated on the same consent, and without it the
search still runs as a plain keyword search with no data leaving the bot.
The staff log finder (/logs stafflogs) works the same way over the staff activity ledger: at most 50 matching entries, one line each, sent only when the same consent is accepted, otherwise a keyword search with nothing leaving the bot.
/ai ask sends the member's own question, and the staff tools send what the staff member typed plus, for /ai draft and /ai catchup, the recent messages of the channel they ran it in (redacted the same way, and only with consent). /ai guide and /ai write send no member content at all.
One deliberate difference: those log entries keep their in-game identifiers. Steam hexes, licences, character and stash ids, server ids and money amounts are not redacted, because they are the thing staff are searching for, and removing them would not make an answer vaguer, it would make it wrong. Email addresses, IP addresses and API tokens are still removed, exactly as they are for ticket text.
#Ticket transcripts
When a ticket closes, FiveUnity saves a transcript of the conversation and posts a View Online Transcript link to your ticket log channel. If DM transcripts is on under Dashboard → Support desk → Tickets, the same link is sent to the member who opened the ticket. The link is signed and stops working after 30 days.
#If the bot is removed from your server
Removing FiveUnity does not delete anything straight away. Your data is marked and enters a 3-day grace period:
- Re-invite the bot within those 3 days and everything is restored exactly as it was: settings, tickets, cases, the lot.
- After 3 days a daily clean-up job permanently deletes the server's data. That deletion cannot be undone.
A Discord outage does not start the clock; only an actual removal does.
A lapsed subscription is not a deletion. When a plan expires the bot stops acting, but every setting stays put until you renew. See Plans and billing.
#Delete everything now
Two routes, both irreversible:
- In Discord:
/factory-reset, which only the server owner can run. It asks you to confirm with a button first. - On the website: Dashboard → Core → Danger zone, open to the server owner or any Administrator. You have to type the server's name exactly to confirm, and a server can only be reset once every 10 minutes.
Both remove the server's configuration along with its tickets, queues, purchase records, ban evidence, player statistics and permission groups. Both offer an optional pass that also deletes the channels and categories FiveUnity was configured with. Leave that off unless you are sure those channels are not used for anything else.
#Revoking access
- Sign out at the top right of the dashboard ends your session. It does not remove the bot or change any settings.
- To disconnect FiveUnity from your Discord account entirely, revoke it in Discord under User Settings → Authorised Apps.
- To cancel billing, use Manage billing on the Billing page, which opens the Stripe customer portal.
#Contact
Questions about privacy, or a request about your data, go to support@fiveunity.com, or open a ticket in the FiveUnity Discord. Include the Discord server id you are asking about so we can find the right records. We aim to reply within 24 hours.
The full policy, including who the data controller is and how to complain, is at fiveunity.com/privacy.