Sheriffly

Sheriffly is a Discord bot and this website, sheriffly.com. This page explains, in plain words, what we keep, why we keep it, and how to get it removed.

The short version: we only keep what Sheriffly needs to work in your server. We don't sell it, we don't show ads, and we don't read your ordinary chat messages.

01What we store

Depending on which features a server turns on, Sheriffly stores:

  • Server settings. The channels, roles and people chosen in /setup or the dashboard, and text you write for Sheriffly (embeds, ticket questions, application forms, custom messages). Discord IDs are numbers that point to a server, channel, role or user.
  • Moderation records. For each warning, timeout, kick or ban: the member, the moderator, the reason and the time. For quarantined members, and for staff stopped by excessive-moderation limits, the roles to give back later.
  • Reports. When someone uses Report Message: the reported message's text, who wrote it, who reported it and why.
  • Tickets and applications. Who opened, claimed and closed a ticket and their form answers; application answers, the decision and who made it. Ticket transcripts are posted in Discord, not kept by us.
  • Shifts. When a shift started and ended and the time counted, plus the Roblox user ID used to check you were in-game.
  • ER:LC. Your private server's API key, stored encrypted, plus the server's name. When staff run :ban or :kick in-game, we keep an ER:LC case: the player's name, the staff member's Roblox name and ID, the reason and the time.
  • Log history. A copy of each log Sheriffly posts (and a summary of in-game logs), so server managers can search them on the dashboard. Log history is deleted after 30 days, and straight away when Sheriffly is removed from the server.
  • Social Alerts. The creators you follow (their handle, name and profile picture link) and which uploads and streams were already announced.
  • Voice rooms. Who owns each temporary room while it exists.
  • Suggestions. Ideas sent with /suggest, your user ID and the server you sent it from.
  • Roblox verification (when it's available). Your Roblox user ID, username and display name. You sign in on roblox.com: we never see your Roblox password, and the sign-in token is used once and thrown away.
  • Dashboard sign-in. When you log in with Discord: your user ID, username, avatar and the list of servers you're in, so we can show the ones you manage. We ask Discord for nothing else. We never get your password or email address. Your session ends when you log out or after a few days.

02Account Standing

Account Standing shows how risky a member looks, based on moderation across servers. It's off until a server's owner or Bot Managers turn on sharing, and a server only sees other people's standing while it shares its own.

  • What's shared. For each warning, timeout, kick, ban or quarantine in a sharing server: the member's user ID, the type of action, when it happened and whether a reason was given. We also note facts used to decide if it counts, such as how old the server was, how many members it had, how long the member had been there and how many actions the moderator took around then.
  • What isn't. Other servers never see the reason text, any messages, or which server took the action. Only staff of sharing servers can look someone up.
  • Your own standing. Anyone can see their own with /standing check, including the servers involved.
  • Appeals. A server can remove its own case from standing at any time. You can also ask the Sheriffly team in our support server to review your standing. When a server stops sharing, its actions stop counting straight away.

03What we don't collect

  • We don't read or store ordinary chat messages. The only message text we keep is a message someone reports.
  • We don't record voice.
  • We don't collect passwords, email addresses or payment details.
  • The website doesn't use advertising or tracking cookies. The dashboard uses one cookie to keep you signed in.

04How we use it

Only to run Sheriffly's features in the servers that use it: logging, moderation, tickets, alerts and so on. We don't sell or rent your information, and we don't use it for advertising.

To work, Sheriffly talks to a few other services, and only sends them what that feature needs:

  • Discord, to run the bot and the dashboard sign-in.
  • Police Roleplay Community (PRC), using your ER:LC API key, to read your private server and run the commands you ask for.
  • Roblox, for verification sign-in when it's available.
  • YouTube, Twitch and TikTok: Sheriffly reads the public pages of the creators you follow to see if they posted or went live. It doesn't send them anything about you.

05Where it's kept, and for how long

Everything is stored on Sheriffly's own server, not with a third-party database company.

  • While Sheriffly is in your server, its settings and records are kept so the features keep working.
  • Log history is kept for 30 days at most.
  • When Sheriffly is removed, your ER:LC API key and log history are deleted straight away. Other settings are kept in case you add Sheriffly back. Ask us and we'll delete them.
  • Sign-in attempts and dashboard sessions expire on their own.

06Your choices

  • Server owners can turn features off in /setup or the dashboard, or remove Sheriffly from the server at any time.
  • Anyone can ask us to see or delete the information we hold about them. Message us in our support server.
  • Roblox links can be removed with /unlink when verification is available.

07Children

Discord requires users to be at least 13 (or older where local law says so). Sheriffly follows the same rule and isn't meant for anyone younger.

08Changes and contact

If we change this policy we'll update this page and the date at the top. Questions? Ask us in our support server.