Data protection and ongoing operations
Once workflows run automatically, the question shifts from implementation to operations: who sees which data, who notices a disruption first, and who can adapt the workflows later? The following answers cover data protection, access, training and handover.
- Where is our data held? Services we operate run in data centres in Germany. Where data can remain in your own systems, it stays there — we do not mirror anything to additional places that the workflow…
- How is access to our systems handled? We work with personal accounts limited to what the task requires, and with two-factor sign-in wherever the system supports it. Shared accounts and passed-around passwords are…
- Do we need a data processing agreement? As soon as we process personal data on your behalf — customer data in an automated workflow, for instance — we conclude a data processing agreement under Article 28 of the General…
- What happens after rollout, in day-to-day operations? After handover we accompany the first few weeks closely, because special cases tend to surface only in live operation. After that the workflow moves into regular support. This…
- Will our staff be trained? Yes, and in our view this point often decides whether the change sticks. An automation nobody understands gets worked around — side routes emerge in spreadsheets and notes, and…
- Can we run the solution ourselves later? Yes. We rely on open, transparent technology and hand over documentation, configuration and access, so your team or another provider can carry on. That creates no lock-in. Many…