Veyqen Imaging

Image Upload & Content Policy

Last updated: 08 Sep 2026

1. Files You May Submit

Clients may submit image files that are relevant to a requested editing project and that they are authorized to provide. Common project types can include personal photographs, business images, product photographs, catalog imagery, marketing assets, and other lawful digital images.

2. Rights and Permission

By submitting a file, the client confirms that the client owns the content or has the permissions necessary to submit it for editing. The client is responsible for rights associated with photographers, models, property, artwork, logos, packaging, confidential materials, and other protected subject matter.

3. Prohibited Content

Do not submit content that is unlawful to possess or process, content intended to facilitate fraud or impersonation, malicious files, material submitted without necessary authorization, or content that creates a serious safety, exploitation, or legal concern.

A project may be declined or stopped if the submitted files or requested manipulation appear unlawful, deceptive, abusive, or outside the intended service scope.

4. Sensitive and Confidential Images

If a project contains commercially sensitive, private, or confidential imagery, the client should identify that concern before or when submitting files. Ordinary editing service does not automatically create a specialized regulated-security relationship unless separate terms expressly establish one.

5. File Quality

The achievable result depends heavily on the source file. Low resolution, severe compression, clipped highlights, blocked shadows, motion blur, focus errors, missing pixels, or other source limitations may restrict what can be improved.

Editing cannot reliably recreate detail that was never captured in the original image.

6. File Formats

Accepted formats may vary depending on the project and available workflow. Common raster formats can include JPG, PNG, TIFF, or other formats agreed for the project. Large, unusual, layered, or proprietary files may require review before acceptance.

7. Malware and Unsafe Files

Files must not contain malicious code, harmful scripts, intentionally corrupted data, or other material designed to compromise systems or interfere with service operation. Suspicious files may be blocked, quarantined, or rejected.

8. Metadata

Image files can contain metadata such as timestamps, camera information, location data, author information, or editing history. Clients should remove metadata they do not wish to provide when that information is not necessary for the project.

9. Backups

Clients are responsible for maintaining independent backups of original files and important final files. Veyqen Imaging is not intended to serve as permanent archival storage for client images.

10. Temporary Storage and Deletion

Project files may be stored for the period reasonably necessary to review, process, revise, deliver, secure, and administer the project. Retention can vary based on workflow, dispute needs, legal requirements, and technical backup cycles.

Clients should download and independently store final deliverables rather than relying on indefinite availability through a project transfer location.

11. Output Specifications

The client should identify required dimensions, aspect ratio, file type, transparency, compression, color-space needs, naming conventions, or other output requirements before final export where those details matter to the intended use.

12. Batch Projects

For large groups of images, a representative sample may be useful to establish the editing approach before the full batch is completed. Consistency can depend on how similar the source images are in lighting, color, background, exposure, and composition.

13. Refusal or Removal

Files may be rejected or removed from active processing when they violate this policy, create technical risk, or cannot reasonably be processed within the agreed scope.

14. Policy Updates

This policy may be updated as file-transfer methods, security practices, supported formats, or legal requirements change. The stated update date identifies this version.