Privacy Policy

Scope of This Policy

This policy applies to all applications created and operated by bloxlog.org, including but not limited to Bloxlog and Bloxlog Automod. It covers what information is collected, why, how long it's kept, and how it's protected.

Not all of our applications collect the same data. Where an app collects data beyond basic operational information, this is noted in the relevant sections below. Apps that do not collect or store data beyond what is needed to function will not retain information beyond the active session.

This policy does not apply to Fluxer or any other services operating independently from bloxlog.org applications.

Information We Collect and Store

Some bloxlog.org applications collect and store data to support auditing functionality and to help our developers make every app better. Depending on which application you are using, this may include:

• Server or guild identifiers (guild IDs) and, where available, guild names
• User identifiers (user IDs) and display names, where an action or event involves a specific user
• Channel identifiers and role identifiers associated with application configuration
• Moderation and configuration settings chosen by server administrators
• Audit event records, including event type, timestamp, and relevant context, which may include the content of flagged messages where a content filter is active
• Bot action records, such as when the application joined a server or when settings were changed
• Technical information needed to troubleshoot errors and diagnose issues

We only collect information that is directly relevant to the functionality the application provides.

Audit and Event Logging

Applications that provide auditing or moderation functionality maintain structured event logs used for auditing purposes and to help our developers identify issues and improve application behaviour. Log entries may contain:

• Timestamp of the event
• The guild or server identifier the event occurred in
• The type of event, such as a word filter trigger, a configuration change, or a bot action
• The user ID and display name of any user involved in the event
• Where a content filter is triggered, the specific message content that caused the flag
• Configuration actions taken by administrators, such as setting channels, roles, or filter options

These logs are stored securely on our servers and are not publicly available. Access is limited to authorised members of the bloxlog.org development team and, where applicable, authorised representatives of the relevant community.

Log Retention

Audit and operational event logs are not kept indefinitely. Applications may issue automatic reminders to server administrators when data is approaching a retention threshold, giving them the opportunity to review or request deletion before logs are removed.

Server administrators and authorised community representatives can request that their server's data be removed from our systems at any time.

Where no deletion request is made, logs are automatically cleared after a limited period, generally within 2 to 6 months depending on the application and volume of data involved.

Server Information Storage

BloxLog stores server information needed to correctly identify and restore existing environments. This lets it recognise previously configured servers, restore required information after restarts, and maintain correct associations between config and connected environments. This information is stored internally and is not publicly accessible.

Configuration Information

BloxLog holds internal configuration records needed for operation, including server identifiers, application settings, and required operational config. This is stored securely and only used to run the application.

How We Use Information

Information collected by bloxlog.org applications is used to:

• Provide auditing and moderation functionality within the application
• Maintain application reliability and restore service after restarts
• Help our developers identify bugs, diagnose issues, and improve all applications
• Review audit records where requested by authorised community representatives
• Comply with applicable legal requirements

We do not use collected information for advertising, user profiling, or any commercial purpose unrelated to the operation and improvement of our applications. We do not sell data to third parties.

Access to Information

Access to data held by bloxlog.org applications is restricted. It is not publicly accessible and is only made available where necessary for maintaining, securing, or operating an application, or where access is shared with an authorised community representative. We apply reasonable technical and organisational measures to prevent unauthorised access.

Transparency with Authorised Community Representatives

We believe communities have a right to know what data our applications hold about them. Where a server administrator or other authorised representative requests access to the data held for their server, we will share that information with them transparently. This includes audit log records, configuration and settings data, and any other information collected in connection with their community's use of our applications.

Access is limited to individuals who can reasonably demonstrate they are an authorised representative of the relevant community. Requests can be made via the contact details at the bottom of this page.

Data Sharing

We don't sell, trade, or hand over operational information to third parties. Information may only be disclosed where required by law, needed to protect application security, or needed to investigate abuse, security incidents, or technical issues.

Security

We take reasonable technical and organisational steps to protect information handled by BloxLog, preventing unauthorised access, alteration, disclosure, or misuse. That said, no internet-connected system can be guaranteed fully secure.

Third-Party Platforms

BloxLog runs within the Fluxer platform. Information processed by Fluxer is subject to Fluxer's own privacy practices. BloxLog is only responsible for information handled directly by the BloxLog application.

Your Rights & GDPR Compliance

bloxlog.org adheres to the General Data Protection Regulation (GDPR). If you are located in the UK or European Economic Area, you have the following rights regarding any personal data associated with you or your organisation:

• Right of access — request a copy of the data we hold about you or your server
• Right to rectification — request correction of any inaccurate information
• Right to erasure — request deletion of your data; we will action valid requests promptly
• Right to restriction — request that we limit how we process your data in certain circumstances
• Right to object — object to processing where you believe it is not justified
• Right to data portability — request a copy of your data in a structured, machine-readable format

These rights apply regardless of whether you are located in the EEA. We will respond to all valid requests within 30 days.

Changes to This Policy

We may update this Privacy Policy when needed due to changes in BloxLog, operational practices, or legal requirements. The latest version replaces previous ones once published.

Contact

Questions about this policy or how BloxLog handles information can be sent to support@bloxlog.org or through the official Fluxer server.