Your drawing is the most sensitive thing you send.
So it is handled as the most sensitive thing we hold. This page describes what the code actually does with an uploaded file, in the order it does it.
- Document
- Confidentiality and evidence handling
- Revision
- A
- Effective
- Applies to
- micromotion.us and the projects opened through it
What happens to a file you attach
Six steps, all of them before any person opens it.
-
The format is checked against the bytes, not the browser
The extension must be on the allow-list (.pdf,.png,.jpg,.jpeg,.webp,.heic,.step,.stp,.igs,.iges,.dxf,.zip,.csv,.txt). The leading bytes must then prove the file really is that format, or the file is rejected with a message that tells you what to re-export. A renamed executable does not get in.
-
Size ceilings are enforced
Up to 6 files, 20 MB per file and 60 MB per project. Anything larger is refused rather than truncated.
-
The file is renamed to a generated identifier
The stored name is a random UUID plus the verified extension. Your original filename is kept only as private metadata on the project record. Filenames carry program names, customer names and revision states, so the filename itself is treated as confidential and is never echoed into a public page, a URL or an email subject line.
-
It is written outside the public web root
Storage is a private directory, owner-only, created with restrictive modes, in a location the static file server has no path to. There is no route on this site that serves an uploaded file, at any URL, with any token.
-
It is quarantined
Every stored object is marked quarantined until it has been scanned. Staff tooling does not release a quarantined object for viewing.
-
It is logged
One access-log line per stored object: timestamp, project identifier, generated asset identifier, byte length and SHA-256 digest. The digest is what proves the file you sent is the file we analyzed.
Access
Least privilege, and a record of who used it.
Access to stored evidence is limited to the engineer who owns the project and to the application engineer triaging it. Retrieval happens through internal tooling with its own authorization and its own log, never through the public server. The database role that serves this website can write a project and read the project it was handed a valid link for. It cannot read the restricted source catalog, and it has no path to the evidence store at all.
The link to a project record contains a high-entropy access token. Only the SHA-256 hash of that token is stored, and comparison is constant-time, so a stored record cannot be used to recover a working link. A request with no token, a wrong token or an unknown project identifier gets exactly the same answer, so the link cannot be used to discover whether a project exists.
Physical samples and failed units
A failed motor is evidence. It is handled as evidence.
| Stage | What is recorded |
|---|---|
| Shipping instructions issued | Project identifier, expected sample count, and the identifier written on the outside of the package. |
| Receipt | Date, condition on arrival, photographs of the package before it is opened, and the person who received it. |
| Intake | Each unit tagged with the project identifier and a unit number. Nameplate and as-received condition photographed before anything is disturbed. |
| Inspection authorization | Your written approval of the scope before any destructive step. Teardown is not started without it. |
| Teardown | Every step photographed and logged against the unit number, with the person who performed it. |
| Retention | Parts retained in the project's labeled container for the agreed period. |
| Disposition | Returned to you, retained, or destroyed, as you chose in the agreed scope. The choice and the date are recorded. |
Findings, photographs and measurements from a paid analysis belong to the program they were produced for. They are not published, shown to another customer, or used as a marketing example without your written permission for the specific material.
Do not send patient data or protected health information. Ever.
Micro Motion needs the mechanism, the load, the duty cycle and the failure. It never needs a patient identifier, an image containing one, or a clinical record. This site is not built to hold that data and will not accept responsibility for it. Redact before you attach.
If your organization requires a mutual non-disclosure agreement before you send anything, say so in a review and we will execute yours. The controls on this page apply from the first upload, with or without a signed agreement in place.