Legal条款

Privacy Notice隐私政策

Last updated October 29, 2026最后更新：2026 年 10 月 29 日 · Version版本 2026-10-29-commerce

At a glance

  • We keep what's needed to run your account, your private writing projects, your AI conversations, and your purchases.
  • When you use an AI feature, your request and the book context it needs (not only the text you highlighted) are sent to our AI provider to produce the answer.
  • Your drafts are private. They reach the catalog only if you submit them and they are approved.
  • Account and manuscript data are stored with Cloudflare, AI requests are processed on computing resources we operate and by our AI provider, and payments are handled by the payment provider named at checkout, so your data is processed internationally; see section 12.
  • We don't sell personal data and don't run advertising or ad tracking. Card details stay with the payment provider, and your manuscripts aren't sent to it.
  • You can download a copy of your data and ask for corrections or deletion from your page or by email.

1. Who we are

EveryoneWriter (“we”, “us”) decides how the personal data described here is used. The service is offered to customers in the United States. Contact us about privacy at noobility@gmail.com.

2. What we collect

  • Account: your email address; your role (reader, writer or editor); account status; when you joined and last signed in; and which version of the terms you accepted and when. Sign-in codes are stored only as hashes and stop working after 10 minutes.
  • Sessions and security: for each sign-in session, the time, the IP address it started from and the browser's description (user agent), so you can sign out everywhere and misuse can be investigated. IP addresses are also used to limit repeated sign-in attempts.
  • Your writing: the books, chapters, characters and story notes in your projects, your project and writing preferences, and the AI conversations you save.
  • AI usage and credits: for each AI request, its size, the credits it used and when; your credit balance; and records of credits added, used, expired and refunded.
  • Purchases: which payment provider sold the purchase; its customer, transaction and subscription identifiers; the amount, currency and date; the status of your AI writing plan (and of any reading membership bought before reading became free); billing period dates; and cancellation and refund records. We don't receive or store full card details; the payment provider handles them.
  • Publishing: when you submit chapters, a snapshot of them with the pen name, synopsis and other details you enter, and the review outcome and notes.
  • Privacy requests, support and reports: requests you make from your page, and emails you send us, with our replies. This includes reports of content that may break our rules, with any text, AI output or identifiers you choose to include.
  • Operational logs: like most websites, our servers and Cloudflare record requests (IP address, page requested, time, browser details) to keep the service running, protect it and fix faults.

Reading the catalog is free and needs no account. Your reading position and reading settings are kept in your own browser, not on our servers (see section 8).

3. How we use it

  • to provide the studio, the AI features, the catalog and the purchases you ask for;
  • to keep your account secure and prevent abuse and fraud;
  • to keep accurate credit, billing and refund records, including those the law requires;
  • to review submissions and publish approved books;
  • to review reports and suspected breaches of the AI content safety rule and other content rules, and decide what to do (see section 5);
  • to answer support and privacy requests and tell you about important changes to your account or these policies;
  • to find and fix problems with the service.

We don't send marketing email without your agreement.

4. How the AI features handle your writing

  • When you make an AI request, your instruction and the parts of your project the request needs, which can include the selected passage, the current and other chapters, characters, story notes and earlier messages in the conversation, are processed on computing resources we operate and sent to our AI processing provider, named in the AI processing provider details.
  • The provider processes this to generate a response, under its own terms and privacy policy and the settings of our account with it. Its contact route is listed in section 6.
  • Each request also carries our fixed content-safety instructions (see the Terms). These are instructions to the AI; they don't add any personal data to the request.
  • We don't use your writing to train AI models of our own, to promote the service, or for sale.
  • Responses are shown to you; changes to your manuscript take effect only when you apply them. Conversations you save are stored with your project.

5. Who can see your writing

  • Your projects are private to your account. Other writers and readers can't open them.
  • Nothing is shown in the catalog unless you deliberately submit chapters and they are approved. Reviewers work from the submitted snapshot, not your other drafts. Once approved, the published edition is stored separately and is public.
  • We, as the operator, can technically access stored data. We do so only when needed: to give you support you've asked for, to keep the service running and fix faults, to make and restore backups, to handle privacy requests, to review a content report (below), or where the law requires. We don't otherwise read or use your private writing.
  • Content reports. When a breach of our content rules is reported or suspected, the operator reviews the text, AI output and identifiers provided in the report, together with the existing account, usage and security records needed to assess it and decide what to do, such as a warning or restricting AI features. Reports are reviewed by the operator, not sent to an outside moderation service. We look at only what's needed for that report, not at private projects in general.

6. Service providers

  • Cloudflare hosts the service and its data, sends sign-in emails, and protects the site from attacks. Separately, Cloudflare Web Analytics adds a small script to our pages that measures page loads and performance, such as page views and load times, without setting cookies; we use it to keep the site fast, not for advertising or profiling. Cloudflare privacy policy
  • Payment provider (merchant of record): each purchase is sold by the provider named at checkout and on your receipt, which is Paddle, or Creem if your checkout and receipt name Creem. That provider runs checkout, payment, fraud prevention, tax, receipts, subscriptions and refunds. It does this on its own account, as an independent controller of the data it collects, under its own privacy notice: Paddle privacy notice, Creem privacy notice. When you start a purchase, we send the provider the plan or recharge and its price, a reference code that lets us match the payment to your account, and, if you've bought from that provider before, the customer ID it gave you. Our checkout doesn't send your account email; you enter your billing email and payment details directly with the provider. The provider then sends us what we need to deliver and support the purchase: its transaction, customer and subscription references, the amount and currency, the payment, refund or subscription status, and billing period dates (see section 2). We don't send your manuscripts, projects or AI conversations to payment providers as part of payment processing.
  • Our AI processing provider processes AI requests as described in section 4; see the AI processing provider details below.
  • Google: pages load fonts from Google Fonts, which receives technical request data such as your IP address; our contact inbox is Gmail, so emails you send us are handled by Google. Google privacy policy

These providers receive only what they need for their part of the service. Each linked policy explains how that provider handles data and how to contact it.

7. What we don't do, and when we disclose

  • We don't sell or rent personal data, and we don't share it for advertising. The site has no advertising or ad-tracking programs.
  • We may disclose information if the law requires it, or where reasonably necessary to protect people's safety, prevent fraud, or defend legal rights.

8. Cookies and browser storage

We use one essential cookie to keep you signed in. Your browser's local storage keeps your language, theme, reading settings and reading positions. Reading positions stay on your device: they're never sent to us, and they can remain after you sign out, so on a shared device clear them from your page or your browser settings. When you use the studio, browser storage may also keep editor preferences, such as text size and layout, and, if you start a purchase, a temporary note used to confirm it when you come back. Cloudflare may set strictly necessary security cookies, and the payment provider sets its own cookies when its checkout opens. Cloudflare Web Analytics measures page performance without cookies (section 6). We don't use advertising or analytics cookies.

9. How long we keep data

  • Account data and your writing are kept while your account exists and as needed to provide the service.
  • Sign-in codes stop working after 10 minutes and are removed in later clean-ups. Sessions end when you sign out or after 30 days without use. Operational logs are kept for a limited time.
  • Payment, credit and refund records are kept as long as needed for accounting, tax and legal obligations. For any purchase sold by Creem, we keep the sales, tax and audit records for that transaction for at least seven years, or longer where the law requires. This applies to those financial records only, not to your manuscripts or other account data.
  • Content reports and the decisions we make on them are kept as long as needed to handle the report, any review you ask for, and repeated breaches.
  • Deletion. Account deletion starts as a request that we review. When an account can be deleted, access is closed and data that directly identifies you, such as your email address, is removed or de-identified where appropriate. Records we need to keep, such as payment, transaction and legal records, are kept for as long as necessary and may remain identifiable: they can include the payment provider's transaction and customer identifiers and internal pseudonymous identifiers. Pseudonymized records are not anonymous, and we continue to protect them as personal data. Published works, publication agreements and financial records may need separate handling, which can limit or delay deletion. Deleting an account doesn't erase financial records the law requires us to keep, and it doesn't cancel a subscription with the payment provider, so cancel renewal first.
  • After deletion. So that a deleted account isn't quietly recreated, we keep a minimal record: a fingerprint computed from the email address and a marker that the account was deleted. A new account for that email is created only if you sign up again yourself; it starts empty. This record isn't anonymous (someone who knows the email could match it), so we treat it as personal data.
  • Backups. The service can make encrypted backups to recover from failures, and a backup may include writing and account records. Where a backup exists, data deleted from the service can remain in it until that backup is retired once it is no longer needed for recovery. Backups aren't used to run the normal service, and if one is restored, deletions recorded since it was made are applied again.

10. Security

We use reasonable technical and organizational safeguards for a service of this size: sign-in by one-time email codes stored as hashes, sessions you can end on every device, separation between accounts, access limited to need, and backups encrypted with a passphrase that is never sent to the service. No system is perfectly secure, and we can't guarantee that data will never be accessed without authorization. If we learn of a breach that affects you, we will tell you as the law requires.

11. Your choices and rights

  • Copy. Signed in, your page (or the author page for writers) downloads what your account holds as a JSON file. Manuscript text is exported with each project's own backup in the studio.
  • Correction and deletion. You can request these from the same page or by email. Each request shows its status and our reply; you can withdraw it while it's pending. If we can't fully meet a request, for example because a published work or legally required record is involved, we'll explain why.
  • Verification. We may ask you to confirm a request from the email on your account. We will never ask for a password or your card details.
  • Your state's law. Depending on where you live, you may have further rights, such as to know, access, correct or delete personal data, or to appeal a decision about your request. Contact us to use them; we'll respond within the time the law requires. You may also complain to a consumer protection or data protection authority.

12. Where data is processed

  • Storage and processing. Cloudflare stores the service's account and manuscript data. AI requests are also processed on computing resources we operate, and by our AI processing provider (section 4). Cloudflare, the payment provider, our AI processing provider and Google operate internationally, so your data may be stored or processed in the United States and other countries outside the one where you live.
  • Questions and requests. Each provider's privacy policy, linked in section 6, explains how it handles international transfers and how to contact it directly. For questions about cross-border processing, or to use any rights the law that applies to you gives you, contact us at noobility@gmail.com.

13. Age

The service is intended for adults who can enter into a binding contract and is not directed to children. We don't knowingly collect personal data from children. If you believe a child has given us personal data, contact us at noobility@gmail.com and we will delete it.

14. Changes and contact

If this notice changes in a way that matters, we'll show the new version here and, where appropriate, tell you before it applies. Questions or requests: noobility@gmail.com.

要点速览

  • 我们保存运行你的账户、私人写作作品、AI 对话和购买记录所需的信息。
  • 使用 AI 功能时，你的请求以及所需的作品上下文（不只是你选中的文字）会发送给我们的 AI 服务商以生成回答。
  • 你的草稿是私密的，只有在你主动投稿并通过审核后才会进入书库。
  • 账户和书稿数据由 Cloudflare 保存，AI 请求在我们运营的计算资源上以及由我们的 AI 服务商处理，付款由结账页面显示的付款服务商处理，因此你的数据会在多个国家和地区处理；见第 12 节。
  • 我们不出售个人数据，也不进行广告投放或广告追踪。银行卡信息由付款服务商处理，你的书稿不会发送给付款服务商。
  • 你可以在个人主页或通过邮件下载数据副本，或申请更正、删除。

1. 我们是谁

EveryoneWriter（以下称“我们”）决定本政策所述个人数据的使用方式。本服务面向美国用户提供。隐私相关事宜请联系 noobility@gmail.com。

2. 我们收集哪些信息

  • 账户：你的邮箱地址；你的角色（读者、作者或编辑）；账户状态；注册时间和最近登录时间；以及你同意的条款版本和同意时间。登录验证码只以散列形式保存，10 分钟后失效。
  • 会话与安全：每次登录会话的时间、登录时的 IP 地址和浏览器描述（User-Agent），以便你可以在所有设备上退出，也便于调查滥用。IP 地址还用于限制反复尝试登录。
  • 你的作品：作品中的书、章节、角色和故事笔记，你的作品与写作偏好设置，以及你保存的 AI 对话。
  • AI 用量与积分：每次 AI 请求的规模、消耗的积分和时间；你的积分余额；以及积分发放、使用、到期和退款的记录。
  • 购买：销售该笔购买的付款服务商；其客户、交易和订阅标识；金额、币种和日期；AI 写作方案的状态（以及在阅读免费之前购买的阅读会员的状态）；计费周期日期；以及取消和退款记录。我们不会接收或保存完整的银行卡信息，这些由付款服务商处理。
  • 出版：你投稿时，所选章节的快照以及你填写的笔名、简介等信息，以及审核结果和意见。
  • 隐私申请、客服与举报：你在个人主页提交的申请、你发给我们的邮件以及我们的回复，包括对可能违反我们规则的内容的举报，以及你自愿附上的文字、AI 输出或标识信息。
  • 运行日志：和大多数网站一样，我们的服务器和 Cloudflare 会记录访问请求（IP 地址、所请求的页面、时间、浏览器信息），用于维持服务运行、保护服务和排查故障。

阅读书库免费，无需账户。你的阅读位置和阅读设置保存在你自己的浏览器中，不在我们的服务器上（见第 8 节）。

3. 我们如何使用这些信息

  • 提供写作台、AI 功能、书库以及你购买的服务；
  • 保护账户安全，防止滥用和欺诈；
  • 保存准确的积分、计费和退款记录，包括法律要求保存的记录；
  • 审核投稿并出版获批的作品；
  • 审核针对 AI 内容安全规则及其他内容规则的举报和疑似违规，并决定如何处理（见第 5 节）；
  • 答复客服和隐私申请，并就账户或本政策的重要变更通知你；
  • 发现并修复服务中的问题。

未经你同意，我们不会发送营销邮件。

4. AI 功能如何处理你的作品

  • 你发出 AI 请求时，你的指令连同该请求所需的作品内容（可能包括选中的段落、当前及其他章节、角色、故事笔记以及对话中的先前消息）会在我们运营的计算资源上处理，并发送给我们的 AI 处理服务商，其身份见 AI 处理服务商详情。
  • 服务商处理这些内容以生成回应，并依照其自身条款、隐私政策以及我们账户的设置进行处理。其联系方式见第 6 节。
  • 每次请求还会附带我们设定的固定内容安全指令（见服务条款）。这些是给 AI 的指令，不会在请求中加入任何个人数据。
  • 我们不会用你的作品训练我们自己的 AI 模型、推广服务，也不会出售你的作品。
  • 回应会显示给你；只有在你确认应用后，书稿才会被修改。你保存的对话会与作品一起存储。

5. 谁能看到你的作品

  • 你的作品仅对你的账户可见，其他作者和读者无法打开。
  • 除非你主动投稿并通过审核，任何内容都不会出现在书库中。审核依据的是投稿快照，而不是你的其他草稿。获批后，出版版本单独存储并公开展示。
  • 作为经营者，我们在技术上能够访问已存储的数据，但只在必要时才会访问：为你提供你所请求的支持、维持服务运行和排查故障、制作和恢复备份、处理隐私申请、审核内容举报（见下文），或法律要求时。除此之外，我们不会阅读或使用你的私人作品。
  • 内容举报。当有人举报或我们怀疑存在违反内容规则的情况时，经营者会审核举报中提供的文字、AI 输出和标识信息，并结合评估和决定处理方式（例如警告或限制 AI 功能）所需的现有账户、用量和安全记录。举报由经营者本人审核，不会发送给外部审核服务。我们只查看处理该举报所需的内容，不会因此普遍查看私人作品。

6. 服务商

  • Cloudflare：托管服务及其数据，发送登录邮件，并保护网站免受攻击。此外，Cloudflare Web Analytics 会在我们的页面中加入一个小脚本，用于衡量页面加载和性能（例如页面浏览量和加载时间），不设置 Cookie；我们用它来保持网站流畅，不用于广告或用户画像。Cloudflare 隐私政策
  • 付款服务商（记录商户）：每一笔购买都由结账页面和收据上显示的服务商销售，即 Paddle；如果结账页面和收据显示由 Creem 销售，则为 Creem。该服务商负责结账、付款、防欺诈、税费、收据、订阅和退款，并以自己的名义、作为其所收集数据的独立控制者，依照其自身的隐私政策处理这些数据：Paddle 隐私政策、Creem 隐私政策。你发起购买时，我们会向服务商发送所选方案或充值及其价格、一个用于把付款与你的账户对应起来的参考编号，以及（如果你此前在该服务商处购买过）它分配给你的客户编号。我们的结账流程不会发送你的账户邮箱；账单邮箱和付款信息由你直接在服务商处填写。之后，服务商会把交付和支持该笔购买所需的信息发给我们：其交易、客户和订阅编号，金额和币种，付款、退款或订阅状态，以及计费周期日期（见第 2 节）。处理付款时，我们不会把你的书稿、作品或 AI 对话发送给付款服务商。
  • 我们的 AI 处理服务商：按第 4 节所述处理 AI 请求，见下方 AI 处理服务商详情。
  • Google：页面从 Google Fonts 加载字体，Google 会收到你的 IP 地址等技术请求数据；我们的联系邮箱是 Gmail，因此你发给我们的邮件由 Google 处理。Google 隐私政策

这些服务商只会收到其负责部分所需的信息。上述各项政策说明了该服务商如何处理数据以及如何与其联系。

7. 我们不做的事，以及何时披露

  • 我们不出售或出租个人数据，也不为广告目的共享个人数据。本站没有任何广告或广告追踪程序。
  • 在法律要求时，或为保护他人安全、防止欺诈或维护合法权利而合理必要时，我们可能会披露相关信息。

8. Cookie 与浏览器存储

我们只使用一个必要的 Cookie 来保持登录。浏览器的本地存储会保存你的语言、主题、阅读设置和阅读位置。阅读位置只保存在你的设备上，不会发送给我们，并且退出登录后仍可能保留；在共用设备上，请在个人主页或浏览器设置中清除。使用写作台时，浏览器存储还可能保存编辑器偏好（例如字号和布局）；如果你发起购买，还会临时保存一条记录，用于你返回时确认该笔购买。Cloudflare 可能设置严格必要的安全 Cookie；打开付款服务商的结账页面时，该服务商会设置它自己的 Cookie。Cloudflare Web Analytics 衡量页面性能时不使用 Cookie（见第 6 节）。我们不使用广告或分析类 Cookie。

9. 保存期限

  • 账户数据和你的作品在账户存续期间、为提供服务所需的范围内保存。
  • 登录验证码 10 分钟后失效，并在之后的清理中删除。会话在你退出登录或 30 天未使用后结束。运行日志只保存有限的时间。
  • 付款、积分和退款记录按会计、税务和法律义务所需的期限保存。对于由 Creem 销售的任何购买，我们会将该笔交易的销售、税务和审计记录保存至少七年；法律要求更长时，按法律要求保存。这仅适用于这些财务记录，不适用于你的书稿或其他账户数据。
  • 内容举报及我们对其作出的决定，会在处理该举报、你要求的复核以及应对屡次违规所需的期限内保存。
  • 删除。账户删除从一份由我们审核的申请开始。账户可以删除时，我们会关闭访问权限，并在适当情况下删除或去标识化直接识别你身份的数据（例如邮箱地址）。我们需要保留的记录（例如付款、交易和法律记录）会在必要期限内保存，并可能仍可识别到你：其中可能包含付款服务商的交易和客户标识以及内部假名标识。假名化记录并不等于匿名，我们仍将其作为个人数据加以保护。已出版的作品、出版协议和财务记录可能需要单独处理，这可能限制或延迟删除。删除账户不会抹去法律要求我们保留的财务记录，也不会取消你在付款服务商处的订阅，请先取消续订。
  • 删除之后。为防止已删除的账户被悄悄重建，我们会保留一份最少量的记录：根据邮箱地址计算出的指纹，以及该账户已被删除的标记。只有你本人重新注册，才会为该邮箱建立新账户，新账户从空白开始。这份记录并非匿名（知道该邮箱的人可以将其对应起来），因此我们仍将其作为个人数据对待。
  • 备份。本服务可以制作加密备份以便从故障中恢复，备份中可能包含作品和账户记录。如果存在备份，已从服务中删除的数据可能仍保留在该备份中，直到该备份不再用于恢复而被停用。备份不用于服务的日常运行；如果恢复某个备份，会重新执行该备份制作之后记录的删除。

10. 安全

我们采用与本服务规模相称的合理技术和管理措施：以散列形式保存的一次性邮箱验证码登录、可在所有设备上结束的登录会话、账户之间相互隔离、按需限制访问，以及用从不发送到服务器的口令加密的备份。没有任何系统是绝对安全的，我们无法保证数据永远不会被未经授权地访问。如果我们得知影响到你的数据泄露事件，会依法通知你。

11. 你的选择与权利

  • 副本。登录后，个人主页（作者为作者主页）可以把账户中保存的数据下载为 JSON 文件。书稿正文可通过写作台中每部作品的备份导出。
  • 更正与删除。你可以在同一页面或通过邮件提出申请。每份申请都会显示状态和我们的答复；申请处理前你可以撤回。如果我们无法完全满足某项申请（例如涉及已出版作品或法律要求保留的记录），我们会说明原因。
  • 身份确认。我们可能会请你通过账户邮箱确认申请。我们绝不会索要密码或银行卡信息。
  • 你所在州的法律。根据你的居住地，你可能还享有其他权利，例如知情、访问、更正或删除个人数据，或对我们就你的申请所作的决定提出申诉。如需行使这些权利，请联系我们；我们会在法律要求的期限内答复。你也可以向消费者保护或数据保护机构投诉。

12. 数据处理地点

  • 存储与处理。本服务的账户和书稿数据由 Cloudflare 保存。AI 请求还会在我们运营的计算资源上以及由我们的 AI 处理服务商处理（见第 4 节）。Cloudflare、付款服务商、我们的 AI 处理服务商和 Google 在多个国家和地区运营，因此你的数据可能在美国及你居住地以外的其他国家存储或处理。
  • 问题与申请。第 6 节链接的各服务商隐私政策说明了其如何处理跨境传输，以及如何直接与其联系。如对跨境处理有疑问，或需行使适用于你的法律所赋予的权利，请联系我们：noobility@gmail.com。

13. 年龄

本服务面向能够订立有约束力合同的成年人，并非针对儿童提供。我们不会在知情的情况下收集儿童的个人数据。如果你认为有儿童向我们提供了个人数据，请联系 noobility@gmail.com，我们会将其删除。

14. 变更与联系

如果本政策有重要变更，我们会在此公布新版本，并在适当时于生效前通知你。如有问题或申请，请联系：noobility@gmail.com。

本政策提供英文和中文版本，两者内容一致。