Privacy — RegEvidenceHub CableCert

Last updated: 14 October 2026. CableCert processes user-supplied structured-cabling CSV evidence to inspect its fields and, when the user provides an expected cable-ID list, compare that list with the submitted evidence.

Data and purpose

For inspection and audit requests, the selected MCP endpoint receives CSV text, source filename, expected cable IDs, and an optional expected test-limit label. It returns mapped fields, record counts, and evidence exceptions with available source-row provenance. The no-payment OpenAI endpoint is /openai/mcp; it performs these checks without payment and handles CSV inputs in memory. The separate commercial endpoint /mcp may use x402 payment. Its explicitly selected paid continuation flow stores only normalized fields needed to resume the audit; it does not store raw CSV bytes or unmapped fields.

Recipients

Inputs and results are processed by the RegEvidenceHub CableCert service and its current host, Railway. When the user invokes CableCert in ChatGPT, relevant prompts, files, tool inputs, and results are also processed by OpenAI under OpenAI's policies. See OpenAI's privacy policy and ChatGPT chat and file retention controls.

For eligible tool calls, CableCert logs operational attribution: product/tool name, timestamp, event and outcome category, deployment, an explicitly supplied distribution channel, and protocol-provided client name/version or request ID when available. If configured, a reduced event (product ID, event type, source channel, test classification, and object-count flags) is sent to the RegEvidenceHub commercial platform for aggregate usage attribution. It contains no prompt, CSV, cable ID, name, or evidence row. Payment facilitation and entitlement processing occur only on the commercial flow; the payment facilitator receives the payment proof/transaction metadata needed to verify payment, while the shared platform receives continuation and entitlement references, not raw CSV.

Railway and network infrastructure may process connection metadata such as IP address, request route, timestamp, and status for hosting, security, and diagnostics. See Railway's privacy policy. Payment providers apply their own policies; see Coinbase's privacy notice and Stripe's privacy policy.

Retention

The no-payment ChatGPT endpoint processes raw CSV in memory for the request and does not intentionally persist it. The commercial paid-continuation flow temporarily stores normalized audit fields and expected IDs for up to the configured lifetime (24 hours by default); a background cleanup task removes expired continuation files within five minutes after expiry while the service is running. Application attribution logs contain metadata only and are retained according to the service's operational log management. Railway may retain infrastructure logs under its current policy and configuration.

Your choices and requests

You can choose not to submit a file, redact it, or use synthetic evidence. Do not submit passwords, secrets, or personal data that is not required for the check. ChatGPT users can manage or delete chats and files through their account controls. For product-held data or a paid continuation case, contact RegEvidenceHub support and include the case reference if available; do not post evidence publicly. Requests about OpenAI, Railway, Coinbase, or Stripe data must be made to those providers.

Scope and changes

CableCert reports evidence exceptions for human review. It does not certify cabling, decide TIA compliance or safety, or accept contractor work. We will update this notice if data practices change.