Privacy notice

AIDC-AI.IO controls the public site, Agent API, MCP discovery surface, Site Finder, and EngineSession preview tools. Privacy requests can be sent to contact@aidc-ai.io.

Contact forms collect name, email, role, and message. Email verification collects a work email address, requested access scope, optional EngineSession id, and delivery status. Site Finder and EngineSession flows process selected site details, parcel or geometry evidence, design constraints, rackPlan, power, cooling, network, validation, BOM, estimate, and manual override data needed to generate and validate the shared 3D graph. API and MCP calls process the JSON payloads submitted to the endpoint, request metadata, rate-limit tier, and optional API-key hash lookup data.

Static tools may use browser localStorage to preserve selected site handoff data, active EngineSession ids, viewer preferences, graph inspector state, or manual rack plan edits on the same device. Clearing browser site data removes those local records. Server-side EngineSession preview records are currently engineering-preview runtime records and may be reset, replaced, or removed between deployments.

We use submitted data to operate the engine, create and validate EngineSession artifacts, provide contact and verification workflows, protect against abuse, diagnose reliability issues, and respond to requests. We do not use contact briefs for third-party advertising, do not sell personal information, and do not enroll contacts in marketing lists without a separate opt-in.

We use infrastructure and communication providers only as needed to run the service: Vercel for hosting and request logs, Slack webhook forwarding when configured for contact notifications, Resend when configured for email verification, and Upstash Redis when configured for API rate limiting or API-key tier lookup. We may also disclose data where required to comply with law, enforce terms, or protect the service from misuse.

Contact submissions are kept only as long as needed to respond, maintain business records, or handle abuse/security issues. Email verification links expire after 15 minutes; email access cookies expire after 7 days; passphrase session cookies expire after 24 hours. API rate-limit records and hosting logs follow the configured provider retention settings. Browser localStorage remains until the user or browser clears it.

AIDC-AI.IO is a design engine, not a public data-sharing forum. Engineering inputs are processed to generate OPR/BOD, rackPlan, SLD, Sankey, pandapower, validation, BOM, estimate, procurement, and commissioning artifacts from the shared graph. We do not intentionally train third-party foundation models on submitted basis briefs unless a separate written agreement says so.

Email contact@aidc-ai.io to request deletion of a contact submission, or to ask which records reference your email address. You can also request correction, deletion, or processing limits for personal data associated with an EngineSession where we can reasonably identify the record. We respond within 30 days.

We use request-size guards, rate limits, signed HTTP-only cookies, API-key hashing for tier lookup, and limited public views for sensitive procurement artifacts. No internet service can guarantee perfect security; do not submit secrets, passwords, private keys, regulated personal data, or confidential third-party materials unless you are authorized and have an appropriate engagement agreement.

If this notice changes materially we update the "Effective" date above and describe the change in the site changelog (engineering preview).