This Privacy Policy describes how National Bus Community (“we”, “us”) collects and uses information when you use the NBC BusBot Discord bot and the related website at https://nationalbuscommunity.co.uk.
About NBC BusBot
NBC BusBot is run by the National Bus Community (NBC). It is built for the NBC Discord server, and other Discord servers may also add it.
Available in any server
These commands work in any server that has added the bot. Some also work in DMs with the bot, or anywhere once you add the app to your own Discord account (a user install):
- Bus vehicle, stop, and timetable lookups via bustimes.org (also available as a user install)
/depot-reminderand/vehicle-reminder: DM alerts for the operators or vehicles you choose/transittracker-log: a user’s TransitTracker log. Only public TransitTracker profiles with a linked Discord account can be shown./transittracker-all-time-map: a user’s TransitTracker all-time map. This is a TransitTracker Pro feature, so it is only available for Pro subscribers with a public profile and a linked Discord account./transittracker-league: a TransitTracker leaderboard of the members of the server it is run in. Only members with a public TransitTracker profile appear.
NBC server only
These features only run in the National Bus Community server and are not available in other servers:
- NBClock (the daily midnight message role and leaderboard)
- Support tickets
- Staff moderation
- Quote images
- TransitTracker Pro role sync: the NBC role for members who subscribe to TransitTracker Pro. “Pro” always refers to the TransitTracker subscription.
Information we collect
From every server the bot is in:
- Discord account data: user IDs, usernames/tags, and avatars when you use bot commands or log into the admin dashboard.
- Server 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.
- 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).
- 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. Who added the bot to a server may be taken from that server’s audit log where the bot has permission to read it.
- 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.
When you use the related features:
- Depot reminder subscriptions: your user ID and chosen operator codes.
- Vehicle reminder subscriptions: your user ID and chosen vehicle identifiers.
- TransitTracker lookups: TransitTracker results (such as usernames, ranks, and logged services) are held temporarily to avoid repeat requests.
In the NBC server only:
- NBClock data: midnight message timing for participants in the NBClock channel (wins, offsets, and related stats).
- Support tickets: ticket content, participants, staff notes, ratings, and transcripts.
- Moderation records: warnings, timeouts, bans, and related case data.
- Quote votes: message and user IDs when you vote on quote images.
Information shared with TransitTracker
TransitTracker features work by sending Discord user IDs to TransitTracker:
/transittracker-logand/transittracker-all-time-mapsend the Discord ID of the user being looked up./transittracker-leaguesends the Discord IDs of that server’s members (excluding bots) to find which have linked TransitTracker accounts.- Pro role sync sends the Discord IDs of NBC server members to check their TransitTracker Pro status.
TransitTracker only returns information for profiles that are public, and Pro status for linked accounts. Your TransitTracker privacy settings are managed on TransitTracker.
How we use information
To operate the bot, provide transit information, send depot-change and vehicle trip/board alerts, run NBC server features (NBClock, support tickets, moderation, quote images, and TransitTracker Pro role sync), 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. Server 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.
Cookies
The website sets a single session cookie, and only when an administrator logs into the dashboard. It expires after 7 days. We do not use analytics or advertising cookies.
Third parties
The bot queries third-party services to provide features: Discord, bustimes.org, TransitTracker, Flickr (vehicle photos), CARTO (map backgrounds for all-time map images), and Network Rail Open Data. 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]