Local-first, always.

Renma keeps three small pieces of data on your device, inside Chrome's chrome.storage.local:

• Your rules — filename templates, domain mappings, folder routes, duplicate mode, and site scope.
• Recent history — the last renamed files (original name, new name, source domain, timestamp) so the popup can show them and offer undo.
• Basic counters — how many files were renamed, grouped by domain, for the small stats view in Options.

You can wipe all of it any time from the popup ("Clear history") or by removing the extension.

• Send your filenames, URLs, or history anywhere.
• Read the contents of pages you visit.
• Include analytics, telemetry, or third-party scripts.
• Sync anything across devices or browsers.

• downloads — required to observe a download and suggest a new filename before the file is written.
• storage — required to remember your rules and recent history locally.
• notifications — optional; used only to show a small confirmation when a file is renamed.
• contextMenus — required to add the "Save with Renma" right-click entry.

Renma asks for the minimum surface area that lets it do its one job.

If you enable dimension tokens ({width}, {height}), Renma briefly fetches the image bytes to read its size, then discards them. Nothing is uploaded and nothing is cached beyond the resulting number.

The extension itself has no third-party integrations. This marketing website loads Google Fonts to render the wordmark; if you'd prefer to avoid that, browser-level font blocking works normally — Renma the extension is unaffected.

If the extension ever starts handling data differently, this page gets updated first and the release notes reference the change.

Questions or concerns? Open an issue on the GitHub repo — that's the fastest path to a real reply.