Your writing is yours. Know where the data lives.
This notice describes the new Publishify test platform. The legacy Studio and MCP plugin do not have the same data flows.
Updated: 13 November 2026
Guest drafts
Guest books are saved in the browser’s local database. Clearing browser data can remove these drafts; keep independent exported copies.
Accounts and server sync
Account code uses passkeys and recovery codes. Server records include user details, passkey public keys and hashes of session/recovery tokens. Account sync also stores manuscript text in server-side book storage; acceptance tests are ongoing.
Editorial processing
Live reviews are disabled. When enabled, selected text will be sent to a model service with explicit consent; temporary review copies are designed for deletion after the job. Reports may include short source quotes. We do not promise exact deletion times before retention and cleanup testing is complete.
Google and Drive
If you choose Sign in with Google, we receive only your name, email address and Google’s stable account ID; your Google password never reaches Publishify. If you connect Google Drive, your books are written from your browser straight to a Publishify folder in your own Drive as Markdown files, without passing through Publishify’s servers. The app can see only the files it created in your Drive. You can disconnect at any time; the files in your Drive stay yours. This marketing site does not collect Google keys or manuscript text.
Dictation
Using dictation may send audio to the browser’s speech-recognition service. Availability depends on the browser and device.
Exported files
You decide where and with whom to share an exported file. If you upload it to another service, that service’s privacy and publishing terms apply. Publishify does not provide hosted reading pages or store distribution.
Deletion and support
Book deletion and cleanup queues are implemented; complete account deletion is unfinished. Do not use the test workspace as your only archive.