Effective date: Set on publication
Service operator:
Contact:
1. What umask does
umask is a Discord bot that lets a server owner choose an existing staff role and an elevated role. Authorised staff receive an owner-issued phrase and may use it to obtain the elevated role temporarily. umask attempts to remove the role when the session expires or ends. It does not edit the elevated role's own permissions.
2. Reduces risk; never guarantees protection
umask is designed to reduce a server's exposure to compromised accounts holding standing privileged access. It does not guarantee immunity from account compromises, role misuse, unauthorised moderation, outages or other attacks. It is an additional safeguard, not a substitute for Discord account security or careful administration.
It cannot prevent abuse during an active elevated session, a compromise of the server owner, a stolen authentication phrase, or privileges granted through another role, bot or integration.
3. Server-owner and staff responsibilities
- Owners select their own role permissions, staff members and allowed session lengths; they must confirm the configuration is appropriate for their server.
- umask requires Manage Roles and a bot role positioned above the elevated role, ideally immediately above it. It does not need the target role's individual permissions merely to assign it. Administrator access is not required.
- For safety, the current bot will not manage elevated roles with Administrator or Manage Roles enabled. Permanent staff permissions must not bypass the role-elevation requirement.
- Staff must protect their authentication phrases and report suspected compromises. Owners should revoke compromised credentials promptly and keep independent recovery access.
- Use umask only where authorised and in compliance with Discord rules and applicable law.
4. Availability and expiry limits
umask depends on Discord, PebbleHost, the network and its local SQLite database. If the bot is offline, cannot contact Discord, or loses its records, it may be unable to remove an elevated role on time. Permissions can remain assigned beyond their intended expiry. The bot attempts reconciliation when available again, but this is not a guarantee. Owners should remove roles manually where necessary.
5. Privacy, records and requests
Staff credentials, session metadata and server settings are processed as described in our Privacy Policy. Completed session history is intended to support legitimate server security monitoring and investigation. Routine history is retained for approximately 90 days unless a specific lawful preservation need is documented. Staff may request access, correction or deletion of their personal information via our Data requests page, support@umask.app, or private support tickets.
Requests are assessed individually. A server owner's desire to keep records for an investigation does not automatically defeat an individual's privacy rights; conversely, an erasure request does not necessarily require us to discard specific evidence needed for a recognised legal purpose. We consider necessity, proportionality and applicable law, and explain the outcome where appropriate. Approved requests do not immediately erase every backup copy, and active sessions may first require safe role revocation.
6. Service changes and support
We may update or temporarily suspend umask for security, operational and maintenance reasons. We do not represent the bot as independently audited or certified. Contact or use our support server for support or abuse reports.
7. Responsibility and applicable rights
Owners remain responsible for their role configurations, staff access decisions and emergency recovery procedures. Nothing here excludes liability or statutory rights that cannot lawfully be excluded. Any additional warranty and liability terms should be reviewed for the operator's jurisdiction before public launch.