Privacy Policy

Last updated 2026-05-13

1. Scope

This Privacy Policy describes what Sploodji ("the Service") collects, how that information is used and stored, and the choices available to users and server administrators. It applies to the Sploodji Discord bot and the dashboard at sploodji.com.

2. Information we collect

From the Discord bot

  • Guild metadata. Guild ID, channel and role IDs, and configured feature flags. Guild names, icons, and member lists are not stored in bulk.
  • Interaction context. The IDs of users, channels, and messages involved in commands you run, so the relevant feature can act on them.
  • Feature data. Only the fields each feature requires, such as verification photo URLs and review state, ticket transcripts, profile fields, economy balances, embed templates, and custom commands.
  • Audit entries. Who made which configuration change, when, and against which feature.

From the dashboard sign-in

  • Discord OAuth scopes. We request only identify and guilds, used to display your username and avatar and to list the servers you administer. We do not request email, connections, direct-message access, or any write scope on your behalf.
  • Session tokens. Held in an encrypted, server-side cookie. OAuth access and refresh tokens are not written to disk.

3. Information we do not collect

  • Email addresses, phone numbers, real names, or IP addresses beyond transient access logs.
  • Direct messages between users.
  • Messages in channels the bot has not been invited to act on.
  • Browser fingerprints or third-party advertising identifiers.

4. How we use information

Collected information is used solely to operate the features you or your server administrator have enabled. We do not sell data, share it with advertisers, or use it to train machine-learning models.

5. Storage and security

Data is stored in a managed CockroachDB cluster with TLS in transit and at-rest encryption provided by the database host. Dashboard sessions are signed with a server-side secret, and CSRF protection is applied to every non-safe HTTP method. Verification photos are stored as Discord CDN URLs only; the Service does not download or rehost user images.

6. Retention

  • Guild configuration and feature data persist while the bot remains in the server. If the bot is removed, the data is retained for 30 days so that re-inviting restores configuration, then deleted.
  • Audit entries are retained for 180 days.
  • Ticket transcripts follow the retention configured on each panel; the default is 90 days after closure.
  • Dashboard sessions expire after 7 days of inactivity.

7. Your rights

You can:

  • Review what is stored about you. Sign in to the dashboard and visit your profile and per-server pages, or run /profile view in Discord.
  • Correct or remove your data. Use commands such as /profile clear and ticket closure, or ask the server's administrators to remove your data through the dashboard.
  • Request full deletion. Contact the maintainer through the support server linked from the Documentation. Verified deletion requests are honoured within 30 days.

8. Age requirement

The Service is not directed at anyone under the age of 18 and is permitted to operate only in age-restricted (18+) Discord servers. If we become aware that information about a person under 18 has been collected, we will delete it.

9. Third parties

The Service relies on Discord for authentication and message delivery, and on a managed CockroachDB host for storage. We do not embed third-party analytics, advertising, or tracking scripts in the dashboard or documentation pages.

10. Platform safety reporting

The bot includes a /safety-report command for severe Discord platform safety concerns. Submissions are stored separately from general feature data, are visible only to the bot owner and designated safety reviewers, and are never shared with the subject of a report or with appellants. A full transparency notice covering risk scoring, follow-up procedure, and the appeals process is available at Platform Safety Reporting.

For any child-safety concern, we strongly encourage you to also report the matter directly to Discord and to the appropriate child-protection authority in your jurisdiction. The bot's report flow is supplemental, not a substitute.

11. Changes

Material changes to this policy will be announced in the support server and reflected by the updated date at the top of this page.

Confirm