When you create a Revizto project, you can choose where to publish your project: to the cloud, to a shared location, or locally (none). These publishing locations indicate the data storage option being used for the project (cloud, shared location, or local device).

Each data storage option comes with different levels of collaboration and access requirements. The sections below give more information on the data storage policies that apply to each option as well as the Revizto retention policy.

• Cloud storage
• Shared location storage
• Local storage
• Revizto retention policy

Cloud storage

This option stores all your project data (scenes, sheets, and issue tracker data) in protected cloud storage. Cloud storage is the best option for full collaboration. A project that is stored in the cloud occupies a project slot in a license.

The following diagram shows a sample Revizto data flow with cloud storage:

We have three groups of cloud storage locations that operate independently from each other: global, China, and KSA.

• Cloud storage (global)
• Cloud storage (China and KSA)

Cloud storage (global)

We have the following global cloud storage locations: 

• ANZ (Australia)
• Canada
• Europe (Ireland)
• Japan
• North America (USA)
• South America (Brazil)
• Southeast Asia (Singapore)
• Switzerland
• UAE
• United Kingdom

In all these locations, we host our cloud services on Amazon Web Services. Models and their revisions are hosted on Amazon S3.

User accounts (full name, email, and hashed login credentials) are replicated across all servers in the global group, allowing users to log in to any of the above servers with the same Revizto account. However, no other data is replicated to other locations or copied by us from any of our locations. For example, if a customer is located in Oceania, the license is issued to the Oceania server and the customer can only store their data in that location. They won’t be able to store their models on other Revizto servers as the access will be denied.  

For more information on data security, see the following resources:

• Amazon Web Services Compliance
• Amazon Web Services Cloud Security

Cloud storage (China and KSA)

We also have separate, dedicated cloud storage in China (Shanghai) and KSA for customers in those locations. In these locations, we host our cloud services on Alibaba Cloud. 

The China and KSA servers operate fully independently from each other and the group of global servers. No data is replicated to other locations and no data is copied by us from these locations. For more information on data security, see Alibaba Cloud Trust Center.

Shared location storage

This option stores scenes and sheets on a network drive in your company’s local network. Meanwhile, limited issue tracker data (issue screenshots, dates, issue tags, names of project members, and communication between the project members) will be stored in the cloud. Shared location is best if your company's security policy requires storing data on your internal servers. Only people who have access to the local network can open the model and the project. A project that is stored in a shared location occupies a project slot in a license.

The following diagram shows a sample Revizto data flow with shared location storage:

Local storage

This option stores everything, including models and issue tracker data, on your local device. The project data will only be available on that device. Other users can sign in to the project from that device but cannot access it from any other device. A local project does not occupy a project slot in a license.

Without some cloud access, the project will not be able to fully use collaboration features such as the issue tracker or clash detection, meaning local storage is not suitable for collaboration. It can be useful in some cases, however, such as saving a copy of a cloud project as a local project to experiment on something.

Revizto retention policy

• Revizto's current data retention policy: Per Section 5.4 of the Revizto License Terms (https://revizto.com/en/eula/), Revizto makes Customer Data available to Customers who have terminated their subscription for retrieval, for a period of 90 days post-termination. During that time (and although the License Terms state that this is done "without any further notice"), Revizto sends reminders to Customers to notify them that their data will be deleted, unless the Customer opts for a prolonged Customer Data retention package. In case a Customer without an active license does not respond to these notices, Revizto is legally obliged to delete Customer Data. As long as the Customer has an active Revizto license, their data is not deleted. Once the license expires, the Customer has 90 days to retrieve the data related to the expired license, and they will receive at least 2 prior deletion warnings before we actually do delete their data. If a Customer has 10 project-based licenses, and the licenses for projects 1-5 have expired whilst the licenses for projects 6-10 are still valid, then it means that their data related to projects 1-5 will be subject to our 90 days post-termination rule as well.
• Prolonged data storage, after the end of a license agreement, is to be agreed on separately at the time of termination. Revizto can, as such, enter into a data storage agreement with its Customers for the time period required by the Customer.
• Data extraction: Note that Revizto has no access to Customer Data, unless the Customer explicitly shares that data; and Customer retains full control over its own data. Upon expiry or termination of the Revizto license, any project-related data can be extracted by the Customer from the Revizto platform in the following formats: 2D drawings as PDF files, and collaboration issues as BCF files. While native 3D models cannot be directly exported, a complete project archive containing all 2D, 3D, and issue data can be delivered as a single executable (.EXE) file, which can be viewed on a Windows computer without requiring any active Revizto license.

Additional information can be obtained in our Data Management Policy.