FAQ – Technical Questions

Are there backups of a NOOA instance if it were to go down?

Yes. NOOA is backed up daily. In the event of data loss, a previous backup can be restored.

How frequent are the backups taken and where are they stored?

NOOA backups are taken daily and they’re stored in Google Cloud –servers. This allows for the data to be automatically mirrored across storage devices in multiple locations inside the cloud for added security.

Will the user input data be purged after they are completed with the challenge? If not, what’s the length of time before the user data expires?

No, they will remain in the MySQL database. This kind of behavioral user information will become quite valuable for the organization as data on their competence for strategy execution. This information will also help organizations when designing further transformations.

Can the user input data be purged?

Yes. All data can be cleared if necessary, but it is not recommended (see the previous answer for more details).

Does NOOA have SOC1 Type 2 and/or SOC2 Type 2 documentation?

No. SOC1/SOC2 audits are for service organizations, which manage a company’s financial data. No financial data will be on the NOOA platform.

In addition, currently NOOA does not allow for custom files or documents to be added to a challenge.

Will TripleWin Oy be marketing, anonymizing , de-identifying, or data masking any of the data in NOOA?

No. For further information, please refer to the Privacy Policy and Terms of Service.

Is there a DR (Disaster Recovery Plan) for NOOA?

NOOA is a cloud based software currently hosted on Google Cloud –servers and as such, the DR-plan by Google is applicable.

What kind of security and certificates does NOOA servers have?

NOOA is located in Google Cloud –servers and the security documentation provided by Google is applicable:

Google cloud security

Google cloud certifications

What if the servers hosting our NOOA platform go down? Is there a possibility of data loss?

Google Cloud has a Service Level Agreement of 99.95% and to minimize service interruption due to hardware failures, natural disasters or other incidents, Google has built a highly redundant infrastructure of data centers.

Google has an RPO target of zero, and their RTO target is instant failover (or zero).

Google’s computing platform assumes ongoing hardware failure, and it uses robust software failover to withstand disruption. All Google systems are inherently redundant by design, and each subsystem is not dependent on any particular physical or logical server for ongoing operation. Data is replicated multiple times across Google’s clustered active servers so that, in the case of a machine failure, data will still be accessible through another system. They also replicate data to secondary data centers to ensure protection from data center failures.