Trust Center

Security, hosting and data in Switzerland

This page describes how we manage data residence, access, traceability, backup, operational continuity and recovery of the platform.

The objective is to offer a clear overview of the technical and organizational controls applied to the service, useful in the evaluation, procurement and technical comparison phases.

For dedicated insights, additional documentation is available on request.

Control areas

Perimeter

What this page covers

The platform is designed with attention to data residence, separation of environments and access control.

The perimeter described on this page concerns in particular:

  • application and document data managed within the service
  • access and authorizations to modules and information
  • recording of events relevant for operational and traceability purposes
  • backup, restoration and operational continuity procedures
  • organizational rules supporting data governance

Further details on the technical perimeter, the authorization model and the supporting documentation are available during the technical comparison phase.

Hosting e residenza del dato in Svizzera

The application infrastructure is hosted on Amazon Web Services (AWS), with main services located in the Europe (Zurich) Region, in line with data residency and operational continuity requirements.

Environment management includes separation between operational and test contexts, with dedicated rules for access, use and change management.

The location of the main application data is defined technically and contractually based on the scope of the service provided.

Backup, retention e verifiche periodiche

Backup procedures are defined according to data criticality and the operational needs of the service.

Copy retention is configured to support recovery, control and operational continuity needs, within the agreed perimeter.

The effectiveness of copies is verified through periodic restore checks to confirm the integrity, availability and usability of saved data.

Log operativi e monitoraggio continuo

The platform collects operational and access events useful for analysis, operational diagnosis and verification of relevant activities.

Service monitoring is aimed at identifying availability anomalies, application errors and critical events requiring technical intervention or escalation.

Visibility into events is regulated according to authorized roles and the perimeter of responsibility.

Ruoli, accessi e permessi

System access follows a role-based authorization model, with differentiated privileges according to operational responsibilities.

Permissions can be applied to modules, data, functions and sensitive operations, in line with the principle of access based on operational need.

Authorizations are managed through an internal process of assignment, review and update.

Audit trail e tracciabilità delle azioni

Actions relevant for operational and control purposes can be associated with the user, date and event context, according to the traceability perimeter provided by the system.

Traceability supports internal checks, audits, reconstruction of operational sequences and reduction of undetected errors.

The audit trail is a central element for accountability and control, governance and process oversight.

Continuità operativa

Operational continuity is managed through technical and organizational procedures designed to keep the service usable even in degraded conditions or in the presence of anomalies.

Priority processes are identified and handled according to escalation logic and operational priorities.

Coordination between technical oversight and operational oversight helps reduce the impact of incidents on daily work.

Recovery e ripristino del servizio

Recovery procedures are defined to support the orderly restoration of the service and priority components in the event of a technical incident or significant interruption.

Restoration may involve data, application components and configurations relevant to returning to operation.

Procedures are periodically reviewed and updated based on the evolution of the service and its risk profile.

Policy documentali e governance

Data management is supported by internal rules on information classification, responsibilities, access, retention and document review.

Operational policies define the framework for the correct use of information and the controlled management of sensitive processes.

The governance approach aims to align regulatory requirements, internal processes and technical measures consistently with the customer’s operating context.

Documentation available upon request

Summary security sheet

Technical comparison on the authorization model

In-depth information on hosting and data perimeter

Clarifications on backup, recovery and operational continuity

Additional information on document governance

More detailed documentation can be shared depending on the context of the negotiation and the level of detail required.

FAQ

Frequently asked questions during the technical evaluation phase

Where is infrastructure and data hosted?

The application infrastructure is hosted on Amazon Web Services (AWS), with main services located in the Europe (Zurich) Region. The location of the main application data is defined in accordance with the agreed service perimeter.

Do you have separation between production and testing?

Yes. The environments are managed with separation between operational contexts and non-production contexts, with dedicated access and use rules.

How are backup and recovery handled?

The backup and recovery procedures are defined based on the criticality of the data and are subjected to periodic checks.

Is there a system of roles and permissions?

Yes. Access to functions and data is managed via a role-based authorization model, with differentiated privileges.

Are the activities traceable?

The system provides traceability of events relevant for operational and control purposes, according to the envisaged perimeter.

Is it possible to delve deeper into the security model?

Yes. For technical evaluation and procurement needs, it is possible to request a dedicated technical discussion on the security perimeter, the authorization model and document governance.

Do you share detailed documentation publicly?

This page provides a public summary of the operating model. Further documentation is shared upon request, based on the scope of the technical evaluation and procurement needs.

Do you need a greater level of detail?

It is possible to request a dedicated technical comparison to delve deeper into hosting, access, traceability, recovery and document governance.