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

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

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. Zush may still contact backend services for licensing, updates, support, or operational checks.

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

Zush does not use your file content or custom prompt text to train Zush-owned models.

Regulated documents: medical, legal, financial

If you handle documents under confidentiality or regulatory obligations — patient records, client files, financial statements — choose the AI mode that matches your posture:

Offline AI processes supported files entirely on your device with local models. Nothing about the file content is transmitted. This is the mode to prefer for regulated content.
BYOK sends analysis to your own provider account (OpenAI, Anthropic, or Google) under the agreement your organization has with that provider.
Cloud mode uses Zush’s managed AI processing and is designed for general files, not documents you are obligated to keep in-house.

In every mode, renaming happens in place on your disk: Zush never uploads, moves, or stores your files, and filenames and folder structure stay local.

Two practical caveats. First, an AI mode does not replace your organization’s security, access, retention, or naming policies. Second, filenames can surface in sync logs, attachment lines, and search indexes, so keep details that do not need to appear in a folder listing inside the document. The medical records workflow shows how to combine this with Offline AI or organization-controlled BYOK.

Read the full policy

This page is a practical product summary. For the legal version, read the Privacy Policy.