Telemetry & privacy
What data the plugins send to setyenv.com, and when.
The presence report (both editions)
Once a day the suite reports that it exists — one call per site, not per plugin. It is how we count hosts and containers running the product.
| Data point | Purpose |
|---|---|
| Site fingerprint | Opaque site identifier (a hash, not the URL). |
| Host name | The host of the site's home URL (what a DNS lookup shows). |
| Runtime | wordpress, or docker inside our published image. |
| Edition | community or enterprise. |
| Licence key | Only on an Enterprise site, so the host is linked to its licence. |
| Plugin versions | Which versions of the suite plugins are installed. |
| PHP / WordPress version | Compatibility tracking. |
| Last seen timestamp | When the site last checked in. |
The licence check (Enterprise only)
A site with an Enterprise key verifies it once a day (Licenses): the key and the site fingerprint. Nothing else.
The update check (both editions)
WordPress's standard update check calls the Setyenv update channel (updates.setyenv.com) with the plugin slug, the installed version, the site's identity (the key, or the fingerprint when there is none) and whether auto-updates are on for that plugin — see Plugin downloads.
What is NOT sent
- No record content.
- No workflow definitions.
- No agent conversations.
- No API keys or connection credentials.
- No user data, no personally identifiable information.
Retention
The presence row is kept per site and overwritten by each report; a host that stops reporting leaves the active count after a few days. Licence activations are kept with the licence.
GDPR
The portal's customer dashboard has its own privacy policy covering account data — see GDPR & privacy. Deleting your account deactivates your licences and removes their activations.