Privacy and Security in Zush
Zush is designed to rename files by analyzing the minimum useful content for the selected workflow. What is processed depends on the AI mode and file type.
Cloud and BYOK processing
Section titled “Cloud and BYOK processing”In Cloud AI and BYOK modes, Zush may process an analysis payload such as:
- compressed image or design previews
- sampled video frames
- subtitle or transcript context
- extracted document or PDF text
- temporary iWork preview output when needed for analysis
- audio metadata, transcript context, or bounded audio payload when transcription is required
- MIME type, extension, language preference, regenerate settings, and custom prompt text
Original full-resolution files and local folder paths are not sent as separate fields in normal cloud operation, except where a bounded audio payload or temporary document preview is required for analysis.
Offline AI processing
Section titled “Offline AI processing”Offline AI uses local Ollama models for supported analysis. In this mode, supported file analysis content is processed on your device instead of by Zush cloud or third-party AI providers. To configure local models, use the Ollama setup page. Zush may still contact backend services for licensing, updates, support, or operational checks.
BYOK keys
Section titled “BYOK keys”BYOK keys are stored locally in secure platform storage. In BYOK mode, the key is used to validate the provider and process selected AI requests. Zush does not permanently store BYOK API keys.
Training
Section titled “Training”Zush does not use your file content or custom prompt text to train Zush-owned models.
Read the full policy
Section titled “Read the full policy”This page is a practical product summary. For the legal version, read the Privacy Policy.