1. Information processed
Dashboard sign-in uses Discord OAuth with the identify and guilds scopes. Sakura receives your Discord user ID, username, avatar details, and the servers and permission data Discord returns so the dashboard can show servers you can manage. The dashboard does not request your email address.
The dashboard session stores sign-in and permission-check data, including an OAuth access token, in a server-side session. The session cookie is HttpOnly, SameSite=Lax, and configured as Secure when the site uses HTTPS. Sessions use a rolling seven-day cookie lifetime.
When the bot is used in a server, it stores server configuration and feature data such as server, user, channel and role IDs; enabled settings; scheduled actions; code-feed state; and feature-specific records or statistics. Some features store user reminders. These records are needed to operate and persist the features configured by server administrators.
Message content may be processed to provide a feature. If moderation logging is enabled, the bot can store violation details including message content and related user, channel, and message IDs in the server’s moderation log. The bot may also send content to a channel when a configured feature requires it.
2. How information is used
Information is used to authenticate dashboard users, verify server-management access, apply server settings, deliver bot features, maintain moderation and safety functions, and diagnose or restore service data. Sakura does not use Discord OAuth data for advertising.
3. Storage and retention
Dashboard sessions and bot data are stored on the service infrastructure. Server data may be held in the bot’s database and supporting files, with backups used for recovery. The service does not promise a fixed retention period for backups.
Feature records are retained while needed to operate the service or configured feature. Removing the bot or a dashboard session does not necessarily erase already stored server data or backups. Where a feature provides a delete or reset control, server administrators may use it for that feature. For a broader deletion request, contact the operator through the Support Server link in the footer, if available, and identify the relevant server and records. Requests may be subject to verification and applicable legal or operational requirements.
5. Security
Reasonable technical and organizational measures are used to protect service data. No internet transmission or storage system can be guaranteed completely secure. Do not share dashboard access or grant bot permissions beyond what your server needs.
6. Your choices and requests
You can revoke Sakura’s OAuth access through your Discord authorized applications settings, sign out of the dashboard, and ask a server administrator to remove or reset feature data where controls are available. You can also contact the operator through the Support Server link in the footer for a privacy or deletion request. Applicable local law may provide additional rights.
7. Children and platform rules
Sakura is a service used through Discord and does not knowingly seek information directly from children. Your use must comply with Discord’s eligibility requirements and applicable law.
8. Policy updates
This policy may be revised as the service changes. The current version and its revision date will be posted on this page. Continued use after an update means the revised policy applies to subsequent use, to the extent permitted by law.
Discord platform policies
Your use of Discord remains subject to Discord’s own terms and privacy practices.