Attribution

While few and far between, we've got a few

If you're simply using the API with a Discord Bot 100% Unrelated to Security to add to a blacklist of nasty people you want to remove from your bot, and it only happens in the backend and never shown to users then you're fine not giving us attribution

We define personal use here as in a private bot for example, your Discord server's Bot.
And it quite heavily depends but we'll list some examples, its always best to clarify during application:

A Public list of users on the Blacklist: In this case you'd put attribution on this list somewhere

A event that goes through members at some point and checks if they should be banned and if true bans them: you'd place this in a 'credits' section somewhere

For 99% of cases of a private server bot, we requires you have CyberShield in it so users can report at ease

We generally don't allow bots with security as their main focus to use our API, as it conflicts with our no compete guidelines, other bots however we're good on (usually)

As with the prior one its best to get clarification during application, however here's some examples:

A /user-info command where theres a field of "Malicious User" or similar: A subtext of attribution next to/under this field would work.

A Application bot that blocks blacklisted users from applying: Attribution should be in application logs and in a command like /help or /credits

Your Attribution should include a link to https://cybershieldbot.xyz and https://docs.cybershieldbot.xyz/threat-reports

We generally recommend these be put in Masked links to reduce clutter, just make sure you name 'CyberShield' in it, and mention for the docs link that users should report any users that meet threat criteria