Private Bucket
Uploaded files are stored in a non-public container; access is governed by the operating business.
Trust & IP
Your drawings stay under controlled use
Submitted files are intended for quotation, engineering review and project coordination. The handling model is designed to keep project information out of public reach.
Handling model
Private storage, no public URLs
The RFQ service is designed to store production files in a private object bucket. Files are not assigned public URLs.
Encrypted Transit
Files are submitted over HTTPS and validated by field whitelist before any storage action.
Strict Checks
File type, size and count limits are enforced server-side, not only in the browser.
Need-to-Know
Files are shared with selected manufacturing partners only for the project they support.
Retention Governance
Retention, deletion and access procedures must be configured by the operating business before launch.
No False Claims
We do not publish partner certifications, equipment or case evidence without verification.
Current build status: the file-handling architecture is defined and the worker enforces validation,
but live storage, access controls and retention are not yet activated with real credentials.
Production submission remains disabled until configuration is complete.
Confidentiality
Before you share restricted files
If project information is subject to confidentiality, request an NDA before uploading. Marking the NDA box in the RFQ tells the team to establish a confidentiality agreement first.
- Redact or watermark externally shared previews where useful.
- State export-control or compliance constraints in the RFQ notes.
- Use a work email the team can reach for clarification.
Questions about file handling?
Review the privacy policy or contact the team before sharing restricted project information.
Read Privacy Policy