Privacy

How we process your data.

The complete list of what a site running the Plugie Insights SDK can send, and when. It is generated from the code, not written by hand.

This is the complete inventory of what a site running the Plugie Insights SDK can send. If a field is not listed anywhere on this page, no shipped SDK sends it.

Fields we collect

Sent today by the shipped WordPress SDK, only after you switch data collection on, and only for as long as it stays on.

Path Type Optional Trigger Purpose
event.consent.accepted_at string no event When data collection was agreed to on this site. On an event the server does not read it – a withdrawal is dated by when the event happened, not by this – so here it only travels as part of the consent state CON-3 puts on every message.
event.consent.enabled boolean no event Whether data collection is switched on here. On an event the server does not read this field: when the event is a withdrawal of consent it records the withdrawal from the event type itself rather than trusting this flag.
event.consent.version string no event Which version of the consent notice was agreed to here. On an event it is read only when the event withdraws consent, where it records which notice is being withdrawn from.
event.event_id string no event A random identifier for this one event, so that an event resent after a network failure is recorded once rather than twice.
event.feedback.comment string yes event The optional comment the site owner typed in the survey, at most 300 characters. The survey the SDK draws asks them not to include personal information; a plugin that draws its own is asked to do the same. Sent only when they answer and write something; it tells the plugin authors what a reason alone cannot.
event.feedback.reason string yes event The short key of the reason the site owner picked when deactivating, such as found_better. Sent only when they answer the survey; it tells the plugin authors why sites leave.
event.feedback.status answered | skipped | not_asked yes event Whether the site owner answered the deactivation survey, chose to skip it, or was not asked (the survey is off, the plugin was deactivated in bulk, from the command line or network-wide, or no answer reached the deactivation in time). Sent with every deactivation, so the plugin authors can tell a quiet survey from an unasked one.
event.installation.id string no event The random identifier this site created for itself the first time the plugin ran. It is not derived from your site address or from any account. On an event the server does not read it – the event is attributed using the access token this install registered with – so a wrong value here cannot attach an event to another install.
event.occurred_at string no event When this event happened, by the site’s own clock. It places the event in order against the others from this install, and when the event withdraws consent it also becomes the date on the consent record – the date your consent history is ordered by.
event.plugin.id string no event Names the plugin this report is about. The server does not route by it – which plugin a report belongs to is settled by the access token this install registered with – so a wrong or forged value here cannot direct data anywhere else.
event.plugin.version string no event The version of the plugin running here. For a plugin_deactivated event the server stores it alongside the deactivation survey answer, so the plugin authors can break deactivation reasons down by version; for the other three event types it is not read, and the version in use is measured from the periodic report instead.
event.sdk.version string no event The version of the Plugie reporting library built into the plugin. On an event the server never reads it: the withdrawn-version check and the copy kept for tracing both happen on the periodic report. A plugin_deactivated event stores its own plugin version alongside the deactivation survey answer (see plugin.version), but this SDK version is not part of that – no event stores it.
event.type plugin_activated | plugin_deactivated | plugin_uninstalled | consent_revoked no event Which of four things happened here: the plugin was activated, deactivated, uninstalled, or data collection was switched off. This is how the plugin’s authors see installs gained and lost.
registration.consent.accepted_at string no registration When data collection was agreed to on this site. This is the message where it is kept: it becomes the date on the consent record, and the consent history is ordered by it.
registration.consent.enabled true no registration Confirms that data collection was switched on here before anything was sent. It is refused unless this is true, and the value is written into a new consent-record row on every registration – the very first registration for a new install opens this install’s consent history, and any later registration (for example after this install’s token is lost or rejected) adds another row to that same history rather than reopening it.
registration.consent.version string no registration Which version of the consent notice was agreed to here. It is written into that same consent-record row on every registration, and the dashboard reads the most recent row – from registration or from a later consent_revoked event – to say which notice a site is currently on.
registration.environment.environment_type local | development | staging | production no registration Whether WordPress reports this site as local, development, staging or production. It is set on the install record when the install is first created, and the dashboard counts production sites only unless asked otherwise, so a staging copy is not counted as a real install from the start.
registration.environment.php string no registration The PHP version this site runs. On a registration the server does not read it – the install record keeps only the environment type – so this figure is collected from the periodic report instead.
registration.environment.wordpress string no registration The WordPress version this site runs. On a registration the server does not read it – the install record keeps only the environment type – so this figure is collected from the periodic report instead.
registration.installation.id string no registration The random identifier this site created for itself the first time the plugin ran. This is the message where it does its work: together with the plugin it is what the install record is keyed on, so a site that reinstalls or restores a backup is recognised as the same install rather than counted twice. It is not derived from your site address or from any account.
registration.plugin.id string no registration Which plugin is registering. This is the one message where this field decides anything: it selects the plugin your new install is attached to.
registration.plugin.version string no registration The version of the plugin registering. The server does not read it here – the install record does not store it – so which releases are in use is measured from the periodic report instead.
registration.sdk.version string no registration The version of the Plugie reporting library built into the plugin. On a registration the server does not read it: the install record is created from the plugin, the identifier and the environment type, and the withdrawn-version check runs on the periodic report instead.
snapshot.consent.accepted_at string no snapshot When data collection was agreed to on this site. On a periodic report the server does not read it – the consent record is written at registration and when consent is withdrawn – so here it only travels as part of the consent state CON-3 puts on every message.
snapshot.consent.enabled boolean no snapshot Whether data collection is switched on here. It is stored on the report itself, so each report carries the consent state it was collected under.
snapshot.consent.version string no snapshot Which version of the consent notice was agreed to here. It is stored with the report, and compared against the version the plugin now requires so the server can tell your site a newer notice exists. The report is stored either way, less any list of other plugins or theme when the versions differ; the plugin decides whether to ask you again.
snapshot.environment.environment_type local | development | staging | production no snapshot Whether WordPress reports this site as local, development, staging or production. It is stored on the report and kept current on the install record, and the dashboard counts production sites only unless asked otherwise, so test and staging copies are not counted as real installs.
snapshot.environment.php string no snapshot The PHP version this site runs. It is stored with each report and rolled up daily, so the plugin authors know which versions are still in use before they drop support for one.
snapshot.environment.wordpress string no snapshot The WordPress version this site runs. It is stored with each report and rolled up daily, so the plugin authors know which versions are still in use and must keep working.
snapshot.features object of object of boolean | number | string no snapshot The usage measurements the plugin’s own authors defined – counts, on/off settings and chosen options for that plugin’s features. Which measurements exist is decided by the plugin and not by Plugie, and each value is a single number, true/false, or a short label.
snapshot.identity_conflict boolean yes snapshot A true/false flag set when this install looks as though it was copied or moved – restored from a backup, say, or cloned to staging. While it is set the server stops recording changes in the measurements, so a clone does not add invented activity to the history of this install. The site address it is derived from is hashed and kept on the site; only this flag is sent.
snapshot.installation.id string no snapshot The random identifier this site created for itself the first time the plugin ran. It is not derived from your site address or from any account. On a periodic report the server does not read it – the report is attributed using the access token this install registered with – so a wrong value here cannot attach data to another install.
snapshot.installation.lifecycle active | deactivated no snapshot Whether the plugin reports itself as active or deactivated here. The server does not read it on a report: an install starts out counted as active and moves only when it sends an activation or deactivation event, never because of this field.
snapshot.plugin.id string no snapshot Names the plugin this report is about. The server does not route by it – which plugin a report belongs to is settled by the access token this install registered with – so a wrong or forged value here cannot direct data anywhere else.
snapshot.plugin.version string no snapshot The version of the plugin running here. It is stored with each report and rolled up daily, so its authors can see which releases are still in use and whether a problem is confined to one of them.
snapshot.sdk.version string no snapshot The version of the Plugie reporting library built into the plugin. On a periodic report it is checked against the list of withdrawn versions – a withdrawn one is told to stop and its report is not stored – and otherwise kept with the report, so a figure that looks wrong can be traced to the code that produced it.
snapshot.sent_at string no snapshot The time this site’s own clock recorded when it sent the report. It is stored exactly as sent and is not what orders your history – the server uses the time it received the report for that – so a site whose clock is wrong cannot reorder its own record.
snapshot.snapshot_id string no snapshot A random identifier for this one report, so that a report resent after a network failure is stored once rather than twice.
snapshot.steps object of string yes snapshot When this site first reached each step of getting started with the plugin: milestones the plugin’s own authors name, such as connecting an account, and activated, recorded when collection is allowed, or the plugin is switched on with collection allowed, on a site that holds no access token from Plugie: one that has not registered yet, or whose token the server refused. Each entry is a step name and a timestamp from this site’s own clock. Custom step names are chosen by the plugin’s authors, as measurement names are, and are limited to lowercase letters, digits and underscores; no user, email or address is recorded with them. It is recorded only while collection is allowed, and it shows the authors where new sites stall before the plugin is useful to them.

Fields sent only if the plugin turns them on

Sent by the shipped WordPress SDK only when the authors of the plugin you installed have turned them on, and only while your consent is for their current notice. Before turning these on, the authors must publish a new notice that names them and raise its version, so that you are asked again; the SDK holds these fields back until you accept the current version, but it can check neither the notice’s wording nor that its version was raised. If the version was raised, a site that accepted an earlier notice keeps sending the fields above and none of these until it accepts the new one.

Path Type Optional Trigger Purpose
snapshot.plugins.active string[] yes snapshot The slugs (short names) of the other plugins active on this site. Sent only if this plugin’s authors turn it on and you have accepted their current consent notice, which they must update to name it. It lets them find conflicts with plugins commonly installed alongside theirs.
snapshot.plugins.inactive string[] yes snapshot The slugs of the other plugins installed here but not active. Sent only if this plugin’s authors turn it on and you have accepted their current consent notice, which they must update to name it. Separating installed from running shows whether a conflict is even possible.
snapshot.theme.slug string yes snapshot The slug of this site’s parent theme. Sent only if this plugin’s authors turn it on and you have accepted their current consent notice, which they must update to name it. Themes are a common source of display conflicts, so it tells them which to test against.

What else leaves your site

These two rows are not fields inside a request body, so “collected” above does not describe them: an IP address reaches any web server because that is how HTTP works, and a bearer token travels in a request header, not the JSON payload. Saying a connection detail is seen is a different claim from saying it is logged, so what matters for each row is not why it arrives but what becomes of it – which is why this table states handling rather than purpose. Why each one reaches our servers at all:

  • connection.ip_address: 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.
  • connection.authorization: A random token issued to this install when it registers and sent with each later report, so that one install cannot write into another install’s history.
Path Type Optional Triggers Handling
connection.ip_address string no registration, snapshot, event 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.
connection.authorization string no snapshot, event Sent to your site in readable form exactly once, in the reply to registration. The server keeps only a SHA-256 hash of it, so a copy of the database holds nothing that could be replayed as your install. It identifies the install and not you. It is absent from the registration request itself, because that is the call that issues it.

What the server can tell your site to do

Everything above travels from your site to us. This section is the other direction, and it is not data collection at all – which is exactly why it needs saying here, because nothing else on this page would have told you. Our reply to a report can carry an instruction, and the reporting library obeys it: we can tell a site to stop reporting for good, to wait before sending again, or how often to send. A server that can change what code on your site does is worth disclosing whether or not it collects anything by doing so.

The limits of that, which are as much the point as the instructions themselves: each one reaches the reporting library and nothing else on your site, none of them carries code, a file path or an address, and the library acts on one only when it arrives on a successful reply – so the same word in a reply that rejected your access token is ignored, and a rotated credential cannot silence a site for good. None of them can arrive before you opt in either: with collection switched off the library sends no request, so there is no reply to carry one.

Instruction Sent with What it does to your site How long it lasts Who sets it
stop the reply to a periodic report Tells this site to stop sending, and the reporting library writes that to the site’s own settings and checks it before every later request – so it outlasts the reply that carried it and survives a restart. Lifecycle records go on being held locally, up to a cap of fifty, and none of them is ever sent. Permanent. Nothing in the reporting library ever lifts it; only a site administrator clearing the stored flag by hand would start reporting again. Plugie, not the plugin’s authors. It is issued when the reporting library’s own version appears on a refusal list held in our server’s configuration, which is how a faulty release of the library is contained without waiting for every site to update it.
retry_after the reply to a registration, a periodic report or an event Tells this site to send nothing until a stated number of seconds has passed. The reporting library stores the deadline and refuses every send before it. Exactly as long as the reply says – at least one second, at most thirty days. It lapses on its own; nothing has to lift it. Plugie. It is what our rate limiter answers when a source has used up its allowance for the hour, and the delay it names is what is left of that hour.
consent_version_outdated the reply to a periodic report Tells this site that the plugin’s authors now ask for a newer consent notice. It stops nothing except any list of other plugins or theme, which only the current notice can cover: the report that carried it was already stored without them, and the site keeps sending everything else the reporting library collects, and none of them, until you agree. That includes anything a later version of the library collects that the notice you agreed to may not name, such as onboarding steps. The reporting library records the version now asked for so the plugin can put the question to you again. Until you are asked again and agree, or do not. Nothing expires it, and nothing is withheld from you while it stands. The plugin’s authors, by naming a required consent version for their plugin.
collection_interval the reply to a registration Sets how often this site sends its periodic report – daily or weekly. The reporting library stores the answer, and it overrides whatever interval the plugin was built with. Until a later registration replaces it. Registration is lazy, so a change made here reaches a site that is already reporting only when that site registers again – after its access token is lost or refused – and not on its next report. The plugin’s authors, from their Plugie dashboard.

Three of the four rows above are statuses our reply can carry; collection_interval is a field on the reply to registration rather than a status, and it is listed with them because from your side it is the same fact. A fourth status, accepted, is not listed because it instructs nothing beyond carrying on as scheduled. A test fails if a fifth status is ever added to the contract without a row here.

What this page can and cannot guarantee

A test fails if a field in the schemas above has no documented purpose, and a test fails if this file ever stops matching what the schemas produce right now – so a new or changed field cannot arrive silently: it always shows up in this file’s diff. What that test cannot do is tell a documented purpose from a correctly documented one, because nothing mechanical can check that a sentence is true of the code beside it. The instruction table is narrower still: those rows are written by hand rather than read out of a schema, so the test behind them fails when the contract gains a reply the table does not name, and cannot check that any row describes its instruction correctly. This page is accurate as verified when it was last generated and reviewed, which is not the same claim as accurate.