Privacy Policy

Product data update — 25 October 2026

Welcome images and customization are available in every plan. Uploaded images are not private and can be accessed by anyone with their URL. Original uploads up to 10 MB are prepared in the browser for the 1.5 MB storage limit; file-type, signature and daily upload limits still apply.

When XP, optional roles, counters or temporary voice rooms are enabled, the service processes the server, user, channel and role identifiers, activity and configuration needed for those features. Bot-owner analytics are restricted to the authorized operator; total bot server counts are not public. Language and last-server preferences are stored in the browser and grant no access rights.

Effective 25 October 2026 · Discord Application ID 1556398502861602826

Plain-language summary: ARB DisBot processes only the Discord and website data needed to provide configured features, security, support and account access. Ordinary message content inspected for moderation is not stored in the core event journal. We do not sell Discord API data or use it for advertising profiles.

1. Controller and contact

The operator and data controller for ARB DisBot is Ahmad Al Masri in Germany. Postal and contact details are provided in the Impressum. For privacy, access, correction or deletion requests, use the official support page at arbdisbot.com/support or join the official support server at discord.gg/wfQSVaMFmj and open a private ticket marked “Privacy / Data request”.

Never send us your Discord password, token, backup codes, QR-login data or payment credentials. We may ask for your Discord User ID and, when relevant, a Server ID only to locate records and verify authority.

2. Scope

This policy applies to the ARB DisBot Discord application, the official website at arbdisbot.com, its Discord OAuth sign-in, saved dashboard drafts, support requests and the official support server.

Discord remains a separate provider/controller for the Discord platform and independently processes account and platform data under Discord’s own terms and privacy policy.

3. Discord data we process

Server configuration

Server IDs, channel IDs, role IDs, feature settings, language roles, exemptions, allowlists, moderation thresholds, configured support/log channels and plan entitlement state. This is used to provide the settings chosen by server administrators.

User and moderation identifiers

Discord User IDs for actors, targets, ticket owners, exemptions, trusted webhook creators, moderation-quota accounting and security-alert recipients. User IDs are preferred over usernames because names can change.

Security and event metadata

Join/leave events, role/nickname/timeout changes, Discord Audit Log action IDs, channel/role changes, voice moves/server mutes, moderation outcomes, and message edit/delete metadata such as message ID, channel ID and author ID. The event journal intentionally records that message content is not stored for message edit/delete logging.

Message content processed transiently

Message text can be inspected in memory for anti-spam, mention protection, invite detection, exact-match auto-replies and the custom help trigger. Ordinary chat content processed by these checks is not written to the core event journal.

Verification and tickets

Verification uses a temporary arithmetic challenge linked to Server ID and User ID. Ticket metadata includes a ticket ID, Server ID, User ID, Discord channel ID, status and creation time. Ticket message contents are not copied into the bot database; closing a ticket through the configured flow deletes the Discord ticket channel.

Security snapshots, quotas and structure backups

Security features may store limited snapshots of administrative roles, moderation quota counters and evidence identifiers. Structure backup is an optional paid feature controlled by the server owner. A snapshot can contain role/channel IDs and names, permissions, channel types, topics, parent relationships and permission overwrites. It does not contain Discord message history, message attachments or direct messages. Owners can create a snapshot manually, enable or disable scheduled snapshots, preview snapshots, delete individual snapshots, and request non-destructive recreation of missing roles or channels. Recreated Discord objects receive new IDs; a limited mapping from old snapshot IDs to recreated IDs may be stored with that snapshot to avoid duplicate recreation.

Cancellation and withdrawal declarations: We record name, email, Stripe subscription ID, requested action, time, optional reasons, and limited abuse-prevention metadata. With a configured verified mail provider, we email the receipt and inform the operator for review. Retention depends on applicable accounting, contractual and legal requirements.

4. Website and Discord OAuth data

The official website uses Discord OAuth to sign users in. During sign-in, Discord provides an OAuth access token that is used transiently to call Discord’s /users/@me endpoint. ARB DisBot does not persist that Discord OAuth access token in its website database.

The website creates a signed, HttpOnly, Secure, SameSite=Lax session cookie containing the Discord User ID, username, display name and a bounded list of up to 25 server IDs and names for servers identified as owned during sign-in. The session lasts seven days. The bot checks server ownership again before applying a dashboard job.

When a signed-in user saves dashboard settings, the website stores the Discord User ID as the owner, the draft settings JSON and an update timestamp in Cloudflare D1. Stored settings do not grant a paid entitlement. Saving also queues supported settings for bot validation and acknowledgement. The “Save” action queues an authenticated, short-lived job; the bot checks ownership, active plan, prerequisites and permissions, then acknowledges the result. The website stores the job payload, owner and server IDs, status and timestamps, and a bounded live-state snapshot of effective settings, plan, prerequisite and permission booleans. These job and live-state tables currently have no automatic deletion schedule; request removal through support. Strong protection policies require separate confirmation and can affect future Discord events, not immediately punish a member.

Dashboard users on every plan may upload a custom welcome image. Supported images are limited to PNG, JPEG, WebP or GIF up to 1.5 MB and are stored in the existing Cloudflare D1 database as binary image data under a random name. To limit storage abuse, the website also stores the signed-in Discord User ID, UTC day and upload-attempt count in a short-lived D1 rate-limit record. The image is served from an ARB DisBot URL so Discord can render it. Anyone who has that exact image URL may be able to retrieve the file, so users should not upload confidential images. Replacing or removing an uploaded image triggers deletion of the previous ARB DisBot-hosted image when ownership can be verified.

When a signed-in user submits a support request, the website stores the Discord User ID, request ID, request type, preferred language, title, body, status, support response and timestamps. Support administrators can view requests for the purpose of answering them.

Security operations and emergency control: The website stores a bounded snapshot of the last 30 bot-recorded administrative actions per server, including action type, actor/target IDs, a short reason and time. Access requires verified server ownership. The website snapshot currently has no automatic expiry and is subject to verified data removal requests. The bot locally retains temporary emergency settings, their prior values and expiration time for safe restoration after outages or restarts.

5. Billing foundation and payment data

Official checkout uses Stripe or a separate PayPal checkout, depending on the selected payment method. Each provider processes payment and billing data under its own terms; ARB DisBot does not store card numbers or security codes. The website keeps subscription, invoice and payment-event metadata needed to verify entitlements and prevent duplicate processing.

For official checkout, Stripe processes payment and billing data under Stripe’s own terms. ARB DisBot is designed not to store card numbers or card security codes. Its website database may store billing metadata needed to track a subscription, including the Discord owner ID, Stripe subscription ID, Stripe customer ID, selected plan and billing interval, Stripe price ID, subscription status, current-period end, cancellation-at-period-end flag, optional Server ID, and timestamps. Stripe event IDs/types may be stored to prevent duplicate webhook processing. For PayPal, we retain the corresponding order/subscription and payer identifiers, payment and refund status, plan, server and owner linkage, period end, timestamps and event IDs needed to verify access and prevent duplicate processing. Card details and PayPal account credentials are not stored by ARB DisBot.

The one-time 7-day Prime Plus trial stores the Server ID, owner User ID, claim time and expiry so the same server cannot reset the trial by removing and re-adding the bot. The trial does not itself create a payment or automatic charge. When it expires, paid entitlements stop and the server falls back to the Free tier.

6. Optional music

When music is used, a user-selected SoundCloud search term or SoundCloud URL may be processed through SoundCloud-related services to resolve or stream the selected audio.

7. Purpose and legal bases

  • Provide commands, configuration, verification, tickets, moderation and other requested features.
  • Protect servers, detect abuse, preserve limited security evidence and prevent duplicate event handling.
  • Enforce plan entitlements, technical limits, exemptions and one-time trial rules.
  • Operate website sign-in, dashboard drafts and support requests.

Where the GDPR applies, processing may rely on performance of the requested service, legitimate interests in operating and securing the service, and legal obligations for records that must be retained by law.

8. Current retention

  • Verification challenges: expire after 5 minutes and are deleted after success, expiry or invalidation.
  • Core moderation/action records: automatically purged after 30 days.
  • Event journal: automatically purged after 30 days and capped at the latest 50,000 events per server.
  • Closed ticket metadata: purged after closure once the record is older than 30 days from creation.
  • Security deduplication events: generally 7 days; temporary security holds are removed when they expire.
  • Security snapshots and moderation quota records: automatically purged after 30 days.
  • Structure backups: optional and retained by count; the current implementation keeps up to 7 recent backups for Prime and Prime Plus. The owner can delete a stored snapshot at any time. Disabling scheduled backups stops new scheduled snapshots but does not silently delete existing snapshots.
  • Discord server configuration and most operational records: removed when ARB DisBot leaves a server through the normal Guild Delete flow.
  • Website session: the signed session cookie expires after 7 days.
  • Website drafts, dashboard jobs/live-state snapshots and support requests: there is currently no automatic expiry. They remain until replaced, no longer needed, or removed following a valid deletion/administrative request.
  • Welcome-image upload counters: daily counters are used only for abuse prevention and old day buckets are removed on a rolling basis of roughly 8 days.
  • Uploaded welcome images: there is currently no fixed automatic expiry. An ARB DisBot-hosted image is deleted when the user removes/replaces it through the supported flow and ownership can be verified, or following a valid deletion request. Orphaned files may also be removed during maintenance.
  • Trial/entitlement/subscription history: not part of the automatic 30-day purge. Trial claim identifiers may be retained to enforce the one-time 7-day trial; paid subscription records may be retained as needed for entitlement integrity, anti-abuse, accounting, disputes or legal obligations.
  • Stripe and PayPal billing metadata/events: the current foundation does not implement an automatic expiry. Records may be retained for subscription integrity, duplicate-event prevention, accounting, disputes and legal obligations, then deleted or anonymized when no longer required.

9. Service providers and sharing

We do not sell Discord API data and do not use it to build advertising profiles. Data may be processed only as needed by:

  • Discord — platform, OAuth, Gateway/API events, commands, permissions and audit data.
  • Cloudflare — official website hosting, D1 database including optional welcome-image draft storage, and network delivery.
  • Hetzner — bot infrastructure and operational database hosting.
  • SoundCloud — optional music search/stream resolution.
  • Stripe and PayPal — payment, checkout and subscription processing for the selected payment method. PayPal is a separate payment flow; Stripe Managed Payments does not process those payments.

These providers operate under their own terms and may process data internationally using their applicable legal transfer mechanisms.

10. Privileged Discord data

ARB DisBot may require privileged intents such as Guild Members and Message Content because member-join handling, moderation, anti-spam, invite protection and related security features require the associated events or fields. Access is limited to functionality the application actually provides.

11. Security

Application tokens, environment files, bot databases, backup dumps and user data are kept outside the public source repository. Sensitive moderation actions remain subject to Discord permissions and role hierarchy. No system can guarantee absolute security; report suspected exposure through private support and never post secrets in public channels.

12. Your rights and deletion requests

Depending on applicable law, including the GDPR, you may have rights to access, correct, delete, restrict or object to processing and to receive information about your data. You may also have the right to complain to the competent data-protection authority.

Submit requests through the official support page or a private ticket in the official support server. Include only the minimum information needed to identify your records. We may verify account or server ownership before disclosing or deleting records.

13. Bot removal

When the bot is removed from a Discord server through the normal Guild Delete flow, ARB DisBot removes that server’s configuration, moderation/action records, ticket metadata, verification challenges, security state, quota state, community auto-reply data, structure backups and event journal records from the operational bot database. Trial and entitlement history may remain for the limited purposes described above.

14. Cookies and website telemetry

The official website uses the strictly necessary signed session cookie described above for authenticated features. ARB DisBot does not use that session cookie for advertising. Infrastructure providers may process technical connection data, such as IP addresses and request metadata, to deliver and secure the website.

15. Changes

We may update this policy when ARB DisBot’s functionality, providers, legal obligations or data practices change. Material changes will be reflected by changing the effective date and publishing the current version at this URL.

16. Contact

Privacy/support: arbdisbot.com/support or Official ARB DisBot Support.

Discord Application ID: 1556398502861602826