← Back to Bot Hound

What Bot Hound Can Access

Bot Hound uses OAuth 2.0 to request only the specific permissions it needs. Here's exactly what we ask for and why.

The short answer

You don’t have to connect anything to run a Bot Check — checks work without an account. If you do choose to sign in with 𝕏, Bot Hound requests a narrow set of permissions: just enough to identify your account. We cannot post tweets, send DMs, follow accounts, or change your profile. We do not ask for access to your followers list.

• We only request the specific scopes listed below — nothing more
• We will never post tweets, send DMs, follow accounts, or read your direct messages
• You can revoke Bot Hound's access at any time from your 𝕏 account settings

Permissions we request

Signing in is optional — it exists so you can hold a prepaid balance and keep your report history. When you do sign in with your 𝕏 (Twitter) account, Bot Hound requests these OAuth 2.0 scopes:

• users.read — read your profile (to identify your account)
• tweet.read — read tweets (required by the API alongside users.read)

That’s it — identity only. Because we don’t request offline access, we don’t receive a refresh token: our access ends when the short-lived access token expires.

What we actually do

• Read your profile (to identify your account)
• Run a Bot Check on the public 𝕏 account you enter, and generate a verdict report

A Bot Check analyzes the account you enter — its public profile, recent public tweets, and profile image. We fetch that public data from 𝕏 (directly or via a third-party 𝕏 data provider). We never access your followers, and the account you check does not need to be connected to Bot Hound.

What we do NOT do

Bot Hound does not have permission to perform any of the following:

• Post or delete tweets
• Like, retweet, or bookmark
• Follow or unfollow accounts
• Send or read direct messages
• Change your profile or settings

Last updated: July 11, 2026