Skip to main content
BackBased Bot

Based Discord Bot

Privacy Policy

Last Updated: October 19, 2026

This Privacy Policy ("Policy") describes how the Based Bot ("the Service", "we", "us") collects, uses, stores, and discloses information in connection with your use of the Service. By accessing or using the Service, you acknowledge that you have read, understood, and agree to be bound by the terms of this Policy. If you do not agree, you should discontinue use immediately.

1. Scope and Application

This Policy applies to all interactions with the Service, including but not limited to interactions conducted within Discord guild environments, private messaging contexts, and any auxiliary interfaces through which the Service may be accessed. The Policy governs the collection and handling of information arising from such interactions to the extent permitted and required by applicable law.

The Service operates as an automated software agent deployed on the Discord platform. All use of the Service is further subject to Discord's own Terms of Service and Privacy Policy, over which we exercise no control and for which we bear no responsibility.

2. Information We Collect

In the ordinary course of providing the Service, we may collect and process certain categories of information. The nature and extent of information collected varies based on how the Service is configured and how you interact with it. Such information may include, without limitation:

  • Interaction Data. Content submitted to the Service through commands, mentions, replies, or direct communications, together with relevant channel context, is processed for AI assistance, summaries and configured moderation. Deleted-message and edited-message disk archives are disabled. Per-request temporary artifacts used by supported AI features are cleaned up when processing finishes; generated image delivery has its own temporary artifact lifecycle.
  • Platform Identifiers. Discord user IDs, usernames, server IDs and channel IDs are personal data. They are retained where needed for service delivery, settings, access control, DM contact/server lists and administrator-configured features. The DM contact list contains identity and contact metadata, not message bodies.
  • Usage and Event Data. Records of Service interactions, including command invocations, timestamps, associated channel and guild context, and operational metadata, collected for the purposes of monitoring, diagnostics, abuse prevention, and service improvement.
  • Verification Data. The community questionnaire may ask about religious background and interests. Users may decline to disclose personal beliefs or sensitive details and request manual verification. Automated review is instructed not to grant or deny access based on religion or other protected characteristics. Answers and AI review reasons are kept only in process memory while pending, not in the verification database or staff-channel notices. Authorized staff view answers through short-lived private responses. Do not submit credentials, health or financial details, or personal information about anyone else.
  • Moderation Data. Ordinary messages may be processed in small batches for administrator-configured moderation. Moderation notices and audit entries posted inside Discord remain subject to Discord and server retention controls. Disabling local archives does not delete arbitrary Discord server history.
  • Audio Data. Where the Service is active within voice communication channels, audio signals may be temporarily processed in real time for the purpose of enabling voice-interactive features. Such audio data is not retained in any persistent form following the conclusion of the relevant processing operation.

3. Purposes of Processing

Information collected in connection with your use of the Service is processed for one or more of the following legitimate purposes:

  • Provision, operation, and maintenance of the Service and its constituent features;
  • Fulfilment of requests submitted by users or guild administrators;
  • Ensuring the security, integrity, and availability of the Service;
  • Enforcement of administrator-configured policies and applicable terms;
  • Detection, investigation, and prevention of unauthorised use, abuse, or violations of these terms;
  • Compliance with applicable legal or regulatory obligations.

We do not process personal information for advertising purposes, nor do we use collected data to construct inferences about individuals beyond what is necessary to deliver the Service.

4. Third-Party Service Providers

In the course of providing certain features of the Service, user content and interaction data may be transmitted to third-party artificial intelligence infrastructure providers. Such transmission is necessary for the delivery of AI-powered functionality and is governed by the applicable terms and privacy policies of those providers. We do not control, and are not responsible for, the data practices of any third-party provider.

Depending on the feature and configuration, providers can include Google-model inference, OpenAI Codex, and voice services such as Sarvam and Deepgram. Their applicable terms and privacy policies govern their processing. The operator confirms that the configured upstream API uses zero-data-retention processing and does not use submissions to train models. Verification uses only those upstream API models, not the local CLI fallback. Provider controls must be maintained when configuration changes.

We do not use Discord message content to train our own machine learning or AI models, or for advertising.

Except as described in this Policy or as required by law, we do not sell, rent, license, or otherwise disclose personal information to third parties.

5. Data Retention

Verification answers and AI reasons expire after three days while pending and clear earlier on review completion, bot restart or unload. Expired answers cannot be retrieved; housekeeping removes expired memory entries every five minutes while online. Users may need to resubmit after a restart. Verification identifiers and status metadata also expire after three days, with database cleanup at startup and every five minutes while online. New database rows contain no answer or AI-reason payloads.

The obsolete deleted/edited-message archives have been removed and are no longer created. DM contact metadata, server/settings records, operational diagnostics, and feature metadata for statistics, invite attribution and giveaways remain stored while needed for their disclosed functions or until removed following an applicable deletion request. These records may outlive 30 days and must not be treated as anonymous. This application cleanup does not rewrite repository history, database backups or independent Discord records.

6. Data Security

We implement reasonable technical and organisational measures designed to protect the information we process against unauthorised access, disclosure, alteration, or destruction. The service and local database are hosted on encrypted Oracle Cloud Infrastructure storage. Oracle encrypts boot volumes, block volumes and their backups at rest using AES-256, as described in its Block Volume Encryption documentation. This is infrastructure-level encryption, not a claim of separate application-level encryption for every field. However, no method of electronic storage or transmission is entirely secure. Accordingly, while we endeavour to apply commercially reasonable safeguards, we cannot guarantee absolute security and disclaim liability for unauthorised access or loss of information beyond our reasonable control.

7. Children's Privacy

The Service is not directed to individuals who do not meet the minimum age requirements applicable to their use of the Discord platform in their respective jurisdiction. We do not knowingly collect or process information from individuals below such applicable minimum age.

8. Your Rights

Subject to applicable law and the technical constraints of the Service's deployment model, you may have certain rights with respect to the information we hold about you, including rights of access, correction, deletion, restriction of processing, and data portability. The availability and scope of such rights will depend on your jurisdiction and the nature of the information concerned.

To request access, correction, deletion or manual verification, contact @jalkarna on Discord with your user ID and the relevant server ID. Do not send passwords or tokens. Requests cover application-controlled records; Discord and independent providers have their own data controls.

Use .help privacy to find the policy and deletion contact. .autoreply me off disables random replies for you, not administrator-configured moderation. Server administrators control bot access through Discord permissions and may remove the bot.

9. Third-Party Platform Dependency

The Service operates exclusively on and through the Discord platform. Discord, Inc. independently collects and processes personal information in accordance with its own privacy practices. This Policy does not govern Discord's data practices, and we expressly disclaim responsibility for any data processing undertaken by Discord independently of the Service.

10. Modifications to This Policy

We reserve the right to modify this Policy at any time and at our sole discretion. Any changes will be reflected by an updated "Last Updated" date at the top of this page. Your continued use of the Service following the posting of any modifications constitutes your acceptance of the revised Policy.

11. Contact

For privacy-related inquiries, requests for data deletion, or any other concerns regarding this Policy or our data practices, please contact @jalkarna directly on Discord. Include your Discord user ID and relevant server ID so the correct records can be located.

© 2026 Jalkarna Gautam. All rights reserved.

Terms of Service →