When you log in with Discord, the consent screen lists a few permissions. Here's exactly what each one does and why we use it - nothing here is used for anything shady.

identify

Lets us see your Discord username, avatar, and user ID. This is how the site knows who you are so it can show your dashboard, your profile, and your name instead of just "logged in".

guilds

Lets us see a list of servers you're in. We only use this to check whether you're in the Fairview Roleplay server - we don't read, store, or do anything with the rest of your server list beyond that check.

guilds.members.read

Lets us read your roles and nickname inside the Fairview Roleplay server specifically. This is how the dashboard knows your staff rank, whether you're verified, and what you have access to.

guilds.join

Lets our bot add your Discord account directly into a server - so clicking "Join Discord" anywhere on the site drops you straight in, instead of sending you to a regular invite link you'd have to click through separately. This is also how the "Join Server" button works on department pages, dropping you straight into that department's Discord server the same way. We also use it to automatically bring you back into the main server if a ban on your account gets lifted, so you don't have to track down a new invite yourself.

This scope only lets us add you to Fairview Roleplay's own servers - the main server and our department servers. It cannot be used to add you to any other server, read your messages, change your account settings, or do anything outside of that single action.

What we don't do

• We never post messages, send friend requests, or take any action as you.
• We never read your DMs or messages in other servers.
• We never sell or share this data with anyone outside the Fairview Roleplay team.

You're always in control - you can revoke access at any time from Discord's own User Settings → Authorized Apps (or Connections → Authorized Apps on mobile). Doing so also logs you out of the website automatically, so there's never a stale login sitting around after you've revoked access.

For the full breakdown of what we store and for how long, see our Privacy Policy and Cookie Policy.