Privacy
Almost every tool runs entirely locally in your browser. The only network calls are read-only lookups to Discord's public API for invite and vanity-code checks. We do not log, store, or sell any data you paste.
This site does not use cookies, tracking pixels, or third-party analytics. There are no accounts, so there is no profile data.
This policy applies to distools.net and all its subpages.
What we collect
Nothing, beyond what your hosting provider records automatically. Standard web-server logs (IP address, user agent, requested URL) may exist at the infrastructure level to keep the site running and protected from abuse, but these are retained only as long as needed and are never shared with third parties.
Tools that decode tokens, build embeds, generate timestamps or convert text all run client-side. The moment you leave the page, the input is gone. We have no database of pasted tokens, no message history and no clipboard data.
What happens when you use a network tool
A small number of tools - the invite info checker and the vanity-code checker - send a request from your browser to Discord's public API. That request goes directly from your device to Discord and is subject to Discord's own privacy policy. We do not proxy it, log it, or see the response. Tools like the webhook sender and message logger only connect to the webhook URL you provide; that webhook is owned by the server you choose to target.
Because requests originate from your browser, your IP address may be visible to Discord (or the webhook target) just as it would be for any normal visit. If that matters to you, use these tools with the same care you would use for any website.
Third-party services
This site does not embed third-party trackers, social widgets or advertising networks. The only external requests a page can make are the optional tool lookups described above. We deliberately avoid external fonts, analytics scripts and cookie banners because none of them are needed for the tools to work.
Changes to this policy
If this policy changes, the updated version will be published on this page with a new revision date. Because we collect almost nothing, most changes will simply clarify how a tool behaves rather than introduce new data collection.
If you have questions about privacy on this site, use the contact page to get in touch.
Data retention and deletion
There is no user data to retain or delete, because there are no accounts and no client-side storage tied to your identity. Anything you paste into a tool exists only in the memory of your own browser session and is discarded when you leave the page or close the tab.
Your browser may offer to remember form inputs, and your browser's autofill is entirely under your control. This site does not use localStorage or sessionStorage to store tool inputs.
Children's privacy
This site is not directed at children under 13, and we do not knowingly collect personal information from anyone. Because the site operates without accounts, tracking or data collection, there is no mechanism for any personal data to reach us in the first place.
Your choices
Since the site sets no cookies and runs no analytics, there are no consent banners, no opt-out toggles and no preference cookies to manage. If you want the most private experience, that is already what the site provides: everything runs locally, and nothing is recorded.
If you prefer not to use the network-based tools (invite and vanity checks), simply avoid those pages; all other tools work completely offline once the page is loaded.
External links
Some pages link to external sites, including Discord's own help center and developer documentation. This policy does not apply to those sites, and we encourage you to read their privacy policies if you visit them.
How privacy is enforced technically
The site is served as static HTML with client-side components, which means tool inputs are processed by JavaScript running on your device. Nothing is posted to an application server, and the page itself carries no tracking scripts. Content-Security-Policy headers, where supported, further restrict which resources a page may load, so third-party requests cannot be injected by the page itself.
For the handful of tools that talk to Discord's public API, requests are made directly from your browser. That design choice is deliberate: by refusing to proxy those calls, the site guarantees it never sees your invite codes, vanity lookups or the API responses they produce.
Version and contact
This policy was last reviewed on 25 August 2026. Questions, concerns and deletion requests - although there is nothing to delete - can be sent through the contact page, and we will answer from a human inbox rather than an automated system.
Because this policy describes behaviour rather than a business model, it changes rarely. When it does change, the revision date above moves and the summary section at the top of the page explains what was updated.
The bottom line
If you take one thing from this page, take this: the tools on this site process your input locally, the few network calls go straight to Discord or the webhook you choose, and the site itself stores nothing about you. There are no accounts, no profiles, no analytics, no advertising identifiers and no data brokers in the chain.
That design is not an accident. It is the reason the site can offer tools like a token decoder without asking you to trust us with anything - because there is nothing for us to receive. If a future feature would require collecting data, it will be announced here with the same level of detail before it ships, and it will be opt-in.
In short: this site collects nothing, stores nothing and sells nothing. If that ever changes, the change will be visible in this policy and explained in plain language on the page where the feature ships, not buried in a footnote. You can rely on this summary even if you do not read the rest of the document.