This Privacy Policy describes how National Bus Community (“we”, “us”) collects and uses information when you use the NBC BusBot Discord bot and related website at https://nationalbuscommunity.co.uk.
About NBC BusBot
NBC BusBot is the official Discord bot for the National Bus Community. It is built for the NBC Discord server. A wider public release is planned later.
Most features only run in the NBC Discord: NBClock (role assignment and daily tracking), support tickets, staff moderation, quote images, and TransitTracker PRO role sync. Outside the NBC server, those guild-only commands are blocked.
Some commands are registered globally and work in any server where the bot is present, or in DMs with the bot:
- Bus vehicle, stop, and timetable lookups via bustimes.org — these can also be added to your Discord account as a user-installed app, making them usable in DMs and other servers; command usage is recorded as described below wherever the commands run
/transittracker-league: TransitTracker leaderboard for the server you run it in/nbclock-leaderboard: NBC midnight win counts (uses NBC channel data; viewable from any server with the bot)- DM commands:
/depot-reminder,/vehicle-reminder,/transittracker-log, and/transittracker-all-time-map(TransitTracker commands require a public TT account with Discord linked)
Information we collect
- Discord account data: user IDs, usernames/tags, and avatars when you use bot commands or log into the admin dashboard.
- Guild data: server names, IDs, settings, channel and role structure, and the bot’s permissions in each server.
- Command usage: which commands were run, when, in which server/channel, and by whom (including denied attempts).
- Message metadata: when the bot observes messages in servers it is in, we record metadata such as timestamps, author IDs, channel IDs, attachment/embed counts, and reply/thread info. We do not store full message content by default.
- NBClock data: midnight message timing for NBC channel participants (wins, offsets, and related stats).
- Support tickets: ticket content, participants, staff notes, ratings, and transcripts when you use NBC ticket features.
- Moderation records: warnings, timeouts, bans, and related case data for NBC server moderation.
- Quote votes: message and user IDs when you vote on quote images in the NBC server.
- Depot reminder subscriptions: your user ID and chosen operator codes.
- Vehicle reminder subscriptions: your user ID and chosen vehicle identifiers.
- App installation records: when you add the bot to a server or authorize the app on your Discord account, we store your user ID, username/tag, authorization timestamp, and revocation when applicable. Guild install attribution may be obtained from server audit logs where permitted.
- Expanded message metadata (operational logging): attachment filenames/types/sizes, embed titles, reaction counts, edit/delete timestamps, display names, and thread/parent channel context. Full message content is not stored unless diagnostics capture is enabled (see below).
- Diagnostic logs: structured operational logs recording what the bot did and any errors — log level, a short description, the feature involved, related server/channel/user IDs, command names, and error details. These exist to diagnose faults and monitor reliability.
- Diagnostics content capture: bot administrators can temporarily enable deeper logging for a specific server to investigate a problem. While enabled for a server, truncated message text snippets (up to 300 characters, with credential-like values redacted) may be stored alongside message metadata from that server. This is off by default.
How we use information
To operate the bot, provide transit information, send depot-change and vehicle trip/board alerts, run NBClock features, handle NBC support tickets and moderation, render quote images, sync TransitTracker PRO roles, diagnose issues, and maintain an admin-only audit dashboard.
Retention
Command usage and message metadata are retained for approximately 90 days, then deleted automatically. Revoked app installation records are pruned on a similar schedule. Guild structure snapshots are kept while the bot remains in a server. Ticket transcripts, moderation cases, NBClock history, and reminder subscriptions are kept for as long as needed to provide those features.
Diagnostic logs are retained per server, typically for 30 days, and each server's logs are additionally capped by a storage budget — when either limit is reached, the oldest entries are deleted first. Administrators may set shorter (or, within limits, longer) retention for individual servers, and logging can be reduced or disabled per server; warnings and errors may be kept in preference to routine entries when limits apply.
Third parties
The bot queries third-party services (Discord, bustimes.org, TransitTracker, RealTimeTrains, Network Rail Open Data, and others as configured) to provide features. Those services have their own privacy policies.
Admin access
Collected operational data is accessible only to authorised bot administrators via a protected web dashboard.
Contact
Privacy questions: [email protected]