Skip to main content

Frequently Asked Questions

Hosting​

Where is your cloud service located?​

priint:cloud is hosting in the Google Cloud datacenters in Frankfurt, Germany (europe-west-3).

Do you offer separate and specific instances for customers or is it a shared application platform (multi-tenant)?​

priint:cloud is a cloud-native, multi-tenant application. Customers share resources which will scale-up when the need arises.

Data Security​

Do I retain ownership of data I sent to you?​

Data transferred to priint:cloud in order to perform our service will stay your property.

How long is the data retained on the system?​

We typically store data only for as long as we need to provide our service. Source data is being used to create the rendered documents and deleted shortly afterward. Generated documents will be deleted shortly after being delivered to the customer. You may override these setting by specific configuration.

What is the data sanitization process if a customer cancels the service offering?​

Your data is only stored as long as we need to deliver our service. If a customer cancels our service, the account will be deactivated at the end of the contract time. Any residual data (comet project, configuration, etc.) will be removed.

Will you use the data for any purpose other than the delivery of the service?​

We only use your data for the delivery of our service.

What is the data sanitization process if a customer cancels the service offering?​

Your data is only stored as long as we need to deliver our service. If a customer cancels our service, the account will be deactivated and any residual data (comet project, configuration, etc.) will be removed.

Performance​

What is the expected rendering time ?​

This depends on several factors

  • size of the content data
  • size of the generated PDF
  • complexity of the comet_xml project
  • number and size of the media assets to be loaded during rendering
  • performance of the media asset service (depends on the service itself, the bandwidth, etc.)
  • concurrent load on the rendering service
    the system will automatically scale up or scale-down depending on the general load but this can take a minute to be applied

Renderings with PdfRenderer can take all between 1 or 2 seconds and several minutes. Typical 1- or 2-page datasheets are in the a-few-seconds range. Whereas complex catalog chapters with hundreds of products and articles may render much longer. Per default the maximum rendering time is set to 60 sec. For longer renderings the default must be overridden via renderpdf config.