Does plusnet keep copy's of event log

1. What the question really means: “keep copies of event log”

The user is asking whether Plusnet retains the same event-log entries customers see in the Hub Manager (connect/disconnect messages, firewall blocks, remote admin attempts) on its own systems — a separate question from whether the router stores and displays those logs locally — and available reporting addresses both the local event viewer and a narrower set of remotely collected hub data ^{[1] [2]}.

2. The local Hub Manager event log — what customers see

Customers can access an event log by logging into the router UI (typically via 192.168.1.254 and the admin password on the router card), and community threads show users routinely inspecting that Hub Manager log for connection drops, firewall messages and other diagnostics; that log is therefore local to the hub’s management interface ^{[1] [5]}.

3. What Plusnet says (via staff/community posts) it collects remotely

Plusnet product-team responses on the official community forum state that the data the hub reports back to Plusnet (“inform”) is relatively limited — examples cited by staff include PPP user, IP address, firmware version and activation/last/first contact timestamps — implying Plusnet’s centrally stored data is operational metadata rather than a mirror of the full local event log ^[2].

4. Policy context: data-retention documents exist but are not granular about event logs

Plusnet has published a Data Retention Policy and related schedule on its site and discussed retention on its community forums; those documents and threads acknowledge retention practices but the forum excerpts provided do not spell out a definitive list of every field retained from hub event logs or precise retention durations for the hub “inform” dataset cited by staff ^{[3] [4]}.

5. Evidence gaps, competing signals and practical implications

Community reports show variance in the Hub Manager’s verbosity across hub models (Hub One vs Hub Two) and users asking how to clear logs, which reinforces that much of the detailed log content is local to the router; at the same time staff-confirmed “inform” values suggest Plusnet retains limited lifecycle and identity metadata centrally, but the available sources do not provide a full technical inventory or retention time‑frame for those remote records, meaning definitive claims about every event-log field cannot be made from the cited reporting ^{[6] [7] [2]}.

6. How a concerned user can verify or act on this

Practical steps that follow from the reporting: inspect the router’s Hub Manager to see the local event entries (login via 192.168.1.254), consult Plusnet’s published Data Retention Policy and schedule for broader retention practices, and if needed request clarification from Plusnet support or a data‑subject access request for what data they hold — the sources point to published policy pages and forum staff responses but do not contain a one‑click definitive technical spec for hub inform retention ^{[1] [3] [4] [2]}.

Conclusion

Available Plusnet forum posts and company policy pages indicate the event log customers see in the Hub Manager is primarily local to the router, while Plusnet’s centrally retained hub “inform” data — as described by staff on the community forum — is narrower, covering operational metadata like PPP user, IP address, firmware version and contact timestamps rather than the full, verbose event stream; however, the reporting here is forum- and policy-based and does not include a comprehensive published technical specification of exactly which event-log fields are retained centrally or for how long ^{[1] [2] [3] [4]}.