Privacy

Who operates the service

HinoGuard is operated by Green Paprika LLC, New Mexico, United States. The legal entity and postal contact details are listed below. A Discord server owner or administrator independently decides how their community uses the bot and what moderation actions they take.

Information processed

When you sign in, we receive the Discord account identifier and basic profile details supplied through the identify scope, plus the list of servers Discord says you may manage through the guilds scope. We use these to authenticate you, display eligible servers and enforce access rights.

When a server uses HinoGuard, we process the server's identifier, name, channel and role references, configuration, permissions and operational status. Features that are actually enabled may create moderation case records, audit events, suggested content, ticket or form submissions and the Discord identifiers needed to associate those records with their authors or targets.

Support requests may include the subject, category and content you submit along with the account associated with the request. Service operation also creates technical security and diagnostic records such as timestamps, request results and failures. Please avoid submitting passwords, payment details or other sensitive data in tickets.

Discord access and privileged intents

HinoGuard uses Discord application commands and the Discord API to perform actions requested by authorized users. Receiving a command or handling a ticket does not mean the bot continuously reads every message in a server.

On this deployment, privileged continuous member-list, general message-content and per-user presence tracking are not enabled for HinoGuard's public feature set. If a future feature needs a privileged Discord intent, we will identify its purpose and update the relevant user-facing information before enabling it. The Discord Developer Portal permissions shown to an application owner do not by themselves prove that an intent is used by the deployed bot.

The bot can still receive basic guild, channel, role, interaction and message metadata needed for ordinary Discord functionality. Each enabled module should use only the data necessary for its stated purpose.

Purposes and legal bases

We use account and server data to provide the requested dashboard, commands, configuration and support. Where GDPR applies, processing needed to provide requested services may rely on performance of a contract; proportionate security, fraud prevention and reliability processing may rely on legitimate interests; and records required by law may rely on legal obligations. Consent is obtained where a particular processing activity legally requires it.

We do not sell Discord API data or use private moderation or support conversations to build advertising profiles. We do not use the information to assess employment, insurance or other unrelated eligibility.

Service providers and transfers

Discord provides authentication and bot interactions. Our server infrastructure is hosted with netcup GmbH; Cloudflare provides DNS, reverse proxy and network-security services. These providers may process limited operational information needed to supply their services.

Because the operator is a US entity and providers may operate internationally, processing or access outside the European Economic Area may occur. Where applicable, international transfers must rely on a lawful transfer mechanism. Details relevant to a particular request can be obtained from support.

How long data is kept

Account, authentication and server settings are used while an account or a configured server needs the service. Session data follows its technical expiry or revocation. Moderation cases, tickets, submissions and audit records remain only as long as their feature's operational purpose, proportionate security/history needs or a legal requirement justifies them.

Audit logs default to no automatic expiry. An authorized server administrator can configure the audit-log retention period to 30, 90, 180 or 365 days; the configured cleanup does not automatically erase other types of records. There is no single retention period for every category. Deleting a server configuration does not necessarily remove shared moderation records. Requests to remove particular records are assessed individually, including lawful security and legal exceptions.

Security

Access to server administration is constrained by Discord permissions and HinoGuard authorization. We use access controls, session protections and operational logs to maintain the service. No online service can guarantee absolute security. Please report suspected exposure through Support without posting private tokens or credentials.

Your rights and deletion requests

Depending on the applicable law, you can request access, correction, deletion, restriction, objection or portability of personal information, and lodge a complaint with a competent data-protection authority. We may need enough information to verify that a request relates to your account or the record concerned.

Signed-in users can open a private support request, and anyone unable or unwilling to sign in can write to the operator's postal address below. Describe the data or server concerned without sending secrets or unnecessary personal data. Removing the bot from a Discord server also stops future operation there but does not automatically erase all historical records.

Changes to this policy

We update this page when data practices, enabled features, providers or legal requirements change. Material changes to sensitive Discord data access should be described before the relevant feature is enabled. The date above identifies this published revision.