Plenix 2026.10.33 — An incident register and clearer end-of-subscription rules
Plenix now keeps a formal register of every incident and data breach, emails you before it changes a supplier that handles your data, and ends a cancelled subscription at exactly the end of the term you paid for.
T
The Plenix Team·13 October 2026·2 min read
Release 2026.10.33 is about how Plenix runs as a company: how we record things that go wrong, how we tell you about changes to our suppliers, and what happens when a subscription ends.
New features
- A formal incident and breach register. Every service incident, security incident and personal data breach at Plenix is now recorded in one register, with what happened, who was affected, the cause, the fix and what we changed afterwards. An entry cannot be deleted, and it cannot be closed until the cause and the fix are written down.
- Notification clocks. When an incident involves personal data, the register counts down the 24 hours we allow ourselves to tell affected customers and the 72 hours the law allows to tell the regulator, and shows clearly when a notice is overdue.
Changes
- We email you before we change a supplier. When Plenix adds or replaces a supplier that handles customer data, the administrator contact on every customer account is emailed at least 30 days before the change. You do not need to subscribe to anything. The supplier list stays at plenix.cloud/sub-processors.
- The register starts with our two 2026 outages. The sign-in outage in August and the Windows agent outage in October are both recorded. Neither involved customer data. The register holds no personal data breach.
Fixes
- A cancelled subscription ends when the paid term ends. A subscription paid by direct debit, PayPal or bank transfer that was cancelled stayed active after the end of the term. It now ends on the last day you paid for, in the same way as a card subscription. Your workspace then stays read-only for 90 days so that you can view and export your data.