← Back to homepage

Security and transparency

How we protect access to your data, what we log, and how integrity checks work.

Authentication and sessions

Password hashing

Passwords are stored using the Argon2id algorithm — one of the safest hashing algorithms. The original password cannot practically be reconstructed from the hash.

Session management

After login, a session with limited validity is created. The session cookie is HttpOnly and Secure — not accessible from JavaScript.

Check it yourself: DevTools → Application → Cookies → HttpOnly and Secure.

Protection against repeated attempts

After several failed login attempts, the account may be temporarily blocked. This helps protect against automated attacks (brute-force).

CSRF protection

Key forms and server actions are protected against Cross-Site Request Forgery attacks.

What we log

Audit records serve transparency — so the organization has an overview of who did what.

  • ✓Login and logout
  • ✓Creation and closure of votes
  • ✓Submission and change of votes
  • ✓Upload and modification of documents
  • ✓Changes to roles and memberships
  • ✓Publication of announcements
  • ✓Export of data and protocols

What we DON'T log

  • —Content of private messages (we only log the fact of sending)
  • —Passwords in any form
  • —Activity on other websites
  • —Personal notes of members

IP address and browser identifier are recorded for key administrative actions (login, voting, changes) for security and traceability. This data is not public and serves exclusively for audit purposes.

File storage

Documents and attachments are stored outside public access. Download goes through an authorized endpoint — the system verifies membership in the organization that owns the file. The organization logo and banner may have a public address because they appear on the public profile.

Integrity check

Timeline entries can be provided with a cryptographic hash (SHA-256). If the hash matches the content of the entry, the entry has not been changed after saving. This is a technical tool for transparency — it is not a legal certification or official verification.

After signing in you can compare an entry hash on the timeline. That is a technical check, not an official certification.

Scope and boundaries of the system

Verwalt.ch is designed for transparent internal management. Here's how the system works and what to expect.

  • ·Legal validity of decisions depends on your organization's bylaws
  • ·Exports and protocols are technical outputs for internal use
  • ·Voting is by default attributable (linked to the account). Admins can enable a secret ballot (min. 4 voters).
  • ·Control hashes verify the integrity of records, not their legal validity
  • ·The system is a management tool, not a replacement for official registers or data boxes

What we do not have yet

  • ·We do not have ISO 27001 or SOC 2 certification
  • ·We do not have 24/7 monitoring or a contractual availability SLA
  • ·We will publish a penetration test only after it is finished — not sooner

Personal data protection (GDPR support)

  • ·Export of personal data: members can download their data (GDPR Art. 20)
  • ·Account deletion: on request — personal data is pseudonymized
  • ·Data retention: expired sessions, tokens, and temporary exports are cleaned periodically
  • ·Organization isolation: each request is bound to the session organization; automated tests check the separation

Platform operator: TimeDeals Pavelka, Berglistrasse 28a, 8180 Bülach, Switzerland (UID: CHE-393.597.780). Contact for data protection: privacy@verwalt.ch