Lumion Cloud: Security and Privacy FAQ

Different types of Lumion Cloud data may be stored by different services. Cloudflare and Microsoft Azure are used as storage providers for original and AI-enhanced renders using infrastructure in Western Europe.

Lumion Cloud does not currently offer customer-selectable data regions. For example, it is not possible to request US-only storage.

Current internal documentation identifies Cloudflare and Microsoft Azure as providers used for Lumion Cloud storage and service infrastructure. Lumion also uses specialized AI and analytics providers for specific features, as explained in section 4.

No. Lumion Project files and source model files remain on your computer unless you deliberately upload supported content to the Lumion Cloud platform. Lumion Cloud is designed for rendered outputs and collaboration; it is not intended for storing or editing Lumion Project files or CAD source model files.

When you upload a render, send one to Lumion Cloud from a Lumion product, or use a cloud-based AI feature, the content you select must be transferred to Lumion Cloud so that the requested service can be provided.

No. Lumion does not use customer production data in its development or testing environments.

Lumion Cloud uses separation and access-control measures to prevent one customer's deposited data from being mixed with or exposed to another customer. Development and production environments are also separated, and production data is prohibited from being used outside the production environment.

Yes. Lumion Cloud protects data in two ways:

At rest: Lumion Cloud databases are encrypted using AES encryption.
In transit: communications with Lumion Cloud are encrypted using TLS.

Encryption keys are managed through controlled systems. Access is limited to authorized administrators, and key use is monitored.

For cloud AI operations, transfers between Cloudflare, Lumion's AI service, and AI providers use HTTPS. Cloudflare storage is encrypted at rest.

Access to operational systems and customer data is limited to authorized personnel according to their roles and responsibilities. Lumion uses controls that include role-based access control, multi-factor authentication, centralized identity management, auditing, and monitoring.

Access permissions are reviewed and removed or changed when a person's responsibilities or employment status changes.

Lumion Cloud uses layered security controls that include firewalls, a web application firewall, intrusion detection and prevention measures, DDoS protections, vulnerability management, security monitoring, and endpoint protection.

Lumion also performs platform, network, configuration, and application vulnerability assessments, as well as third-party penetration testing. External web-application security assessments are conducted approximately once per year.

Yes. Lumion maintains authentication, access, user-operation, administrator-operation, error, system-failure, and security-incident logs in accordance with internal retention policies. These logs are access-controlled and used for monitoring, troubleshooting, and incident response.

The customer-facing Activity Log is not the same as Lumion's internal security and infrastructure logs. Some login, access, or activity records that are not available through a built-in customer interface may be provided upon request, subject to availability and appropriate verification.

Lumion has documented responsibilities and procedures for detecting, assessing, escalating, and resolving security incidents. Lessons learned are used to improve these procedures. When required by applicable law or contract, affected customers and relevant authorities are notified.

Lumion also monitors service availability, performance, unauthorized access, suspicious activity, signs of cyberattacks, malicious network traffic, and remote administrative access.

Lumion reviews functional, non-functional, and security requirements during development and uses approval processes at relevant stages. Secure-development measures include coding standards, secure coding practices, source-code review, awareness of open-source components, change testing, and separation of development and production environments.

External contractors involved in development, maintenance, or operations are selected and managed under documented requirements covering security, incident reporting, data deletion, legal compliance, audit rights, service levels, and acceptance criteria.

Lumion maintains an approved information-security policy, has assigned responsibility and authority for security management, and performs regular security-risk assessments that are reported to management.

Where Lumion Cloud uses or provides API integrations, API users are authenticated, credentials and authentication information are access-controlled, communications are encrypted, and access tokens have expiration periods. Access to credentials used for third-party APIs is limited to personnel who need it for their work.

That depends on the sharing setting and permissions you choose.

Only those invited: access is limited to people invited directly and people who inherit access from a parent project or folder.
Anyone with the link: anyone who obtains the link can access the shared item.

Projects and renders are private by default. Before using Anyone with the link, consider whether the content contains confidential, personal, or commercially sensitive information.

Lumion Cloud uses predefined roles to control what a person can do:

Owner: has full control, including user and content management and transfer of ownership.
Admin: can manage users, settings, and content, but cannot transfer ownership.
Editor: can upload, edit, and organize content, but cannot manage users or sharing settings.
Viewer: can view and comment on shared content.

Permissions may be inherited from a project by its folders and renders. Review both direct and inherited access when sharing sensitive content.

Learn more about roles and access in the articles below:

• Knowledge Base: How do you Manage Access and Permissions?

• Knowledge Base: How do you collaborate and share content using Lumion Cloud?

Not necessarily. A client or other external reviewer can use an invitation link to view content and provide feedback without creating a Lumion Account. A Lumion Account is required to upload and manage content in Lumion Cloud though.

Not currently. Sharing is controlled for individual projects, folders, and renders, but Lumion Cloud does not currently provide an organization-level administrator control that disables public sharing across the entire account.

These features process content differently:

The Lumion Pro AI Upscaler is powered by Real-ESRGAN and runs locally. The statement that no image is uploaded applies to that feature only. It does not apply to the AI Upscaler or AI Enhancer in Lumion Cloud.

The AI Enhancer is optional. It processes an image only after you select the feature and submit an enhancement request. Using Lumion Cloud for ordinary storage, review, or collaboration does not automatically send every image through an AI model.

 To provide the feature, Lumion Cloud and the selected AI provider process:

• the render image you submit;
• basic image metadata, such as its format and dimensions;
• a system prompt supplied by Lumion; and
• any custom prompt you enter.

Image transfers between Cloudflare, Lumion's AI service, and the selected AI provider use HTTPS. The current workflow makes the image publicly retrievable through an unlisted URL that contains a randomly generated, hard-to-guess hash.

The following providers and models are used for Lumion Cloud AI features:

The AI Enhancer lets the user choose between Flux [PRO] and ChatGPT Images 2. Providers or models may change if a model is discontinued or no longer meets the service's requirements.

Lumion Cloud’s core application infrastructure is hosted in Microsoft Azure’s West Europe region. However, the processing location for an AI enhancement may also depend on the selected model and the service provider used to perform that enhancement.

Some images and prompts may therefore be transmitted to specialized AI service providers for processing outside the Azure West Europe region.

Lumion does not currently use source or enhanced renders to train AI models. However, third-party AI providers may use submitted renders for training.

Authorized Lumion Cloud staff members with administrator rights can access original images, generated images, and prompts. AI providers may also process prompts and content through their safety systems.

Yes. AI providers apply their own safety rules and may reject requests involving prohibited or potentially unlawful content. Lumion records provider errors and the associated prompts for service operation and troubleshooting.

Not currently. Lumion Cloud does not currently provide an organization-level control that disables AI features for every user in the organization.

The possibility of adding such a control is being considered, but this is not a product commitment or confirmed timeline.

Customers retain the ownership rights associated with content they deposit in Lumion Cloud. Lumion and its subprocessors require only the rights necessary to host, process, transmit, and provide the requested service, as described in the applicable terms.

Only upload content that you are authorized to process and that complies with your organization's policies, client agreements, and applicable law. Avoid including unnecessary personal information, confidential annotations, credentials, or other sensitive material in images and prompts.

If your organization requires approval before using external or generative AI services, obtain that approval before using the AI Enhancer.

Lumion handles personal data in accordance with applicable privacy requirements, including the GDPR. The Lumion Privacy Statement explains what personal data Lumion collects, why it is processed, and the rights available to data subjects.

Yes. Privacy requests can be submitted to Lumion in accordance with the Privacy Statement and applicable law. Contact Lumion Customer Support for assistance.

Lumion's terms address the return or deletion of customer data, and deposited data can be deleted upon a verified customer request. Lumion maintains documented procedures intended to ensure that disposed information cannot be recovered.

Deleting a render or closing an account may not remove every related record immediately. Some information may need to be retained temporarily in backups, security logs, billing records, or other records required by law.

No. Lumion is not currently ISO/IEC 27001 certified and does not currently hold another public information-security certification listed in the assessment. Lumion continues to develop its security program with reference to established industry practices.

Certification is different from the technical and organizational security controls described in this article.