Legal
Terms, privacy, and what leaves your machine
Two of the three below are documents a lawyer has to write. The third is a plain-language summary that can be written from how the software actually behaves, and it is written.
Plain-language summary
Your books stay with you
Everything the studio produces lives in a volume on the server you deployed. There is no account on our infrastructure and no copy of your material on it.
One outbound path you choose
Book text and prompts go to the AI provider whose key you supplied, and to the render, training, transcription and speech hosts you pointed the server at. Nothing else leaves.
One form, one third party
Every page here is static and contacts nobody, with one exception: the founding-teams application on /betais a JotForm embed, so loading that page contacts JotForm and submitting the form sends what you typed to them as well as to us. No other page on this site loads anything from anyone.
No telemetry to us
The desktop app and the server report nothing to us. They do record performance telemetry for you — it is written locally, shipped to your own server, and goes no further. An air-gapped install is a supported configuration rather than a workaround.
What this page does not decide for you
Whether you hold the rights to a book, a voice or a piece of footage is yours to establish. The studio records where material came from; it does not tell you whether you were allowed to use it.
End-user licence agreement
Not written yet
Scope of the licence, what an organisation may do with the Core and with each product, what happens on lapse, and the warranty position.
Needs: A lawyer. Nothing here is drafted by an assistant, and the site will not ship a template EULA with the product's name substituted in.
Privacy policy
Not written yet
What this website collects (currently nothing), what the software transmits (listed above), and how to ask about either.
Needs: A lawyer, plus a decision on whether this site ever runs analytics. Today it runs none. The only third party involved at all is JotForm, on the /beta application form, which will need naming in a real privacy policy.
Third-party licences
Not written yet
The open-source components in the desktop Core and the server, with their licences.
Needs: The generated dependency licence report from the product build, published as an artifact beside each release.