Our Privacy Policy

Our Commitment To Community

Privacy Policy

1. Introduction

Welcome to Inkalyze. Your privacy is critically important to us. This Privacy Policy explains how Inkalyze ("we", "our", or "us") collects, uses, stores, and protects information obtained through your use of our Discord bot, related services, and any associated web-based dashboards or APIs (collectively, the “Service”). It also outlines your rights regarding the data we collect and how you can exercise those rights.

1.1 About Inkalyze

Inkalyze is a modular Discord bot and companion service designed to enhance server safety, structure, and usability. Our platform offers intelligent moderation, automated server analysis, and private user tools such as bookmarks, personal notes, digests, and interactive insights. Inkalyze is operated by Fatal Glitch Studios, located in New Mexico, USA.

1.2 Scope of This Policy

This Privacy Policy applies to:

• All users interacting with the Inkalyze Discord bot, regardless of role (e.g., server owners, moderators, or members)
• All data collected through the bot in Discord servers where it is authorized
• All use of our web dashboardand APIs
• All feature-specific tools including moderation logs, smart bookmarks, activity summaries, and AI-generated insights

This policy does not apply to:

• Discord as a platform, whose privacy practices are governed by Discord’s Privacy Policy
• Third-party services optionally integrated with Inkalyze (e.g., Notion, Zapier), which are governed by their respective privacy terms

1.3 Key Privacy Principles

We follow the following privacy commitments:

• Transparency: We clearly describe what data we collect and how it’s used.
• Data Minimization: We only collect data necessary to provide and improve the service.
• User Control: We offer tools and options for users to manage or delete their private data (e.g., bookmarks and notes).
• Security: We employ reasonable security measures to protect user data from unauthorized access or disclosure.
• Compliance: We strive to meet requirements under applicable data protection laws, including the General Data Protection Regulation (GDPR), the California Consumer Privacy Act (CCPA), and Discord's Developer Terms of Service.

1.4 Consent & Acceptance

By using Inkalyze or authorizing it within your Discord server, you agree to the collection and use of your data as outlined in this Privacy Policy. If you do not agree with this policy, please refrain from using our services and remove the bot from your server. If you are a server owner or administrator, it is your responsibility to:

• Ensure that your community is informed of the bot’s capabilities
• Comply with local regulations related to user privacy within your community
• Configure the bot’s features responsibly, particularly those involving data logging or moderation

2. Information We Collect

Inkalyze collects different types of information depending on how users interact with the system. This section outlines the categories of data collected, how they are gathered, and which features rely on them.

2.1 Data Collected from Discord API

When Inkalyze is authorized in a server, we receive data directly from Discord via their official API and Gateway. This includes:

a. User Identification Data

• Discord User ID (used as a persistent identifier)
• Username and discriminator (e.g., user#1234)
• User avatar URL
• Server roles and nickname (if applicable)
• Discord account metadata (e.g., bot status, if the user is a bot)

📌 Purpose: Used to attribute actions (e.g., moderation logs, bookmarks) to specific users, personalize summaries, enforce permissions, and associate user-generated content (like notes) with a profile.

b. Server and Channel Metadata

• Server ID, name, and icon
• Channel IDs, names, types, and categories
• Role IDs, permissions, and hierarchy
• Thread and category structure
• Webhook configurations (optional alerts)

📌 Purpose: Enables server-wide scanning, optimization tools, permissions analysis, channel mapping, role rationalization, and server scorecard generation.

c. Message Content

• Raw message content (text only) — only in channels the bot has permission to view
• Author ID, channel ID, message ID, timestamp
• Attachments (metadata only; we do not store file contents)
• Optional context (e.g., 5 messages before/after for replay mode)
• Reactions and message references (e.g., reply chains)

📌 Purpose: Used for: detecting and flagging violations such as spam, slurs, profanity, and external links; analyzing tone and clarity using AI to support moderation; enabling replay mode and incident timelines for review; allowing users to save messages privately through bookmarks and whisper saves; and generating digest summaries and keyword usage insights.

We do not collect or store full message histories unless explicitly tied to a logged moderation event or user action (e.g., saved bookmark or violation log).

2.2 User-Generated Data (Private Utilities)

Inkalyze provides features that allow individual users to create and manage private utility data. These are not visible to others by default.

a. Smart Bookmarks

• Saved message ID, author ID, channel/thread ID
• Optional tags or categories (e.g., #todo, #guide)
• Context snapshot (partial message content)

b. Personal Notes

• Freeform text stored by the user
• May be tied to a thread, channel, or message

c. Whisper Save Mode

• Similar to bookmarks, but logged silently with minimal metadata
• Optionally includes the first 100 characters of the saved message for reference

d. User Digest Summaries

• Opt-in statistics like: top words used, message activity patterns, saved items
• Digest is generated per user and only viewable by the user

e. Message Drafts, Goal Trackers, and Prompt Boards

• Localized, user-created entries (e.g., personal reflections, unsent drafts)
• Tied to the user ID only and stored privately

📌 Purpose: Enhance personal productivity and memory within the Discord server context. None of this data is public unless explicitly shared by the user.

2.3 Behavioral and Analytical Data

To support automated moderation, community health evaluation, and server optimization, Inkalyze collects the following behavioral metadata:

a. Message Activity

• Message frequency per user/channel/hour
• Thread activity over time
• Conversation density and keyword clustering

b. Violation & Moderation Data

• Violation type, timestamp, location
• Severity score and escalation level
• Moderator action taken (e.g., warn, mute, restrict)

c. Server Engagement Metrics

• Role and channel usage patterns
• User join/leave events
• Retention indicators and churn patterns
• Moderator response time tracking

📌 Purpose: These metrics support AI-generated insights, auto-generated reports, raid detection, and moderator workload analysis. Where possible, this data is anonymized or aggregated for trend modeling.

2.4 Technical and Diagnostic Data

Inkalyze’s backend systems may collect limited technical data to support performance monitoring and debugging.

a. Bot and API Logs

• Request timestamps
• Feature/module triggered
• Response status codes
• Diagnostic errors or exception messages

b. System Metrics

• Server count
• Shard ID (if using sharding)
• Module performance and load

📌 Purpose: Helps us improve system reliability, manage scalability, and debug unexpected behavior. These logs do not include message content or personal user data unless tied to a specific violation or API request.

2.5 Data from Optional Integrations

If a server admin connects Inkalyze to third-party platforms (e.g., via webhook or API):

• We may store basic configuration info (e.g., webhook URL, destination label)
• We do not access third-party account credentials
• We do not share Discord user data with third-party services unless explicitly configured by the admin

📌 Purpose: Enables optional alert forwarding, synchronization, or reporting to platforms like Notion, Zapier, Slack, etc.

3. How We Use the Data

Inkalyze uses the data it collects solely to provide, maintain, and improve the services offered through our Discord bot, companion dashboard, and supporting backend systems. Below is a detailed breakdown of how each category of data is used and which features depend on it.

3.1 Moderation & Behavioral Monitoring

We process message content, user metadata, and channel structure to support automated moderation features and ensure safe, healthy server environments.

Uses:

• Message scanning: for profanity, spam, slurs, links, and filtered terms.
• Tone monitoring: AI-supported analysis of hostility, sarcasm, or passive aggression.
• Violation handling: automatic escalation (e.g., log ? warn ? mute ? restrict).
• Replay mode: capture of message context (before/after) during violations.
• Watchlists: flagging of users for stealth monitoring based on prior patterns.
• Incident timelines: construction of mod-viewable case summaries for complex events.
• Violation clustering: grouping of similar offenses by type, time, or user.

?? Data Used: Message content, user ID, channel ID, timestamps, violation metadata

3.2 Server Analysis & Insight Reports

We analyze server architecture and user behavior to generate automated health reports and optimization recommendations for server owners and moderators.

Uses:

• Server scorecards: metrics across engagement, structure, moderation, and safety.
• Channel & role analysis: detection of unused or redundant structures.
• Permission audits: identification of risk-prone role configurations or permission gaps.
• Engagement maps: activity heatmaps by channel/time.
• Predictive warnings: alerts for declining activity or mod burnout risk.
• Tone drift analysis: visualizations of shifting community sentiment.

?? Data Used: Server metadata, channel/role info, activity logs, moderation trends

3.3 User Utility Tools (Private Features)

We enable individual users to store and retrieve personal content, such as saved messages and private notes, within the Discord context.

Uses:

• Smart bookmarks: allow users to tag and organize saved messages for future reference.
• Personal notes: let users write and store notes linked to specific threads or messages.
• Whisper save mode: quietly saves message metadata without alerting others.
• Digest summaries: personal reports showing saved activity, top words, or reply trends.
• Draft lockers and goal trackers: provide productivity tools stored securely by user ID.

?? Data Used: Message metadata, user ID, tag labels, note contents (only for that user)

We do not share user-created utilities with other users or servers unless explicitly requested.

3.4 Logging & Visualization

Moderators and administrators can access automated logs and visual tools to help maintain transparency, structure, and accountability.

Uses:

• Violation history logs: searchable by user, channel, type, or date.
• Deletion and mute records: stored to support dispute resolution or trend detection.
• Activity timelines: provide visual patterns for moderators to assess user/server activity.
• Incident digest cards: embedded visual summaries of moderation outcomes.
• Pattern recognition: identifies spikes in violations or coordinated abuse.

?? Data Used: Event metadata, message logs (if flagged), moderation actions, timestamps

3.5 Feature Configuration and Personalization

Each server or user may configure Inkalyze modules and tools to match their community�s needs and personal preferences.

Uses:

• Feature toggles: server admins can enable or disable specific modules (e.g., moderation, AI suggestions, utility tools).
• Custom thresholds: for spam filters, tone sensitivity, and violation severity scoring.
• Digest configuration: per-user control over the frequency and depth of private summaries.
• Dashboard views: display server health reports, bookmarks, notes, and alerts.

?? Data Used: Server ID, user ID, module settings, personal feature preferences

3.6 AI and Language-Based Assistance

Inkalyze uses AI technologies (e.g., OpenAI, Claude, LanguageTool) to enhance moderation and clarity suggestions.

Uses:

• Tone interpretation: detects sarcasm, aggression, or escalating behavior.
• Post clarity suggestions: AI-generated tips for rewording vague or confusing messages.
• Digest summarization: compacts conversation threads for easier review.
• Conflict resolution tips: optional moderator advice based on sentiment analysis.

?? Data Used: Message snippets (temporarily anonymized), server configuration, user settings

We do not store or permanently transmit full message histories to third-party AI systems. Only anonymized or partial excerpts are sent when necessary, and always for analysis only � not for model training.

3.7 System Maintenance, Security, and Debugging

Inkalyze collects technical and event-level data to maintain service availability, diagnose issues, and safeguard system integrity.

Uses:

• Error logging: tracks bugs and exceptions to improve reliability.
• Permission mismatch alerts: warns admins if critical bot permissions are revoked.
• Rate limit management: ensures bot operations comply with Discord usage guidelines.
• System health monitoring: uptime and load tracking for scalable performance.

?? Data Used: Internal logs (no message content), error traces, API call metadata

4. Legal Bases for Processing

Inkalyze processes user data under several lawful bases, as defined by applicable data protection regulations such as the General Data Protection Regulation (GDPR), the California Consumer Privacy Act (CCPA), and similar laws. We only collect and use data when we have a legitimate legal basis to do so.

4.1 Legitimate Interests

We process certain types of data because it is necessary for the proper functioning, security, and improvement of our service � and because these activities benefit both our users and their communities.

• Real-time message scanning and violation detection
• AI-supported behavior analysis and escalation logic
• Moderation logs and replay features
• Server health scoring and risk analysis
• Internal analytics and performance tracking

?? This basis is used: when processing supports community management, security, and infrastructure without compromising user rights. Optional features allow opt-outs where appropriate.

4.2 Contractual Necessity

Some features require data processing in order to fulfill the services we offer to server owners and admins who authorize Inkalyze in their community.

• Running core bot features in servers where it is installed
• Executing user commands like bookmarks or digest generation
• Rendering dashboards, insights, and notifications

?? This basis is used: when the bot or dashboard must process information to deliver the requested features as part of an implied service agreement.

4.3 Consent

We rely on explicit consent before processing user-generated content or enabling personal tools that go beyond basic server functionality.

• Saving and storing bookmarks, notes, or whisper saves
• Generating personalized digests or activity summaries
• Using AI-enhanced tone or clarity suggestions
• Syncing with optional third-party services (e.g., Notion, Zapier)

?? This basis is used: when users choose to activate optional features that involve personal data. Consent may be withdrawn at any time via settings or support requests.

4.4 Legal Obligation

We may retain or disclose data when required to do so by applicable law, such as compliance with lawful subpoenas or data retention rules in certain jurisdictions.

?? This basis is used: only when mandated by legal authorities or governing bodies under applicable law. Requests are reviewed for validity before any action is taken.

4.5 Protection of Vital Interests

In very rare cases, we may preserve or report specific data if it is necessary to protect someone�s life, safety, or physical wellbeing (e.g., responding to imminent harm, serious threats, or abuse reports).

?? This basis is used: only in exceptional circumstances where real-world harm may be prevented by cooperating with official channels.

5. Data Storage & Retention

Inkalyze is designed to collect only the data necessary to operate its features effectively, and we retain that data only as long as needed to fulfill its purpose. This section outlines how different types of data are stored, the retention policies we apply, and how users or server admins can manage or request data deletion.

5.1 Storage Infrastructure

• Primary Data Store: A document-based database used to store logs, configuration data, bookmarks, notes, and moderation events.
• Temporary Cache: In-memory storage for real-time processing such as message context snapshots and active violation detection.
• Local Logs: Minimal diagnostic logs maintained by the system for internal monitoring, which do not include message content unless related to a flagged event.

?? Purpose: Maintain secure, scalable, and performance-optimized infrastructure for service delivery and issue diagnosis.

5.2 Retention Periods by Data Type

• Message Content (Moderation): 30-90 days (configurable). Stored only if linked to a violation or saved action.
• Smart Bookmarks / Notes: Retained until the user deletes them.
• Whisper Saves / Digest Data: Retained until the user disables the feature or deletes entries.
• Violation Logs & Incident Timelines: 90-180 days (server configurable).
• Server Configurations: Retained while the bot is active in the server. Removed automatically after bot removal unless archived.
• Audit & Event Logs (System): Up to 30 days for diagnostic purposes (server configurable).
• User AI-Generated Suggestions: Not stored permanently. Processed in real time only.
• System AI-Generated Suggestions: Up to 30 days for user management purposes (server configurable).
• Third-Party Integration Data: Retained only for as long as the integration is active.

5.3 Data Deletion and Expiry

• Automatic Deletion: Moderation logs, AI prompts, and event traces are purged based on retention schedules. All server data is queued for deletion 7-14 days after bot removal.
• Manual Deletion: Users can delete their bookmarks, notes, digests, and other personal data via bot commands or the dashboard.
• Deletion by Request: Verified requests from server admins or users will be processed within 30 days to permanently remove applicable data.

?? Note: Some deletion requests may require Discord OAuth verification to ensure ownership and prevent unauthorized removal.

5.4 Data Portability

Users and server owners may request a downloadable export of their personal or configuration data in a machine-readable format (e.g., JSON or CSV).

• Users: Can export bookmarks, notes, and digest activity
• Admins: Can export moderation logs and server settings

?? Fulfillment: Data exports are provided within 30 days of a verified request.

5.5 Data Persistence After Bot Removal

• When the bot is removed from a server, all active features stop immediately.
• A 7-day grace period is applied for accidental removals or reinstalls.
• After the grace period, all server-related data is permanently deleted unless otherwise requested by the admin.
• User utility data that is not server-dependent (e.g., bookmarks) may persist until deleted by the user.

?? Note: This ensures that server data is removed cleanly and user content remains in the user�s control beyond bot installation status.

---

6. Data Sharing & Third Parties

Inkalyze does not sell, rent, or trade user data. We share data only when it is essential to deliver specific features, when a user or server admin has explicitly enabled an integration, or when required by law. This section outlines the conditions under which data may be shared, and with whom.

6.1 No Public Sharing of Personal Data

• User bookmarks, notes, whisper saves, or digest summaries
• Server-specific configurations or moderation logs
• Message content (outside of Discord) unless shared directly by a user or admin

?? Clarification: All personal utility data remains private to the individual user unless explicitly disclosed by the user themselves.

6.2 Discord Platform Dependency

• We rely on Discord to provide identifiers, messages, server structure, and permissions.
• All user activity and message data remains subject to Discord�s Privacy Policy.
• We do not access DMs unless the bot is messaged directly by a user.

6.3 Optional Integrations with Third-Party Services

Inkalyze may allow server admins to enable optional connections to third-party platforms to enhance functionality (e.g., sending alerts, syncing logs, receiving summaries).

Examples of integrations:

• Webhook platforms like Slack, Notion, Discord webhooks
• Productivity syncs (e.g., Zapier or custom dashboards)
• Language and AI services (e.g., OpenAI, Anthropic, LanguageTool)

When integrations are active:

• Only data explicitly required for the selected integration is sent.
• No third-party receives access to Discord login credentials or internal Inkalyze databases.
• These integrations are entirely opt-in and can be disabled at any time via the dashboard or admin command.

6.4 AI and Language Processing Providers

Inkalyze may optionally transmit short, anonymized message snippets to third-party services for:

• Tone analysis
• Post clarity suggestions
• Digest summarization
• User requested suggestions
• Conflict forecasting or content improvement

We do not share:

• Full conversation logs
• Discord IDs or usernames
• Sensitive content not required for the specific feature

?? Note: These requests are processed in real time and not stored beyond their immediate use unless part of a moderation case or violation log.

6.5 Hosting and Infrastructure Providers

To deliver a secure and reliable service, Inkalyze may store data on third-party hosting providers (e.g., cloud-based database and compute services). These providers:

• Are under contractual obligations to safeguard data
• Do not access or use the stored content for any purpose outside of storage and security
• No data is stored outside trusted infrastructure platforms chosen for compliance with data privacy standards

6.6 Legal Compliance & Enforcement

We may disclose data if:

• Required by law, subpoena, or government request
• Necessary to enforce our Terms of Service or investigate potential violations
• Required to address security, fraud, or abuse incidents

?? Clarification: We will always evaluate the legitimacy of such requests and limit disclosure to only what is legally required.

6.7 Business Transfers (if applicable in the future)

• If Inkalyze is ever merged, acquired, or transferred, user data may be part of the transaction.
• We will notify users in advance (via Discord or our website).
• Any successor entity will be required to honor this Privacy Policy or provide clear notice of changes.

---

7. Security Measures

Inkalyze is committed to protecting the data we process from unauthorized access, misuse, loss, or alteration. We employ a combination of technical, administrative, and organizational safeguards designed to ensure confidentiality, integrity, and availability of both user and system data.

7.1 Application-Level Security

a. Role-Based Access Control (RBAC)

• All sensitive features (e.g., moderation logs, configuration tools, utility exports) are accessible only to authorized users based on Discord roles or verified OAuth permissions.
• Users without appropriate role permissions cannot execute commands or access dashboard modules beyond their scope.

b. Scoped Command Restrictions

• Bot commands are designed with Discord permission checks to ensure users can only run commands in servers and channels they are authorized to interact with.
• Certain features (e.g., audit logs, behavior insights) are restricted to server moderators and administrators only.

c. CSRF & Session Protection

• Dashboard sessions are protected using secure tokens to prevent cross-site request forgery (CSRF) and hijacking attacks.
• Session expiration and token rotation policies are in place to limit long-term unauthorized access.

7.2 Infrastructure & Data Protection

a. Encrypted Data Transmission

• All communication between our bot, dashboard, and server infrastructure is encrypted using HTTPS and TLS protocols.
• We use Discord's secure gateway and REST API for data exchange with Discord servers.

b. Secure Storage

• Sensitive records (e.g., violation logs, personal notes) are stored in an encrypted database or document-based system.
• Internal data access is restricted by API keys or secured admin interfaces.

c. Minimal Storage Scope

• We store only the data necessary to deliver each feature.
• We automatically purge data tied to expired features (e.g., removed bots, deleted integrations) based on retention schedules.

7.3 Bot Operation Safeguards

a. Rate Limit & Abuse Protection

• We respect all Discord rate limits and implement internal throttling to avoid flooding or over-requesting.
• Abuse detection systems flag unusual bot usage patterns, such as mass spam, repeated data access, or unexpected command surges.

b. Permission Drift Alerts

• Inkalyze continuously audits its own permissions and can notify server admins if critical access (e.g., to read messages or manage roles) is unexpectedly revoked.

c. Violation Escalation Control

• All escalation logic (e.g., auto-warn, restrict, or mute) is logged and can be reviewed to prevent false positives or abusive enforcement.
• Violation events are scored by severity, and extreme actions (e.g., bans) must be approved by server moderators unless explicitly configured otherwise.

7.4 Staff and Developer Access

Only authorized developers or trusted system operators have access to infrastructure and internal tools used to monitor or maintain Inkalyze.

• Only authorized developers or trusted system operators have access to infrastructure and internal tools used to monitor or maintain Inkalyze.
• All access is logged and restricted via role-based accounts.
• There is no general access to user-created content such as bookmarks or notes unless explicitly authorized by a user or required for bug investigation or abuse review.
• Any incident involving unintended access is documented, reviewed, and remediated.

7.5 Monitoring and Intrusion Detection

• Internal health checks and uptime monitors continuously assess bot and dashboard performance.
• Critical errors or unauthorized access attempts trigger alerts and automatic protective responses, such as session termination or IP restriction.

7.6 Responsible Disclosure & Security Reports

If you discover a security vulnerability in Inkalyze, we encourage you to report it to us immediately. We maintain a responsible disclosure policy and will respond promptly.

• Reports can be submitted via Our discord Server, via Support on our website, or emailing: support@inkalyze.com.
• Security researchers who follow responsible disclosure will not be subject to legal action.

7.7 No Guarantee

While we make every effort to secure your data and provide a reliable service, no platform can guarantee absolute security. Users are responsible for maintaining the security of their own devices and Discord accounts. We encourage server owners to use Discord�s native security tools in conjunction with Inkalyze.

---

8. User Controls & Rights

Inkalyze empowers users and server administrators with tools to access, manage, and remove their data. We also honor rights granted under applicable data protection laws, including the General Data Protection Regulation (GDPR), the California Consumer Privacy Act (CCPA), and similar frameworks.

This section explains what rights you have and how you can exercise them.

8.1 Individual User Controls (via Bot or Dashboard)

a. View and Manage Saved Data

• Smart bookmarks
• Notes and whisper saves
• Digest preferences
• Message drafts and personal goal trackers

? How: Use the Inkalyze bot commands or dashboard.

b. Opt-In / Opt-Out of Features

• Digest summaries
• AI-generated clarity or tone suggestions
• Whisper Save or activity tracking

? How: Use the settings menu in the dashboard, or contact support.

c. Delete Personal Utilities

All personal utility data (bookmarks, notes, etc.) can be deleted on demand.

? How: Through the dashboard or by request.

8.2 Rights for All Users (GDPR/CCPA-Aligned)

Regardless of where you live, Inkalyze offers the following rights to all users:

a. Right to Access

You may request a copy of the data Inkalyze has collected about you.

? How: Contact support and verify your Discord identity.

b. Right to Rectification

If any stored personal data is incorrect or outdated (e.g., nickname-based labels), you may request correction.

? How: Edit via the dashboard or submit a correction request.

c. Right to Erasure ("Right to be Forgotten")

You may request that all data associated with your Discord ID be permanently deleted.

? How: Submit a deletion request with verification. We will complete requests within 30 days.

d. Right to Restrict Processing

You may request that we stop processing specific data categories (e.g., message summaries, AI usage).

? How: Use dashboard controls or contact support.

e. Right to Data Portability

You may request an export of your personal data in a machine-readable format (JSON or CSV).

? How: Submit a data export request using your verified Discord ID.

f. Right to Object to Automated Decisions

If you believe our AI moderation or behavioral scoring systems have acted unfairly, you may object and request human review.

? How: Contact support with a description of the situation. We will manually evaluate the logs and take appropriate action.

8.3 Server Administrator Controls

If you're a Discord server owner or admin, you can:

• Enable or disable any Inkalyze module or feature
• Configure retention durations for moderation data
• Request deletion of all data related to your server
• Disable the bot entirely, which triggers an automatic data purge after a retention window

? How: Use server-level commands or dashboard tools.

?? Admins are responsible for informing their communities of the use of bots like Inkalyze, especially if they rely on privacy-sensitive features like moderation logging or AI analysis.

8.4 Identity Verification

• We may request that you verify your identity via Discord OAuth login or bot-based validation before processing any export, deletion, or correction request.
• We will never ask for your Discord password or TOTP code.

8.5 Data-Related Support

All requests related to user rights, data access, deletion, or questions about our practices can be submitted through:

• ?? Support Email: support@inkalyze.com
• ?? Our Discord: You can use the support channels on our official server.
• ?? Web Form: Use our Dashboard which can be found on our website at https://inkalyze.com

---

9. Childrens Privacy

Inkalyze is not intended for use by individuals under the age of 13, or any minimum age required in your country for online services.

9.1 No Direct Targeting of Children

• Inkalyze does not knowingly collect personal information from children.
• Our features are designed for use by Discord servers, which themselves are governed by Discord�s Terms of Service � requiring users to be at least 13 years old (or older in some jurisdictions).
• We do not market the bot, dashboard, or any services directly to children.

9.2 Server Responsibility

• Because Inkalyze is installed and configured by Discord server administrators:
• Admins are responsible for ensuring compliance with age restrictions in their community.
• Admins should not enable features like moderation logging or personal tracking if they operate a server intended for younger audiences without first ensuring lawful parental consent where required.

9.3 If You Believe a Child�s Data Has Been Collected

• If you are a parent or legal guardian and believe that Inkalyze has collected personal data about a child under 13:
• Please contact us immediately at support@inkalyze.com
• Upon verification, we will promptly delete the child�s information from our systems.

---

10. Updates to This Privacy Policy

We may update this Privacy Policy from time to time to reflect changes in our features, legal obligations, or operational practices.

10.1 Notification of Changes

If we make significant changes to how we collect, use, or store personal data:

• We will notify affected users through reasonable means, such as:
• A notice posted by the bot in admin-allowed channels
• An announcement on our website or changelog

10.2 Versioning and Effective Dates

• Each version of this Privacy Policy will include:
• A last updated date
• A version number, where applicable

This allows users and server owners to compare changes over time and understand how their data is treated.

10.3 Continued Use Implies Acceptance

Your continued use of the Inkalyze bot or dashboard after an update to the Privacy Policy constitutes acceptance of the revised terms. If you disagree with any future version of the policy:

• You may disable the relevant feature(s)
• Or remove the bot from your server and request data deletion

---

11. Contact Information

We welcome questions, requests, and concerns regarding this Privacy Policy or your personal data. Whether you're a server administrator, a regular user, or a parent seeking information, we're here to help.

11.1 General Contact

For all privacy-related inquiries, including:

• Questions about this Privacy Policy
• Data access or export requests
• Data correction or deletion requests
• Concerns about security or misuse
• Reports of potential violations involving minors

You can contact us at:

• ?? Email: support@inkalyze.com
• ?? Web Support : https://inkalyze.com/support/

11.2 Verification Process

• We may require you to verify your identity via Discord login or bot interaction before fulfilling any privacy-related request.
• We will never ask for your password, 2FA code, or API tokens.

11.3 Supervisory Authorities

If you are located in the European Economic Area (EEA) or United Kingdom, and you believe your data protection rights have been violated, you have the right to lodge a complaint with your local supervisory authority or data protection office.

11.4 Legal Entity

Below is our Legal Entity Information for this project.

• Developer & Operator: Fatal Glitch Studios, LLC
• Jurisdiction: New Mexico, USA

---

• Date Created: 07/01/2025
• Date Updated: 07/01/2025
• Policy Version: #01