Security & Privacy

RenamerX is built as a local-first desktop application. That design choice affects both privacy and security.

What stays local

Normal file processing is designed to stay on your machine.

That includes:

• reading supported files
• extracting text and metadata
• generating previews for images and videos
• producing rename suggestions
• applying and undoing file operations

Routine rename generation is not based on uploading your working files to a hosted AI service.

What uses network access

Network access is still needed for a small set of product operations:

• downloading local runtime resources during setup
• opening the checkout flow
• activating a license
• validating a license periodically

These are product and licensing operations, not the normal rename pipeline.

License key handling

RenamerX stores license state and related billing data in encrypted local storage on the device instead of leaving that information as plain app state.

That means the product protects local billing state, but it should not be described as relying on the system keychain.

Folder and file access

RenamerX works on files you explicitly add or on folders you explicitly configure.

When scanning folders, the app intentionally skips common hidden or build-system directories such as:

• hidden dot-directories
• node_modules
• target
• dist
• build
• coverage

This reduces accidental intake of irrelevant system or developer files.

Review before apply

A privacy-first app still needs operational safety. That is why RenamerX defaults to review-first rename flows instead of changing files immediately.

Review First helps prevent:

• incorrect names being applied silently
• large accidental rename mistakes
• automation running beyond your confidence level

Local metadata and previews

RenamerX may extract file metadata, document text, or visual previews locally to improve naming quality.

That processing is part of the local workflow. It is not the same as sharing your files with a remote service.

Practical guidance for sensitive material

If you work with confidential files:

• start with Batch Rename, not Auto Apply
• validate your template on non-sensitive examples first
• keep your controlled vocabulary small and deliberate
• review suggested names before apply when context matters

A simple summary

RenamerX is designed so that your file understanding workflow happens locally, while setup, purchase, and license operations use the network when needed.