File handling & security

Know where your file goes—and who can reach it.

This is the practical lifecycle for uploads, analysis, saved work, sharing, retention, and deletion requests across 3D Print Pass.

Saved work
Saved to your account
Administration
Authorized admin roles
Shared reports
Bearer link or selected account

The file lifecycle

A visible chain of custody, with important differences by workflow.

Model uploads and troubleshooting photos do not take exactly the same path. The distinctions below are intentional.

  1. 01
    Receive

    Supported file types enter the workflow you chose. Request-size and format checks apply at intake.

  2. 02
    Inspect

    Accepted model files and profile images follow the checks enabled for their route. When troubleshooting photos are available, they receive narrower file and image-header checks.

  3. 03
    Process

    Geometry metrics, workflow evidence, or optional AI analysis is produced for the requested task.

  4. 04
    Scope

    Signed-in saved work is tied to its owner. Anonymous checks do not create saved report history.

  5. 05
    Share or request a privacy action

    You choose whether to use a tokenized report link. Signed-in users can open a tracked request for account-data access, export, correction, erasure, restriction, or objection.

1. How 3D Print Pass Handles Your Files

The five-step lifecycle above covers intake, inspection, processing, saved access, and sharing. Read the route-specific limitations before submitting a file.

Open a tracked account-data request for access, export, correction, erasure, restriction, or objection. Submitting a request does not itself delete every record.

2. Storage & Security

Upload controls differ by route. Saved Upload records its configured custody and scanning states; an external-malware verdict exists only when that integration actually runs. New file submissions to the 3D File Structure Check and Print Analysis photo fields are paused. The written Print Analysis path and public examples remain available.

Upload only trusted, non-sensitive images. Production configuration requires HTTPS, secure cookies, and HSTS, but each release still needs a live transport probe before encrypted delivery is treated as verified.

3. Access Controls

Account pages, saved reports, billing tools, and dashboard views require authenticated access. Admin tools are role-restricted.

4. Retention & Deletion

Saved reports support quote history and customer handoff. The tracked privacy-request area records account-data requests and their status. Legal, billing, security, provider, and backup records may remain when a documented disposition or active legal hold requires retention.

5. Tokenized Report Links

Customer report links are tokenized. A bearer link can be opened by anyone holding it. A confirmed-account link is limited to the selected signed-in recipient. Both can expire or be revoked; review the access mode and report before sharing.

6. Your Control

Signed-in file checks can create owner-scoped saved reports. You choose when to unlock, share, download, or request support for them.