Ownership
You own the creative output you generate, subject to provider/platform terms.
- Keep provider/platform terms in mind.
- Do not treat product copy as legal advice.
- Export copies of finished work before deleting projects.
Trust and rights
FictionOS is designed so writers can keep control of their work.
The trust story is simple: bring your own key, export your manuscript, preserve revision history, delete projects, and use disclosure-support language instead of platform promises.
BYOK
Your model account
Bring your own OpenRouter key; FictionOS does not mark up model usage.
Export
Portable work
DOCX, TXT, EPUB, manuscript, analysis, architecture, and JSON backup surfaces.
Disclosure
Safer wording
Designed to support AI-assisted disclosure workflows.
Inputs
Premises, manuscripts, voice samples, and project notes are account-scoped work inputs.
Outputs
Generated prose remains exportable, with ownership phrased alongside provider/platform caveats.
API keys
OpenRouter keys are encrypted before storage and used server-side for model calls.
Exports
DOCX, TXT, EPUB, manuscript, analysis, architecture, and JSON backup support portability.
Deletion
Projects can be deleted; export before deletion if you need an offline copy.
Disclosure
Designed to support AI-assisted disclosure workflows.
Privacy
Project data is account-scoped, API keys are encrypted before storage, and public copy should avoid implying that third-party providers have no independent data policies.
Disclosure support
The right public claim is "designed to support AI-assisted disclosure workflows." The wrong public claim is suggesting any marketplace approval outcome is certain.
Publisher/studio diligence
Revision history, exportability, quote-vs-actual cost tracking, and human approval flows make the product more serious for professional workflows.
This page deliberately avoids legal promises. That is a feature, not a weakness: credible trust copy is careful copy.