高级Claude Code

服务条款生成 Skill:SaaS 条款与隐私政策

用这个服务条款生成器 Skill,根据网站实际行为准备条款与隐私政策。助手会先检查功能、数据收集和宣传说法,再依据经营事实起草两份文档,并集中列出尚未确认的信息,帮助团队在发布前核对网站做法与对外承诺,避免政策之间相互矛盾。

浏览量
0
复制次数
0
收藏
0
01

服务条款生成器如何把业务资料变成草稿

Legal ToS Privacy 先阅读网站代码与宣传内容,确认需要描述哪些功能和数据处理行为,再生成条款、隐私政策草稿以及缺失经营信息的问题清单。先核对事实,再写承诺,可以减少套用模板时加入网站并不存在的功能。

原始流程主要面向 SaaS 产品。实物商品店铺还需要提供配送、退货和退款规则,以及主体和数据处理信息。输出适合作为审核材料;除非开发任务已明确包含创建政策页面或补充同意控件,否则这些工作需要另外安排。

02

是否适合你的店铺

Legal ToS Privacy 适合 SaaS 团队,以及带有自定义网站功能、希望条款和隐私说明与实际业务一致的店铺。它从代码与宣传文案开始检查,再生成文档并集中列出需要补充的经营信息,适合准备一套相互对应的审核材料,而不是直接套用通用政策模板。

01

先查网站实际做了什么,再写对外承诺

起草前检查功能、数据收集、第三方服务和公开说法。本页案例区分了结账演示与真实订单处理,也识别出选择同意之前加载的脚本,让团队能够据此修正文案,不把尚未实现的控制写成已经存在。

02

用同一套业务资料起草条款和隐私政策

两份文档共同使用账户、支付、取消与数据处理事实,实物商品再补充配送和退货条件。把草稿一起审核,可以检查某一处承诺是否与另一份政策或实际经营方式冲突,减少各自套模板造成的不一致。

03

集中补齐商家资料,再安排上线工作

将缺失主体资料和待确定的政策选择集中交给经营者与审核人员。把需要回答的经营问题和需要修改的网站功能分开,团队就能知道下一步究竟是补充事实、确定规则,还是开发实际控件。

03

使用前的特殊要求

开始运行前,先准备下方业务资料及软件环境。

完整原作者文件包

运行前准备兼容的 AI 编程助手,以及原作者完整的四文件 Skill 目录。

代码与业务资料

运行前准备脱敏源码副本及确认的业务、数据处理事实。

政策审核者

运行前准备审核法律决策、推断身份及无关框架依赖的负责人。

04

安装

安装完整 Skill 包,再使用上面准备好的店铺资料开始任务。

将指令复制给 Codex 或 Claude Code,让助手从原始仓库下载固定提交,安装完整文件并检查所需依赖。

  1. 打开能访问本机文件和终端的 Codex 或 Claude Code。
  2. 复制下方指令发给正在使用的应用,由助手选择该应用的安装目录。
  3. 查看返回的安装路径和文件检查结果;需要时新建会话,再要求助手使用已安装的 Skill。
请在我当前使用的应用中安装 legal-tos-privacy,直接执行文件安装,不要只解释步骤。 原始仓库:https://github.com/galyarderlabs/galyarder-framework.git 固定提交:ab209fa59e8a4d8d9c354564097bc123aefd7dbb Skill 路径:skills/legal-tos-privacy 1. 将这个版本下载到新目录。执行随包脚本前,先阅读 SKILL.md 和安装参考文件,不替换成其他作者的包。 2. Codex 安装到 ~/.agents/skills/legal-tos-privacy,Claude Code 安装到 ~/.claude/skills/legal-tos-privacy,只安装到我正在使用的应用。安装完整 Skill 文件夹,保留 scripts、references、assets 和随包声明;将仓库根目录许可证一并保留。先检查所有目标目录;已有安装时,说明差异后再决定是否替换。 3. 比较来源和安装目录的文件清单、文件哈希,检查文档要求的运行时、依赖及外部连接。只配置此 Skill 所需的本地依赖,适用时使用隔离环境;账号登录由我在本地完成,不把凭据贴进聊天。 4. 返回来源提交、实际安装路径、文件检查结果及尚未完成的运行环境配置,说明如何调用 legal-tos-privacy。文件复制与应用发现分别检查,需要时新建会话。不要执行生产任务,也不要把安装完成说成已确认业务效果。
05

开始使用:三个店铺任务

以下是主要功能的用例提示词,可以直接复制使用。

01

起草 SaaS 服务条款

起草 SaaS 服务条款,输出包含账户、支付及取消规则的条款草稿。 代码、现有政策及已确认业务资料。

查看 Prompt 和变量收起 Prompt 和变量
使用 Galyarder Labs 原作者 legal-tos-privacy 完整包,阅读三份参考指南。起草账户、账单与取消规则。以 [INPUT] 为事实依据,未知资料列为问题,不发布。

需要替换的变量

[INPUT]
代码、现有政策及已确认业务资料。
02

起草隐私政策

起草隐私政策,输出与实际数据处理对应的隐私草稿。 代码、现有政策及已确认业务资料。

查看 Prompt 和变量收起 Prompt 和变量
使用 Galyarder Labs 原作者 legal-tos-privacy 完整包,阅读三份参考指南。把数据收集与服务商清单对应到隐私草稿。以 [INPUT] 为事实依据,未知资料列为问题,不发布。

需要替换的变量

[INPUT]
代码、现有政策及已确认业务资料。
03

发布前找出缺口

发布前找出缺口,输出矛盾报告及待补业务资料清单。 代码、现有政策及已确认业务资料。

查看 Prompt 和变量收起 Prompt 和变量
使用 Galyarder Labs 原作者 legal-tos-privacy 完整包,阅读三份参考指南。将草稿与代码、营销及退款规则比对。以 [INPUT] 为事实依据,未知资料列为问题,不发布。

需要替换的变量

[INPUT]
代码、现有政策及已确认业务资料。
06

实际使用案例:整理一套条款与隐私政策审核材料

模拟店铺提供 4 个网站文件和美国/加拿大经营规则。结账页只是浏览器演示;首页在顾客作出同意选择之前加载测试 Google 标签。

使用步骤与 Prompt

  1. 准备下方案例输入资料,保留商品、政策和经营记录中的金额、单位及时间口径。
  2. 先检查店铺实际功能、承诺与数据收集,再根据完整商家问卷写服务条款和隐私政策,列出待商家批准的网站修改。
  3. 提交下方完整 Prompt,查看右侧主要产物;需要交接给同事时,下载包含全部交付文件的压缩包。

案例输入资料:business-inputs.zip

Use the legal-tos-privacy Skill.

Draft English terms of service and a privacy policy for the attached storefront using the merchant facts and completed business questionnaire. Audit the site's actual claims, features and data collection first. Keep delivery, refund and consent terms consistent, provide complete review drafts, and list any remaining business questions and website changes for the merchant to approve. This is a fictional merchant exercise, not a legal opinion.

The attached business materials are:
- inputs/merchant.json
- inputs/simulated-merchant-answers.json
- inputs/storefront/store/checkout.html
- inputs/storefront/store/contact.html
- inputs/storefront/store/index.html
- inputs/storefront/store/styles.css

Deliver a complete result.md report that the operations team can read, plus any finished files needed for this task. Keep supporting calculations and evidence with the deliverables. Write the report in English; use the requested target language for customer-facing copy. The business datasets are fictional examples unless the brief explicitly names a live public website.

运行结果

下方直接展示本次 Prompt 产生的主要文件,保留实际输出语言。

Store terms and privacy drafting package

Audit outcome and release decision

Completed the requested review drafts against the supplied storefront and completed fictional business questionnaire. The code audit found a static product homepage, a checkout preview with email/address fields and a prevented submit event, a contact page and one stylesheet. There are no accounts, uploads, subscriptions, payment gateway, backend order submission, first-party storage calls or connected carriers. Source hashes and findings are in storefront-audit.json.

The homepage's Google tag loads unconditionally. The questionnaire elects to disable it before public launch; this drafting task has not changed the site. The documents therefore identify the current request and future removal separately, instead of claiming valid consent or completed removal. The demo has no production analytics property or verified Google retention configuration.

Ready for merchant/counsel review; not ready for live merchant publication. All template variables are resolved using the fictional questionnaire. Resolved training details are not verified legal identity, a working address or working contacts. No real purchase, message, refund or vendor connection was made.

Consistency decisions

  • Separate handling from carrier transit: 1–2 business days standard, 5–7 preorder; US transit 3–5, Canada 7–12.
  • US shipping is $5.95 below $75 after discounts and free at $75; Canada is $18, no free threshold, seller-paid import duties/taxes. US PO boxes allowed, Canadian PO boxes not allowed.
  • Voluntary unused/original-packaging returns are requested within 30 days; no restocking fee. Customer pays change-of-mind return postage, seller pays confirmed-defect return postage. Outbound postage follows the completed questionnaire's separate rule.
  • Refund processing is 5–10 business days after inspection/approval under the merchant's business-day convention; confirm that convention with the operator before use. Mandatory refund deadlines take precedence, especially cancellation for delayed dispatch.
  • Planned explicit terms assent and separate dispatch acceptance are not presented as existing checkout features. Privacy consent remains a separate purpose-specific issue.
  • Omit account, subscription, AI-output and user-upload clauses because those features do not exist. Do not invent an arbitration provider, liability cap, product warranty waiver or indemnity absent merchant selection and legal review.

Approval questions and website changes

PriorityOwnerRequired decision/changeAcceptance evidence
Before any public launchEngineeringRemove unconditional Google tag and config call under chosen no-analytics launch planClean-browser network capture with zero Google requests across every page
Before real collectionOperator / privacy leadReplace fictional entity, address and contact; identify hosting/mailbox/payment vendors and processing countriesVerified working channels and documented vendor/data inventory
Before taking ordersEngineering / operationsImplement reviewed assent, order review, acceptance notice, invoice method and itemized taxes; publish linked policiesTest order through actual chosen payment/fulfillment flow with retained acceptance evidence
Before policy approvalOperationsConfirm refund business-day convention, return dispatch/receipt deadlines, cancellation handling, carrier basis and return instructionsApproved policy matrix matching checkout and support procedures
Before real collectionPrivacy leadImplement retention/deletion, security and incident responsibilities; determine state/Canadian applicability and transfer needsTested request/deletion workflow, provider terms and jurisdiction assessment
Before live termsCounsel / operatorReview product warranties, proposed Texas law/venue, any desired liability cap, mandatory consumer rights and deadline rulesApproved final text; no automatic arbitration/class waiver
At launch and changesContent ownerReplace simulation date/labels only after real approval; link terms/privacy near relevant collection; version noticesPublished date/version and consistency check against real code

The complete questionnaire resolves drafting fields, but it cannot verify a real business or implement a system. These are review and deployment gates, not omitted template blanks.

Official reference checks

The FTC merchandise-order rule explains that inability to meet promised shipment timing requires a delay-consent or refund process. The draft preserves that requirement rather than treating carrier estimates as a blanket excuse.

The California Attorney General's CCPA guidance describes consumer rights and covered-business duties. This fictional dataset cannot establish the real operator's applicability or exemption, so the artifact does not copy a potentially outdated threshold from the Skill reference as a current legal conclusion.

Canada's PIPEDA fair information principles inform the review of purpose, collection, retention, safeguards and access. Federal/provincial applicability still needs assessment for an actual business.

Complete review documents

The following are the full generated drafts, also included as separate files in the package.

Terms of Service — Cedar & Cart Training LLC

Review draft. Last updated November 2, 2026 (simulation only). Cedar & Cart Training LLC, the address and the domain in this document are fictional training examples. This document is a complete drafting exercise for review by the merchant and qualified counsel, not a legal opinion or permission to launch a store. Do not place real orders, make payments or send parcels using these details.

1. Operator and scope

Cedar & Cart Training LLC is the fictional operator of Cedar & Cart Demo at https://cedar-cart.example. Our training notice address is 100 Example Lane, Demo City, TX 00000, USA, a non-deliverable example. The training contact is [email protected], which does not receive real messages.

The current demonstration shows ceramic mugs, linen towels and a checkout preview. It does not create orders, collect payments, open accounts or provide subscriptions. The purchase provisions below describe the operator's proposed business terms and do not imply that purchasing is currently available. No real contract is formed by using the preview.

2. Eligibility, assent and order acceptance

The proposed store is for adults aged 18 or older who have legal capacity to contract. Before a real order could be submitted, the operator plans to display these terms with an affirmative acceptance checkbox and an order-review step. That process is not implemented in the supplied preview.

Under the proposed process, an order request or invoice is not acceptance. Acceptance occurs only when the operator sends a separate dispatch-confirmation email. Availability, delivery details, price, taxes and any proposed correction must be clear before the customer commits. An error does not authorize an unapproved higher charge. If the operator cannot fulfill an order, it will explain the situation and provide cancellation and refund rights required by law.

3. Prices and payment

All proposed prices and charges are in USD. In the fictional operating plan, approved requests are manually invoiced; applicable taxes and shipping charges are itemized before acceptance. No card or bank details should be entered into this website. The demonstration has no payment processor and accepts no payments. A real payment method and the related privacy disclosures must be selected and reviewed before taking money.

There are no recurring subscriptions, free trials or automatic renewals. Changes to future prices do not retroactively alter an accepted order without the customer's agreement or another lawful basis.

4. Dispatch, transit and delivery

The proposed fulfillment location is Austin, Texas. Business days mean Monday through Friday excluding US federal holidays. Standard handling is 1–2 business days; preorder handling is 5–7 business days. Carrier transit starts after handoff and is additional to handling. These are estimates rather than guaranteed arrival dates, and no holiday cutoff or daily order cutoff is promised.

DestinationProposed serviceTransit after handoffShipping chargeAddress restrictions
Contiguous United StatesUSPS Ground Advantage3–5 business days$5.95 below $75 merchandise subtotal after discounts; free at $75 or morePO boxes accepted
CanadaUPS Standard7–12 business days$18; no free-shipping thresholdNo PO boxes

For Canada, the seller pays the stated import duties and taxes under the supplied DDP plan. Do not add buyer-paid import-duty language. Tracking is to be emailed after carrier handoff. Address-change requests should be made before handoff and are not guaranteed.

If dispatch cannot occur within a legally binding promised time, the operator must provide the required delay notice and cancellation/refund choice. Calling a date an estimate does not remove mandatory duties. A missing shipment should be reported after its estimated window so the operator can investigate with the carrier; the investigation does not waive applicable delivery or refund rights.

5. Cancellation, returns and refunds

Contact support before carrier handoff to cancel. Under the proposed rule, cancellation is accepted while the order has not dispatched; after dispatch, the return process applies, subject to any stronger mandatory rights.

For voluntary returns, request instructions within 30 days after delivery. Items must be unused and in their original packaging. Send an item only after receiving the order-specific return instructions. The address in this training document must never be used for a real parcel. There is no restocking fee.

The customer pays return postage for a change of mind; the seller pays it for a confirmed defect. Original outbound postage is not refunded for a voluntary change-of-mind return, but is refunded for a confirmed defect or where mandatory rights require it. Support reviews the facts before deciding the appropriate remedy.

Report damage within seven days with the order number and photos to help investigation. This reporting request does not remove statutory defect rights or automatically entitle or limit a customer to replacement. After inspection and approval, the planned refund processing time is 5–10 business days to the original payment method. Mandatory refund deadlines take priority; this period must not be used to delay a legally required cancellation refund. Bank posting may be separate from the operator's processing time and is not quantified by this intake.

6. Website use and intellectual property

Use the website for legitimate browsing and, if a reviewed purchase flow is later launched, genuine orders. Do not disrupt the site, introduce malicious code, impersonate someone, or attempt unauthorized access. Site materials remain the property of their respective rights holders; browsing does not transfer copyright or trademarks. You may use the materials for ordinary personal shopping, subject to applicable law. The supplied site has no public uploads, user accounts or user-content licensing feature.

7. Privacy and external services

The accompanying Privacy Policy describes what the supplied demonstration currently does and the separate proposed operating plan. Acceptance of purchase terms is not blanket consent to optional analytics or marketing. The current homepage contains an ungated Google test script, which the operator has elected to remove before launch. This drafting exercise does not implement that removal.

Carrier or future payment-provider services may have their own applicable terms, but using a provider does not remove the operator's obligations to the customer. No carrier or payment integration is currently connected in this demonstration.

8. Availability, warranties and responsibility

The demonstration may be interrupted or changed. It does not promise continuous availability or that all display errors will be absent. These website limitations do not exclude product descriptions, statutory product warranties, required remedies or consumer rights that cannot lawfully be restricted.

The merchant has not selected a monetary liability cap or a broad consumer indemnity in the completed intake, so this review draft does not invent either. Liability follows applicable law, including rules that cannot be excluded for injury, fraud, intentional misconduct or other protected claims. Any later limitation must be reviewed for the actual products, jurisdictions and consumers; it cannot erase an existing refund obligation.

9. Disputes, interruptions and changes

The proposed governing law is Texas law, without overriding mandatory consumer protections. Courts in Travis County, Texas are the proposed venue only where mandatory consumer venue rights permit. This exercise adopts no arbitration agreement or class-action waiver. Customers may contact support to discuss an issue, but that invitation does not suspend statutory deadlines or prevent lawful remedies.

Events outside reasonable control may affect fulfillment, but do not eliminate mandatory delay notices, cancellation rights or refunds. The operator may restrict abusive website access; doing so does not cancel valid customer rights or permit keeping payment for unfulfilled obligations.

Material changes are to receive a dated website notice and, where lawful contact information exists, appropriate email notice. Fresh assent is required where applicable; changes do not silently rewrite accepted orders. If a provision is unenforceable, the remaining provisions continue to the extent lawful. This preview sends no notices and implements no assent mechanism.

10. Contact and review status

Training contact: [email protected]. Training notice address: 100 Example Lane, Demo City, TX 00000, USA. Both are fictional and must be replaced with verified working business details before any real use. Merchant approval, operational implementation and qualified legal review remain required before publication as a live store's terms.


Privacy Policy — Cedar & Cart Training LLC

Review draft. Last updated November 2, 2026 (simulation only). This is a fictional merchant drafting exercise. Its domain, contact and address are training examples, not working channels. The policy distinguishes the supplied demonstration from proposed operations so that planned controls are not represented as already deployed.

1. Who is responsible

Cedar & Cart Training LLC is the fictional operator of Cedar & Cart Demo, https://cedar-cart.example. The proposed privacy coordinator uses [email protected]. The notice address is 100 Example Lane, Demo City, TX 00000, USA. Neither contact should be used for real requests. Before real collection begins, the operator must provide working contact methods and identify the responsible legal entity.

2. What the supplied demonstration does now

The checkout preview displays email and delivery-address fields. Its script prevents submission and displays “Demo only. No payment or order created.” The supplied application does not send those values to a backend, create an order, store an account or take payment. Do not enter personal information in this training preview. A visitor's browser may have its own form history; that behavior is outside the application's demonstrated storage.

The homepage currently requests an external Google tag script using the test identifier G-TEST000000, without a consent choice. A request to that service can expose network information such as an IP address and browser request details. The source also queues an analytics configuration call. The test identifier does not establish that a production analytics property receives or retains events. Google-side storage, cookies, retention, processing countries and advertising configuration have not been measured in this exercise. The application itself has no cookie or storage-key calls.

This existing script is a launch blocker. The operator's selected plan is to remove analytics before public launch. This document records that decision; it does not remove the script or certify consent. Until verified removal, the demonstration must not be described as free of third-party requests. No other external host, operational mailbox, payment processor or customer database is identified in the supplied materials.

3. Proposed customer information and purposes

The following is an approved fictional operating plan, not a statement that these systems currently exist.

InformationProposed source and purposeProposed recipient categoriesPlanned retention
Name, email, delivery address and order detailsCustomer order request; review, fulfillment, receipts and customer supportAuthorized staff; selected fulfillment/carrier services when neededCompleted-order and tax records: seven years, subject to applicable duties and documented holds
Support messages, order reference and relevant damage photosCustomer correspondence; answer questions and assess return/damage claimsAuthorized support staff and the necessary carrier or service provider12 months after resolution, unless a documented legal hold applies
Invoice/payment statusA future separately reviewed invoice process; reconcile payment and refundsA provider selected and disclosed before useRecord-specific legal and accounting schedule; no payment-data system currently exists
Optional analyticsNone in the chosen launch planNone after verified removal of the test tagNo production analytics retention claimed

Collect only the information needed for the stated task. Do not request payment credentials by support email or collect unrelated identity documents to answer an ordinary order question. The future payment method, provider, actual fields and retention require a privacy update before collection. USPS and UPS are planned carriers rather than connected services in the current demonstration.

4. Sharing and business purposes

The supplied operator policy prohibits selling personal data or using targeted-advertising sharing. No such application workflow is present. This does not certify Google's downstream configuration or a Global Privacy Control implementation; the test tag is to be removed before launch.

In the proposed operating plan, providers should receive only what is necessary for their service, under appropriate terms reviewed before use. Disclosures required by law or needed for a documented legal claim should be limited and recorded. Any business transfer would require separate assessment and appropriate notice. No unlisted provider relationship, marketing list, social-login service or public profile is implied.

5. Cookies, choice and marketing

The supplied application sets no first-party cookies or storage keys. The external Google script has not been fully inventoried, so this is not a claim that no third-party identifier can be processed. There is no functioning consent-management interface in this particular input website. Removing the test script is the chosen launch plan; any later optional tracking must first receive a new inventory, legal-basis assessment, notice and choice controls where required.

The demonstration sends no marketing emails. A future marketing program requires its own lawful collection, sender identification and unsubscribe process. Agreement to store terms or contacting support should not be treated as automatic marketing permission.

6. Retention and deletion

For the fictional plan, resolved support correspondence is deleted after 12 months and completed-order/tax records after seven years, subject to applicable legal duties. Records under a documented legal hold are restricted to what the hold requires and released when no longer needed. Deleted records are planned to expire from backups within 30 days. None of these server processes has been implemented or tested in the demonstration. The schedule must be checked against the real operator's obligations and systems before it becomes a live promise.

7. Security and international processing

The planned controls are role-based access, administrator MFA, encrypted transport and backups, an incident coordinator and incident logging. Required incident notifications must follow applicable law. These are operating requirements, not verified protections currently deployed by the preview. No system can guarantee absolute security, but this does not remove legal duties to protect information.

The proposed business is US-based and ships to Canada. Google processing locations were not measured. The exercise asserts no international transfer agreement or safeguard. Real hosting, email, carrier and payment providers, their processing locations and any required transfer measures must be assessed and disclosed before use.

8. Requests, rights and complaints

The planned process accepts privacy requests through the designated support contact and notice address once replaced with working business channels. Verify requests proportionately, for example through an existing order/email relationship, without requesting unnecessary ID documents. Support authorized agents after appropriate verification. Aim to respond within 30 days or any shorter applicable deadline; use lawful extensions and explanations where permitted. Provide a second-person review for an appeal where applicable. The fictional mailbox does not operate this process.

Depending on the applicable law, rights may include access or knowledge, correction, deletion, portability, objection or opt-out, restriction of certain sensitive-data uses, withdrawal of consent and non-discrimination. Applicable exceptions, verification and response requirements must be assessed rather than assuming every right has identical scope everywhere.

For California, the real operator must assess CCPA applicability and required notices and opt-outs, including legally relevant sale/sharing and preference signals. No real revenue, historical consumer count or processing dataset is supplied, so this draft claims neither an exemption nor full state-law compliance. Other US states may impose different duties.

For Canada, customers may raise concerns with the operator's privacy coordinator or the Office of the Privacy Commissioner of Canada or the relevant provincial authority. The responsible authority and applicable federal/provincial law depend on the actual business. The proposed purposes, collection, retention and access practices require that assessment before launch.

The proposed sales territory does not target the EU or UK. That fact alone is not a legal exemption for a future deployment; assess territorial scope and any additional rights, representatives or transfer requirements before operations expand.

9. Children

The proposed store is intended for adults aged 18 or older and does not knowingly request children's information. If information about a child is collected inadvertently, the planned coordinator will investigate and delete or otherwise handle it as required by law. No age-verification or parental-consent system is implemented in the demonstration.

10. Policy updates and contact

The plan is to post a dated notice for material changes and contact affected customers when lawful contact details exist. Obtain fresh consent or assent when required. The preview sends no emails. Review this notice whenever a provider, data field, purpose, retention practice or market changes.

Training privacy contact: [email protected]. Training notice address: 100 Example Lane, Demo City, TX 00000, USA. Both are fictional. Qualified legal review, verified business details and functioning request channels are necessary before real publication.

案例中的商家经营资料为模拟数据;涉及网站检查时,报告中的页面观察来自所列公开网址。

07

输出能用到哪一步,还需核对什么

把生成文件或估算结果用于店铺前,先核对下方使用限制。

SaaS 与实物商品区别

Skill 侧重 SaaS 条款与隐私,零售配送及退货需提供明确规则。

法律适用性

测试核对草稿是否符合输入,不认证条款在各地区的法律适用性。

待补业务资料

未知主体、地址、保存期限及适用法律选择需由商家提供。

常见问题

下面说明条款与隐私文档需要哪些经营资料、如何选择起草流程,以及发布前怎样核对内容与网站实际行为。

服务条款与隐私政策分别解决什么问题?

服务条款说明使用或购买服务的规则,例如账户、付款、允许的用途、取消及双方责任;隐私政策说明个人数据如何收集和处理。写好其中一份,不代表另一份也完成了,但企业身份和联系信息等共同事实必须一致。

Legal ToS Privacy 从产品与网站证据出发,让两份草稿对应同一套实际业务。应提供真实的账户、结账、客服和数据流程,并检查冲突:只有结账演示的网站不应写成已处理真实付款,隐私说明也不应承诺代码里不存在的控制功能。

小店铺起草隐私政策前,需要整理哪些信息?

先清点结账、联系表单、账户、分析工具及客服实际收集的信息,再整理企业联系渠道、每条数据流的用途、相关服务商、保存期限及请求处理方式。ICO 面向小型机构的英国指引说明了用途、保存与共享信息为什么需要清楚表达;具体适用要求仍与销售市场有关。

代码扫描可以发现表单或标签,但不能推断未公开的数据保存政策,也不能替你确定企业主体。这些经营决定需要你提供。Skill 的缺项清单有用之处,正是把“网站里发现的事实”与“仍需经营者补充的信息”分开。

SaaS 或订阅业务还需要补充哪些条款资料?

需要说明试用结束后的处理、计费与续费方式、取消后哪些权益变化、是否退款或发放余额,以及关闭账户后访问权限与存储数据如何处理。如果允许用户上传内容,还应提供内容权利、管理流程及导出行为。草稿应对应已经实现的产品,而不是路线图里的理想状态。

本页展示的是虚构实物商品店铺案例,不是订阅计费的完整测试。用于 SaaS 时,可按它的审查与提问流程补充自己的订阅事实,再对照定价页、结账和取消界面核查;代码不能确定的合同选择,由相应审核人处理。

可以直接复制别家店铺的条款,或者套通用模板吗?

模板可以帮助你发现要讨论的事项,却不能证明其中的说法适合自己的业务。别家店铺可能使用不同支付服务商、服务不同地区、采用不同退款规则或保存数据的用途。只替换公司名称,不会消除这些实质差异。

更有用的任务是:把已有草稿与自己的网站、经营资料对照,列出缺少依据的说法和未确定的决定。Legal ToS Privacy 的价值就在这种审查与起草流程。合同选择和特定地区要求仍应交给审核人处理;文字写得完整,并不证明政策与实际功能已经一致。

什么情况下选 Legal ToS Privacy,什么情况下选 Compliance Pages?

当前重点是审查代码和宣传承诺、生成相互对应的条款与隐私文档,并集中补齐经营决定时,选 Legal ToS Privacy 更贴近任务。完整示例在原审计及草稿之后,由辅助续跑使用明确标注为虚构的商家回答补齐了 33 个变量。

如果还要在网站中创建政策页面、导航和同意控件,Compliance Pages 更适合。条款文档完成,不会自动把横幅接到分析脚本上。两者一起使用时,应共享一套经营资料,并指定每个页面由哪份产物负责,避免后一次工作覆盖已经审核的政策选择。

发布或更新生成的条款与隐私政策前,应该检查什么?

先核对企业主体与联系信息,清除全部未解决的占位符,再把文档与真实支付、退款、数据及账户流程对照。功能问题应单独处理:修改一句同意说明,并不能修复顾客作出选择前就加载的脚本。保留本次文档版本和采用的经营决定,方便后续追溯。

产品变化时,重跑受影响的审查步骤并检查差异,更新对应承诺;是否需要另行通知或重新接受,由负责审核的人按具体情况判断。本地案例完成了变量补齐与结构检查,但原样发布仍是在描述一家虚构商家,而不是你的业务。

暂无评论。

发表评论

请先为每一项打分,再分享你的真实使用体验。

任务有效性
安装与使用难度
稳定性与边界
文档清晰度
首次获得有效结果

原始页面未公开评分、评价、Product Hunt 投票、Stars、Forks、安装或下载数量。