Privacy at NexusDock.

1. Scope

This Privacy Policy applies to the hosted NexusDock service and website at nexusdock.co. It does not govern a NexusDock deployment that you or another operator host independently. A self-hosted deployment is controlled by its own operator.

2. Information NexusDock handles

Account and identity information

When you sign in, NexusDock handles information needed to identify and secure your account, such as a verified email address and identity-provider identifiers when you use a supported sign-in provider.

Connected-device information

NexusDock handles information needed to identify and route work to devices you explicitly connect, such as a device name, device identifier, operating system, online status, software version, and the capabilities the device reports.

Content you choose to store

If you use Recall or Workflow, NexusDock stores the content and metadata required to provide those features. You decide what to save. Credentials and secrets should not be stored in Recall or Workflow content.

Integration and authorization information

NexusDock handles authorization records and related metadata needed to connect compatible MCP clients and services. Authentication credentials are treated as sensitive security material.

Usage, diagnostics, and billing information

NexusDock may process service usage, request identifiers, operational diagnostics, and subscription state needed to run, secure, troubleshoot, meter, and bill the hosted service. Payment details may be handled by a payment provider rather than stored directly by NexusDock.

3. Connected devices and requested actions

NexusDock can route a request from a compatible AI client to a device that you explicitly connect. Depending on the action you request and the capabilities available on that device, the connected device may access local files, applications, browsers, or other resources.

Connecting a device does not mean every file or resource on that device is automatically uploaded to NexusDock. Information is exchanged as needed to provide the capability or action you choose to use.

4. How information is used

• Provide and secure your NexusDock account and personal workspace.
• Connect, identify, and route requests to devices you authorize.
• Provide Recall, Workflow, MCP integrations, and related product features.
• Operate, monitor, troubleshoot, and protect the hosted service.
• Measure usage and administer subscriptions or applicable service limits.
• Comply with legal obligations and respond to valid legal requests when required.

5. AI clients and third-party services

When you connect NexusDock to ChatGPT, Codex, Claude, or another compatible client, information required to perform your requested action may be exchanged between that client, NexusDock, and a connected device or service. Third-party clients, identity providers, payment providers, hosting providers, and other services are governed by their own privacy practices.

6. Data isolation and security

NexusDock uses access controls and workspace isolation designed to prevent one account from accessing another account's workspace data. The hosted service uses HTTPS for public network access and treats authentication material as sensitive.

No internet service can guarantee absolute security. You are responsible for protecting your sign-in methods and for deciding which devices, services, and capabilities to connect.

7. Retention and deletion

NexusDock keeps account and service data for as long as needed to provide the hosted service, maintain security and operational integrity, satisfy applicable obligations, or until the data is deleted through available product controls.

You can remove connected devices, revoke supported authorizations, and manage Recall and Workflow content through the controls available for those features. When an account is deleted through a supported NexusDock account-deletion flow, its active access credentials are invalidated and cleanup of the associated workspace data begins. Backup and infrastructure cleanup may complete after the live account has been removed.

8. Your choices

• Choose which devices and services to connect.
• Remove a connected device when you no longer want NexusDock to route work to it.
• Revoke supported MCP or OAuth authorizations.
• Choose what long-term context to store in Recall and what workflows to keep.
• Use supported account-deletion flows when they are made available for your account and current interface.

9. Changes to this policy

NexusDock may update this policy as the hosted service changes. The current version is published at this URL with its effective date. Material changes may also be communicated through the service when appropriate.

10. Questions and requests

For questions about this policy, privacy requests, or the product controls available to you, email [email protected] or see NexusDock Support. Do not post credentials, private account data, payment information, or sensitive personal content in public support reports.