Private workspace by default
Uploaded manuscripts, evaluations, reports, revision decisions, and prepared package materials belong inside the author’s account workspace unless the author deliberately exports or shares them.
Security & Access Controls
Private by default. Shared by author action.
RevisionGrade is designed as a private manuscript workspace, not a public posting platform. The security model is built around clear ownership, controlled access, deliberate exports, bounded retention, and keeping operational internals away from normal author-facing surfaces.
Plain-language posture
Your manuscript stays private unless you choose a controlled outward action.
Evaluation and revision happen inside the account workspace.
Exports and controlled package access happen by author action.
Retention has a defined clock, warning period, and renewal path.
Security contract
Four boundaries protect the author-facing experience.
The important question is not whether security language sounds reassuring. It is whether the product keeps manuscript access, sharing, and operational authority inside clear boundaries.
Author-controlled outward movement
A download, prepared submission package, or controlled Storygate workflow is an intentional boundary crossing. Completing an evaluation does not publish, index, or automatically distribute the manuscript.
Controlled professional access
Storygate-style access is creator-approved, access-controlled, and logged. Controlled manuscript discovery is not public browsing, and access does not transfer authorship or revision authority.
Operational details stay internal
Raw worker traces, internal job identifiers, provider diagnostics, maintenance controls, and machine-facing failure details belong in operational or support surfaces rather than the normal author experience.
Retention & deletion
Retention is governed, not indefinite.
Customer-content retention is designed around a two-year active-use clock, advance warning, a Retain path, and fail-closed deletion safeguards.
Customer content follows a two-year active-use retention clock.
A warning is required 30 days before content becomes eligible for automated retention deletion.
Choosing Retain—or qualifying new activity—renews the retention clock and clears stale deletion eligibility.
Legal holds and last-second activity checks block automated deletion when preservation is required.
What this page does not claim
Security language should be precise enough to trust.
RevisionGrade should describe controls that exist and avoid certifications, guarantees, or exposure models it cannot substantiate.
No public manuscript indexing by default.
Completing an evaluation does not automatically publish the manuscript or make it discoverable.
No public exposure of raw operational traces as part of the normal author experience.
No claim of SOC 2 or another formal security certification unless it has actually been obtained and is current.
No unsupported promise that security controls eliminate every possible risk.
No substitution of this page for the binding Privacy Policy or Terms of Service.
Security FAQ
Direct answers about access, retention, and exposure.
This is a plain-language product trust page. Binding legal terms remain in the Privacy Policy and Terms of Service.
Can my manuscript appear in public search?
Not by default. Manuscripts are private author materials. Exporting a file or approving a controlled package workflow is an author-directed action, not automatic public indexing.
What happens to my content if I stop using RevisionGrade?
RevisionGrade uses a two-year active-use retention policy for customer content. The retention design requires a 30-day warning before eligible automated deletion, and Retain or qualifying new activity renews the clock.
Does downloading a report make it public?
No. A download is a private author-facing export. What happens to that file afterward is controlled by the author.
How is Storygate access different from public posting?
Storygate-style access is intended to be creator-approved, controlled, and logged for appropriate publishing professionals. It is not an open manuscript directory.
Where do technical failure details belong?
Technical diagnostics belong in support, admin, and operational views. Normal author-facing pages should use clear status language without exposing raw internal traces.
Does RevisionGrade claim a formal security certification?
Not on this page. Certification claims such as SOC 2 should appear only when they are independently verified, current, and applicable to the service being described.
Trust by design
Protect the manuscript while the system diagnoses it.
Continue to Privacy & Research Controls for manuscript-use and research boundaries, or begin an evaluation when ready.