Privacy Policy for Audio Merge Plugin

Data Handling and Privacy

The Audio Merge Plugin for Dify is designed to combine multiple audio files into a single output file. This privacy policy outlines how user data is handled during the operation of this plugin.

Data Collection and Storage

1. Audio Files: When merging audio files:

   • Files are uploaded by the user at the time of use
   • Files are loaded into memory or stored temporarily in secure temporary directories during processing
   • All input files and intermediate data are automatically deleted immediately after processing completes
   • No audio content is permanently stored, logged, or persisted by the plugin

2. Merged Output: The resulting merged audio file:

   • Is generated only as explicitly requested by the user
   • Is returned directly to the user through Dify’s response system
   • Is not retained, cached, or stored by the plugin after delivery
   • Any temporary working files are securely removed upon completion

Data Processing

All audio data processed through this plugin:

• Remains entirely on the host server where the plugin is deployed
• Is processed locally using pydub (and optionally FFmpeg)
• Is never transmitted to external services, cloud APIs, or third-party servers
• Exists only for the duration necessary to perform the merge operation

Third-Party Access

The plugin does not:

• Share, sell, or disclose any user audio data to third parties
• Collect analytics, usage statistics, or telemetry data
• Use cookies, trackers, or identification mechanisms
• Depend on or communicate with external online services for core functionality

Note: If FFmpeg is installed on the system, it is used locally only—no data leaves the server.

User Responsibility

Users of this plugin are responsible for:

• Ensuring they have appropriate rights and permissions to upload and process the provided audio files
• Complying with applicable copyright, privacy, and data protection laws
• Understanding that while the plugin does not store data, their Dify platform or hosting environment may have its own data retention policies
• Securing the downloaded merged audio files according to their own organizational or personal security practices

Security Measures

The plugin implements the following safeguards:

• Uses Python’s secure tempfile facilities or in-memory BytesIO for temporary data
• Ensures all file handles are properly closed and temporary resources are cleaned up
• Processes audio exclusively in local memory or isolated temporary storage
• Avoids writing sensitive data to persistent disk unless required by system constraints (and even then, auto-deletes)

Changes to This Privacy Policy

This privacy policy may be updated to reflect changes in the plugin’s implementation, dependencies, or best practices. Significant updates will be documented in the plugin’s repository changelog and reflected in future releases.

Contact

If you have questions, concerns, or requests regarding this privacy policy or how your data is handled, please contact the plugin author through the GitHub repository:

https://github.com/samanhappy/dify-audio-merge-plugin