Contact

Write to support@gptcleanuppro.com. That address covers defect reports, questions about how a specific tool behaves, questions about the handling of submitted text, and anything arising from the privacy policy or the terms of service.

No response time is stated on this page. A commitment that cannot be verified from anything published here would be worth less than its absence, so none is made. What is within this page's control is telling you what makes a report actionable, which the following sections do.

Several categories of request do not apply to this service at all. There is no authentication system, so no credential to recover; no payment processing, so no invoice, refund or cancellation; and no stored profile, so nothing held under your name to correct.

A report containing these three elements can generally be investigated without a follow-up exchange.

Step 1

Identify the page by URL. Many routes on this site perform closely related operations with materially different behaviour, so the specific page is load-bearing.

Step 2

State the expected result and the observed result separately. The discrepancy between the two is the defect; either one alone is not.

Step 3

Give the browser and device, and whether the behaviour is deterministic or intermittent. An intermittent fault is a different class of problem from a consistent one.

Submitted text is not retained on this side. That is the correct privacy position and it carries a direct consequence for support: a report cannot be investigated by retrieving what you ran, because no record of any run exists. There is no log to consult, no stored input and no output history.

So the message itself is the entire evidence base. A minimal reproduction, two or three lines showing input and observed output, is worth considerably more than a full document, and it lets the problem be examined without anyone handling your real material.

Include

Page URL, expected result, observed result, and a minimal reproduction.

Include

Browser, device, and whether the behaviour reproduces consistently.

Exclude

Confidential or personal text. Electronic mail is an unencrypted copy held in a third party's system, so reproduce with substitute text.

Exclude

Screenshots intended to show invisible characters. They are by definition not visible in an image; the text itself is what carries the evidence.

A cleaner returning identical text is ordinarily correct. Where the input contained none of the characters that tool targets, an unchanged output is the accurate result rather than a failure to act, and treating it as a fault misreads what the operation does.

A cleaner removing more than anticipated is ordinarily correct as well. The space removers delete all whitespace and concatenate words rather than normalising doubled spaces, which their pages state before the operation runs.

A server tool refusing to run has reached a documented bound: 5 runs per rolling 24 hours, with each run accepting between 1 and 12,000 characters. Locally executed tools carry neither bound, because no server participates in them.

Whether a given text will pass a particular third-party detector. Those systems are operated by other companies and their behaviour changes without notice, so any answer would constitute a guess presented as a commitment.

Whether a specific use is permitted by an institution, employer or publishing platform. Their published rules govern, they are the only authoritative source for their own policy, and nothing run here alters an existing disclosure obligation.

Whether a specific text was produced by a person or a model. The analysis tools report signals observable in the text, which is evidence about the text and not proof of authorship. That is a property of the method rather than a limitation of the reply.

Direct these to the same address. The substantive answer is unusual enough to be worth stating in advance: there is almost nothing held to disclose, correct or erase.

No account exists, no profile is constructed, and text submitted to a server tool is written to no database, log or cache under this service's control. The single retained record is a counter enforcing the run allowance, keyed to the first 32 characters of a SHA-256 hash rather than to an address, and it expires automatically after 86,400 seconds. The privacy policy sets out precisely what that record contains and what it does not.

Every factual claim on this site is intended to be traceable to the implementation behind it: what an operation performs, whether anything is transmitted, and what bounds apply. That standard creates one specific and predictable failure mode, in which behaviour changes and the page continues describing the prior behaviour.

A page that no longer matches the code is treated as a defect rather than a question of wording, so a report identifying one is materially useful. Name the page and quote the sentence. Until it is corrected, the tool's observed behaviour is the authority, not the description.