Pre-release notice · pilot version: pilot-2026-11-05 · Effective November 5, 2026

Privacy

Manalytics, LLC operates Folio. Folio is designed to keep research correspondence and manuscript history private. This notice describes the intended first hosted release and must receive legal review before public launch.

Information Folio handles

Folio may store account identifiers, identity-provider issuer/subject identifiers and observed email, your dated Terms acceptance and Privacy acknowledgement, researcher profiles, paper and authorship records, submission histories, reminders, settings, and files or messages that you deliberately import. Journal correspondence can contain names, email addresses, manuscript details, reviewer comments, and private action links.

How information is used

Information is used to maintain your research portfolio, reconstruct submission histories, generate requested exports, deliver reminders, secure the service, and diagnose failures. Automated extraction creates proposals for review; it does not silently replace confirmed history.

Sharing and visibility

Research records are private by default. Authorized collaborators may see shared work records according to their membership role, but private notes, mailbox evidence, account settings, and reviewer-service material remain account-specific unless an explicit product control says otherwise. Folio does not sell personal information.

Service providers and measurement

The current hosted pilot uses Auth0 for sign-in and Railway for application and PostgreSQL hosting. Other processors for email delivery, error monitoring, and backups require verification before their use is described as active. Optional analytics will remain off until a privacy-reviewed, metadata-only implementation and appropriate choices are in place. Manuscript titles, email bodies, reviewer comments, action links, and uploaded files must never be analytics properties.

Security and retention

The hosted pilot requires encrypted transport, server-side sessions, and account-scoped access controls. Backup configuration, storage region, retention periods, and deletion automation still need verification and documentation. No system can guarantee absolute security; Folio will document incident and recovery procedures before public launch.

Your choices

You can correct confirmed records without erasing their provenance, control profile visibility, export account data, revoke sessions, and disable notifications. Hosted account deletion, evidence-retention controls, and a support contact must be operational before public sign-up.

Notice changes and contact

Folio will show a revised notice before requiring acknowledgement of a materially changed version. A dedicated privacy contact and request procedure are not yet published; this is a blocker for open self-service registration. The pilot does not intentionally use third-party cross-site advertising trackers. Any future tracker or optional analytics must be disclosed here before it is enabled.