Skip to content

PRIVACY.md

Latest commit

 

History

History
52 lines (32 loc) · 3.29 KB

PRIVACY.md

File metadata and controls

52 lines (32 loc) · 3.29 KB

Privacy Policy

This privacy policy outlines how the MinIO Plugin handles your information when you use it to interact with MinIO object storage.

Data Collection

The plugin requires the following information to function:

  1. MinIO Credentials: Your MinIO endpoint URL, access key, and secret key are required to authenticate with your MinIO instance. These credentials are passed as workflow parameters and are used solely for making API requests to your MinIO server on your behalf. The plugin does not store these credentials persistently.

  2. User Inputs: Data you provide when using the plugin's tools, such as:

    • Bucket names
    • Object/file names
    • File content (text or binary data)
    • Content types (MIME types)
    • Binary encoding flags

Data Processing

  • MinIO Credentials: Your credentials are used exclusively to authenticate API requests sent from the plugin to your MinIO instance. They are transmitted only to your specified MinIO endpoint and are not used for any other purpose.

  • User Inputs: The data you provide is used to:

    • Read files from your MinIO buckets (for the read tool)
    • Write files to your MinIO buckets (for the write tool)
    • Construct API requests to perform these operations

  • File Content: When reading files, the plugin retrieves content from your MinIO buckets and returns it to your workflow. When writing files, the plugin sends your content to your MinIO buckets. The plugin may temporarily buffer file content in memory during read/write operations, but does not persist this data.

Third-party Services

This plugin interacts directly with your MinIO server via the MinIO API. Your use of MinIO is subject to your MinIO instance's privacy policy and terms of service. The plugin acts as an intermediary, sending your requests and data to your MinIO server and returning MinIO's responses. No data is shared with any other third-party services.

Data Retention

The MinIO Plugin itself does not store your MinIO credentials or user input data persistently. Credentials are passed as workflow parameters and are managed by your workflow execution environment. File data resides within your MinIO instance and is subject to your MinIO server's data retention policies. The plugin may temporarily cache data in memory (up to 10MB) during operations, but this data is cleared after each operation completes. Logs generated by Dify during plugin execution might contain operational data but are handled according to Dify's platform policies.

Data Security

  • Credentials and file content are transmitted securely when using HTTPS endpoints
  • The plugin uses standard MinIO authentication mechanisms
  • No data is logged or stored outside of your MinIO instance
  • Temporary memory buffers are cleared after operations complete

User Rights

Your rights regarding the data stored within your MinIO instance (buckets, objects, files) are governed by your MinIO server's settings and policies. You can manage your data directly within MinIO. For data handled by the Dify platform (like workflow execution logs), please refer to Dify's privacy policy and user settings.

Contact Information

If you have any questions or concerns about the privacy practices of this plugin, please contact the plugin author (michaelcizmar).

Last updated: December 19, 2025