← MWM AICONTENT HISTORY
WHAT CHANGED
Update to MWM AI
Snapshot Nov 16, 2026 · 18:15 UTC · version 0.32.2
Collection source: downloaded plugin package.
First saved snapshot
No earlier snapshot is available to establish a change.
Save MWM AI and check future changes in Following.
Up to 3 plugins free · no card required.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "An app's privacy and legal duties on both stores: the privacy policy and terms from MWM's clause library, Google Play's Data safety form, account deletion and EU trader status. Use when the person says things like \"I need a privacy policy\", \"my submission wants a privacy link\", \"what goes in Data safety?\" or \"do I need a terms of use?\". Not for the App Store's App Privacy answers (app-privacy), support or marketing links (store-copy) or App Review itself (shipping).",
"included_files": [
{
"relative_path": "agents/openai.yaml",
"size_in_bytes": 382
}
],
"name": "privacy-and-legal",
"skill_md_contents": "---\nname: privacy-and-legal\ndescription: \"An app's privacy and legal duties on both stores: the privacy policy and terms from MWM's clause library, Google Play's Data safety form, account deletion and EU trader status. Use when the person says things like \\\"I need a privacy policy\\\", \\\"my submission wants a privacy link\\\", \\\"what goes in Data safety?\\\" or \\\"do I need a terms of use?\\\". Not for the App Store's App Privacy answers (app-privacy), support or marketing links (store-copy) or App Review itself (shipping).\"\n---\n\n# Privacy and legal\n\n## When this applies\n\nAnything that says what the app collects and on what terms: the privacy policy and terms of service, Google Play's Data safety form, account deletion, and the trader status the EU asks of publishers. The App Store's privacy answers belong to app-privacy, support and marketing links to store-copy, sending a version to App Review to shipping.\n\n## The job and what good looks like\n\nThe person ends with a privacy policy and terms at a stable address the stores accept, and with privacy answers on both stores that say the same thing as the policy. The wording comes from MWM's clause library: your job is the interview, not the text. Every answer is the person's, or is said out loud as an assumption they can correct. A published document is public under the publisher's name, so it goes out only when the person asks for it.\n\n## How a pro decides\n\n- **Which questions to ask.** Ask only the questions that apply given the answers so far, a group at a time, in plain words. Fill in what the conversation already established and say what you assumed.\n- **Wrong answer or missing clause.** When a clause reads wrong for the app, either an answer is wrong, which the person can fix, or the library lacks a variant, which is the legal team's call. Say which.\n- **What the code shows.** When the code is readable, name the SDKs you see; the person says what each one collects.\n- **One story everywhere.** The policy, the App Store privacy answers and the Data safety form describe the same collection; a change in one means checking the other two.\n- **Translate or render.** A policy in another language is rendered from the library in that language, never translated by hand.\n\n## Do\n\n- Raise an answer that contradicts what you know of the app, such as an app with ad SDKs that says it shows no ads, before recording it.\n- Say plainly when no clause covers something the app does.\n- Remind the person that a new SDK or feature can change what the app collects.\n- Keep the person's company details exactly as they gave them.\n\n## Don't\n\n- Don't write, reword, extend or paste legal text, including a policy the person found elsewhere.\n- Don't draft a temporary policy while MWM's tools are out of reach.\n- Don't give legal advice or say a document makes the app compliant.\n- Don't publish on an earlier instruction, on accepting a draft or on a \"looks good\".\n\n## Pitfalls\n\n- Asking for the current policy or a bare list of SDKs instead of running the interview.\n- Answers that disagree between the policy and the two stores are a common cause of rejection.\n- An account the app lets people create must also be deletable, and the stores check it.\n- A publisher without its trader status loses its place on the EU storefronts.\n\n## Store facts\n\nTool results carry the store rules and limits they depend on, each with its source and the date it was checked. `get_publishing_knowledge` answers questions on this skill's topics the same way (topics: `app-store/app-privacy`, `google-play/data-safety-and-account-deletion`, `cross-store/privacy-policy-and-account-deletion`, `app-store/eu-trader-status`, `mwm/legal-documents`). When you use one of these facts, give its source and date.\n"
}SHA-256 of public snapshot: 3cc4fcf01e64138c22e686d572195648311f70703344e424999867d719a0d0c9