What the public site collects

The public website collects only the information a visitor chooses to submit through the faculty-demo form: name, institutional email, institution, job title, program area, estimated cohort size, intended use, optional message, consent, and coarse campaign attribution.

The public scenario preview runs without identifying information and does not collect student data, microphone input, or voice recordings.

How submissions are used

MechNetIQ uses faculty-demo submissions to respond to the request, discuss OT-Praxis, and evaluate fit for a founding-partner pilot. Form content is stored in Cloudflare D1 and is never included in analytics events.

Protected-lab AI processing

When an institution enables the bounded Controls Engineer consultation and a signed-in learner chooses to use it, OT-Praxis sends the learner's free-text message and only learner-visible session context to OpenAI for response generation. Hidden ground truth is not included. The permanent OpenAI API credential remains on the server and is not sent to the browser.

OT-Praxis sends Responses API requests with store: false. The generated response and the OT-Praxis tool-invocation audit are retained in institution-controlled Cloudflare D1 as part of the reviewable instructional record under the institution's applicable policy. Retention, access, and deletion terms for pilot learner records will be set with each participating institution; this page does not promise a fixed retention period.

Security and anti-spam

The site validates form data on the server, rate-limits submissions using a one-way keyed hash of network metadata, and can verify Cloudflare Turnstile when credentials are configured. Raw IP addresses are not stored by the application.

Analytics

If same-origin product analytics are enabled, OT-Praxis records only allowlisted interaction names, the page path, a pseudonymous browser-session hash, and coarse UTM campaign fields. It does not send names, email addresses, messages, or other form content to analytics.

Future pilot data

Future pilot data practices will be defined contractually with participating institutions. Raw voice recording will not be retained by default in the pilot design. The system is designed around data minimization and institution-controlled retention. This statement is not a claim of FERPA compliance.

Retention and access

Faculty inquiries are retained only as long as reasonably needed to respond, evaluate the pilot, and maintain business records. Pilot learner-record retention will follow institution-specific policy and contract terms. A reviewed administrative process—not a public delete route—handles access, correction, or deletion requests.

Contact

Use the faculty-demo form for privacy questions until a dedicated privacy address is configured.