Scribo handles manuscript files, submission metadata, reviewer activity, and limited account information to keep the workflow legible. Privacy language should explain that operational reality without hiding behind generic software boilerplate.
Scribo stores the information needed to operate the manuscript pipeline: account identity, role membership, manuscript package details, submission records, review activity, and the status history that tells teams what happened and when.
The product uses this information to authenticate users, maintain role-appropriate access, route manuscripts through submission and review lanes, and preserve a trustworthy record of editorial actions over time.
Operational records should remain available long enough to support real editorial work, auditability, and user reference. Access is scoped by role so people see the context they need without exposing private author details more broadly than necessary.