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. AI processing is handled through external providers subject to their applicable data-use and retention terms.
Overview
Every project is protected with per-user row-level security, encrypted in transit and at rest, and gated by explicit membership rules. When you use AI-assisted features, relevant content is sent through the platform's AI gateway to an external model provider for processing under that provider's applicable terms.
Why writers use it
- Project access is role-scoped. Authorized collaborators can access content you share with them, and limited operational or service-provider access may occur when reasonably necessary to provide, secure, support or comply with law.
- Data is encrypted in transit and at rest.
- Content sent for AI features may be processed and temporarily retained by external providers under their applicable service, safety, and data-retention terms.
Key capabilities
- Row-level security on every table
- Role-scoped collaboration
- Selected administrative actions are logged
- AI processing routed through the platform's secured server-side gateway
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. Project access is role-scoped, and limited operational or service-provider access may occur when reasonably necessary to provide, secure, support or comply with law.