Legal

Privacy Policy

Last updated: July 19, 2026

This Privacy Policy explains what information CypherHound processes when you use it, and what happens to it.

1. What we process when you run a command

To execute a slash command, CypherHound temporarily handles:

As currently built, CypherHound does not write command inputs, results, or user/server IDs to any database or persistent log. Each request is processed in memory and discarded once a response is sent. If that changes — for example, if logging is added for abuse prevention or rate limiting — this policy will be updated to describe what's retained and for how long before that change ships.

2. Where your input goes

Depending on the command, your input is forwarded to the relevant public data source to retrieve results:

These are independent third-party services with their own privacy practices, which we don't control. We only send the minimum needed (the query itself) — no additional Discord identifiers are forwarded to them.

3. What we don't do

4. Data retention

Because command inputs and results are not persistently stored (see Section 1), there is generally nothing to retain or delete. Standard Discord platform logs (e.g. gateway connection logs) may exist transiently at the hosting level for operational stability, and are not used for any purpose beyond keeping the bot running.

5. Children's privacy

CypherHound is not directed at children and does not knowingly process data from users below Discord's own minimum age requirement (13, or higher where required by local law).

6. Your choices

You can stop CypherHound from processing any data associated with you at any time by not using its commands, or by having a server administrator remove the bot from a server.

7. Changes to this policy

If our data practices change — most notably, if we begin retaining logs — this page will be updated and the "Last updated" date above will change accordingly.

8. Contact

Questions about this policy can be sent to fludixbusiness@duck.com — replace this with your own contact address before publishing.