Privacy policy, last updated 29th October 2025 (dd/mm/yy | 29/10/15). Any updates of these policies that apply to the public will be announced in our communications server with a dedicated ping to users who have chosen to be pinged for such actions etc.
This is managed by kablankooo and ObviouslyTiger.
Scopes
applications.commands | Without this scope, a Discord bot cannot have commands, so this is required for us to have as a bot.
bot | This scope makes the Discord bot a bot.
Permissions
Add Reactions | This permission allows ERSMS to react to content within your guild. ERSMS will be able to react with any reaction publicly available to all users on the platform of Discord or from the database of the ERSMS application. This permission is required when trying to tell a user that something has been completed (eg. with a checkmark) without trying to send embeds / content which may clutter channels over time.
Attach Files | This permission allows ERSMS to attach any file to your channel(s). File size restrictions are the same as any average non-nitro user on the Discord platform. ERSMS uses this permission when providing downloadable files, such as transcripts from tickets.
Ban Members | This permission allows the ERSMS application to ban users within your guild. This permission is dangerous to enable to random members and can be disabled if needed if you aren't using modules such as "sync ER:LC bans to Discord". ERSMS uses this permission if a guild manager decides to enable certain modules to carry out synchronization of bans between the Emergency Response : Liberty County private server that they manage over to the said guild.
Change Nickname | This allows the bot to change their own nickname. A very safe permission to enable within a Discord server. ERSMS may use this if specific modules such setting the bot's name to something similar to the guild's name automatically.
Embed Links | This permission allows ERSMS to provide links that also result in embedded content. This may be used when trying to show a user / member in a guild that a link that ERSMS is providing is safe as being able to see the website behind it. This permission also allows ERSMS to send embeds, which show a very nicely organised set of information which is easy to read.
Kick Members | This permission is also dangerous (see permission description "Ban Members") as it can remove users from a guild (even if temporarily). As told with the "Ban Members" permission, certain modules such as "sync punishments to Discord". A manager may decide that anyone who is warned 10 times within a certain timeframe should be kicked in their communications server.
Manage Channels | This permission allows ERSMS to configure channel permissions and information including but not limited to names and role permissions within a channel / category. ERSMS uses this permission when using tickets such as ticket claiming, creating ticket channels and changing their names based on commands such as /claim, /add-user, /remove-user etc.
Manage Nicknames | This permission allows ERSMS to change any user's nickname as long as their highest role is below ERSMS' highest role. This is used when a user has verified using ERSMS and the verification module has been enabled by the guild managers who may configure nicknames to be set to their Roblox name, age or whatever other pre-set they may choose from.
Manage Roles | This permission allows ERSMS to manage any role's permission and users in the role etc if that role is below ERSMS' highest role. This is used when a guild manager decides to enable modules such as in-game roles, on-shift roles, verified roles or on-member-join roles. This permission is necessary to do all of these actions. However, ERSMS is not programmed to modify a role's permission on a server scale, however may do so in a channel one (see "Manage Channels").
Manage Webhooks | This permission allows ERSMS to manage webhooks. Webhooks are a sort of user that isn't really a real user or a bot, but more like a messenger who is told what to do by using POST requests. ERSMS uses these when needing to mass send items such as message logging etc etc. This is also used when a guild manager decides to make certain commands such as session messages send things with webhooks, which allows the ERSMS bot to create a custom user with the server's icon and name with some other modifications as an unverified application to make the guild look more professional based on a manager's preferences.
Moderate Members | This permission is mostly based on making users be on a server mute / timeout. ERSMS only uses this permission if certain modules are enabled such as on certain events in the ER:LC server or moderation logs, the user may be moderated in the actual communications server.
Read Message History | This is a basic permission which allows ERSMS to see messages that were sent when ERSMS was offline. This is used when reading messages needed for ticket transcripts when ERSMS may have been temporarily shut down.
Send Messages | This is another basic permission which ERSMS needs when using await channel.send(). This may be used when alerts from in-game commands or automatic events are being posted or when a command is some sort of panel and a manager wants it has a plain message, not as a response to a command interaction.
View Channels | Pretty obvious what this does. ERSMS needs to have this permission to well, have access to channels it needs to send messages in etc etc.
Send Messages in Threads / Create Public or Private Threads / Manage Threads | This is a permission which allows ERSMS to create a sub-channel type thing in a message, where users type about the message that the thread is linked to. ERSMS uses this when using the application module or certain alerts, where moderators can discuss things.
Administrator | ERSMS only uses this permission to have access to all channels to log messages such as sending of messages, editing or deletion etc. The permission is not used for anything other than to have access to all channels and bypass restrictions.
Gateway Intents
Server Members | This intent allows ERSMS to see all information about users in a guild. ERSMS uses this information when verifying users or syncing moderations across ER:LC and Discord. This is used for promotions, infractions and more when we need information about users such as ids, avatars etc even if one doesn't directly interact with a command.
Message Content | This is used for message logging (sending, editing and deleting messages). This is only used for the "message logs" module but it's only sent to a channel, and is not saved in any file, hardware or any copy at all, just in a guild's specified channel.
Saved Information
Saved information is saved in an "sqlite3" database. This is a very compact way of saving data in rows, columns etc. This is necessary for verifications between Roblox users and Discord users (for example when a Roblox user executes a command, it should sync over to Discord to log it. Data can be requested to be removed but may take up to 1 month. We can extend this period over to 6 months if we need legal action against you.
Data is not encrypted but will be encrypted after the ERSMS app reaches 300+ members. ERSMS will be suspended if it gets to 500+ members without restriction. Data access is restricted to two people and two people only - kablankooo and ObviouslyTiger (the two developers).
Saved information is not given to unauthorized third-parties without your undeniable consent. We will not sell or distribute any data about any user no matter what.
After a bot is removed from a guild, data is saved for 7 days and then deleted without being able to restore it at all if the bot is removed. This gives server owners chance to restore information such as moderation logs if ERSMS was kicked / removed mistakenly. We may manually extend this grace period to 2 months if we deem it necessary to investigate for legal actions.
Some data may vary - see our data storage policy.
