Merlin Script Workshop is operated by the independent developer Merlin. Questions about privacy and requests to access, correct, or delete personal information may be sent to 464421609@qq.com.
To provide registration, sign-in, email verification, saving and publishing, AI generation, safety review, troubleshooting, and product analytics, we process account details; characters and scripts you submit; images you choose to upload; AI prompts and generated results; task and quota records; necessary IP and browser information; and first-party analytics such as feature categories, key actions, success or failure, and active time.
The site cannot read photos you do not select. It does not collect contacts, microphone data, or precise location, does not sell personal information, and does not perform cross-site advertising tracking.
When you use AI character icons or script logos, prompts and reference images are sent to the model provider identified in the interface. When you use your own API key, the key is used only for that request and is not written to the database or logs. Prompts, reference images, and results may still undergo site safety review.
To prevent illegal, abusive, or infringing use, necessary task records and billing metadata may be retained for up to 180 days. Compressed review copies of inputs and outputs may be stored privately. Ordinary review copies are normally retained for 30 days; confirmed violation evidence may be retained until an appeal or investigation ends, generally no longer than 180 days.
First-party product analytics are enabled by default after registration and acceptance of this policy. Verifiable import, export, rendering, resource-loading, or runtime failures may be recorded as controlled diagnostic events containing the feature, operation stage, stable error code, low-precision device category, version, and random session identifier. These events do not contain prompts, work content, filenames, images, full URLs, email addresses, API keys, full User-Agent strings, or stack traces. Signed-out visitors are not included, and raw events are retained for up to 90 days. Signed-in users can disable analytics and request deletion of account-linked events under Privacy & Data.
Signed-in users may submit a problem description, device category, and up to three screenshots. Reporting remains available when product analytics are disabled. A report is linked to a recent automatic diagnostic only when analytics are enabled and the account, time, and feature match. Screenshots are re-encoded on the server, stored outside public static directories, and accessible only to administrators. Closed reports are normally retained for 180 days; screenshots are normally retained for 90 days after closure and no longer than 180 days. You may request deletion using the contact email above.
We do not use your prompts, reference images, work, or generated results by default to train foundation models, LoRAs, or training datasets. Any future training use will separately explain its purpose, scope, and duration and request separate permission.
Creator profiles are currently experimental previews visible only to the signed-in profile owner. Administrators may access them only when necessary for feature validation. The existing public-profile implementation is retained but disabled by default. Login names, email addresses, drafts, pending work, management roles, and non-public certificates do not appear in the preview.
Creator Monthly uses only aggregated data derived from already approved, public script versions, such as character appearances, type distribution, and co-occurrence. Public reports do not expose user IDs, nicknames, browsing activity, or non-public work. A published report is a frozen snapshot and does not silently change when later data changes.
Accounts and deliberately saved work are normally retained until you delete them or close the account. Temporary tokens, security logs, product analytics, and AI review copies are removed under their respective retention periods. Routine administration exposes only necessary summaries or review material to administrators. You may use the contact email above to request access, correction, a copy, or deletion of personal information.
Users under 14 should use the service with consent and guidance from a guardian. We do not routinely request identity documents. If we discover that we processed information about a child under 14 without guardian consent, we will stop that processing and delete the information as required by law.
If the purpose of processing, types of information, recipients, or retention periods change materially, we will publish a new version and request confirmation before the relevant features are used again.