One record per project, and nothing else.
A technical answer needs the evidence that produced it, so that evidence is what we keep. There is no advertising profile behind this site and no data is sold. What is held is a project: your requirement, your evidence, your consent, and what we did with them.
- Document
- Privacy notice
- Revision
- A
- Effective
- Applies to
- micromotion.us and the projects opened through it
What is collected
Every field below comes from something you typed, attached, or carried in on a link. Nothing is bought or inferred.
| Class | What it is | Where it comes from | Why it is held |
|---|---|---|---|
| Contact identity | Name and email address | You type it into a review form. | To answer you, and to attach the answer to the right program. |
| Company and role | Company name, your role on the program | You type it into a review form. | To route the request to the right engineer and to judge production context. |
| Requirement text | Application, mechanism, envelope, voltage, speed, torque, duty, life, noise, feedback, environment, volume, stage, timing, production location, and the problem as you wrote it | You type it into a review form, or it carries in from a saved selector or tool result. | It is the technical question. Without it there is no answer. |
| Incumbent reference | The part number, nameplate or description of what you use today | You type it into a review form. | To screen a cross-reference candidate. |
| Uploaded evidence | Drawings, photographs, datasheets, CAD, duty profiles, spreadsheets | You attach files to a review form. | It is the evidence the screening is built from. Handling is described in Confidentiality. |
| Consent record | That you agreed, the statement you agreed to, the timestamp, and whether you asked for the newsletter | The consent checkbox on the form. | To prove the basis on which the record is held, and to honor an opt-in separately from a project. |
| Campaign source | utm_source, utm_medium, utm_campaign when present in the link you followed | Query parameters on the inbound link. | To learn which technical material produces real engineering requests. |
| Referring page | The referrer header, truncated to 300 characters | Your browser sends it with the form post. | Same purpose as campaign source. It is stored on the project, not on a profile. |
| Event log | An allow-listed event name, the route, a short allow-listed payload, a timestamp, and the project identifier when the event was raised by your own submission | First-party events posted by the site. | To measure whether a page, a tool or an offer works. See the payload rule below. |
Legal basis
Two bases, used for different things, and never mixed.
Consent. A review form cannot be submitted without agreeing to Micro Motion holding the submitted information to answer the request. The agreement, the exact statement, and the time it was given are stored on the project. A newsletter opt-in is a separate checkbox and is recorded separately, so declining it does not affect the answer you get.
Legitimate interest in answering a technical request. Once you have asked an engineering question, holding the requirement, the evidence and the working needed to answer it, and keeping the record that shows what was quoted against what, is the ordinary conduct of the request. It is also what a production customer needs years later when a part has to be re-qualified.
Withdrawing consent stops any newsletter and, on request, deletes the project record. Records we are required to keep for tax or contract reasons are named in the retention table and are the only exception.
How long each class is kept
Retention is set separately for an inquiry that never became a program, a live project, and paid work. It is not one blanket period.
| Record class | Kept for | Then |
|---|---|---|
| Unqualified inquiry | 12 months from the last contact | The project, its requirement text and its uploaded evidence are deleted. A minimal line stays in the event log: offer, route, date. No identity, no requirement text. |
| Active project | For the life of the program, plus 7 years after the last activity on it | Deleted. A production motor is qualified against a record; a supplier who deletes it at 12 months is useless to you at the first field return. |
| Paid analysis | 7 years from the report date | The report, its measurements and its photographs are deleted. Physical samples follow the disposition you chose when the scope was agreed. |
| Uploaded evidence | The same period as the project it belongs to | Deleted with the project, or earlier at your request. Evidence can be deleted without deleting the project. |
| Consent record | 6 years from withdrawal or from the end of the project | Kept after deletion of the rest, because it is the proof of the basis on which the record was held. |
| Event log | 25 months | Deleted. Entries carry no name, no email address, no IP address, no requirement text and no filename. An entry raised by your own submission carries the project identifier and is deleted with the project it belongs to. |
| Newsletter opt-in | Until you unsubscribe | Removed from the list. The record that you had opted in is retained under the consent line above. |
Confidential requirements never reach a third-party analytics service.
This is enforced in code, not by policy alone.
The site records its own events on its own server. The endpoint that accepts them takes an event name from a fixed allow-list, the route, and a short payload whose keys are also allow-listed. Anything else in the payload is discarded before the event is written. Requirement text, uploaded filenames, incumbent part numbers and calculation inputs or outputs are not on that list and cannot be recorded through it.
Where a third party is genuinely involved, it is named here: a transactional email provider carries the receipt to your address, a hosting provider runs the server, and a managed PostgreSQL provider stores the project record. Each is a processor acting on Micro Motion instructions. Nothing is sold, and no advertising network receives anything from this site.
Who sees your record
-
The engineer who owns the project
Full access. This is the person who answers you.
-
Application engineering, for triage
Reads the requirement to route it. Uploaded evidence stays quarantined until it has been scanned.
-
A named test lab or machining partner
Only on a scope you approved, only the drawing or sample that scope needs, and only after you have said so in writing.
-
Nobody else
Your requirement is not shown to another customer, published as a case study, or used in marketing without your written permission, named program by named program.
Asking for deletion, correction or a copy
One request covers the project, its evidence and the consent record.
This site does not publish a general mailbox, because a technical request answered from a general mailbox loses its evidence. Say whether you want the whole project deleted, only the uploaded evidence removed, a field corrected, or a copy of what is held. Two routes reach a person:
- Reply to the receipt email you were sent when the project opened. It carries the project identifier and reaches the engineer who owns it.
- If you have no project yet, open one at Replace a motor and write what you need in the requirement field. A person reads every submission.
A deletion request is answered within 30 days and normally within 5 business days. You will be told what was deleted and what was retained under the consent or contract lines in the retention table. If you are in a jurisdiction with statutory data rights, use the same route: the request is handled the same way whether or not a statute compels it.