
Imagild's Privacy Policy says private uploads are not published or placed in the Skill Market without your explicit action, and private photographs are not used to train a public model without separate, explicit consent. Processing an image still requires the infrastructure and model providers needed for that job. Private processing, public sharing, training permission and storage duration are different decisions.
Key Takeaways
- Uploading a private photo is not the same as publishing it in a public market.
- The privacy policy distinguishes necessary service processing from public-model training consent.
- Review the image, prompt and intended recipients before submitting sensitive work.
- Keep an independent approved copy; cloud processing is not permanent archival storage.
Understand what the upload is for
Start with the task you want performed. A personal portrait, a client product photo and a public promotional image can have different sensitivity and sharing requirements. Identify whose photograph it is, what permission you have to process it and who should receive the result.
The Privacy Policy describes information supplied to the service and the providers involved in performing requested jobs. Its statements about private photographs do not mean that a cloud generation happens entirely on your device. Do not substitute “private” for “offline,” “no processing by another provider” or “no records of any kind.”
For a client project, read the current policy before submitting rather than relying on a remembered marketing phrase. If a contract requires a particular processing location, retention period or provider restriction, obtain the necessary clarification before uploading. This guide cannot establish compliance with a contract it has not reviewed.
Separate the four decisions
Use this checklist to keep different permissions from collapsing into a single yes or no.
| Decision | Question to settle |
|---|---|
| Processing | May this image and its instructions be used for the requested task? |
| Publication | May this specific result be shown to this audience? |
| Training | Has separate permission been given for the use described in the current policy? |
| Retention | How long will service copies and your own archive remain available? |
A person's permission to prepare a private portrait does not establish permission to place it in an advertisement. Your own decision to download a result also does not determine what a recipient may later do with their copy. Review public use as a separate approval step.
The Terms of Service require the necessary rights and permissions for uploads and instructions. This article explains the service's stated boundaries; it does not provide copyright clearance or determine another person's consent.
Minimize the information in the task
Inspect both the photo and the text you plan to submit. A portrait brief may need an expression, lighting direction and intended crop without needing a home address, booking reference or unrelated client details. Remove those details when they do not help the requested edit.
Look beyond the main subject. A background notice, a visible badge or a screenshot's surrounding interface can contain information you did not intend to include. If you prepare a reduced working copy, retain the authorized original privately and make sure the copy still supplies enough visual evidence for the job.
The location-metadata guide covers a separate file check before sharing. Removing visible information and checking metadata are complementary tasks; neither proves that every possible identifying detail has been eliminated.
A hypothetical private-to-public project
Imagine a client approves a portrait for a private presentation. You use an authorized working image and a brief without unrelated personal details. Later, you want to show the result in a public case study. Treat that as a new publication decision: identify the exact image, intended channel and audience, then obtain the appropriate approval before sharing.
This scenario is a proposed review process, not a claim that Imagild supplies automatic consent tracking, a client-approval system or legal clearance. Keep your permission record in a suitable private location instead of embedding it in a public image caption.
Plan storage and deletion separately
The current privacy policy gives source photographs and generated Library results a media-retention window tied to processing completion. Account, transaction and operational records have different purposes and retention conditions. Do not assume that every record disappears when a media file does.
The 90-day archive guide explains how to download and verify accepted files while available. A private Library link is not a permanent backup. If you need earlier deletion or clarification about a particular record, use the support contact in the policy and identify the request without posting the image publicly.
Check the result's destination before sending it
Before public use, confirm the approved version, visible details, recipients and sharing channel. If you reuse the brief for another client, follow the private-detail removal checklist. A successful visual result does not automatically make the surrounding instructions safe to reuse.
Sources and scope
Based on the published Privacy Policy and Terms of Service, checked October 30, 2026. The privacy policy is the authority for its commitments; this article adds a practical decision checklist. No provider audit, legal compliance assessment, training-data investigation or deletion test was performed. Contact Imagild support when your project needs clarification before processing.
Prepared by Imagild Editorial, the company editorial team responsible for these guides. AI assisted research and drafting. Report a correction.
Cover: AI-generated conceptual illustration; not an application screenshot, observed result, private account record or privacy guarantee.