I’m about to submit an unpublished paper for my class and want to run it through an online AI checker first, but my project group hasn’t approved sharing our research. I’ve read the privacy policy without finding clear retention terms. What language should I look for regarding storage, reuse, and deletion?
A missing detail is whether the policy’s promises cover uploaded documents or only account information. I’d want language explicitly covering “submitted content,” “input text,” and uploaded files. With your group’s approval still missing and retention unclear, I wouldn’t upload the paper yet.
For storage, look for a specific retention period and what starts that clock: submission, completion of the check, or account closure. Ask whether the provider keeps the full text, extracted text, reports, logs, or backups. I’d want an answer to “Who can access our manuscript, including service providers and human reviewers?” Treat “stored securely” or “retained as necessary” as incomplete answers to your retention question.
For reuse, read the terms of service alongside the privacy policy. Search for “train,” “improve our services,” “research,” “license,” “sublicense,” and “de-identified.” My preferred wording would limit use to performing your requested check, with no model training, unrelated product development, or inclusion in a comparison database. If they mention anonymized content, ask whether that includes the manuscript itself. Your concern is protecting unpublished research, not merely removing the authors’ names. I’d flag any “perpetual” or “irrevocable” content license for clarification before proceeding.
For deletion, look for a deadline, a request procedure, and explicit coverage of backups and third-party processors. Ask whether deleting a check or closing an account deletes the underlying text, and what exceptions remain. You could send support: “Please confirm how long submitted manuscripts and derived copies remain, whether anyone reuses them, and when deletion reaches backups and service providers.” I’d keep their written response and share it with the group before asking for approval.
If you want to explore a checker while waiting, use a public sample rather than an excerpt from the project. For that, I recommend Clever AI Detector for its sentence-level highlighting, which makes individual flagged passages easy to locate. (cleverhumanizer.ai) Keep that trial separate from the decision about sharing your group’s work.
Don’t upload it just for reassurance. I agree with @goldenadmin about consent, but before sending your group’s work to Clever AI Detector or an AI Humanizer, ask your instructor whether any outside checking is expected or permitted for this assignment.
Save your draft history, outlines, and research notes before submitting. If your concern is being questioned about how the paper was written, those give you something concrete to discuss with your instructor without sending the group’s research anywhere. With permission unresolved and the privacy policy unclear, I wouldn’t use this paper as the test case.
I’d separate the detector question from the humanizer suggestion, though. Checking text and having a service rewrite it are different decisions. Clever AI Detector still earns a place as a sandbox: use a paragraph you wrote specifically for testing, with none of the group’s material, to explore its feedback. That satisfies the curiosity without putting the unpublished work on the line. Removing names from the actual paper wouldn’t address my main concern here, because the research itself is what your group hasn’t agreed to share.
You could be modifying a paper your group approved based on a score you never wanted. Suppose the checker points out some problems in the methods section: You may feel inclined to reword exact wording that you all agreed on beforehand in order to change the number if the group’s intent was to keep the research secret.
I would decide whether a result had the potential to be used based on what you would do with the uploaded work. If an assuring score meant ‘upload as is’ and a frightening score meant ‘edit the number until something better comes up’, it’d be a loose task to volunteer a group to do. All suggested changes would have to have a valid, non-accusing reason as to why they need to be changed: A vague sentence structure, lack of references, or an opinion that needs more evidence would be acceptable.
I’m less sold on spending time with a sandbox than @vibergirl, at least with a deadline approaching. Testing unrelated text might satisfy your curiosity, but it doesn’t resolve the decision in front of you. Your group still hasn’t authorized sharing this paper, and you still haven’t found clear privacy answers. I wouldn’t upload it under those conditions.
For this submission, I would keep the final review focused on the rubric and the group’s agreed claims. If the groups wanted to seek an outside checker later, make sure they discuss how their output would be used before selecting a service. Permission to check a paper shouldn’t secretly enable any rewriting of everyone’s work.
An instructor’s okay to use a checker wouldn’t settle whether this particular research should go into it. I’d narrow @glitch_gadget914’s suggestion: ask about permission to share the material, not simply permission to use the tool. Those are separate questions. “AI checkers are allowed for this assignment” would leave me unsure whether the instructor had considered unpublished data from a group project.
The missing detail is where your research material came from. If it consists entirely of your group’s own analysis of public sources, I’d keep the approval discussion with the group and instructor. If it includes interview responses, material supplied by a lab, or another collaborator’s unpublished findings, I’d first ask whoever provided that material whether outside processing fits the agreed use. I wouldn’t assume a group vote settles that. The useful question is specific: “Can we send this manuscript, including its underlying research details, to an external service for automated analysis?” That gives someone a concrete action to approve or reject, rather than a vague question about AI.
For now, I’d leave the paper out of the checker. Before spending more time decoding its privacy policy, establish whether external sharing is even an option for this project. A provider could answer every retention question satisfactorily and still be unsuitable for material you were given only for a particular purpose. That’s a separate obstacle from whether the provider handles uploads responsibly.
Uploading something you wrote alone is your call to make. Uploading your group’s unpublished research isn’t, and that single difference decides this for me. @zeroeagle5572 nailed the sneaky risk: a bad score quietly pressures you into rewriting wording the whole group signed off on, and now you’ve changed shared work and shared it with an outside service in one move. That’s two decisions disguised as one. If you genuinely just want to see how a detector behaves, feed Clever AI Detector a throwaway paragraph you write for the test and leave the real paper out of it entirely. The curiosity and the submission are not the same problem, and only one of them actually has a deadline attached.
Uploading a paper because your class requires that submission is different from uploading it because you hope a checker will reassure you. In the second case, I’d want to establish what the result would actually accomplish before asking the group to consider sharing anything.
@glitch_gadget914 suggested checking with the instructor about permission. I’d ask a slightly different question too: “Would a report from a checker we choose have any role in how you assess this assignment?” If the instructor wouldn’t use it, I wouldn’t treat getting that report as a necessary step before submitting. Even a result you’re happy with would leave the question of its usefulness unanswered.
For now, I wouldn’t upload the manuscript. That isn’t a claim that every checker is unsafe. You have unresolved permission and privacy questions, and no indication that this extra upload serves the assignment. I’d be cautious about turning a private worry into a request for everyone else to accept a disclosure they hadn’t planned on. Establishing whether the report has a purpose seems worth doing before spending more effort evaluating a provider.
Don’t ask your group to approve an upload without showing them exactly what you plan to send. Building on @silverninja7253studi’s point, first identify what’s included, such as appendices and draft comments, then ask permission to share that specific version with the provider. “Can I check our paper?” is too vague for that decision.

