← Back to Goldie
Privacy policy
Last updated: 9 October 2026.
Goldie is a Discord bot with a web dashboard. Goldie is run and managed by GoldenScripts, an individual developer
based in the United States, who hosts the bot, owns the Discord application and is responsible for the data
described here (the "data controller"). This policy describes what GoldenScripts stores when Goldie is in a
server, and when someone uses the dashboard.
The bot is built from modules. Server managers decide which modules are on in their server and how they are set
up; GoldenScripts does not configure servers. Every module is off until a server manager turns it on, and a module
only stores something in a server where it is on.
Contact: [email protected].
Where the data is kept
Everything is stored in one Postgres database on hardware owned and run by GoldenScripts in the United States,
which also runs the bot and the dashboard. No third-party hosting provider is used. The database is not reachable
from the internet. Nightly backups of it are kept on that same hardware for 14 days and are then deleted.
The bot, the dashboard, the database and the web server also write short technical logs, such as a server
adding the bot or a message that could not be delivered. These can include server names and IDs, channel IDs
and user IDs, but never message text, passwords or tokens, and visitors' IP addresses are not logged. The logs
stay on the same hardware and are not sent to any logging or error-tracking service. They are rotated, so each
part keeps only its most recent 30 MB of logs and older lines are deleted. The bot's and the dashboard's logs are
also kept in the database for 7 days so the bot's owner can read them, and are then deleted; they are not
included in backups.
If you are outside the United States, using Goldie means your data is processed and stored in the United States.
What the bot stores for every server
When someone adds Goldie to a server, Goldie may send them a short setup guide by direct message (or post it in
a server channel if the DM cannot be delivered). That message is not stored.
- The server's ID, when the bot joined, when it was removed (if it was), and an optional admin role ID.
- Which modules are turned on, and the settings a manager chose. Settings can include channel IDs, role IDs, message text, colors and durations.
- Per-channel on/off overrides.
- A log of configuration changes, made on the dashboard: the Discord user ID of who changed something, what changed, and when.
- Scheduled jobs, such as when a temporary ban should end or a giveaway should finish.
- Which plan the server is on (see "Paid plans" below), and, for servers that had more items than the Free plan allows when plans started, how many they had then.
- Daily aggregate counts of which bot commands and automatic features ran in that server (the server ID, a feature key, the day and how many times). No user IDs or message content. Only the bot owner sees these on the admin panel.
Paid plans
Goldie has a free plan and paid plans (Gold and Golden), sold through Discord. Discord is the payment
processor: you pay Discord, and Discord handles your payment details, billing, renewals, refunds and
cancellations under its own terms and privacy policy. GoldenScripts never sees your card or other payment details.
Discord tells the bot which subscriptions exist (Discord calls them "entitlements"). For each one the bot stores:
- Discord's ID for it, which plan it is for, and whether it is a test or has been refunded;
- the user ID of the subscriber, or the server ID for a subscription bought for a server;
- when it started and when it ends.
A subscriber picks the servers their plan covers on the dashboard (1 on Gold, up to 3 on Golden). The bot stores which servers they picked, their user ID and when.
What each module stores
Only when the module is on in that server. User IDs are Discord's numeric IDs; the bot does not store usernames or avatars.
- Moderation: numbered cases: the action (ban, kick, timeout, warning, purge, and similar), the user ID, the moderator's user ID, the reason, any duration, and when.
- Automod: when it warns, times out, kicks or bans a member, it records a moderation case as above. If the server uses escalating punishments, it also keeps a strike for each rule a member broke (the user ID, which rule, and when) until the strike expires (at most 365 days). To spot raids it remembers recent join times in memory only.
- Leveling: each member's XP, level and when they last earned XP, the reward role for each level, and any XP boosts the server set for roles or channels. Voice XP is counted from who is in a voice channel; only the XP is saved.
- Economy: each member's balance, when they last claimed daily and weekly rewards or last played a minigame, the items they own, the server's shop items, and a log of every balance change (amount, reason, who made it, and the other member in a payment).
- Self-roles: panels: title, description, role IDs, labels, and the channel and message where the panel was posted.
- Starboard: the IDs of a starred message, its channel and its starboard post, and the star count. Not the message text.
- Giveaways: the prize, host, channel, end time, any minimum level, and winners, and the user IDs of members who entered, with how many entries each one has.
- Polls: the question, options and author, and each vote (user ID and choice). In anonymous polls the vote is still stored so nobody can vote twice, but names are never shown.
- Reminders: the user ID, channel, reminder text, when it is due and how often it repeats.
- Tickets: the server's ticket panels, and for each ticket its number and channel, who opened, claimed and closed it, the close reason, and when. The transcript is posted as a file in the server's own channel and is not kept in the database.
- Custom commands: each trigger and response, any role it gives or takes, who created it, and how often it was used.
- Social alerts: the YouTube, Twitch or Bluesky accounts and the RSS feeds a server follows, the channel and role for the alert, and the alert message; plus, for each one, the latest posts or videos seen and whether it is live.
- Welcome: if a server manager uploads a background picture for welcome cards, the picture, who uploaded it and when. It stays until a manager replaces or removes it. The welcome card itself, with the new member's name and avatar, is drawn when they join and posted to Discord; it is not saved.
-
Logging: a history of the events it logged, so managers can search them on the dashboard: the
kind of event (for example a deleted message, a join or a role change), the channel ID, the member's user ID
and username, a short summary such as a message's length or a changed nickname, and when. It never includes
message text. The history is kept for 7 days on the Free plan, 90 days on Gold and 365 days on Golden, and is
then deleted.
-
Logging, deleted images (Gold and Golden, when the server has a message log channel): images
posted in channels the server logs are saved on the bot's own hardware for 7 days, so a deleted image can still be shown in
the server's log channel. Each saved image is deleted when it is posted to the log, or after 7 days, whichever
comes first. These images are not included in backups.
- Fun: nothing beyond its settings.
What the bot does not store
-
It does not keep a database of ordinary chat (apart from the deleted-image archive described above). Logging can post a deleted or edited message into a log channel in
the same server, Automod can quote a message it removed in the server's alert channel, and Starboard can repost a
starred message. To do this, the bot handles the message text in memory only long enough to make the post. Those
posts live in Discord; the bot does not save a copy.
-
Ticket transcripts contain the messages and names from the ticket. Once posted, the transcript file belongs to
that server and is controlled by its staff, not by GoldenScripts.
- It does not store member passwords, and it does not store anyone's Discord token except Goldie's own bot token.
- It does not sell data, and it does not use data for advertising.
Logging, Automod, Starboard, Tickets and Custom commands need Discord's Message Content intent to read message
text. Welcome and Logging need the Server Members intent to see joins, leaves and role changes. The bot does not
use the Presence intent.
The dashboard
- You log in with Discord. The bot asks Discord for two permissions:
identify (your user ID, name and avatar) and guilds (the servers you are in and your permissions there), so it can show the servers you are allowed to manage.
- Discord gives the dashboard an access token. That token lives only in an encrypted session cookie in your browser. It is never saved to the database, and it is never sent to the page's JavaScript. Logging out deletes the cookie; the token also stops working after about a week.
- The dashboard reads a server's channels and roles, your roles there, and the names of people in the configuration log, with the bot's own token, to show the settings and check your access. These are kept in memory for at most ten minutes, not saved.
- Changes you make on the dashboard are stored with the server's configuration, including the entry in the configuration log with your user ID.
- If you send a feature suggestion, it is emailed to GoldenScripts with your Discord name, username and user ID, and any photos you added. It is not saved in the database. If GoldenScripts stops someone from sending suggestions, their user ID, an optional reason and when it happened are stored until the ban is lifted.
- The dashboard only sets the session cookie needed to keep you logged in, and a
theme cookie that remembers the colour theme you picked (dark, light or a seasonal one) for a year. It sets no tracking or advertising cookies, and uses no analytics.
Why, and the legal basis
The bot stores this so it can do what a server manager configured: greet members, keep a moderation history,
track levels and balances, run giveaways, polls, tickets and reminders, post logs and alerts, hand out roles,
and finish jobs after a restart; and so it knows which plan each server is on.
Where data protection laws such as the GDPR or UK GDPR apply, GoldenScripts relies on:
- Legitimate interests: running the features a server manager turned on, keeping a server's moderation and configuration history, and keeping Goldie secure and working.
- Providing the service you asked for: logging you in to the dashboard, saving the changes you make there, and giving you the paid plan you bought.
- Legal obligations: if the law requires GoldenScripts to keep or hand over data.
Who else sees it
- Discord processes every message and event, under Discord's own privacy policy.
- Social alerts read public YouTube feeds, use the Twitch API, read Bluesky's public API, and fetch the RSS feeds a server added, for the accounts and feeds it follows. No member data is sent to them; the sites only see a request from the bot.
- Discord, for payments: paid plans are bought and managed through Discord, which processes the payment.
- Email: if you email GoldenScripts, your message is handled by Namecheap's Private Email service, which hosts the [email protected] inbox.
GoldenScripts does not give the data to anyone else, unless the law requires it.
How long it is kept
-
Data stays while Goldie is in the server, until a server manager deletes it (for example by resetting a
module's settings on the dashboard, or with
/custom delete, /roles panel delete or
/alerts remove; members can delete their own reminders with /remind delete), or until
GoldenScripts deletes it.
-
When Goldie is removed from a server, all of that server's data is deleted automatically 30 days later. If the bot
is added back within those 30 days, the data is kept.
-
When a member leaves a server, their data in that server (such as XP, level, balance, items and moderation cases)
is kept, so it is still there if they rejoin. It is deleted along with the server's data, or sooner if they ask.
-
Subscription records (entitlements) are billing records. They are kept even after the bot leaves a server or the
subscription ends, so GoldenScripts can answer billing questions; ask if you want yours removed. A Golden
subscriber's server picks are deleted when they change their picks, or with the rest of the server's data.
- Deleted data disappears from backups within 14 days.
Your rights and asking for deletion
You can ask GoldenScripts to:
- give you a copy of the data about you, in a common format;
- correct data that is wrong;
- delete data about you;
- stop or limit using data about you, or object to it being used.
GoldenScripts gives these rights to everyone, wherever they live.
- Server managers can turn modules off and reset a module's settings on the dashboard.
- Anyone can leave a server, which stops the bot acting on them there.
-
To make a request (for yourself, or for a whole server if you manage it), email
[email protected]. Include your user ID and, for a server, its ID.
To make sure a request really comes from you, GoldenScripts may ask you to confirm it through Discord before acting.
GoldenScripts will reply within 30 days. Some data, such as a server's moderation case about you, may be kept if
the server still needs it and that need outweighs your request; GoldenScripts will tell you if that happens.
If you are in the EU, the UK or another place with a data protection authority, you can also complain to that
authority.
Children
The bot is a tool for Discord servers. It is not directed at children under 13, or under the minimum age to use
Discord in their country if that is higher. If GoldenScripts learns it holds data about someone below that age,
it will delete it.
Changes
If this policy changes, the date at the top changes with it. Significant changes will also be announced where
Goldie's users can see them. Continued use of Goldie after that date means the updated policy applies.
Contact
Questions about this policy go to GoldenScripts at [email protected].