Privacy Policy

01 Information We Collect

When you use this website or contact ItsMoreno for a commission, the following types of information may be collected:

Information You Provide Directly

• Name or username (e.g., Discord tag) when reaching out for a commission.
• Contact details such as email address, Discord ID, or other communication handles.
• Project details, briefs, or requirements you share during the commission process.
• Payment-related information processed through third-party platforms (no payment data is stored by ItsMoreno directly).

Information Collected Automatically

• Basic usage data via the browser (e.g., page visits) that may be logged by the hosting provider.
• No cookies, tracking scripts, analytics SDKs, or fingerprinting tools are used on this website.

02 How We Use Your Information

Information collected is used solely for the following purposes:

• To communicate with you about your commission or inquiry.
• To deliver the agreed-upon services and provide updates on project progress.
• To process payments through third-party payment platforms.
• To maintain records of project scope and agreements for dispute resolution.

Your information is never sold, rented, or shared with third parties for marketing or advertising purposes.

03 Discord Bots & Data

Commissioned Discord bots may collect and process Discord user data as part of their functionality. The categories of data a bot may handle include:

• Discord User IDs — Used to identify users for features such as leveling, economy, moderation records, and role assignments.
• Discord Server IDs (Guild IDs) — Used to scope bot configuration and data to the correct server.
• Discord Role IDs & Channel IDs — Used for permission checks, reaction roles, and channel-specific features.
• Message Content — Processed in real-time only when required for features such as auto-moderation, keyword triggers, or command parsing. Message content is not stored long-term unless the feature explicitly requires a log (e.g., moderation audit logs), and only when the Message Content Intent is enabled with Discord's knowledge.
• Timestamps & action metadata — Stored for audit logs, moderation records, and leveling/activity tracking.

Data Minimization

Bots developed by ItsMoreno are engineered to follow the principle of data minimization — requesting only the specific Discord Gateway Intents and data types necessary for the bot's core functionality. No data is collected that is not required for a specific, active feature.

Data Ownership & Access

• All data collected by a commissioned bot is owned and controlled solely by the Client who commissioned it.
• The Developer does not retain persistent access to bot data after delivery.
• During contracted maintenance or debugging sessions, the Developer may temporarily access live logs or database records strictly for the purpose of resolving the reported issue. Any such access is scoped minimally and data is not retained, copied, or stored by the Developer beyond the duration of the troubleshooting session.
• Clients are responsible for ensuring their deployed bots comply with Discord's Privacy Policy, Developer Policy, and applicable data protection regulations (GDPR, CCPA, etc.).
• End-users of a bot have the right to request deletion of their data. Clients should implement a mechanism (such as a /forgetme command) that purges a user's stored data on request, enabling compliance with the Right to Erasure under GDPR.

04 Data Roles: Controller & Processor

When ItsMoreno develops a Discord bot for a Client, the following data roles apply under GDPR and equivalent frameworks:

• The Client is the Data Controller — The Client determines the purposes and means of processing personal data (e.g., what features the bot has, what data it stores, which users it serves). The Client bears ultimate responsibility for lawful data processing.
• ItsMoreno acts as a Data Processor — During the development and any contracted maintenance periods, ItsMoreno processes data only on the Client's instructions and for no other purpose.
• Clients who require a formal Data Processing Agreement (DPA) to satisfy their GDPR obligations may request one prior to project commencement.