Where your view is processed

The cloud version of Bloooom by Zaltt sends your selected view outside your organisation. When you press Visualise, the plugin sends the exported view, your prompt and chosen settings over an encrypted connection. Zaltt renders it on a machine it runs in Poland and returns the image.

If your confidentiality agreement does not permit that transfer, do not use cloud rendering on the project. Enterprise is the local option to discuss with Zaltt.

Your work and model training

The trial service terms say that you keep ownership of your model, input and output. Zaltt does not train models on your work, sell your view or result, or give either to anyone outside Zaltt. Using an image in Zaltt’s marketing requires a separate request each time.

Images and usage records

The bundled trial terms commit Zaltt to automatically deleting input and output within two hours of a render. The deletion work is incomplete. The latest recorded checks found image copies in stored jobs and backups, and cleanup of those copies has not been completed. Do not rely on the two-hour deadline for confidential work.

A usage record is retained separately. It includes the access code, time, duration, output size, result, selected style and prompt text. Zaltt uses this record for support, allowances, abuse prevention and understanding how the product is used.

The terms do not give a fixed retention period for this usage record. They also define input to include prompt text while saying that prompt text is retained in the record. That wording needs clarification; the two-hour commitment should not be read as a promise that your prompt disappears after two hours.

The terms say that usage records are not sold or shared outside Zaltt, and are not used to identify you or your projects.

Before using restricted work

Ask Zaltt to confirm the processing and retention arrangement your project requires before sending a view. Do not include confidential names, instructions or other restricted information in the prompt.