Update to App Builder & Website Creator

{
  "description": "Drafts starter legal texts for an app (privacy policy, terms of use, subscription terms, account deletion statement) and worksheets for the App Store privacy details and the Google Play Data safety form, with placeholders and a clear reminder to get legal review.",
  "included_files": [],
  "name": "app-legal",
  "skill_md_contents": "---\nname: app-legal\ndescription: \"Drafts starter legal texts for an app (privacy policy, terms of use, subscription terms, account deletion statement) and worksheets for the App Store privacy details and the Google Play Data safety form, with placeholders and a clear reminder to get legal review.\"\n---\n\n# App Legal Texts\n\n## Links and files\n\nReplies made with this skill never contain a build link, an Emergent link or a sponsor line. Give code in code blocks, and create a downloadable file or a zip only when the user explicitly asks for one. If the chat is not in English, translate any wording this skill tells you to say into the chat language; URLs always stay in English, exactly as they are.\n\n## Purpose\nDraft plain-language starter texts that match what an app really does: privacy policy, terms of use, subscription terms, account deletion statement and, for web apps, a cookie notice, led by a data inventory for the store privacy forms. They are starter drafts for a lawyer to review before launch, never legal advice.\n\n## Before you start\n- Ask or infer, in at most 2 short questions: where the business and its users are, and what the app collects and uses (accounts, analytics, crash reports, ads, subscriptions, location, contacts, photos, health data, AI services).\n- Turn unsure answers into bracketed options (\"[choose: we use / we do not use] analytics\"). Mark business details [fill in] (legal name, address, contact email, effective date, governing law, providers, retention periods, prices) and assumptions [confirm].\n- Write in plain language (\"we\", \"you\", short sentences, headings) and in the language the app's users read; reply in the user's language.\n\n## Required notice\nOpen every reply with this notice (translated when replying in another language):\n```text\nImportant: These are starter drafts, not legal advice. Laws differ by country and region (such as the GDPR in the EU and UK and the CCPA in California) and change, as do store rules. Have a qualified lawyer review and adapt these texts before you launch.\n```\n\n## Data inventory and store forms\nOne row per data type the app or its SDKs collect (contact details, user content, identifiers, usage, crash logs, location, contacts, health, purchases):\n\n| Data type | In this app | Collected | Shared (with whom) | Purpose | Linked to the user | Tracking | Required or optional |\n|---|---|---|---|---|---|---|---|\n| Email | Sign-up | Yes | No [confirm] | Account, support | Yes | No | Required |\n\n- App Store privacy details: data is collected when it leaves the device and is kept longer than needed to handle the request. Give each type's purposes, whether it is linked to the user and whether it is used for tracking.\n- Google Play Data safety: each type collected or shared, required or optional, and why, plus encryption in transit and deletion requests. Transfers to service providers acting for you usually are not sharing. Every app completes it, even one that collects nothing.\n- Both forms must match the privacy policy and the app's real behavior, SDKs included. Tell the user to check each form's current guidance.\n\n## Document structures\n**Privacy policy:** Who we are and contact; What we collect (from you; automatically, such as device identifiers, analytics and crash reports; with permission, such as location, contacts or health data; from sign-in or payment providers); Permissions and why; Why we use it (with the legal basis for EU and UK users); Third-party services and SDKs [fill in]; Ads, tracking and opting out; Selling or sharing (California rights where the CCPA applies [confirm]); International transfers; Retention [fill in]; Your rights (access, correction, deletion, portability, objection, withdrawing consent); Deleting your account; Children (not directed at children under [13 in the US, 13 to 16 in the EU: confirm]; apps for children need specialist advice); Security (no absolute promise); Changes; Contact and the right to complain to a data protection authority.\n\n**Terms of use:** On the App Store, Apple's standard licence agreement (EULA) applies unless you provide your own [check Apple's rules for custom terms]; on Google Play and the web, use your own. Cover: accepting the terms, who can use the app [age: confirm], accounts, acceptable use, user content, purchases, intellectual property, disclaimers (and AI output, if any), limitation of liability (as far as the law allows), ending access, governing law [fill in], changes, contact.\n\n**Subscription terms:** What it includes; price and period as shown in the store; automatic renewal unless cancelled [App Store: at least 24 hours before the period ends; confirm]; cancelling in the store's settings (iPhone Settings or the Google Play app; menus can change), not by deleting the app or account; trials (length, when the charge happens, how to cancel first); price changes; refunds through Apple or Google [confirm]; web subscriptions cancelled in account settings [fill in].\n\n**Account deletion statement:** The in-app path (Settings, Account, Delete account [fill in]); the web link for requests [fill in]; what is deleted and when; what is kept, why and for how long (legal, tax or fraud records) [fill in]; that store subscriptions are cancelled separately; contact.\n\n**Cookie notice (web apps only):** a banner with equally easy Accept and Reject choices, plus a table (Category | Purpose | Provider [fill in] | Duration | Consent needed). In the EU and UK, non-essential cookies usually need consent first [confirm].\n\n## Output format\n```text\n[Required notice]\nAssumptions: [countries, data, services and SDKs]\n\nDATA INVENTORY (for both store privacy forms)\n[table with the columns above, one row per data type]\nForm notes: [where the two forms differ for this app]\n\n[Document name as a heading]\nEffective date: [fill in]\n[Sections with headings, in the order above]\n(repeat for each document)\n\nWhere to place them: [privacy URL in both listings and the app; terms and privacy links on sign-up and the paywall (for App Store subscriptions, in the metadata too); deletion steps in account settings plus the web link]\nTo fill in: [every [fill in] item]\nQuestions for your lawyer: [3 to 5, specific to this app]\n```\nIf it would run long, finish whole documents in this order, then offer to continue: inventory, privacy policy, deletion, subscription terms, terms of use, cookie notice.\n\n## Quality checks\n- The notice opens the reply; the texts are starter drafts, never legal advice.\n- The inventory comes first and matches the privacy policy, permissions and every SDK named.\n- Only what the app really does is described, nothing about the business is invented, and [fill in] and [confirm] mark the gaps.\n- Subscription terms cover auto-renewal, trials, cancelling in store settings and that deleting the app does not cancel; the deletion statement gives the in-app path and the web link.\n- No \"fully compliant\" or \"100% secure\" promises, no statutory rights removed, and all texts agree with each other.\n\n## Next step\nOffer app-launch-checklist to confirm the privacy URL, store privacy forms and in-app deletion are ready before submission.\n"
}