Privacy & Your Data
Exactly what leaves your computer in each mode - Managed, your own API key, or local models - in plain language. No file is ever kept beyond processing.
To rename a file by its content, something has to read that content. This page says exactly what that something is in each mode, and what leaves your computer, in plain language. It applies to NameQuick 3 on Mac and Windows. The formal version is in the privacy policy; this is the version you can actually act on.
The one-sentence summary: your files live on your computer, NameQuick never keeps them beyond processing, and you choose where your file content goes for naming, including nowhere at all.
The three modes, side by side#
Managed
Your own API key
Local models
Managed#
File content for analysis (text, images, or the file) goes through our TLS-encrypted processing service in the EU cloud. It is processed for renaming only, held briefly in a private storage bucket and deleted right after processing (automatically within 24 hours at the latest), and never used for AI training.
Your own API key (Self-Managed)#
The content needed for naming (extracted text, images, or the file itself, for example a PDF, depending on the file and provider) goes directly to the provider you chose, never through our servers. The provider's own terms apply.
Local models (Ollama, LM Studio, MLX)#
No file content leaves your computer: analysis runs on your hardware. Installing engines, downloading models, and license and update checks still use the internet.
In every mode, analysis only reads your files and returns a name suggestion you control. NameQuick changes a file when a name is applied, or when you set up Rules or turn on Write tags & comments into files.
What always stays local, in every mode#
| Data | Where and what |
|---|---|
| API keys | The macOS Keychain or the Windows Credential Manager, not config files |
| Library and rename history | A local database on your computer. They can contain file names and paths. |
| Content Search index | A local database on your computer, never uploaded. Text recognition for scans and images uses the operating system's on-device OCR on Mac and Windows. |
History → Clear History… removes the stored rename receipts; after that, those renames can no longer be undone from History.
What NameQuick's own services see#
| Service | What it sends |
|---|---|
| License checks | Your license key (Self-Managed) or sign-in email (Managed) to validate your plan. Activating a Self-Managed license also sends a device label, your computer's name when available, so you can recognize the activation in the Customer Portal. No hardware serials, no file information. |
| Update checks | The app version, so you get the right update. |
| Anonymous usage data | Technical diagnostics tied to an installation identifier, never file names, paths, or file contents. They help us see what's breaking and what's used. |
Turn anonymous usage data on or off with Share anonymous usage data in SettingsData & Privacy. It is on by default for the direct download and asks for your consent first in app-store versions. Details in the privacy policy.
Common questions#
Does only locally recognized text leave my computer for scans?
No. The Content Search index is separate from naming: for naming with Managed or a cloud API key, the AI model reads scanned pages from the page images, so don't assume only locally recognized text leaves your computer.
Which mode should I use for sensitive work?
Contracts, medical records, client financials? Use a local model: the content is analyzed on your machine, and you can verify it yourself by renaming with Wi-Fi off once the model is set up. If you use a cloud API key instead, prefer paid plans whose data terms fit your needs; free tiers can have different data-use terms. Switching providers takes one click in Settings → AI.
Questions this page didn't answer? Ask us directly: support@namequick.app. Privacy questions get straight answers; it's a thing we like being asked about.