AGREE
Name the evidence and purpose
Request only the specific file needed for the accepted engagement. Set a named recipient, file type and size limits, due date, expiry and approved channel first.
CLOUDEK · DESIGN PREVIEW
Request the right file
through an agreed channel.
A file request could help an engineer ask for limited evidence needed for an accepted support scope. Customer file transfer is not available here. An opt-in pilot panel below can exercise only a hard-coded synthetic marker; it never selects or accepts a file.
FUTURE CUSTOMER WORKFLOW
Preview · not connectedA request with clear boundaries
A future request would explain exactly what is needed, who should provide it and when the link expires. This example uses no customer details and has no working upload controls.
EXAMPLE REQUESTEmail delivery diagnostic bundleIllustrative wording only
FILE LIMITUp to 3 files · 20 MB eachExample limits · not enforced here
EXPIRY7 days after creationExample policy · no link exists
Customer files would appear here
Upload and download are disabled in this preview.
Unavailable until secure upload, malware inspection, recipient verification, expiry and deletion are implemented and reviewed.
SYNTHETIC PILOT ONLY
No file picker · no customer contentTest a one-time marker transfer
This test stores one fixed marker string. It does not accept file bytes, names, types, passwords or other content. The recipient must click to consume the marker once.
ONE-TIME SYNTHETIC LINK
EXPIRY
CONTENTFixed marker onlyNo user file is read or sent.
RECEIVE
Quarantine before review
A future service would need private storage, server-side limits, access checks and an agreed inspection process before making a file available to an operator.
DELETE
Track expiry and deletion
Retention must cover working storage, quarantine, scanner copies, backups and operator downloads. Do not report deletion as complete until the policy can verify it.
Before any customer upload exists
- Verify the customer's authority, named recipient, data purpose, classification and accepted written scope.
- Set strict file-type, byte-size, count, request-rate and expiry limits. Reject unsupported content and fail closed if authorization or inspection is unavailable.
- Choose private storage, region, encryption boundary, malware-inspection provider, subprocessors, backup lifetime and deletion verification.
- Review privacy terms, abuse handling, support ownership, incident response, and an application-level quota and stop switch. Azure budget alerts notify an owner but do not stop spending.
The existing desktop file importer selects a local file for an operator; it is not a customer upload channel. A static website cannot safely receive or retain customer files by itself.
This page does not select, upload, scan, store, display or download customer files. It has no upload control, file storage, malware scanner or download service for customer files. Its opt-in pilot uses only a fixed synthetic marker. Do not place customer data here or treat the preview as a secure transfer service. Prefer the customer's approved file-sharing channel.