Privacy Policy

Last updated: July 22, 2026 · Effective: July 22, 2026

This policy explains how WriteFlow collects, uses, stores, and deletes data for writing generation, World Bible, chapter memory, accounts, payments, free models, feedback, and security controls. It concerns privacy and data handling. For usage rules, refunds, minors, account restrictions, and disclaimers, see the Terms of Service.

Account and identity data

• Email address: registration, sign-in, verification, email changes, password resets, and account notices.
• Password: WriteFlow stores a hash for sign-in verification, not a plaintext password.
• Username, avatar, and invite code: saved when you set them or use the relevant feature.
• Login session: a session token identifies your signed-in state.
• Temporary verification data: verification, email-change, and reset tokens, expiration times, and sending status.
• Account status: validity, freezes, reasons, times, and information needed for appeals.

Creative, World Bible, and Workflow data

• Novel text: input, Plot Guide, AI output, original and polished versions, and generation history.
• World Bible: name, description, cover, timeline, character cards, items, factions, locations, relationships, and other settings.
• Chapters: outlines, order, status, generation records, chapter memory, and recent prose.
• Writing memory: summaries you confirm, state tracking, foreshadowing, callbacks, mysteries, character states, relationship values, and narrative memory.
• Writing choices: preset, prose style, global tags and branches, locked World Bible choices, and stage routes.
• Generation settings: length, selected models, Planner plan count and chosen plan, automatic writing, Checker scope, retrieval setting, World Bible setting, and custom-API enablement.
• Workflow state: Planner, Writer, Checker, Polisher, and Maintainer progress, output version, stopping/cancellation, and state needed for recovery.
• Quality and stopping information: stop reasons, continuity and logic checks, AI-style warnings, quality notices, and necessary provider error information.

Model usage, credits, and interactions

• Model use: model and provider, cost tier, stage, success/failure, stop reason, cancellation, and necessary error codes.
• Usage: input/output tokens, cache hits, estimates, actual credit consumption, and balance changes.
• Free models: daily successful-use counts, limits, and counting status.
• Check-in and invitations: dates, streaks, rewards, codes, invitation relationships, counts, and rewards, subject to each site's existing eligibility rules.
• Mailbox: messages, sending times, read status, and unread counts.
• Prose ratings: when you choose Like or Dislike, the corresponding model version, parameters, and prose snapshot are saved for quality analysis. Manually edited prose is excluded from this rating.

Long-form retrieval data

For Chinese Workflow, saved World Bible card snapshots, chapter memory, and narrative memory may be converted to embedding vectors. Vector IDs, source types, chapter information, and injectable summaries are stored for later Planner retrieval. Retrieval is not currently enabled for English Workflow.

It does not index full prose, future chapter outlines, or short-term next-reading cues. Deleting cards, chapters, or a World Bible, or clearing writing memory, invalidates the source data first. Temporarily remaining vector IDs cannot then be injected into generation prompts.

Payment, technical, logging, and security data

• Payments and orders: product snapshots and versions, order IDs and third-party IDs, product, quantity, amount, currency, status, verification results, granting time, entitlements, exception-review reasons, and billing ledger.
• Payment callbacks: the payment platform may send status and verification data to confirm orders, grant entitlements, and handle exceptions.
• IP addresses: WriteFlow generally does not use IP addresses for profiling. Cloudflare, payment platforms, AI providers, or security logs may briefly process them for transmission, protection, risk controls, and troubleshooting.
• Frontend errors: error type and message, code location, page path, and browser environment may be reported to fix bugs; novel prose is not proactively included.
• Operational and security logs: request times, endpoints, result status, error codes, anti-abuse information, and necessary technical metadata.
• Feedback: text, issue descriptions, order context, and contact details you submit through in-app feedback.

Browser storage

To retain sign-in, preferences, and writing recovery, WriteFlow may use localStorage, sessionStorage, or similar browser storage for session tokens, profile caches, current World Bible IDs and names, presets, prose styles, tags and branches, Planner and Checker settings, retrieval preferences, invite codes, drafts, Workflow state, and other interface settings.

This data stays in the browser or device you use. On a shared device, people with access to that browser may see or use it. Sign out, clear the relevant settings, or remove the website's browser data to delete it.

Custom API keys

Provider names identify connectable APIs. WriteFlow does not record or retain API keys. The provider, model name, and key you enter are used only for the corresponding model requests from the current page; after refreshing or leaving, enter them again.

WriteFlow may send necessary data to the following providers for hosting, accounts, generation, retrieval, email, and payments. Their own terms, privacy policies, and infrastructure determine how they retain, audit, use, and delete it. WriteFlow cannot make commitments beyond their policies.

Provider category	Purpose	Data that may be processed	Location
Cloudflare	Hosting, database, network protection, logs, embeddings, and vector retrieval	Account and creative data, World Bible, memory, billing, network data, logs, vectors, and indexes	May be processed outside China
Built-in AI providers	Writing, planning, checking, polishing, memory maintenance, and world-building	Input, prompts, world and chapter context, memory, parameters, output, and necessary metadata	Provider deployment; processing may be outside China
Enabled model providers such as Google and DeepSeek	Model requests selected by you or assigned within Workflow	Text, context, parameters, output, and usage for the current stage	Provider policy and infrastructure
Payment platforms such as Afdian	Checkout, order confirmation, verification, and exceptions	Order IDs, product, quantity, amount, payment-account identifiers, status, and necessary verification data	Payment platform policy and service arrangements
Email providers	Verification, email-change, password-reset, and account notices	Email address, mail type, verification/reset links, and necessary sending status	Provider policy and infrastructure; processing may be outside China
Your chosen custom-API provider	Model requests for the role you configure	API key, model name, current-stage text and context, parameters, and output	Chosen provider and its policy

Each role uses the model you select in Advanced Parameters. If you do not want content sent to a provider, do not select it for that role or submit the sensitive content.

• WriteFlow does not use your novel text, cards, settings, chapter content, or writing memory to train its own models.
• Like/Dislike feedback is used for quality statistics and troubleshooting, not training WriteFlow's own models.
• WriteFlow does not sell your creative content or give private creative content to advertisers for profiling.
• Built-in and custom-API providers may process requests under their own policies. WriteFlow cannot promise their training, retention, or audit rules.
• To avoid sending a stage to a built-in provider, choose a custom API for that role or do not submit sensitive text.

Data type	Usual retention
Login sessions	Usually seven days; no longer used after logout, reset, account-status change, or invalidation
Verification, email-change, and password-reset tokens	Until used, replaced, or expired
Account information	While the account exists; validity is usually about six months, subject to account status and system rules
Prose, history, World Bibles, chapters, cards, and memory	Until you delete the data, delete the account, or the account expires
Retrieval vectors and indexes	Cleanup follows source deletion; asynchronous deletion may have a short delay
Ratings and quality-analysis snapshots	Until the related records or account are deleted, or quality analysis/troubleshooting no longer needs them
Credits, free-model uses, check-in, and invitations	During the account's existence and as necessary for billing checks, anti-abuse, and disputes
Payment orders, callbacks, and billing ledger	As necessary for verification, financial records, exceptions, refunds, disputes, and applicable requirements
Mailbox, feedback, appeals, and freeze records	As necessary for requests, account security, disputes, and product improvement
Error, operational, and security logs	For the minimum period necessary for troubleshooting, anti-abuse, and service security
Browser data	Until you clear settings, leave the relevant feature, replace preferences, or clear website data; custom API keys are not written to browser storage

• View and correct: edit username, avatar, email, and password in Profile, and manage worlds, cards, chapters, and settings in the World Bible page.
• Export: export generation history in Settings and the billing ledger from Profile → Billing.
• Delete: clear history in Settings, and delete World Bibles, chapters, cards, and related memory in their management pages.
• Delete account: use Profile → Danger Zone. Sign-in stops immediately; the account and related data are removed within three months and cannot then be recovered.
• Manual requests: use Feedback & Suggestions for refunds, appeals, unusual data issues, or other export/deletion assistance.

This policy may change with features, providers, or compliance requirements. For important changes, WriteFlow will make reasonable efforts to notify you through in-app entries or page updates. Use Feedback & Suggestions for privacy, deletion, export, or security questions.

Interpretation and application follow applicable law. For data processing not expressly listed, WriteFlow will consider service necessity, reasonable expectations, and data minimization without excluding or restricting rights you have under applicable law.

Related document: Terms of Service.