Security

This page describes Zizzro's current safeguards and known limitations. No system can guarantee absolute security, and Zizzro has not yet completed an independent security assessment.

Controls in place

• Account-scoped access rules are enforced in the database, with separate sharing rules for records deliberately shared with a household.
• Privileged actions are re-checked on the server, not only hidden in the interface.
• Sensitive credentials for connected calendar accounts are encrypted with AES-256-GCM on the server. The key lives only in server configuration and is never sent to the browser.
• Uploaded files are stored privately, are re-checked on the server for type and size, and are served through short-lived expiring links.
• Sign-in supports two-step verification and signing out other devices.
• Request limits apply to invitations, search, document scanning, uploads, provider sync, data exports, deletion and the public calendar link.
• The public calendar link is treated as a secret: it is never indexed or cached, can be switched off or regenerated, excludes personal-area items by default, and carries titles and times only.
• Decrypted secrets, tokens, app passwords, journal, medication and private-note content are never written to logs or returned in error messages.

Encryption, in plain terms

• In transit: HTTPS everywhere.
• At rest: the database and file storage are encrypted by the hosting platform.
• Extra layer: connected-account credentials are separately encrypted before being stored, so a database copy alone does not reveal them.
• Keys: held in server configuration, never in the app you download. Rotating a key requires re-encrypting stored credentials server-side; reconnecting the affected accounts also resolves it.
• PINs (journal, medications) are a convenience lock on the screen, backed by a salted, hashed check. A PIN is not an encryption key and cannot by itself unlock anything.

Known open items

• The credential Vault is switched off for everyone pending an independent review of its design.
• No third-party penetration test or audit has been completed.
• Uploaded files are checked for type and size but are not virus-scanned.
• Sign-in attempt limits are provided by our authentication platform rather than by Zizzro itself.

Your part

Use a unique password, enable two-step verification, protect your devices, and sign out sessions you do not recognise. Do not share calendar feed links or connected-account credentials. Contact us promptly if you suspect unauthorised access.

Reporting a problem

If you believe you have found a vulnerability, please contact us before disclosing it publicly. See the Support page or email info@zizzro.com with "Security" in the subject. Please include enough detail for us to reproduce the issue and avoid accessing or changing other users' data. We will acknowledge reports and provide updates where appropriate.