Privacy Policy

Story Singularity (戏梦奇点)· effective 25 August 2026

In one sentence: the software never uploads anything you write. There is no account system, we do not set out to collect your identity, and there is nowhere on our servers where your work is kept.
There are two exceptions, and you trigger both of them: when you submit feedback yourself, the description and contact details you fill in are sent to us; when you use an AI feature, the content you selected is sent by your own machine directly to the AI provider you chose (not through us). Each point is set out below.

1. What we do not do

2. Where your creative content lives

Entirely in the local storage of your own computer. Exported PDF, Word, Final Draft and other files are written only to the location you choose. We can neither recover them nor look at them.

Note: uninstalling the software will not necessarily clear this data — files you exported to various places are not deleted, and the application's local storage may remain in a system directory. To erase it completely, delete the exported files by hand and clear the application's data in the way your system provides.

3. AI features: your own key, not routed through us

AI features require you to enter an API key of your own from a provider (DeepSeek, Qwen, Zhipu GLM and so on); you may also set a custom endpoint, or connect to a model running on your own machine. The key is encrypted and stored on this machine through the system's secure storage; when a call is made, the request goes from your machine directly to the provider you selected, through none of our servers.

This means the content you send to an AI is governed by that provider's privacy policy, which is yours to verify. With no key entered, every writing feature in the editor still works as normal.

4. Every situation in which the software contacts our servers

SituationWhen it happensWhat is sent
Reporting a problem Only when you fill the form in and press Send Always sent: the description you wrote, the contact details you left (required, so we can reply), the report type, and the software version.
Sent according to your tick boxes: the runtime environment (operating system and version, processor architecture, Electron version, interface language and zoom, and which area of the software you were in), the most recent crash record, and the recent action log.
Optional, added by you: a name to address you by; a screenshot (which you pick as a file yourself — the software never captures the screen on its own).
Anything ticked can be expanded and read word for word, and unticked, before sending. The crash record is unticked by default — it is ticked automatically only when you arrive from the “Report this problem” button on the crash page, because that is precisely what you came to report; it is the raw text produced when the program failed and may contain file paths or a project name, so expand it and take a look before sending.
Checking for updates At most once a day, or when you click it yourself Nothing is sent. It simply requests a public version file from the website; the comparison happens on your machine. The request carries no version number, no device identifier and no cookie. Automatic checking can be turned off at any time in the Check for Updates dialog.
Downloading and installing an update Desktop version · after you press “Download and install” in the Check for Updates dialog The installer is downloaded from the website only. The request carries no device identifier and no cookie; so that only the changed parts need downloading, from the second update onwards a delta manifest is requested from the website for your current version, which means the website can see which version you are upgrading from. Once the download finishes, the system installs it when you restart or quit — never replacing the program while you are writing.

As with all network requests, the server records the originating IP address and browser identifier in its access log — this is inherent to the HTTP protocol and unavoidable for any website. Those logs are used only to investigate abuse, and are linked to no personal identity.

5. How feedback is handled

The feedback you submit is sent to our inbox as an email and is written to no database. We use it only to locate and fix the problem you reported, or to reply to you through the contact details you left where that is needed. It is used for nothing else and given to no third party.

6. Children

This software is intended for professional and amateur screenwriters, not for children under 14, and it does not knowingly collect information from children.

7. Changes to this policy

If this policy changes, the effective date at the top of this page will be updated. A substantive change to network behaviour will additionally be set out in the software's release notes.

8. Contact us

For privacy questions, please email report@dianjingtech.com.cn, or submit a report from Help → Report a Problem inside the software.