Confidentiality & File Handling
Customer production files are treated as confidential project material, not as public content or default portfolio assets.
ArtworkRelay's operating policy is to use submitted artwork for the requested production-art work and QA, avoid public or portfolio use without explicit permission, and limit access to the people or tools needed for fulfillment.
If your account needs a specific NDA, retention or deletion rule, or restriction on third-party processing, contact ArtworkRelay before sending the file so the requirement can be reviewed for that project.
Current file-handling policy
Use files for the defined production job and QA.
No portfolio or promotional use without permission.
Access follows the work that needs to be fulfilled.
NDA or special restrictions should be raised before submission.
What We Use Submitted Files For
A file submitted to ArtworkRelay is there for a defined production purpose: review, production-art execution, QA, proof or revision where applicable, and delivery of the agreed output.
Review
Understand the source file and the production requirements tied to the job.
Production-Art Work
Prepare or rebuild artwork for the agreed downstream production use.
QA & Proof
Check the artwork against the production brief and handle proof or revision where applicable.
Delivery
Return the agreed output to the buyer for the downstream production workflow.
Submission does not by itself give permission to reuse the artwork for marketing, training examples, public case studies, or portfolio display.
Use the Free Production Test for a qualified real jobAccess Follows the Production Job
The operating requirement is least-necessary access.
People, contributors, and tools involved in fulfillment should receive only the access needed for the assigned production work, QA, or release path. Customer files should not be forwarded or shared outside the authorized ArtworkRelay workflow without project authorization.
See How ArtworkRelay WorksLeast-necessary access
Access is tied to the assigned production work, QA, and release path rather than broad internal visibility.
No unsupported security claims
This is an operating requirement, not a claim about unverified technical controls. ArtworkRelay does not publish unsupported claims about security certifications, encryption architecture, data residency, or audited access systems.
Permission and Project-Specific Restrictions
No Portfolio Use Without Permission
Customer artwork does not become public proof by default.
Files, before/after work, production details, or finished artwork should not be published as portfolio or promotional material without explicit permission. Any future approval for public use is separate from the production job itself.
NDA Requests for Sensitive Work
ArtworkRelay supports an NDA path for sensitive accounts.
If your company requires an NDA or another project-specific confidentiality restriction, raise it before file submission so the requirement can be reviewed before the production workflow starts. This page does not create a universal NDA or replace a signed account-specific agreement.
Discuss an NDA Requirement
Retention and Deletion
ArtworkRelay does not currently publish one universal file-retention period or one automatic deletion deadline for every job.
Before work begins
If your workflow requires a specific retention limit, deletion request, saved production master, or another file-lifecycle rule, state it before work begins.
During the project
The requirement can be reviewed against the needs of that project rather than inferred from a generic website promise.
After the job
File-lifecycle handling remains project-specific when a special retention or deletion requirement has been agreed.
ArtworkRelay does not claim that every file is automatically deleted after a fixed number of days.
No blanket “never leaves internal systems” promise
Tool restrictions should be made explicit before submission when the project requires them.
Project Restrictions Need to Be Stated Up Front
ArtworkRelay does not make a blanket promise that customer files never leave internal systems.
Third-party tools may be part of some production or support workflows. Exact provider-retention, training-use, enterprise-account, or tool-specific settings are not universal public commitments.
If your files cannot be processed by a particular tool class or outside a defined environment, contact ArtworkRelay before submission so that restriction can be reviewed for the project.
Discuss a Processing RestrictionConfidentiality, Rights, and Production QA Are Different Controls
A file can be handled confidentially, still have separate rights questions, and still need production QA before release.
Production approval is not copyright approval
You should submit only artwork that your company owns or is authorized by the rights holder to use and reproduce. ArtworkRelay does not independently clear copyright or trademark rights as part of production-art service.
A file can pass the agreed production-art review and still have separate rights questions. Production approval is not copyright or trademark approval.
Confidentiality is not production QA
Confidentiality governs how submitted artwork is used, accessed, shared, retained, and published.
Production QA checks the artwork against the agreed production brief before ArtworkRelay treats it as release-ready.
Human QA for Production ArtworkBefore You Submit Sensitive Artwork
For a normal qualified production job, you can test one real production file.
If the job involves an NDA, special retention/deletion requirement, restricted tool use, or another sensitive handling condition, contact ArtworkRelay before submitting the file.
This page explains ArtworkRelay's current operating policy for production files. It is not legal advice and does not replace a signed NDA or project-specific agreement.