Security

State the protection. State the limit.

Berlvis treats security as product-specific engineering work, not a universal badge attached to every page.

No blanket guarantee

No internet service can honestly promise that incidents are impossible. Berlvis does not claim independent certification, perfect availability or zero risk unless a named product later earns and publishes that evidence.

Product boundaries

Security controls differ by product. A browser-side Tools workflow, an authenticated bookkeeping record and a tenancy payment record do not have the same threat model and should not be described as if they do.

History and correction

Where financial or tenancy records matter, Berlvis designs for visible corrections and preserved history rather than silent deletion. Product pages state the exact boundary currently supported.

Secrets and support

Berlvis will not ask you to send a password, one-time code, private key or full payment-card details by email. Remove unnecessary personal information before attaching screenshots or records.

Reporting

Send suspected security issues to hello@berlvis.com with the affected product, a clear reproduction and the least sensitive evidence needed. Do not test against other users, damage data or disrupt service.

Disclosure

A verified issue should be investigated, contained and corrected before public detail is expanded. Timelines depend on severity and the affected system; this page does not promise a response window that has not been operationally established.

Last reviewed: 3 August 2026.