Where to write
How to reach GPTCleanupApp
Write to support@gptcleanupapp.com. Use it for bug reports, questions about how a tool works, questions about what happens to text you paste in, and anything about the privacy policy or the terms.
No reply time is promised on this page, because a promise it cannot keep would be worse than none at all. What does make a difference is how much the message gives you to work with, which the next section covers.
- Good reasons to write
- A tool behaving differently from what its page describes, a page that states something untrue, or a question about your data.
- Things that do not exist here
- No login to recover, no password to reset, no subscription to cancel, no invoice to query. None of that applies to this site.
- Worth checking first
- The tool's own page. Three of the most common surprises are the tool working correctly, and they are listed further down.
Workflow
How to report a problem in three steps
A report carrying these three things can usually be acted on straight away.
- Step 1
- Give the page URL. Plenty of tools here do similar-sounding jobs in different ways, so the exact page matters.
- Step 2
- Write what you expected, then what actually happened. Two sentences, and the gap between them is the bug.
- Step 3
- Add your browser and device, and whether it happens every time or only sometimes.
Detail
What makes a report worth sending
Nothing you paste into a tool is kept on our side. That is good for your privacy, and it means a report cannot be checked by looking up what you ran, because no record of it exists anywhere. Whatever is in your message is everything there is to work from.
A short example that reproduces the problem is the most useful thing you can send: two or three lines showing what went in and what came out beats the whole document every time.
- Send
- The page URL, what you expected, what happened, and a short reproduction.
- Send
- Browser and device, plus whether it is consistent or intermittent.
- Do not send
- Confidential or personal text. Email is a copy sitting in somebody else's inbox, so reproduce the problem with throwaway text.
- Do not send
- Screenshots of invisible characters. They do not appear in an image, so paste the text itself.
Often quicker
Three surprises that are the tool working correctly
A cleaner that seems to have done nothing has usually done its job. If your text carried none of the characters it targets, the output matches the input exactly, because there was nothing to take out.
A tool that stripped more than you wanted is usually also correct. The space removers remove every space and join your words together rather than tidying doubled ones, and each page says so before you run it.
An AI tool that stops has hit its allowance: 5 free runs per rolling 24 hours, taking 1 to 12,000 characters per run. The browser-based tools have no limit, because no server is involved in those.
Being honest
Three questions no reply can answer
Whether your writing will get past a particular AI detector. Those systems belong to other companies and change without warning, so any answer would be a guess dressed up as a fact.
Whether your school, employer or platform allows a given use. Their rules decide it, they are the only reliable source for their own policy, and running something here does not change what you have to disclose.
Whether a specific text was written by a person. The analysis tools report signals visible in the text, which is evidence about the text rather than proof of who produced it.
Your data
Asking about data held about you
Same address. The honest answer is unusual here and worth knowing before you write: there is almost nothing held to show you or delete.
No account exists, no profile is built, and text you submit is never written to a database or a log. The one record kept is a counter enforcing the daily allowance, keyed to a truncated hash rather than to you, and it expires on its own inside 24 hours. The privacy policy spells out exactly what sits in it.
Accuracy
If a page here is wrong about its own tool
Every factual claim on this site is meant to trace back to the code behind it: what a tool does, whether it uploads anything, what the limits are. That leaves one specific way to be wrong, where a tool changes and its page keeps describing the old behaviour.
A page that no longer matches the code is a defect and gets rewritten rather than defended, so reporting one is genuinely useful. Name the page and the sentence. Until it is fixed, trust what the tool actually does over what the page claims.