Privacy Policy

The bot may use stored data, as defined below, for different features including but not limited to:

• Command handling
• Providing server and user preferences

The bot may share non-sensitive data with 3rd party sites or services, including but not limited to:

• Aggregate/statistical data (ex: total number of server or users)
• Discord generated IDs needed to tie 3rd party data to Discord or user-provided data

Personally identifiable (other than IDs) or sensitive information will not be shared with 3rd party sites or services.

Apart from Cloudflare Web Analytics, which our CDN uses to count page views and measure load times (see Website Analytics below), the website's help assistant is the one exception, and only when you choose to use it: a question you type there is sent to Anthropic's Claude API together with the conversation so far and, when asked from a server's dashboard, that server's Birthday Bot settings (its chosen channel, role, and event names, and any permission problems), or, when asked from your settings page, your own birthday, time zone, and privacy settings, with the names of the servers where you set an exception. Your Discord ID and server IDs are not included. Anthropic does not use that data to train its models and deletes it within 30 days, except when its safety systems flag a conversation as violating its usage policy (it may then keep that conversation for up to two years) or the law requires it to keep it longer. Birthday Bot keeps the conversation for 30 days to improve the help articles, linked to your Discord account only when you were signed in where you asked and to the server only when you asked from its dashboard, then deletes it.

The bot's data may be updated when using specific commands.

Updating data can require the input of an end user, and data that can be seen as sensitive, such as content of a message, may need to be stored when using certain commands.

The bot may keep stored data in an internal caching mechanic for a certain amount of time. After this time period, the cached information will be dropped and only be re-added when required.

Data may be dropped from cache pre-maturely through actions such as removing the bot from the server.

When a page on this site fails in your browser (a script error, a page that cannot render, or a part of the site that cannot load after an update), the page sends us a short report so we can find and fix the problem: the kind of failure, the error's message and where in our code it happened, the page's path with any server and user IDs removed, the version of the site you were using, your browser's user agent string, and whether your browser had translated the page. Reports are not designed to include anything you typed, and never include your Discord account, the servers you manage, or your IP address; no cookie is set and nothing is stored in your browser. Reports are kept for fifteen days.

To learn which websites and listings bring new servers to Birthday Bot, invite links on this site and on third-party bot directories point at this website before continuing to Discord. When you follow one, we record the link's source, the time, the referring site's host name (when your browser sends it), and, if you complete the install, the server the bot was added to and the permissions granted. No IP address is stored.

While you are on this site, the page keeps in memory how you arrived: any campaign tags in the address, the referring site's host name, the page you landed on, and the time. When you follow an invite link from this site, that information travels with the link so the install can be credited to where you heard about Birthday Bot. Nothing is stored in your browser for this: no cookie, and nothing survives closing the page.

Invite clicks that never complete an install, or that are cancelled on Discord's authorization screen, are deleted after 90 days. For a completed install we keep the server's Discord ID, when the bot was added and removed, its member count at the time, and which link brought it. During the server's first 30 days after the install, we also record when it first used a command or one of the bot's buttons and when it finished setup, whether the server was already set up when the bot joined, whether the welcome message reached the server and its owner, how often and when the vote or Premium requirement, or a free-plan limit, was reached and the last command that reached each, and how often and when Premium buttons in the bot's messages were clicked; these facts are kept with the install record. We use this to see where servers come from and whether they stay; no member identities are stored for it.

When the bot or this site gives out a Premium checkout link, we record the server's Discord ID, which button or page produced the link, and when; a record that does not lead to a subscription is deleted after 30 days, and one that does is kept, marked with when the subscription was first seen as active.

Links from this site and from the bot to places we do not run (the support server, the vote page, the timezone finder, Movie Club) work the same way: they pass through this website on the way to their destination. When you follow one, we record which destination it was, where the link was printed (this site, the dashboard, the Help Center, or the bot's messages), the time, the referring site's host name (when your browser sends it), and the same in-memory arrival information described above. When you follow any other link on this site that leaves it, the page sends us the destination's host name, the page you were on, and that arrival information. No IP address is stored, no cookie is set, and nothing is stored in your browser; these records are deleted after 90 days.

When someone votes for Birthday Bot on top.gg, we record which of our links led to the vote page (for example the vote prompt in the bot, or this website), or the short tag on the link if it carried one, and whether top.gg counted it as a weekend vote; the vote link passes that tag to top.gg, which returns it with the vote it already reports to us. We do not record who followed the link beyond that vote.

This site uses two analytics tools, and neither sets a cookie. Cloudflare Web Analytics, added by our CDN, counts page views and measures how fast pages load. Our own analytics (Umami, running on our server) records, for each page you view: when you viewed it, the page's path with server and message IDs removed, any campaign tags in the address (nothing else from it), the referring site's origin (never the page you came from, and only when your browser sends it), the page title, your country, region and city as estimated from your IP address, your browser, operating system, device type, screen size and language, and how long the page took to load and respond (timings only).

It also records a few actions: following an invite link (and the link's source), following a link that leaves this site (and the destination's host name), starting to sign in, how the dashboard's welcome tour ended (finished or closed early, and the stop it ended on), and asking the help assistant a question (and where you asked, never the question).

Page views are grouped into visits using a hash of your IP address and your browser's user agent string, combined with a secret value that changes every month; your IP address itself is not stored. These analytics store nothing in your browser. The analytics never see your Discord account or which servers you manage. These records have no set deletion date.

Manual removal of the data can be requested through the official support server. Discord IDs such as user, guild, role, etc. may be stored even after the removal of other data in order to properly identify Birthday Bot specific statistics since those IDs are public and non-sensitive.

For security reasons we will ask you to provide us with proof of ownership to the data you wish to be removed. Only a server owner may request manual removal of server data.