This page is maintained by The Unwriter to answer common security and privacy questions about the app. It describes current practices and is not a certification or independent audit.
When you use The Unwriter, we store your Story Blueprint fields (title, theme, conflict, motifs), chapter text you write in the editor, and the coaching responses returned by the AI. These rows are scoped to a randomly generated owner key that lives in your browser's local storage.
We do not require an account, email, or other personal identifiers to use the app.
Manuscript and blueprint data is read and written only by our server-side functions. Row-level security is enabled on every table, and anonymous and authenticated database roles have no read or write access — only the server's privileged service role can reach the data, and it scopes every query by your owner key.
When you request a critique, the relevant excerpt of your manuscript and your Story Blueprint are sent to Anthropic's Claude API for analysis. The response is returned to your editor and saved as a coaching log tied to your owner key. Please review Anthropic's policies for how they handle API inputs.
The app is served over HTTPS. Application server logic runs on edge workers, and the database is managed by our backend provider with encryption in transit and at rest.
Because your data is tied to a browser-generated owner key, clearing your browser's local storage will disassociate this device from your existing workspace. To request deletion of stored content tied to a specific owner key, contact us at the address below.
If you believe you've found a security issue, please email security@theunwriter.com with details so we can investigate.
Last updated: June 2026. This page describes current app behavior and may be updated as the product evolves.