Before You Upload a Client’s Images to an AI Design Tool

Ask for the permission the task needs

Start with a clear question to the client or project owner. Explain the change you want to make, name the tool you plan to use, and say which image you would upload. That is easier to answer than a broad request to “use AI.” You might be asking to extend a background, remove an object, or explore a mood. The client can then approve a defined action rather than guess what might happen to the entire asset library.

Keep the response with the project records. This is a practical way to manage the work, not a universal legal rule. Contracts and client policies differ. If a brief already explains which tools and assets are approved, follow it. If it leaves a material question open, resolve that question before uploading. A creative test can often use a public or specially prepared reference while the original file stays where it belongs.

Read the tool’s terms for the feature you will use

Look at the actual service, model, and account plan involved. A familiar logo on the page does not tell you every detail about how a feature handles uploads. Check what the provider says about training, storage, access, and public sharing. These are separate questions. A statement about model training, for example, does not by itself explain how long a project is kept or who can open a shared result.

Adobe offers a useful named example. Its published AI ethics statement says it has not trained Adobe Firefly on customer content. That is Adobe’s statement about Firefly. It is not a rule for every AI service, and it does not settle every condition of a particular workflow. Use a specific statement for the specific question it answers. For anything else, read the relevant product guidance or ask the provider.

Also check whether the result or project will be private by default in the feature you selected. Do not assume that “saved to my account” and “visible only to me” mean the same thing. If the guidance is unclear, you do not need to settle the whole product’s privacy policy yourself. You need a clear answer about the action you are considering. Choose an approved alternative if that answer is unavailable.

Choose the smallest useful reference

Return to the launch photo. If the task is choosing a background colour, you may not need to upload a high-resolution image with every packaging detail visible. A permitted crop, a sample colour, or a generic object might be enough to explore the direction. Keep the original file and prepare a separate working copy. Choose the copy for the job rather than sending the most detailed asset simply because it is close to hand.

Review what sits around the subject. Faces, badges, delivery labels, and whiteboards can become part of a reference by accident. Remove details that are not needed when you are authorised to do so. But cropping a photo does not create permission to upload it. The order matters: establish the allowed use, then prepare the material for that use. If a real client image is unnecessary, start with an approved substitute.

Label the prepared copy so you can match it to the approved source later. If several similar product photos sit in the project folder, a clear filename helps you avoid selecting another version by mistake. Keep any approval note with that copy. Before uploading, open the selected file once more at full size and check its contents rather than relying on the small thumbnail in the file picker.

Give the upload connection its own check

Once the material and tool are agreed, consider the connection you will use. HTTPS protects the exchange with the website. On a shared network, a VPN connection can also encrypt traffic routed between your device and the VPN server. X-VPN encrypts traffic routed through its service when you work on a shared network. This concerns the network path; the AI service still receives the file you choose to send.

If you use a free VPN app, check its current support for your device and the settings relevant to your task. Keep that choice separate from the AI tool’s file rules. A connection tool does not decide whether a photo may be uploaded, change a provider’s storage terms, or approve a client project. You can make both decisions carefully without expecting one to solve the other.

Keep enough detail for the next edit

Record the approved image, the purpose, the tool, and any conditions that affect reuse. That note can be short. If the client later asks for the same treatment on another product, you can see what was agreed and what has changed. A different model, feature, or account plan may require another look at the relevant terms. Recheck the affected part rather than repeating the whole process for no reason.

Review the output as design work, too. Check the product’s shape, labels, and other details against the source before sending it for approval. Decide where the working files and final version should be stored. The finished result should be something you can explain: which material was used, why it was suitable, and what the client is being asked to approve.