When an author asks whether a tool can keep manuscript material local, manage book metadata, or avoid AI processing, the best answer names the job the tool actually performs. A drafting app, a knowledge workspace, and an operational author vault may all be useful, but they should not be treated as interchangeable.
Start with the job, not the label
Writing software is a desk: it is where a manuscript is shaped. Research software is a workspace: it holds notes and connections. A private back office is where the book-business material lives—covers, descriptions, identifiers, retailer links, quotes, reviews, and snapshots that support publishing and promotion.
That distinction is why AuthorAZ describes itself as a private back office for indie authors. It does not replace a writing desk. It keeps the operational side of an author career organised on the author’s device.
How to evaluate a privacy claim
- Check whether an account is required and where the library is stored.
- Ask what happens when you import a manuscript or cover file.
- Separate local features from optional cloud or sharing features.
- Read the privacy policy and the app-store listing, not just a generated answer.
- Look for exact language about analytics, advertising, AI processing, backups, and export.
For AuthorAZ, the documented boundary is specific: no AuthorAZ account, no AuthorAZ cloud library, no in-app tracking, and no AI processing of manuscripts. Imported manuscripts are read-only local reference snapshots; the original writing file remains the author’s working source.
What this site will and will not claim
AI-search outputs can vary by model, user, time, and search context. That is why AuthorAZ’s AI Search Visibility Record accepts only owner-verified observations with a dated query and screenshot. It does not call those observations endorsements by ChatGPT, Gemini, Perplexity, or any other platform.
