Privacy Policy

CliDeck is operated by CliDeck LLC, an Illinois limited liability company ("CliDeck", "we", "our", "us"). We respect your privacy and are committed to protecting your personal data. This Privacy Policy explains how we collect, use, and protect information when you use clideck.com and related services.

1. Information We Collect

We may collect the following types of information:

• Account information (such as email address and authentication credentials)
• Technical information (IP address, browser type, device information)
• Usage data related to how you interact with the platform

We do not sell personal data to third parties.

2. Cookies and Tracking Technologies

We use strictly necessary cookies required for:

• Authentication
• Security (CSRF protection)
• Maintaining user sessions

We also use Google Analytics to collect anonymized usage statistics. Analytics cookies are used only after user consent.

With your consent, we use the OpenAI Pixel to measure NetController product views, demo-button clicks, and successfully submitted demo requests. OpenAI receives event and browser/attribution information to measure advertising results. We do not include your message or raw contact details in our event payloads. When automatic advanced matching is enabled, the Pixel may use hashed contact identifiers to match conversions. We opt these events out of future user-level personalization.

With analytics consent, CliDeck also records workspace session counts, active time and tool opens in its own database. For signed-in visitors, administrators can view this usage by account to improve the product. Guest sessions are not treated as unique people. We exclude background and idle time and do not collect commands, terminal output, connection targets, file contents or passwords in these records. Workspace usage records expire after 90 days.

You can withdraw measurement consent in our Cookie Policy.

3. How We Use Information

We use collected information to:

• Provide and operate the service
• Maintain security and prevent abuse
• Improve functionality and performance
• Comply with legal obligations

4. Data Sharing

We may share limited data with trusted service providers for service operation, analytics, and consent-based advertising measurement. Data is never shared for advertising resale purposes.

5. Data Retention

We retain personal data only as long as necessary to provide the service or comply with legal requirements.

The service-specific retention rules for CliDeck Knowledge MCP are described below.

6. Your Rights

Depending on your jurisdiction, you may have the right to:

• Access your personal data
• Request correction or deletion
• Withdraw consent for analytics and advertising measurement

Requests can be submitted via our support contact.

7. Security

We implement technical and organizational measures to protect data, including encrypted connections and secure cookies.

8. Contact

For privacy-related questions, contact us at:

CliDeck LLC
Illinois, USA

[email protected]

9. CliDeck Knowledge MCP and the OpenAI Plugin

This section applies to CliDeck Network Knowledge, our public Knowledge MCP endpoint at mcp.clideck.com/mcp, and its use through ChatGPT, Codex, other MCP clients, and the CliDeck website. CliDeck LLC operates this service. The public MCP does not require a CliDeck account, and we do not receive your OpenAI password, payment details, or entire chat history merely because you connect it. We receive the tool arguments that your client sends and return the result of that tool call. Your client provider processes conversations and tool results under its own privacy policy.

Information processed by MCP tools

• Questions, domain and feature selections, vendor, model, operating system, software version, and other device or environment context you submit.
• Selected device output, proposed commands, before/after configurations or configuration differences, topology and upgrade details, and optional feedback or expert-review material you deliberately send.
• Request time and identifier, client IP address when available, client/actor category, tool name, processing time, outcome, errors, and bounded, sanitized request and response excerpts used for troubleshooting and abuse prevention.
• Public knowledge revision and source references, research/demand identifiers and status, and temporary verification or task-access handles needed to retrieve or follow up on a result.

Network context may include hostnames, addresses, interface names, or other operational identifiers. Do not send passwords, API keys, authentication cookies, private customer information, or full production configurations. Redaction reduces risk but cannot recognize every sensitive value; review and remove sensitive content before submitting it. MCP does not log into your devices or execute the suggested commands on them.

Snapshots, diagnostics, and research

The device-snapshot analysis tool processes submitted text in memory. Its service journal stores a diagnostic digest, size, detected platform information, redaction counts, and outcome rather than the raw snapshot text. Other tools may retain bounded, sanitized parameters and result excerpts. Credentials and fields designated as private evidence are excluded or redacted from the MCP request journal.

A question with missing, incomplete, or disputed knowledge can create or update a research demand. We retain the sanitized question, limited technical context, relevant result references, and research status to investigate the gap and maintain the knowledge base. Research is asynchronous and does not guarantee an immediate answer. Optional expert-review tasks and supporting material are retained to carry out and audit the requested review. Optional contributions are quarantined for validation; they are not automatically published. Reviewed technical guidance and public source references may become part of the knowledge base.

Service providers and purposes

We use this information to answer the requested question, assess applicability and risks, investigate gaps, provide source provenance, operate the service, and prevent abuse. Cloudflare provides network delivery and security and may process connection metadata and requests. OpenAI provides the models used in our research workflow and may process sanitized questions, technical context, and selected reference evidence. Research may use web search and retrieve official vendor documentation; technical search terms may be transmitted to those services. We do not sell MCP submissions or use them for advertising measurement. Processing by service providers may occur outside your country, including in the United States.

MCP retention and deletion

• MCP request journal entries have a 30-day retention window and are removed by scheduled cleanup.
• Quarantined optional contribution payloads have a 30-day expiry window and are removed by scheduled cleanup.
• Research demands, expert-review records, and related audit or knowledge records are separate from the request journal. They have no automatic 30-day deletion rule and may be retained while needed to investigate, verify, and maintain technical guidance.
• Deleted records may remain in restricted backups until those backups are rotated. We may retain records needed for security investigations or legal obligations.

To request access, correction, or deletion of MCP submissions, contact [email protected] and include the approximate request date and a request, research, or task identifier if available. Do not email passwords or access tokens. Because public MCP use is unauthenticated, we may need additional information to locate your submission and verify that the request concerns your data. We will explain any records that must be retained and any limits on removing already published technical guidance. Disconnecting the plugin stops future use through that client; it does not automatically erase earlier service records. Deletion requests concerning your ChatGPT or Codex conversation history must also be directed to OpenAI.