Required Disclosure
WordPress.org’s plugin guidelines require every plugin to disclose, in plain language, any third-party service it connects to and what that service does with the data it receives. This isn’t optional or a formality — reviewers check for it, and a plugin that sends telemetry without disclosing it is a common reason for rejection or, for an already-published plugin, removal from the directory.
The Appneck SDK sends telemetry once a site owner consents (see Handling User Consent), which makes Appneck exactly the kind of third-party service the guidelines mean. You need SDK 0.4.0 or later for the snippet below to be true: older versions registered a free plugin with Appneck before the owner answered the prompt. That’s true regardless of how little data a given plugin actually collects — the disclosure requirement is about the connection existing at all, not about the volume or sensitivity of what’s sent.
Where it goes
Paste the block below into your plugin’s readme.txt, under a Privacy
heading inside the Description section (WordPress.org’s Description
section is what’s compiled from readme.txt, and reviewers read privacy
disclosures there specifically — a note only in your plugin’s PHP comments or
on your own website doesn’t satisfy the requirement).
The snippet
Copy this verbatim. It’s already accurate for a default Appneck integration: consent is required before anything is sent, and nothing about integrating the SDK starts data collection on its own.
This plugin uses [Appneck](https://appneck.com) SDK to collect some telemetry data upon the user's confirmation to troubleshoot problems faster & make product improvements, and, with the same confirmation, to email the confirming admin about security and feature updates.
Appneck SDK **does not gather or send any data by default.** The SDK only starts when a user clicks **Allow & Continue** in the admin notice; until then, and if they click Skip, nothing is sent. The data it then shares is: the admin's name and email (for update emails only), the site URL, WordPress, PHP, WooCommerce and plugin versions, installed plugins and active theme, locale, timezone and country, server software, and which plugin features are used. It can be turned off at any time in the plugin's settings.
The one exception is the optional deactivation survey: if a user chooses to answer it, their answers (and their name and email, unless they tick "Send anonymously") are sent when they click Submit.
Learn more about how [Appneck collects and uses this data](https://appneck.com/privacy-policy).
The two bracketed-link lines are Markdown, exactly as WordPress.org’s own
readme.txt parser expects — leave them as [text](url), don’t convert them
to plain URLs or HTML <a> tags.
Pro plugins sold outside WordPress.org
A pro build ('is_premium' => true) shows no prompt and sends usage data and
the site administrators’ names and emails. WordPress.org’s rules don’t cover
a plugin you sell yourself, but data-protection law (GDPR and similar) still
does. Say in your terms of service or privacy policy what is sent to Appneck
and why. The snippet above describes a free plugin; don’t paste it into a pro
build unchanged.
If you already shipped without it
Add it on your next release. There’s no migration or code change required —
this is a readme.txt edit only, and it applies retroactively to however
your plugin already behaves.
Next: Handling User Consent →