PocketAuthor is a workspace for planning, writing, revising, producing, and preparing a book for publication while keeping sources, manuscript structure, edition details, and release work connected.

Yes. The public writing desk stores a local recovery copy in your browser. Download important work and sign in to move it into an account-backed project.

PocketAuthor includes import workflows for existing manuscripts and source material. Always review detected chapters and preserve the original file until the import and backup are verified.

The core product is an author-controlled writing and publishing workflow. Model-assisted tools may be gated or unavailable depending on configuration, and suggestions should never replace author review.

No. Distribution capabilities vary by provider. PocketAuthor can prepare files, metadata, checks, and handoffs, but should only show a submission as accepted after the provider confirms it.

Yes. PocketAuthor models formats separately because identifiers, dimensions, covers, economics, and files can differ even when they share one manuscript.

No. A readiness check can identify common blockers, but printers and distributors apply their own current requirements. Review provider specifications and inspect physical proofs for print editions.

Separately marketed formats generally need separate product identifiers, subject to local rules and provider policy. Decide who owns each identifier before release.

Local-first writing and recovery are available on supported surfaces. Confirm the editor's offline state, reconnect before closing, and keep independent milestone backups.

The editor preserves recent changes and can queue supported work during connection loss. Watch the save indicator and use snapshots or downloaded backups for important milestones.

PocketAuthor includes contributor, comment, assignment, review, attribution, and agreement workflows. Live collaboration and external delivery depend on the specific feature and release state shown in the product.

PocketAuthor does not claim ownership of your original manuscript. Contributor contracts, source permissions, and third-party rights remain your responsibility.

Do not assume manuscript content is sent to a model. Provider-assisted features should disclose their state and require appropriate configuration and approval. Review the current privacy policy for governing terms.

Use project exports, snapshots, source archives, and release files at meaningful milestones. Local-only drafts also need a separate download or copy because browser storage is device-specific.

Yes. Account privacy controls provide export and deletion paths. Export what you need first and separately preserve any local-only drafts.

Include the page, what you expected, what happened, approximate time, browser or device, and any support reference shown. Do not email passwords, private keys, full manuscripts, or sensitive identity documents.