Your data, your code, your server
When a company puts its operations on a single platform, questions about security, availability and how to get out again are entirely fair. Here is the answer to each of them.

Ownership
Everything created on the platform — applications, source code, databases and content — belongs to your company. There is no licence restricting your use and no clause tying the results of the work to us.
If the cooperation ever ends, you receive the source code and a full data export in a form your IT person or another provider can take over. The exit is planned in advance, not negotiated at the end.
Where the data lives
Production data lives exclusively on the production server. It is not transferred to third-party cloud services and is not mixed with other customers’ data — every customer has its own separate environment.
You choose where that server stands. We can provide it, in a data centre in the European Union, or production can run on your existing server infrastructure — in which case we only need the access required for maintenance.
Four things that separate production from experiments
Separate environments
Development and testing take place separately from production. A new feature goes live only once it has been tested — working on it doesn’t disrupt what is already running.
Backups
Data and source code are backed up automatically and regularly; backups are encrypted and stored separately from the server production runs on.
Monitoring
Servers and applications are monitored continuously. Problems such as a full disk, a service outage or an unreachable site are usually known to us before you notice them at work.
Controlled access
Every application requires a login, and permissions are assigned by role — each employee sees what they need for their work, and nothing else.
Personal data protection
Applications that process personal data — records of employees, customers or service users — are designed so that access is limited to those who need it, and it is visible who has accessed the data.
Because the data stays on your server and does not travel to third-party providers, the circle of processors is short and transparent — which considerably simplifies your obligations under the GDPR.
- Login and roles with precisely defined permissions
- Logging of access to sensitive data
- Encrypted data transfer between browser and server
- Encrypted backups, stored separately
- Data in a data centre in the European Union
When something goes wrong
We classify issues by severity — from an outage that stops work to a suggestion for improvement. Each level has its own guaranteed response time, set out in the quote and in the service level agreement. These times are part of the agreement, not a promise on a website.
Page last updated:
Let’s see what a single platform could replace in your company.
A short conversation, no obligation. Tell us where things get stuck — we’ll tell you whether AI BF is the right path and what the first step would be.