Data handling
Agree the data boundary before sharing operational inputs.
The website collects scoping inquiries. It is not an operational-data upload channel. Do not include telemetry, diagrams, credentials, protective thresholds, or sensitive commercial records in the inquiry form.
What the inquiry collects
Name, email, and organization are required. An optional decision description and optional scoping details help route the conversation. Inquiry intent and approved source labels may be recorded with the submission. A receipt confirms stored intake; it does not confirm delivery to an individual or acceptance of an engagement.
How the inquiry is handled
The intake implementation stores submissions in a database and queues notifications for delivery. It includes bot verification, rate limiting, delivery retry, and an optional CRM integration. Service configuration and authorized recipients must be verified before production operation; this page does not claim an independently audited security certification.
Operational data requires a separate agreement
Before exchanging historical site inputs, agree the data owner, permission to share, minimum necessary fields, authorized recipients, secure transfer method, storage location, access, retention, deletion, and permitted use. Confirm whether confidentiality or customer approvals are required. No such transfer is authorized by sending an inquiry.
Retention and correction
The application includes configurable operational retention procedures, but execution and provider retention must be verified by the operator. No universal deletion deadline is promised here. Use the contact route to request clarification or correction, identifying only the minimum information needed to locate the inquiry.
Related operator resources
Continue the proof path
- Scope your next capacity decision.Scope a paid, bounded capacity decision assessment using authorized historical inputs, explicit conditions, model comparisons, and a reviewable brief.
- Tell us where capacity is constrained.Start a scoping conversation about a bounded capacity assessment, input readiness, deliverables, decision responsibilities, or a partner investigation.
- Methods for claims that operators can defendHow GridNinja governs claims, comparisons, corrections, evidence maturity, and Capacity Audit methods.
Proof before autonomy
Start with one capacity question.
Agree the decision, evidence boundary, responsibilities, and paid scope before work begins.