Contact FreeHumanizeAI
Email [email protected] for product, account, privacy, billing, accessibility, or content questions. This address must be monitored by the site operator before the site is submitted for AdSense review.
Operator: FreeHumanizeAI
Contact email: [email protected]
Website: freehumanizeai.com
Postal address: Contact the operator by email for postal correspondence.
What to include
A useful support message identifies the affected page or tool, explains the expected result, describes what happened instead, and includes only the account or transaction information needed to investigate. Do not send passwords, one-time login codes, API keys, full payment card details, government identifiers, medical records, or confidential writing samples.
Product support
Include the tool name, page URL, browser, approximate time, selected mode, and the steps that produced the problem. Explain what you expected and what happened instead. A short non-confidential example can help, but remove names, account details, client information, unpublished research, and other private material. If the problem is intermittent, note whether refreshing or changing the input affected it.
Privacy requests
Use the subject “Privacy request” and state whether you are asking for access, correction, deletion, objection, restriction, portability, or another privacy right. Send the request from the email associated with the account when possible. We may ask for proportionate verification before disclosing or deleting account data. Do not attach identity documents unless the operator specifically requests a secure verification method.
Billing and credits
Include the account email, transaction date, plan or credit pack, amount, currency, tool, and a non-sensitive transaction reference. Never send a full card number, bank password, security code, or one-time authentication code. For a point question, copy the event type and timestamp from the account ledger. State whether the run failed, timed out, or returned a result that could not be used.
Editorial corrections
Include the page URL, section heading, the statement you believe is wrong, and a reliable source or explanation supporting the correction. Distinguish a factual error from a difference in style or opinion. We prioritize errors that could change a user's decision, misstate product behavior, weaken responsible-use guidance, or create an incorrect impression about an organization or source.
Accessibility
Describe the page, device, browser, assistive technology, zoom level, and task that was blocked so we can reproduce and prioritize the issue. Helpful reports explain the control or heading involved, the expected keyboard or screen-reader behavior, and what happened instead. You do not need to disclose a diagnosis or disability to report an accessibility barrier.
Security reports
Describe the affected feature and potential impact without accessing data that is not yours, disrupting the service, or publishing exploitable details before the operator can respond. Do not send active malware or credentials by email. A report should include safe reproduction steps and the minimum evidence necessary to understand the issue.
Response expectations
We aim to acknowledge ordinary support and editorial messages within five business days. Privacy or legal requests may require identity verification and additional time under applicable law. Sending a request does not guarantee a particular refund, content change, or detector outcome, but every complete request should receive a good-faith review.
Before contacting support
Check the relevant tool guide, the Credits page, Methodology, Privacy Policy, and current pricing before sending a message. Confirm that the browser is supported, the page was refreshed after an update, and the input is within the displayed word limit. Save a local copy of important writing before troubleshooting. Support cannot recover text that was never saved to an account or browser.
For sign-in problems, identify whether you used Google One Tap or an email code and include the non-sensitive error message. Never forward a one-time code. For model output concerns, describe the changed fact or lost detail rather than sending an entire confidential document. A minimal example is easier to investigate and safer for everyone involved.
Requests we cannot fulfill
Support cannot guarantee that text will pass an AI detector, conceal prohibited academic or professional assistance, create false evidence, remove lawful source attribution, or provide legal, medical, financial, or academic rulings. We also cannot disclose another user's data, override a school or employer policy, or accept payment credentials by email.
Language and record keeping
Support is currently designed around English-language requests. Clear messages in another language may be translated for handling, which can add time. We retain support records only as needed to answer the request, maintain security and billing records, document a privacy response, improve recurring issues, or meet legal obligations. The Privacy Policy explains the applicable categories and user choices.
Editorial and advertising inquiries
Clearly label proposals involving sponsorship, advertising, affiliate relationships, content licensing, or product access. We do not accept paid links disguised as editorial references, requests to copy third-party articles, or placements that would make an advertisement look like a Humanizer control. Any future commercial relationship must preserve editorial independence, disclose material connections where required, and comply with the site's privacy and advertising policies. General requests for backlinks without a relevant reader benefit may not receive a response.
Journalists, researchers, educators, and accessibility reviewers should identify their organization, deadline, intended use, and the specific claim or product behavior they want confirmed. We can explain documented features and policies but will not provide confidential user data, unpublished security details, or unsupported market-leading claims.