Bdayblaze privacy policy

Privacy rules for a Discord birthday bot designed to stay scoped, private, and practical.

Bdayblaze stores birthday information per server membership, keeps admin tooling private by default, and avoids Message Content intent. This page summarizes what the bot stores, how it is used, and which controls members and admins have. For service rules, admin obligations, and availability limits, see the Terms of Service.

Last updated: April 4, 2026

Back to website Help and FAQ Terms of Service Markdown source

Server-scoped storage

Birthday records are stored for the current Discord server, not as a cross-server global profile.

Minimal collection

The core record is month, day, optional year, optional timezone override, and a visibility setting.

Private admin surfaces

Setup, Studio, previews, analytics, health, and import/export flows are private to the admin using them.

No Message Content intent

Bdayblaze does not rely on Message Content intent for the feature set described on this site.

What Bdayblaze stores

For birthday records, Bdayblaze stores the birthday month and day, an optional birth year, an optional timezone override, and a server-scoped visibility choice. If a server uses tracked member anniversaries, the bot may also store compact anniversary data needed for that feature.

The bot can also store server settings, Celebration Studio configuration, recurring event definitions, compact celebration history, Birthday Capsule wishes, surprise reward state, and lightweight analytics or scheduler state required to run the product.

What stays private

Birthday visibility is server-scoped, with private and server_visible modes.
Birth year is optional and hidden by default in normal member-facing browse flows.
Birthday Capsule wishes stay private until the target member's birthday window opens.
Admin setup, Studio, preview, analytics, health, import, and export flows stay private to the admin using them.

How quests, timeline, and surprises work

Birthday Quests can use wish progress, optional check-ins, and reactions on the shared birthday announcement post. Reaction quests store compact celebration-level totals tied to the announcement message, not per-reactor identity records.

Timeline history stores compact celebration metadata such as counts, quest completion, and reward state. Birthday Surprises remain compact reward records. Nitro concierge is manual admin follow-up only; Bdayblaze does not buy, gift, or deliver Nitro.

Logging, media validation, and safety

Bdayblaze is designed to avoid logging raw birth dates, raw birth years, raw wish text, raw blocked Studio content, or raw blocked media URLs in normal operational logs.

Media validation can make short outbound checks for admin-supplied image URLs so the bot can distinguish direct media from webpages, unsupported files, or unsafe links. The bot does not perform image-content moderation or vision scanning.

Servers can optionally enable a Studio safety audit channel. When enabled, it logs only minimal metadata such as actor, surface, field names, blocked category, and timestamp.

Imports, exports, and deletion

CSV import and export are scoped to the current server and remain private to admins. Export includes only the fields required for bot operation: user id, birthday month and day, optional birth year, timezone override, and visibility.

Members can delete their own birthday record with /birthday remove. Admins can remove records privately with /birthdayadmin member remove. Exported CSV files should be treated as personal data by the server administrators who request them.

What Bdayblaze does not do

It does not build a global birthday identity across servers.
It does not use Message Content intent for the release surface described here.
It does not store individual reactor identities for reaction quests.
It does not run an automated Nitro purchase, payment, or gifting workflow.
It does not include AI-generated birthday cakes or cards in this release surface.