Contact Us
Questions, bug reports, partnership ideas, or tool suggestions: we read every message. Email is the fastest way to reach us, and the form below opens your email app with the details filled in. There is no live chat or phone support, and there is no account to create.
A short message that says which page you were on and what you expected is far more useful than a long one that does not. The sections below cover what to send for each kind of request, and what happens after you press send.
What to contact us about
Most messages fall into one of these five buckets. Picking the closest one and putting the details in your first paragraph makes a reply much faster.
Bug reports
A tool that returned the wrong result, threw an error, or lost what you typed. Tell us which page you were on and what you did, and we can usually fix it.
Tool requests
A job you keep doing by hand that a small tool would handle. Describe the task and the format you need out of it, since that is what decides whether it can be built.
Corrections
A rule that changed, a guide that is out of date, or a link that goes nowhere. Screenshots of what you see next to what the page says help.
Privacy requests
Ask what contact information we hold, ask for it to be corrected, or ask for it to be deleted. We may need to confirm we are talking to the right person first.
Advertising
Questions about ads on the site, or enquiries about working together. The site is funded by display ads, and there is no paid tier to buy into.
Send a message
Tool ideas, bug reports, or general feedback. The form prepares an email for you to send from your own app, so nothing is delivered until you hit send there.
What to include in a bug report
- Which tool or page you were using, and the link to it
- What you expected to happen, in one sentence
- What happened instead, including any error message
- Your browser and device, for example Chrome on Android
- A screenshot if something looks broken rather than wrong
If the tool processes text you typed, include a short sample of it rather than the whole document. A few lines are usually enough to reproduce the problem, and it keeps your content out of the email.
One extra detail helps more than you would expect: whether it happens every time or only sometimes, and whether it changes with the length of the input. A bug that only appears on long text is usually about a limit, and a bug that appears on some inputs and not others is usually a rule that needs checking.
What to include in a tool request
The most useful requests describe the job rather than the tool. A few lines is enough if they cover these points.
- What you are trying to do, in the words you would use with a colleague
- What you have to start with, since that decides what the tool can read
- What you need to end up with, and the exact format you paste it into
- Where the result gets used, such as a Discord message or a spreadsheet
- How you handle it by hand today, if you have a method that works
Include the annoying edge case too. The part that never behaves the way you expect is usually where the useful detail sits, and it is what decides whether a small tool can do the job at all.
If you have already solved it by hand, say what the method was. A spreadsheet formula or a short script tells us what rule the tool should follow, which makes the difference between a request we can build and one we cannot.
What to include in a correction
Something on the site no longer matches what the platform does. Send these and we can correct it.
- The link to the page or guide that is out of date
- What the page currently says, quoted rather than summarised
- What the platform does now, and where you saw it
- A link to the platform documentation, if there is one
- The date you checked, since these things change quietly
For a guide, it helps to say which step no longer matches. For a tool, send the input and the result it gave you, because that is what lets us reproduce it.
Privacy and data questions
Most tools never send anything anywhere. The text, images, and numbers you enter are processed in your browser and stay on your device. Three of the tools work differently, and each one says so on its own page.
- The Discord ID lookup sends the numeric ID you enter to our server so it can ask Discord for public details. The ID and the result are not stored in a database.
- The Discord profile viewer stores a short-lived access token in a secure cookie while you are connected, and removes it when you disconnect.
- The contact form does not deliver your message to our server. It opens your email app with the text filled in, so the message only reaches us if you send it from there. When reCAPTCHA is enabled, a verification token goes to us and to Google before that happens.
You can ask what contact information we hold about you, ask for it to be corrected, or ask for it to be deleted. We may need to confirm we are talking to the right person before we act on it. The Privacy Policy sets out the details in full, including the cookies, the analytics services, and how long rate limit records are kept.
What happens after you send a message
A person reads it. There is no ticket number and no automated first reply that pretends to be help.
- A bug report gets checked against the input you sent. When the fix goes in, the page is corrected and the change is noted on the tool itself.
- A correction gets applied to the page, and guides show a new updated date when the text changes.
- A tool request gets an honest answer about whether it fits what the site builds, even when the answer is that it does not.
- A privacy request gets a reply about what is held and what can be removed.
We will not promise a feature or a release date, because those depend on things that are not ours to decide. What we can promise is that the message gets read and answered.
Response time
We read every message and reply as soon as we can. Most questions get an answer within a few business days, and a bug report usually takes a little longer because it needs checking against the tool. There is no support queue with ticket numbers, so there is no guaranteed deadline. If something is urgent, say so in the subject line and it will be picked up sooner.
Before you write
Many tools run in your browser only. We cannot recover text you pasted into a tool after you close the tab. For privacy questions, see our Privacy Policy.
It is also worth checking the tool page itself first. Each one lists what it does, what it does not do, and the limits it works within, which often answers the question before you need to ask it. The guides cover the reasoning behind several of them in more detail.
Frequently asked questions
Do you answer every message?+
Every message is read by a human. We cannot build every suggestion that arrives, and we will not promise a feature or a date. What we do instead is answer the message, so you know whether the idea was considered and what would make it workable.
My tool gave the wrong answer. Can you fix it?+
Usually, yes. Send the input, the output you got, and the output you expected, and we will look at the tool. When the result depends on a rule that Discord, Roblox or another platform has since changed, the page gets corrected and the change is noted on the tool itself.
Can I advertise on Tolz.me?+
Ads on the site are served by Google AdSense, so there is no direct slot to buy and no rate card. If you run a business that produces tools for the same audience, we are happy to hear the idea, but we cannot sell placement directly.
Do you store what I paste into a tool?+
No. Almost every tool runs entirely in your browser, and the text, images and numbers you enter never reach our servers. The exceptions are the Discord ID lookup, the Discord profile viewer and the contact form, and each one says so on its own page.
How quickly does a broken tool get fixed?+
A tool that has stopped working for everyone is the priority, because it is the version people notice first. A result that is wrong for one input takes longer to pin down, since it usually means tracing back to the rule the tool follows. There is no deadline we can commit to, but you will get an answer about what we found.
Can you set up or fix my Discord server for me?+
No. We can point you to the right setting, the right tool, or the guide that covers it, but we do not administer servers, accounts, or bots on your behalf. None of the tools need access to your account either, with the optional exception of the profile viewer, which only reads your own profile.
I never got a reply. What should I do?+
Check the spam folder first, since automated replies sometimes land there. If it still has not arrived, send the message again and put the link to the page in the subject line so we can find it quickly.