Privacy Policy
Nacos Plugin Privacy Policy
This privacy policy describes how the Nacos plugin ("the plugin") handles information when used with Dify.
Information the plugin processes
The plugin may process the following information provided by the workspace administrator or by a workflow/tool invocation:
- Nacos server address
- Nacos username
- Nacos password
- Optional Nacos 3.x identity header key
- Optional Nacos 3.x identity header value
- Configuration parameters needed to execute a request, such as namespace, data ID, group, page size, history ID, namespace action, or client IP
- Configuration content when you read, write, or roll back a Nacos configuration item
How the plugin uses this information
The plugin uses the information above only to:
- Authenticate requests to your Nacos deployment
- Execute the Nacos operation you requested
- Return the requested result to your Dify workflow, app, or tool caller
The plugin does not intentionally use this information for analytics, advertising, profiling, or resale.
Storage and retention
- Provider credentials are stored by Dify in the workspace where the plugin is installed.
- The plugin itself does not add a separate long-term credential store outside the Dify runtime.
- Request parameters and returned results may appear in Dify workflow run history, logs, or debugging views depending on how your Dify environment is configured.
Network transmission
- The plugin sends requests directly to the Nacos server address configured by the workspace administrator.
- Connections may use HTTP or HTTPS, depending on the server address you configure.
- If you need transport encryption in production, configure your Nacos endpoint to use HTTPS and provide an HTTPS URL.
Data sharing
- The plugin sends data only to:
- your Dify environment
- the Nacos server you configure
- The plugin does not intentionally share your data with unrelated third parties.
Your responsibilities
When using this plugin, you are responsible for:
- Providing only the credentials and configuration data you intend to use
- Securing access to your Dify workspace and your Nacos deployment
- Choosing whether your deployment should use HTTP or HTTPS
- Ensuring you have permission to access, modify, or manage the Nacos resources targeted by this plugin
Changes to this policy
This policy may be updated when the plugin's behavior changes. The latest version is the copy included with the current plugin package and repository.
Contact
If you have questions about this plugin or its data handling, please open an issue in the project repository:
Last Updated: April 27, 2026