Security Overview

1. Privileged Intents and Discord's Review

LFG Hub uses privileged gateway intents, which Discord grants only after a manual review of the bot, its use case and its policies. We completed that review and are approved for:

• Message Content — to convert what a member types in an LFG channel into a structured LFG post.
• Presence — so we can recommend relevant open groups to a member when they start playing a game.
• Server Members— to resolve group membership, pings and moderation actions against the server's actual member list.

These intents are revocable. Misuse of them results in Discord withdrawing access, which would render LFG Hub inoperable. We are also bound by Discord's Developer Policy on top of our own Privacy Policy.

2. What we store

• Discord user IDs, display names and server nicknames
• Which games members play, and when they started or stopped playing
• Preferences members give us themselves — region, platform, language, age range — all editable by them
• LFG activity: who created or joined which group, in which server and channel
• What a member typed in one of your LFG channels, reduced to the options we extract from it plus a short sanitized note

To be explicit about the last point: we do read messages in your LFG channels. This is the purpose of the Message Content intent, and it is what allows a member to post normally rather than use a command. What is retained is the resulting post rather than a transcript: mentions, links and formatting are stripped, the extracted note is truncated to a fixed length, and the original message is removed from the channel once the post is created. No other channel on your server is accessed.

What we do not store

• Email addresses. Discord does not provide them to bots, and we have no other means of obtaining them.
• Passwords or payment details. LFG Hub is free and has no accounts of its own.
• Voice audio. LFG Hub creates voice channels but does not join, listen to or record them.
• Conversations outside your LFG channels.General chat, staff channels, DMs between members — we neither read nor store any of it. Where a member submits a report, moderators of that server may generate a transcript of the reported group's own thread; it is delivered to that server's moderation channel and is not retained by us.
• Data from outside Discord. We do not purchase, enrich or supplement member data from third-party sources, and we do not track members across other sites.

We do not sell personal data, and we do not use it for advertising.

3. Retention and member control

• Presence and activity data is deleted after 30 days by an automated job. Discord's Developer Policy does not permit us to retain it longer.
• LFG channel messages are not archived.The note extracted from one is stored with that member's saved preferences until they change it.
• Members can opt out of activity tracking from the settings button in any LFG channel. All other functionality continues to work.
• Members can have their data erased on request via our support server or by email. Self-service deletion from the member portal is on the way.
• Aggregated statistics we show server owners cannot identify anyone.

4. How the infrastructure is secured

• No member-facing service accesses the data. LFG Hub is a bot rather than a web application. The bot is the only client of our database; there is no public site or API that members authenticate against, which materially limits the attack surface.
• Encrypted at rest, and in transit. Our database is a managed, provider-encrypted instance and connections to it run over TLS. We do not add application-level encryption because we deliberately do not store anything sensitive enough to need it.
• Hosted in the EU, under GDPR jurisdiction.
• Least-privilege access. Database access is restricted and credentials are held in managed secret storage, never in code or config files in a repository.
• Monitored. Errors and anomalies are tracked continuously, so issues are detected internally rather than reported by users.

LFG Hub is built by a small team of professional engineers with a background in cybersecurity. No system can be considered entirely secure; our approach is to limit the impact of any incident by not collecting data we do not need.

5. Permissions on your server

LFG Hub does not require Administrator permission. Setup requires more configuration without it, and we support that path deliberately: granting Administrator to any third-party bot on a large server is a level of access an LFG feature does not require.

You determine which channels are configured as LFG channels. The bot takes no action outside them.

6. GDPR

Our servers are in the EU and we operate in line with the GDPR. In practice that means data minimisation (we collect the least we can), purpose limitation (matchmaking only), a defined retention period (30 days for activity data), and working rights of access, correction, objection and erasure for every member.

No official GDPR certification mark exists for organisations to display, so this page does not carry one. The detail above, our Privacy Policy, and direct contact with our team are what we can offer in its place.

7. Reporting a vulnerability

If you have found a security issue in LFG Hub, contact a team member in our official support server. Security reports are prioritised above all other work, and we will not pursue action against anyone who reports an issue in good faith.

Administrators of large servers who would like to review this with an engineer before installing can request that in our support server.

• GDPR-aligned · EU-hosted
• Discord-approved intents
• Encrypted at rest
• 30-day data retention