# Privacy policy 1.9.8: the admin log keeps only the target ID for customer data 2026-10-23 · Privacy > Admin views and actions that concern a customer are now logged with who, what address, status, size and the ID of the affected object. No content, no search terms, no error text. *What the operations log keeps for customer-related admin views.* Text version Kept: who acted, when, the address, status, duration, sizes and the target ID. Dropped: request and response content, search terms and error text. Since 23 October ZeroLog keeps a detailed operations log for administrator accounts. Until now, when an administrator opened the account list or credited an account, the content of that request went into the log too, and with it whatever customer data the view showed. That has stopped. When an admin view or action concerns a customer, the log keeps who acted and when, the address without search terms, the status code, the duration, the sizes, and the ID of the affected object, for example the account number. It keeps no request or response content, no error text and no search terms. Messages that other parts of the service write during such an action are cut down to IDs and codes. The rule is inverted on purpose. Every admin address counts as customer-related unless it is on a short list of purely operational views (settings, prices, network status, the newsroom). A new admin view is therefore logged without content until someone decides otherwise. The operator's session recording follows the same line. On admin pages it records which button was clicked and which account row it belonged to, but not the visible text or what was typed. What can still point to a customer is the account number of an affected account, and anything an administrator types into an operational view. Entries written before the change expire after 30 days at the latest. The log lives only in memory on our server in Switzerland and is never backed up. Details: section 3.4.1 of the privacy policy, version 1.9.8.