---
title: Security and Trust - SCHILLER
description: Who develops, who runs it, who is liable, where your software runs. Direct
  answers to the questions that come up before every project.
url: https://ad-ze.de/en/security
language: en
---

# Security and Trust

## Who develops here, who is liable, where your data lives

Before you award me a project, you want to know who you are dealing with. This page is not for marketing. It answers the questions that data protection officers, compliance teams and IT leads typically ask. If something is missing, just ask me.

## Who develops and runs it

I build myself, but not everything alone. When a project grows beyond one person, lenne.Tech from Lennestadt can take over development and operation. You know who works on the code before the project starts. No offshore team.

### One point of contact

You have one point of contact: me, even when lenne.Tech works on the project. You always know who is responsible for a question.

### Stack

Ruby on Rails 8, PostgreSQL, Stimulus, Hotwire. Established, well-documented technologies. No exotic frameworks that nobody will understand in five years.

### Rights to the code

For the results made for you, you get an exclusive, perpetual right of use. For reusable building blocks, you get a simple, perpetual right of use. No vendor lock-in, no licensing trap. If you ever want to continue with someone else, I hand over the code along with the documentation.

## Where your data lives

Depending on the project, you decide where your application runs. I do not insist on hosting myself.

### On-premise at your place

Your server, your sovereignty. The application runs entirely in your infrastructure. I only get the access I need for maintenance, and only when you grant it.

### Hosting by me in the EU

If you want, I host your application at providers in Germany. For AI I name every service to you beforehand, including whether data may leave the EU.

### Backups

The database is backed up daily on the server itself, unencrypted. 14 daily, 8 weekly and 12 monthly copies are kept. A restore was tested successfully on October 17, 2026. Retention periods and deletion rules are defined in the project contract; for ADze they are set out in the terms and conditions.

## Insurance and liability

A proper professional liability insurance is not marketing, it is a basic requirement. In a claim, there is a real policy behind me, not a letter of regret.

  Insurer Markel Insurance SE, Munich. Specialist insurer for the IT and telecommunications industry. 

  Product Pro IT, professional indemnity and business liability insurance with open coverage for IT service providers. 

  Coverage for financial loss EUR 500,000 per claim, capped at threefold per insurance year (i.e. up to EUR 1.5 million per year). 

  Coverage for personal injury and property damage EUR 5,000,000 per claim. 

  Cyber and data own-damage insurance Additional EUR 100,000 for my own expenses in IT security incidents. 

A current insurance confirmation is provided before project start or on request.

## When AI is involved

Not every project uses AI. When it does, strict rules apply, which I explain in detail on a dedicated page, including data flow, providers, pseudonymisation and source references.

### Principle

European providers take precedence. Recognised personal data is replaced before it leaves the server. Switching this off takes two approvals. The privacy policy names the exceptions, such as web search, photos of business cards, voice recordings and documents for the knowledge search. The mapping to the clear text stays on the server that runs your application.

 [Go to AI data protection page](https://ad-ze.de/en/ai-transparency)   
## When two offices work on one project

In ADze you can bring people from another office into a single project. Here is what applies technically.

### The data lives in one place

While you work together, the project lives only with the office it belongs to. The other office works in it and gets no copy while doing so.

### Only this one project

The database opens exactly this project to the other office. It does not see your contacts, your other projects or notes you mark as "My office only".

### Sign first, then work

Before the first access, every invited person signs an agreement covering confidentiality, the results of the work and data protection.

### You see who fetches files

When someone from the other office opens a file, the project shows who fetched which file and when. Entries stay for 90 days.

### At the end, what was agreed applies

You decide beforehand whether the other office gets the shared state at the end, only its own contributions, or nothing. ADze sticks to it.

### What ADze cannot do

ADze does not check what the other office does with its copy. What someone downloads during the work stays with them. That is what the confidentiality in the agreement is for.

## Contracts and documents

On request I provide the following documents, before or alongside the project contract.

### Data processing agreement (DPA)

Standard form under Article 28 GDPR. I provide the draft, you review, we both sign.

### Technical and organisational measures (TOM)

Documentation of security measures under Article 32 GDPR.

### Insurance confirmation

Current policy and confirmation of coverage from Markel Insurance SE.

### Record of processing activities (ROPA)

Text module for your internal documentation, once scope and data flows are defined.

 [AVV ↗](https://ad-ze.de/en/pii-anonymizer/avv) [TOM ↗](https://ad-ze.de/en/pii-anonymizer/tom) [Imprint ↗](https://ad-ze.de/en/imprint) [Privacy Policy ↗](https://ad-ze.de/en/privacy) 

## What you will not find on this page

So it is clear what these statements cover and what they do not.

No TISAX. I am not set up for automotive supply chains.

No processing of special-category data under Article 9 GDPR without an explicit project-specific addendum (health data, biometric data, religious belief).

Questions?

If anything in this overview is missing or unclear, write to me directly. An honest reply comes faster than three rounds of email.

[michael@schiller-partners.de](mailto:michael@schiller-partners.de)

Last updated: November 15, 2026
