Last updated: 2026-10-30
I'm a solo developer building Discapp to offer useful, free tools for Discord communities. Here's a plain-language explanation of what happens to information when you use the site. Some tools work entirely in your browser; a few features need to contact Discapp's services or another provider.
You don't need an account or login. I don't use Discapp cookies for advertising or analytics. The Role Icon Maker saves your settings and uploaded images in your browser's localStorage, so your design is there if you come back on the same device. You can remove it by clearing this site's browser storage. Other image and design tools generally work in your browser and don't upload your files unless a feature says it will. hCaptcha is provided by another company and may use cookies or similar storage for security; see its Privacy Policy.
If you send me a bug report, I receive the title and details you write, the page you were on, your browser and platform, language, timezone, screen and viewport sizes, and pixel ratio. I forward the report to a Discord channel I use for support, where people with channel access can read it. I don't keep a separate copy in a Discapp database. I don't set a fixed deletion schedule for Discord messages, so how long a report stays there depends on channel management and Discord's policies. To limit spam, the report service temporarily uses the IP address supplied by the hosting network for an in-memory rate limit of up to ten minutes; that IP isn't included in the report sent to Discord.
I use hCaptcha to help prevent automated abuse of bug reports and user lookups. The verification token goes to Discapp and is checked with hCaptcha. hCaptcha may also process device, browser, network, and interaction signals under its own policies. You can read hCaptcha's Privacy Policy and Terms.
Analytics: I don't currently load Vercel Analytics or another analytics script in the app. If that changes, I'll update this policy to explain what is used.
Hosting and security: The companies that host and protect the site may process basic connection details, such as your IP address, request time, page or API route, and browser information, to make the site work and help prevent abuse. Their settings determine what gets logged and for how long; I don't set one retention period for all of those records. You can read Vercel's Privacy Policy for its practices.
When you use User Lookup, the Discord user ID you enter goes through a Discapp API route to Discord, and the result comes back to your browser. Server Lookup and Vanity URL Checker send the invite or vanity code directly from your browser to Discord. Discord handles those requests under its Privacy Policy. I don't intentionally save lookup inputs or results in a Discapp database.
When you use the Webhook Builder, the webhook URL, message content, optional files, and any message link or thread ID you provide pass through my API service to Discord so it can retrieve or send the message you asked for. A webhook URL can control the associated Discord webhook, so only use one you're allowed to use and keep it private. I don't intentionally save these request contents in a Discapp database. Discord may keep messages sent through its service under its own policies.
I don't sell personal information or use it for advertising or marketing. When a feature needs another service, I send it only the information needed to provide that feature, help prevent abuse, or keep the site running. Discord, hCaptcha, and hosting providers handle information under their own terms and privacy practices.
Have a question about this policy or the way Discapp handles information? Email me at legal@discapp.org.