About DigiCruncher, a forum on AI writing tools
DigiCruncher is a forum for people who use AI writing and productivity tools and want straight answers about them. Someone picking a writing assistant for a small team. Someone whose own essay was flagged by a detector. Someone wondering whether the text they paste into a chatbot is used for training. You ask a specific question, and you get a specific answer that names the setting, the plan and the version.
The forum is independent and sits at the root of digicruncher.com. It is not a section of a larger site, and it does not speak for any tool vendor.
A new community, rebuilt in October 2026
There used to be another forum on this domain. It closed, and none of its posts, accounts or threads were carried over. What you see now is a new community, rebuilt in October 2026 on fresh software with a fresh start. Old links to the previous forum no longer lead anywhere, and we have not tried to recreate its content. Everything here was written for this forum.
What we cover
There are five sections.
- AI writing tools. ChatGPT, Claude, Gemini, Grammarly and other assistants: prompts, settings, editing workflows and getting output that sounds like you. This is also where humanizers are discussed, with a focus on honest use and disclosure.
- AI detectors. How detectors score writing, why they misfire on human drafts, what a flag means and how to document your process if you are flagged.
- Privacy and data. What tools do with what you paste in: training opt-outs, retention, workplace policies, client confidentiality and GDPR questions.
- Reviews. Side by side looks at tools based on documented features, published policies and repeatable tests.
- Help me choose. Tell us your job, budget and constraints and get a shortlist.
Who edits it
Two editors run the forum.
Nathan Cole is the editor. He writes the forum answers on writing assistants, detectors and humanizers. He runs each tool on his own drafts, reads the vendor documentation behind every claim, and says when a result depends on the plan or the model version.
Selin Arda is the privacy and data editor. She covers training settings, retention, workplace policies and data protection law. She works from privacy policies, help centers and official regulator guidance, and quotes the page she read.
Members answer questions too, and many of the most useful replies come from them. Staff replies are marked with the editor's name and role.
How answers are sourced and corrected
Tools change often, so we try to make every answer checkable. When an answer rests on a vendor's documentation, a published policy or a test someone can repeat, it says so and names the page or the steps. When it rests on experience, it says that instead. We state the plan, the model and the date wherever they matter, because an answer that was true for a free plan last spring may not be true today.
If you find a mistake, reply in the thread or write to hello@digicruncher.com. We fix the answer in place, add a short note saying what changed and when, and do not quietly rewrite history. A note beats a silent edit, because readers who acted on the first version deserve to know.
Links to tools, and what they mean
Some threads may link to tools, including tools that have a commercial relationship with us. When that is the case, the thread or review says so. Some links to tools carry tracking parameters so we can see which threads people find useful. These parameters identify the forum and the thread, not you, and following a link never costs you more. Commercial relationships do not decide what we recommend, and a tool does not get a better review because we have a link to it. Our rules for reviews, including disclosure, are in the guidelines.
What we are not
We are not a detector vendor, a school, an employer or a law firm. We cannot tell you whether a particular piece of writing was produced by an AI, and we do not accuse anyone. We do not coach people on deceiving teachers or employers. We do talk openly about using AI tools honestly and disclosing that use where it is expected.
Get in touch
Questions about the forum, corrections, takedown requests and anything else go to hello@digicruncher.com. The contact page explains what to include so we can answer faster. Read the privacy policy and the terms before you sign up.
New here? Start with the staff guide on what to check before you sign up for an AI writing tool, then browse the categories.
Who answers here
Nathan Cole
Editor, DigiCruncher
Nathan edits DigiCruncher and writes the forum answers on AI writing assistants, detectors and humanizers. He runs each tool on his own drafts, reads the vendor documentation behind every claim, and says when a result depends on the plan or the model version.
Selin Arda
Privacy and data editor
Selin covers what AI tools do with your text: training settings, retention, workplace policies and data protection law. She works from privacy policies, help centers and official regulator guidance, and quotes the page she read.