Guide · September 1, 2026 · 3 min read
Birthdays, without a file of birth dates
It is a small feature, and one of the best liked. It calls for two precautions: not collecting more than needed, and landing at the server's local time rather than at midnight UTC.
Contents
What to ask for, and what not to
Wishing somebody a happy birthday needs a day and a month. The year serves no purpose, and collecting it changes the nature of the information: the day and month are harmless, a full date of birth is personal data that identifies somebody and doubles as the answer to security questions all over the place.
The principle is simple: only ask for the day and the month. That is enough for the feature, and it saves you from hosting a file of birth dates you have no use for.
Second precaution: signing up must stay voluntary. Some members would rather not be put in the spotlight that day, for reasons that are none of your business. A member must be able to remove their date as easily as they added it.
The time of the announcement
This is the detail that decides whether the feature feels polished or slapdash. A bot announcing at midnight UTC wishes happy birthday at two in the morning in summertime France, when the channel is empty — and at eleven the previous evening for others.
The announcement must follow the server's time zone, set once and for all. A morning hour works well: early enough for the message to be there when people wake up, late enough not to be lost in the emptiness of the night.
Three settings, and that is all
- The channel — the general one, not a dedicated channel: an announcement nobody reads is pointless.
- The time — in the server's zone. 9 or 10 a.m.
- The role for the day — optional, granted in the morning and removed the next day.
The ephemeral role
Giving a colour role for the day is what turns a line of text into a small event: the username changes colour in the member list, and people notice even if they missed the announcement.
Two conditions for it to work. The role must be high in the list, otherwise its colour is masked by a role above it and the effect disappears. And it must be removed automatically the next day: a birthday role worn by fifteen people all year means nothing any more.
The case of servers over a thousand members
Past a certain number of sign-ups, there is a birthday almost every day, sometimes several. The announcement becomes routine, and stops being read.
Two adjustments help. Group the day's birthdays into a single message rather than one per person. And reserve the announcement for a role — active members, or those who reached a tier — rather than opening sign-up to everybody. The second point is debatable; better to own it explicitly than to let the feature die out on its own.
What it can teach you about the community
Declared birth months give, at scale, an idea of a community's age brackets — useful for knowing who you are addressing. Two reservations: the information is only usable in aggregate, and it must never make it possible to trace an individual. In other words, it is a server statistic, not a per-member record.
Frequently asked questions
Should the year be asked for?
No. It is needed by no part of the feature, and collecting it turns harmless data into sensitive personal data.
What happens on 29 February?
In non-leap years, the announcement takes place on the 28th. That is the expected behaviour: announcing nothing three years out of four would be the worst option.
Can a member change their date?
Yes, as often as they like, and remove it entirely. A member who leaves the server has their date deleted along with the rest of their data.
Can the wish be sent privately rather than publicly?
It is possible, but the point disappears: what people like about this feature is that other members react. A private message from the bot mostly looks like an automatic notification.
Read next : Day-to-day activity, XP and levels, Welcome message.