Overview

DoraBot minimises data collection and processes only what is necessary to operate features and ensure reliability. We do not sell data and we avoid collecting personal information unless you explicitly provide it for a specific feature. This policy describes what we collect, how we use it, how long we keep it, and how you can exercise your rights.

By inviting, configuring, or interacting with DoraBot on Discord, you acknowledge that you have read and understood this Privacy Policy. If you do not agree, please refrain from using the bot and remove it from your server.

Archived versions of this policy are available upon request. For quick questions, please refer to our FAQs. If something is unclear, reach out via the Support Server.

Defined Terms

“We”, “Us”, or “Our” refer to DoraBot as a service or the DoraBot development team.
“The Bot” refers specifically to DoraBot as a utility or service.
“ZTGA”, “Zak”, or “Zak The GoAnimator” refer to the creator and owner of DoraBot, including his associated entities.
“Discord” refers to the communication platform on which DoraBot operates, governed by its own terms and policies.
“You”, “Your”, or “User” refers to any individual or entity interacting with DoraBot, whether as a server owner, moderator, or general user.
“Support Server” refers to the Discord server dedicated to providing assistance and updates for DoraBot.
“Personal Data” means information relating to an identified or identifiable individual (for example, a birthday if you provide it).
“Non‑Personal Data” means information that does not identify an individual (for example, server IDs, channel IDs, role IDs, feature toggles, or aggregated statistics).
“Processing” means any operation performed on data, including collection, storage, use, transmission, and deletion.

Information Collection

DoraBot collects only the information needed to provide requested features, keep the service reliable, and improve performance. We avoid collecting message content and do not passively track background activity.

Types of Information Collected

Non‑Personal Data: Technical and configuration identifiers that enable features to function reliably:
- Server, channel, role, and user IDs necessary to apply configuration and permissions.
- Feature settings (for example, whether birthday announcements are enabled, preferred announcement channel, time zone, or locale if configured).
- Command usage metadata (for example, command name, timestamp, success/error status) for troubleshooting, reliability, and abuse prevention.
User‑Provided Data for Features: Certain features require you to provide information:
- Birthday announcements: Day and month are required; year is optional. If you provide a year, it may be used to calculate an age for display if you enable that option.
- Optional profiles or levels: If a server enables levels, the bot may store XP/level counts and related non‑content metadata.
- Saved roles or join‑rejoin helpers: Role IDs necessary to restore roles when rejoining.
Temporary Command Inputs: Inputs for commands that require immediate processing (for example, a search query or a calculation) are processed in memory and discarded immediately after the response is produced, unless you explicitly save a result as a configuration item.

Data Not Collected

DoraBot does not store user messages or full chat logs.
DoraBot does not track users across servers beyond what is required to operate features in each server.
Personally identifiable information is not collected unless you explicitly provide it for a feature (for example, birthdays).
Sensitive categories of personal data (for example, government IDs, health information, financial data) are not requested and should not be submitted to the bot.

Data Usage

We use collected data exclusively to deliver features, maintain service reliability, and improve user experience. We do not use data for advertising, targeted marketing, or profiling.

Permitted Use: Execute commands, post scheduled or triggered announcements (for example, birthdays), maintain server‑level configurations, prevent spam or abuse, and diagnose operational issues.
Prohibited Use: No data is used to build marketing audiences, sell ads, sell user lists, or profile users for behavioural advertising.
Aggregated Analytics: We may aggregate non‑personal usage metrics (for example, command frequency) to inform improvements. Aggregates do not identify individuals.

Data Retention

We retain data only for as long as necessary to provide requested services, meet security needs, and comply with applicable law. Where retention periods end, data is deleted or anonymised.

Temporary Command Inputs: Deleted immediately after processing.
Birthday Data: Retained until you disable the feature or request removal via support. Users can modify the birth year using commands; day or month changes require support.
Server‑Specific Configuration: Retained while the bot remains in the server. When DoraBot is removed from a server, all of that server’s data will be forgotten after thirty (30) days.
User Data Tied to a Server: When a user is removed from a server in any way, all of their data attached to that server (for example, levels, saved roles) will be forgotten after thirty (30) days.
Grace Periods: The 30‑day period supports accidental removals and restoration requests. During this time, limited backups may exist for recovery and audit. After the period, data is scheduled for permanent deletion.
Legal Holds: If required by law or to investigate abuse, certain records may be retained beyond standard periods and then deleted when no longer required.

Data Security

We implement appropriate technical and organisational safeguards to protect data during transmission and storage.

Encryption: Data in transit is encrypted where applicable. Sensitive tokens are encrypted at rest.
Access Controls: Administrative access is limited to authorised personnel and governed by least‑privilege principles.
Operational Hygiene: Regular dependency updates, key rotation where applicable, and monitoring to detect abuse or anomalies.
Incident Response: If we discover a data incident affecting user privacy, we will investigate, contain, and remediate. Where required by law, we will notify affected parties and relevant authorities.

While we strive for strong security, no system is entirely immune to risk. Please avoid submitting sensitive personal data to the bot.

User Rights

We respect your rights to access, correct, restrict, and request deletion of your data, subject to technical feasibility and applicable law.

Access & Export: You may request a summary of your feature‑related data (for example, your birthday settings, levels). Provide your Discord user ID and relevant server ID.
Correction: You can modify your birth year via commands. For corrections to birth day or month, contact support. Other configuration changes can usually be made by server administrators.
Deletion: You can disable features at any time. For birthday removal or other personal data deletion, contact support; we will process requests within a reasonable timeframe.
Opt‑Out: You may opt out of optional features. Removing the bot from a server triggers the 30‑day forget schedule for that server’s data.
Appeals: If you believe a request was mishandled, reach out on the Support Server with details (timestamps, IDs).

Exercising rights via Discord may require verification that you control the relevant account or administrative role.

Birthday Announcement Feature

Participation: Entirely voluntary. Providing day and month enables announcements. Supplying a year is optional and may be used to compute an age if you opt in to display it.
Visibility: Announcements appear in the server channel configured by admins. Content and formatting may be customised by server settings.
Modification: You can change the birth year via commands. For day or month corrections, contact support to avoid impersonation or griefing.
Opt‑Out: Disable announcements at any time. For full removal of stored birthday data, contact support. Removal follows verification and our deletion schedule.
Retention: If you leave or are removed from a server, birthday data linked to that server will be forgotten after 30 days.
No Sensitive Data: Do not include legal names or other personal identifiers with birthday submissions. The feature works with your Discord identity.

Modifications to this Policy

We may update this Privacy Policy to reflect new features, integrations, or legal requirements. Material changes will be announced on the Support Server or via other appropriate channels. Continued use of DoraBot after changes take effect constitutes acceptance of the updated policy.

The “Effective” and “Last updated” dates at the top indicate when the policy first took effect and when it was most recently updated. Archived versions are available on request.

Contact Us

Questions, concerns, or data requests? Visit the Support Server. Include relevant details such as your Discord user ID, the server ID, timestamps, and the specific feature involved to help us respond efficiently.

Jurisdiction & Regional Notices

DoraBot is developed and operated from Canada. Where regional laws provide additional rights or impose specific obligations (for example, data access or deletion timelines), we will honour those to the extent applicable. If any part of this policy is inconsistent with mandatory local law, that part will be interpreted to meet the minimum required compliance while preserving our commitment to privacy.