How we protect your data, at a glance.

Encrypted connections — in place

All connections run exclusively over HTTPS.

A separate key for each company — in place

We encrypt uploaded files, generated PDFs and sensitive details such as dates of birth, tax numbers and IBANs with a separate data key for each property management company (AES-256-GCM).

Master key outside our servers — in place

The data keys are wrapped with a master key. A managed key service in Frankfurt am Main holds it, not our servers and not the database. Every use is logged.

Passwords only as a hash — in place

We store passwords only as a one-way hash.

Strict tenant separation — in place

Every record belongs to exactly one company. Every query is limited to the company of the signed-in person.

Stored in Germany and the EU — in place

The application and database run in Germany; documents and backups are kept within the EU.

No training on your content — in place

AI analysis runs in Frankfurt am Main. Your content is not used to train the models.

Second factor at every sign-in — in place

All accounts with access to management data — administrators, managers, staff and owners — sign in with a password and a second factor every time. It is also available to caretakers and tenants.

Roles and permissions — in place

Seven roles with graded permissions, plus blocking of individual areas per person. Every request is checked on the server against role and company.

Protection against guessing — in place

Repeated failed sign-in attempts lead to a temporary lock.

Limited sessions — in place

Sessions use signed cookies that are sent only over HTTPS and expire.

Sealed-off server access — in place

Administrative access to production systems is possible only through a private network with key-based login.

Encrypted backups — in place

The database and uploaded files are backed up every working day, encrypted before upload and kept for 30 days separately from the application server.

Restore tested monthly — in place

Once a month we restore a backup as a test and compare the result with the live data.

Alert on failure — in place

If a backup fails, we are notified automatically.

Traceable changes — in place

Changes to legally relevant records are logged with time and person. Finalised bookings are locked against changes.

Monitoring and overload protection — in place

Availability and system load are monitored. An upstream service blocks overload attacks.

Rate limiting — in place

Sign-in and write interfaces are limited against mass requests.

Separate environments — in place

Development, testing and production are separate. Every release can be rolled back to the previous version.

Updates and vulnerability checks — in place

We apply security updates promptly. The libraries we use are checked automatically for known vulnerabilities.

Confidentiality — in place

Everyone who processes data at Savanika is bound to confidentiality, also after their work ends.

Notification within 24 hours — in place

We notify you of a personal data breach no later than 24 hours after we learn of it (Section 7 of the DPA).

Vetted providers — in place

Subprocessors are vetted before use and bound under Art. 28 GDPR. We announce a new one four weeks in advance, and you can object (Section 5 of the DPA).

Deletion after the contract ends — in place

After the contract ends we keep your data available for 60 days and then delete it, or immediately on request (Section 11 of the DPA).

Regular review — in place

Data protection incidents are documented and analysed. We review the measures at least once a year and after every significant change.

External penetration testplanned

A test by an independent provider is planned.