Privacy
Crash reports, anonymous chat, push settings and custom pages
Crash reports and anonymous chat storage remain separate from accounts and chats. Push settings now apply across devices, and custom site blocks are checked for common TypeScript build errors before saving.
When a ZeroLog app crashes, it will be able to send a short report so we can find and fix the fault. The apps do not send these reports yet. That comes with their next updates.
A report holds the error message, the stack trace, the device model, the operating system version and the processor type. It also holds the crash time rounded to the minute and a rough session length.
A report is not linked to an account or a chat, and no IP address is stored with it. Before a report is saved, email addresses, access keys, IP addresses and personal file paths such as your user folder are replaced with placeholders. Any other field the app sends is dropped.
Reports of the same crash are grouped together. Each group keeps only its newest report and is deleted 30 days after that crash was last seen.
Anonymous chat storage
The anonymous chat guide now explains where encrypted messages go. They are stored separately from regular chats and workspaces. If storage fails, you see an error and the message is not saved elsewhere. Deleting an anonymous chat also deletes its encrypted messages. Read the guide for details.
Push notifications
Turning off push notifications now applies to your account on every device. The app will not turn them back on during sign-in or refresh. To receive them again, turn notifications on in the app.
Custom site blocks
Custom page blocks now receive a TypeScript compatibility check before they are saved. The builder corrects unused React imports and unsupported style syntax that could otherwise stop a site build.