Know what happens
before you submit text
The detector sends submitted text to an external detection service for analysis. Use it with non-sensitive material and review the privacy policy before relying on it in a business, school, or regulated workflow.
External analysis
When you run a check, the text is sent to a third-party detection service to produce the result. Do not paste confidential, personal, or regulated information.
Account and contact data
Account creation requires a name, email address, and password. The contact form records the details you provide and technical information associated with the request.
High-impact use needs review
A detector result should not be the only input to a disciplinary, employment, admissions, or publishing decision. Pair it with human review and a documented process.
A clear data-flow starting point
The detector accepts text from the website and sends it to the detection provider for analysis. This page does not make a zero-retention, end-to-end encryption, or certification claim on behalf of that provider.
- Use the privacy policy: It explains the categories of information handled by the site and how to contact the team with a request.
- Keep sensitive material out: Do not paste personal data, private documents, or confidential work into a public detector.
- Ask before scaling: Contact the team before building a workflow that involves sensitive, regulated, or high-impact decisions.
A short checklist before using a detector
Security and privacy depend on the document, the people involved, and the way a result will be used.
| Question | Why it matters |
|---|---|
| Is the text confidential or personal? | If yes, do not submit it without an approved data-processing workflow. |
| Who can see the result? | Limit access to people who need it and make responsibilities clear. |
| What happens after a result? | Write down the follow-up process and give the affected person a way to provide context. |
| Could the result affect someone’s opportunity? | Use more than one source of evidence and keep the final decision with a qualified person. |
Responsible use is more than a badge
A security page should tell you what is known, what is not claimed, and what you should review before sharing text. For sensitive use cases, the right answer may be a separate approved process rather than a public web tool.
Read the data notice
Use the privacy policy to understand the information collected by the site and how to make an inquiry.
Review the recipient
The detection service receives submitted text to return an analysis. Do not assume a public tool fits every data class.
Use human review
A detector result should prompt review, not independently determine a high-impact outcome.
Security FAQ
Where does text go when I run a check?
Text submitted through the detector is sent to an external detection service to produce a result. Do not submit confidential, personal, or otherwise sensitive material.
Should I submit sensitive text?
No. Review the privacy policy and your organization’s requirements first. Contact the team before designing a workflow involving confidential, personal, or regulated material.
What information is collected when I contact the team?
The contact form collects the details you enter, plus technical context such as the IP address, user agent, browser, platform, referrer, and page URL associated with the request.
Can a detection result guarantee a security or privacy outcome?
No. A detector result is separate from security and privacy review. For decisions involving sensitive data, follow your organization’s security, legal, and privacy requirements.
Questions about your use case?
Contact the team before submitting sensitive material or building a workflow that needs a formal privacy, security, or data-processing review.
Contact the team