Privacy

Back to the tool

Your project — the profiles, the canon, the world, the questions — is stored in this browser's localStorage under one key, and nowhere else. There is no Nexet account behind it, no server that receives it and no upload. Clearing your browser data deletes it, which is why the tool offers a JSON export: that file is your backup, and it is the only copy that exists outside the browser.

No signup, no email address, no cookies for tracking you between sites.
No field content is ever transmitted — not a name, not an answer, not a question.
The relationship map's arrangement is kept in a second browser key, and is a view preference rather than part of your project.
Nothing is loaded from a third party except the page's own font files and the analytics script described below.

The page reports anonymous usage counts to Mixpanel, the same analytics the rest of Nexet uses: that a page was opened, that a character was added, that a bible was exported and in which format, how many characters were in it, and which CTA was seen or clicked. Those reports carry counts and enum values, never your words. There is no session recording on this tool — so no replay of a screen full of your unpublished story is ever stored anywhere.

Exported files are produced in your browser and saved by your browser. The tool does not see them leave, and keeps no record that you made one. When you hand a bible to a collaborator, that is a file you chose to send.

If you take the bible into Nexet, that is a separate product with its own account and its own privacy policy, and the tool links to it only when you click. Nothing about your project travels with the click.

The tool's development plan also states what it will not do with your work: no manuscript upload or analysis, no plot generation, no characters written for you. Those are documented limits, not settings.