How to add a Privacy Policy URL to a Discord app or bot

By Paul Cranmer, Founder · Last verified October 2026 · Discord Developer Portal · General Information

Every Discord application carries two optional URLs, terms_of_service_url and privacy_policy_url, which you set in the Developer Portal under General Information. They are shown to users on the authorization screen and in the app's profile, and bot verification and App Directory listings expect both documents to be in place and to describe what the bot reads and keeps. This page gives the exact path and the points the policy must make for a bot that handles messages and member data.

Who this is for

Bot developers approaching verification (75 servers) or an App Directory listing
Teams whose authorization screen shows no legal links
Builders of user-installable apps that read messages or member data

Not for

Private bots that will never leave your own server (still good practice)
A guide to Discord's gateway intents or permissions

What the platform requires

Developer Portal → Applications → your app → General Information has Terms of Service URL and Privacy Policy URL fields; they map to the application object's terms_of_service_url and privacy_policy_url.
Both links appear to users on the authorization screen and in the app's profile, so they must load publicly over HTTPS without a login.
Verification and an App Directory listing expect both documents to be present, to name the app and the developer, and to give a contact.
The policy should cover what the bot reads and stores (message content, user and guild IDs, roles), retention, third parties, and how to request deletion.

Get a live URL first

A bot with a dashboard or a backend is a SaaS product, so it is on the hosted plan: answer the wizard with the bot's name, the Discord data it processes and a contact, and paste the live URL into the Privacy Policy URL field. If you also need Terms, the Terms of Service URL field takes a hosted Terms page.

Get the Discord app policy URL

Step-by-step: paste your privacy policy URL

Create the hosted privacy policy URL. Generate the policy with the bot's name, the Discord data it reads (messages, IDs, roles), what it stores and for how long, and a deletion contact. Copy the live URL.
Open your application in the Developer Portal. Go to discord.com/developers/applications, select the app, and open General Information in the left column.
Paste the Privacy Policy URL and the Terms of Service URL. Scroll to the two URL fields, paste the hosted policy URL into Privacy Policy URL and your Terms URL into Terms of Service URL, then Save Changes.
Check the authorization screen. Open your install link in a private window. Both links should appear below the permissions list and open without a login.
Submit for verification or the App Directory. When the bot approaches 75 servers, apply for verification; for discovery, complete the App Directory listing. Both expect the two documents to be in place and accurate.
Keep the URL stable as the bot grows. New intents and features change what you process. Update the policy text behind the same URL so the links in the portal and on the authorization screen never break.

Field labels to look for

General Information: Name, description, tags, icon, and the Terms of Service URL and Privacy Policy URL fields.
Authorization screen: Where users see the two links before they add the app.
Verification: Required past 75 servers for message content and other privileged intents; the documents are checked.

Common reasons the form fails

Linking a Discord support server or a GitHub README instead of a policy page
A policy that never mentions message content when the bot reads it
Terms field filled, privacy field empty
Links that break when the bot's website moves

User-installable apps

If your bot is user-installable (works in DMs and across servers), the authorization screen is often the only place users see your legal links. Make the policy specific to what the bot does in that context.

Get the Discord app policy URL Learn more

FAQ

Are the two URLs required to run a bot?

The fields are optional in the application object, but verification and the App Directory expect them, and users see them on the authorization screen. Fill both.

Can one policy cover several bots?

Yes, if it names each bot and what each one reads and stores. One stable URL in every app's General Information works.

Do I need a Terms of Service too?

The portal has a field for it and reviewers expect it alongside the policy. Our Terms of Service URL product hosts one the same way.