Company
Security, ownership and support.
Who owns the code and the data, how access, backups and personal-data processing are handled, and what support after rollout includes.
The questions a client's legal team usually asks before signing.
At handover you receive
- the source code and repository access
- technical and user documentation
- access to infrastructure and services
- installation and restore instructions
- a list of open items and next steps
Ownership
- the project source code belongs to the client
- the data in the system is and remains the client's
- documentation, access and credentials are part of the handover
- at the end of the engagement we hand over the entire environment
- third-party libraries are listed together with their licences
Security & access
Access
Every team member has an individual account with limited rights. We do not use shared accounts. Access is revoked when the project ends.
Backups
Regular database and file backups with restore testing. Frequency and retention are set according to project requirements.
Monitoring
Availability, error and load monitoring. Alerts go to the responsible person and incidents are logged.
Personal data
Processing is covered by a data processing agreement with defined purposes, retention periods and sub-processors.
Separate environments
Development, testing and production are separated. Real personal data is not used in testing.
Code review
Changes go through review and testing before they reach production.
Support after rollout (SLA)
Outage
The system or a key part is down. Response within hours during agreed support hours.
Disruption
The system runs but a function does not. Response within one working day.
Defect
A minor defect with no business impact. Scheduled into the next release.
Change request
A change or an enhancement. We estimate the scope and agree a date.
Related reading
Related solutions
Sounds like your project?
Send us the project description, your existing system, the tender documents or the event date.