Privacy
Readme disclosure
Paste this into your plugin’s readme.txt (or its Privacy section) to document this SDK for WordPress.org guideline 7, which requires disclosing any external server a plugin contacts.
Two notes before you paste, which are for you and not for your readers. Guideline 7 also asks, preferably, for a clearly stated privacy policy: if you publish one, link it in your own readme beside this block, in your own words – the text below carries no slot for it on purpose, because a placeholder that ships unfilled is worse on your plugin page than no link at all, and this text is regenerated from our schemas rather than edited by you. And the field-by-field list the closing paragraph names has no public address yet – ask Plugie for the current copy and pass it on to anyone who asks you for it. Until it is published, that paragraph deliberately does not send your readers to a file path inside Plugie’s own repository, which is not something a site owner reading your page on WordPress.org can open. When that address exists this text will carry it, and the drift test will make your committed copy stale until you regenerate it.
This plugin includes the Plugie Insights reporting library, which contacts Plugie’s servers to report usage data tied to a random installation identifier – not your name, email, site address, or account, but a per-install ID that can be recognised across separate reports. That makes this data pseudonymous, not anonymous. None of it is sent before your explicit opt-in in this plugin’s settings, and it stops as soon as you withdraw that consent. What it sends, and when:
- Registration (lazily: on whichever send first finds no token stored, after you opt in, and again if this install’s token is ever lost or rejected): consent, environment, installation, plugin, sdk
- Periodic snapshot (on a recurring schedule the plugin sets, for as long as collection stays switched on): consent, environment, features, identity_conflict, installation, plugin, sdk, sent_at, snapshot_id, steps
- Also in the periodic snapshot, only if this plugin turns it on (and only once you accept its current consent notice, which must name it): plugins, theme
- Immediate events (immediately for activation, deactivation, or uninstall; withdrawing consent only if you separately tick a box offered when you turn collection off – left unticked (the common case), nothing is sent for it): consent, event_id, feedback, installation, occurred_at, plugin, sdk, type
Your site’s IP address reaches our servers the way it does with any web request. It is used only to limit how often one source can register, which is what stops a single machine creating thousands of false installs. The address itself is never written to storage and is never kept beside your data. Before it is used it is replaced by a shortened, one-way fingerprint computed with a secret that is created when the server starts and never saved, so the fingerprint cannot be turned back into an address and stops matching after a restart. Only that fingerprint is stored, as a counter for a single one-hour rate-limit window. Once an install has registered, its later reports are limited by its installation ID rather than by its address.
Our reply can also change what the reporting library does on your site. It can be told to stop reporting permanently, to wait a stated time before sending again, that a newer consent notice is now asked for, or how often to report. Only the reporting library is affected – nothing else on your site – and no reply can reach you before you opt in, because until then nothing is sent and there is nothing to reply to.
The complete, field-by-field list – including the fields sent only if this plugin turns them on, exactly what happens to your IP address and access token, and each instruction a reply can carry – is kept by Plugie as collected-fields.md. It has no public address yet, so ask this plugin’s authors for a copy and they will get you the current one.