WordPress.org Plugin Directory · Platform guide
Privacy policy for WordPress plugin developers
If you publish a plugin on WordPress.org, Guideline 7 says plugins may not track users without their consent, so any usage tracking or phoning home must be opt-in. WordPress also lets your plugin suggest privacy policy text to site owners with wp_add_privacy_policy_content. If your plugin sends data to your own service, publish a privacy policy for it.
What WordPress.org Plugin Directory requires
Detailed Plugin Guidelines — Guideline 7
“Plugins may not track users without their consent.”
Source: developer.wordpress.org verified 2026-10-30
What common SDKs collect
| SDK / API | Data it collects | Source |
|---|---|---|
| Typical plugin data flows |
| Source: developer.wordpress.org |
Everything in this table must appear in your policy if the SDK ships in your build.
Where to put the URL
- 3.1Your plugin’s own site: a privacy policy covering any data your servers receive.
- 3.2Inside the plugin: register suggested text with wp_add_privacy_policy_content on admin_init.
- 3.3readme.txt: say what is sent externally and link the policy.
Sample clause
§ 4.1 · Usage data (opt-in)
If you choose Allow usage tracking in the plugin settings, the plugin sends your site URL, WordPress version, PHP version and active theme to our server once a week. Nothing is sent unless you opt in, and you can turn it off at any time.
Questions
- Can my WordPress plugin collect usage data?
- Only with the user’s consent. Guideline 7 forbids tracking users without consent, so make it opt-in and disclose it.
- Is this for site owners who want a privacy policy plugin?
- No. This page is for plugin authors. Site owners can still generate a website policy with PrivacyPage.