Raw uploaded DOCX bytes are parsed for the request and are not stored by the workspace data store.
Public Beta Privacy Notice
Frame treats manuscripts as sensitive research material. This notice explains the data used by the current free public beta, its retention limits, and how to request deletion.
A tenant-scoped PDF preview may remain in temporary runtime cache for up to six hours.
Saved parsed text, profiles, routes, reports, notes, and project records are tied to the authenticated account.
Data we process
Account data can include email, display name, institution, role, password hash, session records, usage counters, and project ownership. Manuscript processing can include filename, extracted text, title, abstract, keywords, sections, references, study profile, parse signals, routes, reports, notes, and saved outputs. Security and operations logs may include IP address, user agent, route, timestamp, status, timing, and trace identifiers.
Why we process it
We use the data to authenticate accounts, parse manuscripts, generate journal routes and revision guidance, save user-requested workspace records, enforce allowances, prevent abuse, investigate failures, secure the service, and measure beta reliability.
Storage and isolation
Raw uploaded file bytes are not kept in the workspace store. Derived manuscript text and outputs may be stored when they are attached to an account project or explicitly saved. Public-beta workflow and preview access is authenticated and account-scoped; operator access is limited to service operation and troubleshooting.
Retention and deletion
Temporary PDF previews expire after up to six hours. Eligible history and output cleanup uses a 90-day default threshold, but the beta does not yet provide self-service deletion and entire active account or project records may remain until an operator processes a request. Ask for account, project, or manuscript-data deletion at ergfurkancangi@gmail.com; identity verification may be required.
Sharing and external services
Frame does not sell manuscript or account data. The service may use infrastructure providers needed to host, secure, back up, and monitor the deployment, and public scholarly metadata providers to maintain the journal catalog. The optional external generative-AI quality layer is disabled by default for this public-beta configuration; this notice must be updated before manuscript content is intentionally sent to such a service.
Security and beta caution
Frame uses authenticated sessions, tenant checks, host and origin controls, restricted operator routes, and transport security when the production HTTPS deployment is configured. No online service can promise absolute security. Do not upload identifiable patient data, credentials, private keys, or material you are not authorized to process.
Your choices and contact
You may stop using the beta, export available project data, or request access, correction, or deletion by emailing ergfurkancangi@gmail.com. Material notice changes will be published here with a new effective date.