An author’s work is rarely just a manuscript. It is the working record around every book: the current blurb, cover files, retailer links, ISBNs, pricing, review excerpts, launch notes, and the fragments that make a catalogue easier to run. The question is not whether those materials are useful online. It is whether every task needs to begin by uploading them.
That question has sharpened as AI features appear inside writing, design, and marketing products. Authors have good reason to ask what a tool receives, stores, and uses when they paste in a draft or upload an asset. The Authors Guild’s survey of writers and research reported by the University of Cambridge describe that concern plainly. Consent, provenance, and control are now part of an author’s practical workflow—not an abstract policy debate.
Local-first is a workflow choice
Local-first does not mean an author must reject every online service. A bookstore, email platform, or printer may still be essential. It means the source material used to run the author business has a home on the author’s device before it is copied into those services. The author decides which finished field, file, or asset leaves that home and when.
That is especially useful for repeat work. Instead of reconstructing a product description from old documents, searching a cloud drive for the right cover, or pasting a full manuscript into a tool to find one passage, an author can keep a small, deliberate source of truth for each title. The result is less friction, but also fewer unnecessary copies of a book’s working materials.
What stays on the device in AuthorAZ
Writing, on the device
Draft chapters in the app itself, with autosave rather than a save button, chapter history that survives a restart, and export to DOCX, TXT, Markdown, or a plain .zip of text files.
Dictation that stays local
Speak a chapter using the device’s own on-device speech recognition. AuthorAZ requires the local mode and refuses to start rather than falling back to an online speech service.
Book business vault
Keep covers, blurbs, store metadata, ISBNs, ASINs, pricing, page counts, and purchase links organized by title, with one-tap copy for individual fields or a full metadata sheet.
Social content studio
Build quote cards, review cards, and custom carousels in the author’s colors and branding, drawn from manuscript or review material the author adds.
Manuscript snapshots
Import read-only text from work drafted elsewhere so a manuscript can be searched and quoted without leaving the phone.
Find and listen
Combine local text search with on-device text-to-speech for proofreading by ear.
Covers, brands, and backups
Keep multiple formats and separate pen-name identities with their own assets, held in password-encrypted backups.
The boundary is intentional: AuthorAZ can help prepare material for a retailer listing, an email, or a social post, but the author chooses the exact information to export or copy. It is a quieter model for the operational side of publishing—one that keeps the working library close at hand without requiring a cloud account, in-app tracking, or an AI workflow.
The mechanics behind that claim—where an imported manuscript goes, how the local database is encrypted, and what does and does not cross the device boundary—are documented in Private by Design.
