15 entries · Privacy · August 2026 – October 2026
Newsroom
Product changes, pricing and privacy. What changes for you, newest first.
Gray to violet: background to important changes. Editorial user impact, not security severity.
- Privacy policy 1.9.9: a technical access log, kept 14 days The proxy and the app now write one line per response to a log that only root can read. It holds no IP address, no account and no content, and it is deleted after 14 days. A new 14-day access log without IP or account helps find faults; the privacy policy now names it.
- Privacy policy 1.9.8: the admin log keeps only the target ID for customer data 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. The admin log now keeps only IDs, status and sizes for views that concern customer data.
- Privacy policy 1.9.7: a detailed log for administrator accounts only A detailed operations log now exists for administrator accounts only. Customer accounts stay zero-log, but customer data shown in admin views can appear in the log.
- Privacy policy 1.9.6: three security fixes, each with its limit Encrypted memory now reaches the model only in chats with memory on. Vault chats are refused on unconfirmed routes. Container network credentials are bound to their container. Each fix has a stated limit. Encrypted memory entries now go to the AI model only in chats with memory on, and you see how many. Vault chats are refused on routes without a confirmed retention commitment. Nothing to accept again.
- Privacy policy 1.9.5: encrypted memory protects storage only Our earlier wording overstated the encrypted memory. It protects stored entries, but entries in use go to the AI model in plain text. Version 1.9.5 says so. The encrypted memory protects stored entries only: entries in use are sent to the AI model in plain text, so it is not end-to-end. Nothing to accept again.
- Privacy policy 1.9.4: memory is encrypted per account The memory paragraph now says that entries are encrypted with a key per account, and states plainly that this is not end-to-end encryption. The privacy policy now says memory is encrypted per account but not end-to-end, and you do not need to accept anything again.
- Privacy policy 1.8.1: appearance settings The privacy policy now describes what the new appearance settings store, where your background image lives and how to delete it. The privacy policy now explains what the appearance settings store and how to delete your background image, and nothing else changed.
- 7 October: settings reorganised, complete data export, retryable account deletion Settings are split into separate sections. The personal data export and the account deletion cleanup were reworked.
- Trust and security, in one place A new documentation page brings together who operates ZeroLog, where workspace data is stored, and which services receive data.
- Crash reports, anonymous chat, push settings and custom pages ZeroLog Android now sends anonymous crash reports. This update also covers anonymous chats, push settings and custom site blocks. Introduces anonymous Android crash reporting, clarifies anonymous chat storage separation, and improves push notification persistence.
- Featherless data handling and a temporary customer pause Customer inference through Featherless is paused while ZeroLog completes its data protection agreements and confirms resale rights; accounts, credits and saved conversations remain in place. Announces a temporary customer inference pause on Featherless pending revised data agreements and resale confirmations while keeping balances safe.
- Anonymous chats get their own store Encrypted messages from anonymous chats are no longer kept in the main database. Anonymous messages are stored separately; storage and deletion failures are visible and never fall back silently.
- 25 September: waitlist and preview requests ZeroLog has a public waitlist and a preview request form. Both use double opt-in.
- What changed on 4 September We corrected an overbroad data-retention statement and removed the 10% fee on credit top-ups. Removes the 10% credit top-up surcharge and clarifies the exact zero-data-retention scope in the privacy policy.
- Twelve more model providers, and where your prompt goes New providers mean new places a prompt can land. Each is named in the privacy policy with its country and legal basis, and one is excluded from automatic failover. Discloses twelve new AI providers in the privacy policy with jurisdictional details and failover routing rules.