Protection
Security
Your manuscripts belong to you.
Every project is protected with per-user row-level security, encrypted at rest, and gated by explicit membership rules. Your work is never used to train third-party models.
Overview
Every project is protected with per-user row-level security, encrypted in transit and at rest, and gated by explicit membership rules. Your manuscripts are yours — never used to train third-party AI models.
Why writers use it
- Only you and your collaborators can see your projects.
- Data is encrypted in transit and at rest.
- AI providers never retain your content for training.
Key capabilities
- Row-level security on every table
- Role-scoped collaboration
- Audit logging for administrative actions
- No-training data agreements with AI providers
Problems it solves
- Not knowing whether a cloud writing tool is training on your book.
- Losing control of who can see a work in progress.
- Sharing a project and accidentally exposing every other project.
- No audit trail for administrative changes.
How it fits the Mastering Your Scenes Methodology
Trust is a precondition for honest writing. Security exists so you can put unfinished work into the studio without ever wondering where it might end up.