R

Privacy & Research Controls

Manuscript trust is part of the product.

RevisionGrade is built around a simple boundary: your manuscript is not raw material for public exposure. The system may diagnose, recommend, and help package the work, but the author controls visibility, revision decisions, and the path from report to submission.

Plain-language standard

Author-owned. Evidence-led. Controlled by consent.

Manuscript diagnosis starts with the submitted text.

External research, when used, should be bounded to context and plausibility.

Revision recommendations remain proposals until the author decides what happens next.

Trust principles

Four rules govern manuscript handling.

These are product promises for how RevisionGrade should treat submitted prose, evaluation evidence, external context, and downstream manuscript packages.

Manuscript sovereignty

The manuscript remains the author’s creative property. RevisionGrade evaluates submitted text to produce diagnosis, reports, and revision options; it does not claim authorship or replace the writer’s judgment.

Manuscript-first analysis

Evaluation should begin with the submitted pages, not internet assumptions. External context may support classification, market shelf, or comparables, but it must not override the manuscript evidence.

Research by permission and purpose

External research should be bounded to a clear purpose: genre context, public-domain comparison, market positioning, or factual plausibility checks. It should not become broad manuscript sharing.

Author-controlled visibility

Storygate Studio and Agent Readiness materials should remain controlled surfaces. Manuscript packages are not meant to become publicly indexed pages or open browsing inventory.

Research controls

External context should be bounded, not open-ended.

A manuscript evaluation should not become an uncontrolled web search. Research modes should be explicit, purposeful, and subordinate to the text.

Default trust posture

Manuscript-only mode

The report relies on the submitted manuscript and RevisionGrade’s editorial criteria. This is the safest mode when the author wants diagnosis without external context.

Optional support

Bounded context mode

Public information may support genre, shelf, comparables, or factual plausibility checks. The purpose should be clear and limited, and the manuscript remains the primary authority.

Author-controlled output

Package-preparation mode

Query materials, synopsis, comparables, author bio, and Storygate package text may be prepared from the report and author-approved materials rather than exposed automatically.

Manuscript lifecycle

What happens after an author submits work?

The product path should stay understandable: upload, evaluate, revise by decision, then export or package only when the author chooses.

01

Upload or paste

The author submits writing for evaluation through the product workspace.

02

Evaluate

RevisionGrade produces diagnosis, scores, evidence, report sections, and revision priorities based on the submitted text and selected workflow.

03

Revise

Recommendations become author-controlled decisions: accept, keep original, reject, defer, write custom, or use a governed TrustedPath flow where available.

04

Export or package

Reports and prepared materials may be downloaded or assembled into manuscript-facing submission assets under the author’s control.

Guardrails

What RevisionGrade should not do.

Clear negative promises are part of trust. They prevent the product from drifting into public exposure, unsupported market claims, or blind rewriting.

No public indexing of manuscripts by default.
No unsupported promise of publication, agent interest, or market outcome.
No blind rewriting that overwrites the author’s original manuscript.
No treating external search results as stronger than manuscript evidence.
No broad screen, film, TV, or adaptation routing until those workflows exist.
No final revision without author review or an explicit governed automation path.

Privacy FAQ

Direct answers for manuscript trust.

This page is intentionally plain-spoken so authors can understand the trust model before uploading serious work.

Are manuscripts used to train public AI models?

RevisionGrade’s public trust posture is no: submitted manuscripts are author-owned creative work and are not positioned as model-training material. They are used to generate the requested evaluation, report, revision guidance, and author-controlled package outputs.

Can RevisionGrade use external research?

Only in bounded ways. External research should support context such as genre, comparables, public-domain reference, market shelf, or factual plausibility. It should not replace evidence from the manuscript or become uncontrolled manuscript sharing.

Can I keep an evaluation manuscript-only?

Yes. Manuscript-only analysis is the safest default framing: the report reads the submitted text through RevisionGrade’s criteria without relying on outside material for the core diagnosis.

Does Storygate make my project public?

Storygate is intended as controlled manuscript access for readiness-vetted book projects and verified publishing professionals, not public posting. Project visibility should be creator-approved and access should be logged.

Who decides whether a proposed revision becomes part of the manuscript?

The author does. RevisionGrade may diagnose, recommend, and organize repair opportunities, but author choice governs what enters the manuscript or package.

Is this a legal privacy policy?

No. This is a plain-language product trust page explaining the editorial and research-control posture. Formal account terms and privacy policies should govern legal specifics.

Author control

Diagnosis should make the author more informed, not less in control.

Read the methodology next, or begin with a manuscript-only evaluation when you are ready.