Privacy Policy
Privacy at a glance
We do not collect or store your file content.
RenameClick does not collect, access, or store your files, photos, videos, documents, filenames, workspace contents, or AI results on RenameClick servers. With the built-in local AI model, processing happens on your computer.
Local AI stays local
The built-in model runs on your device. We do not upload your content.
Cloud AI is optional
Direct and Windows builds can use cloud AI if configured. The Mac App Store build does not include cloud providers.
No payment cards
Apple and Polar process payments. RevenueCat handles purchase status, not card numbers.
MAS is accountless
The Mac App Store build has no RenameClick account, sign-in, or account portal.
This policy covers RenameClick across Mac App Store, direct macOS, and Windows builds, plus the rename.click website. It explains what we do not collect, what limited data we do collect, and how optional third-party services work.
Mac App Store version
The Mac App Store build is a standalone, accountless app.
The Mac App Store version of RenameClick has no RenameClick account, Clerk sign-in, account portal, or account deletion flow. Pro access is purchased through Apple In-App Purchase. RevenueCat verifies the subscription or lifetime entitlement and restores purchase status using an anonymous App User ID generated by its SDK. We do not send RevenueCat your email address, name, or a custom RenameClick account ID for Mac App Store purchases.
Mac App Store purchases are separate from direct macOS and Windows licenses. They do not sync to Clerk, Polar, or direct-build accounts, and direct-build purchases do not unlock the Mac App Store build.
The Mac App Store build also does not include OpenAI, Google AI, Alibaba Cloud, cloud provider configuration, cloud API-key entry, or cloud AI processing. It supports the built-in Local AI provider and optional user-controlled local or self-hosted servers through LM Studio or Ollama.
1. What We Do Not Collect
RenameClick is designed so your working files stay under your control. We do not collect:
- File contents, photos, videos, documents, PDFs, or text extracted from your files.
- Local filenames, folder names, workspace rows, search results, or AI-generated file names.
- Payment card numbers, bank account numbers, or other payment method details.
- Contacts, precise location, health or fitness data, sensitive personal information, or browsing history.
- Mobile advertising identifiers or data for cross-app tracking.
2. Local AI and File Processing
When you use the built-in local AI model, file analysis happens entirely on your device. RenameClick may read selected files locally to generate names, categories, previews, search matches, and EXIF-based output, but that content is not uploaded to RenameClick servers.
Local server providers such as LM Studio and Ollama are also local-first setups. In those modes, RenameClick sends content from the app to the local server address you configured, such as localhost.
3. Optional Cloud AI Providers in Direct and Windows Builds
In direct macOS and Windows builds, you can optionally connect your own API keys for OpenAI, Google AI, or Alibaba Cloud. These cloud providers are not available in the Mac App Store build. Cloud AI is not required to use RenameClick. If you choose a cloud provider in a supported build, your device sends selected file content, prompts, and related metadata directly to that provider for processing.
- API keys stay on your device: Keys are stored locally with OS-backed secure storage, such as Keychain on macOS and the Windows credential store where available.
- We do not receive your cloud AI requests: RenameClick does not proxy, log, or store the content exchanged between your device and your chosen AI provider.
- Your provider rules apply: Cloud AI processing is governed by the account, terms, and privacy policy of the provider you choose.
Provider privacy policies: OpenAI, Google AI, Alibaba Cloud.
4. Information We Collect
We collect only the information needed to operate purchases, licenses, support, diagnostics, and the website. The exact data depends on which RenameClick build you use.
Mac App Store build
The Mac App Store build does not create a RenameClick account and does not use Clerk. For Apple purchases, RevenueCat may process an anonymous App User ID generated by the RevenueCat SDK, App Store product IDs, entitlement status, purchase dates, expiration dates, refund or revocation status, restore events, store environment, app version, platform, and related purchase diagnostics needed to unlock and support Pro access.
Apple processes App Store billing, payment methods, taxes, invoices, refunds, and subscription management. RenameClick and RevenueCat do not receive or store your payment card number.
Direct macOS and Windows builds
- Account data: Clerk handles sign-in and account sessions in direct and Windows builds. We may receive account identifiers such as user ID, email address, first name, and last name.
- Direct-build license and purchase status: We store plan, entitlement, subscription, receipt, and purchase-status records from Polar and our backend so the app can unlock Pro features and manage direct-build billing.
- Support requests: If you contact support, we process the information you send us so we can investigate and respond.
- Opt-in crash diagnostics: If you enable crash reporting or explicitly send a crash report, Sentry may receive technical diagnostics such as stack traces, app version, OS version, runtime platform, and sanitized logs. We do not intentionally include file contents in crash reports.
- Website analytics: We use Cloudflare Web Analytics on rename.click to understand aggregate website traffic and performance. We also use Google Analytics 4 for website usage measurement and Google Ads conversion tracking for install-related button clicks, subject to your consent choices. This is website-only measurement and does not include app file contents or local app data.
5. Payments and Billing
Mac App Store purchases are billed by Apple through Apple In-App Purchase. Apple processes payment methods, taxes, invoices, receipts, refunds, and subscription management according to Apple's policies. RevenueCat receives App Store purchase and entitlement metadata so RenameClick can unlock Pro access and restore purchases, but RevenueCat does not process payment cards for RenameClick.
Direct-build subscriptions and purchases may be processed by Polar. Polar processes payment methods, tax, invoices, receipts, and billing portal access for direct macOS and Windows licenses. RenameClick receives only the purchase, subscription, and entitlement information needed to activate and manage your license.
6. Website Analytics, Ads Measurement, and Consent
We use Cloudflare Web Analytics for cookie-free website usage measurement. We also use Google Analytics 4 to understand page views and website usage, and Google Ads conversion tracking to measure clicks on the Download, Mac App Store, and Microsoft Store buttons.
We do not send file contents, local filenames, app workspace data, or local AI results through website analytics or ads measurement. Google tags are configured with Consent Mode. Before you make a choice, analytics and ads storage are denied by default. If you reject optional storage, Google tags may send limited cookieless measurement pings for modeling and diagnostics, but they should not write analytics or advertising cookies for RenameClick.
The consent banner lets you accept all optional measurement, reject optional measurement, or choose analytics and install measurement separately. You can reopen the banner from Cookie settings in the footer.
You can review provider privacy information here: Cloudflare Privacy Policy and Google Privacy Policy.
7. Third-Party Services
We use third-party services only for specific roles:
- Clerk: direct and Windows build authentication, account sessions, and user identifiers.
- Apple: Mac App Store billing, subscriptions, receipts, refunds, and purchase restoration.
- RevenueCat: Mac App Store purchase status, subscription and lifetime entitlement verification, restore purchases, and anonymous customer profiles for purchase support.
- Polar: direct-build billing, subscription management, receipts, and payment confirmations.
- Sentry: opt-in crash reporting and technical diagnostics.
- Cloudflare: website delivery, security, Turnstile abuse protection, and cookie-free Web Analytics for rename.click.
- Google: Google Analytics 4 website measurement, Google Ads conversion measurement, and Consent Mode processing.
- OpenAI, Google AI, and Alibaba Cloud: optional cloud AI processing in direct and Windows builds only when you configure and use those providers.
We do not permit these vendors to use your information for unrelated advertising or tracking purposes.
8. Storage and Security
Account, license, purchase entitlement, and support metadata is stored in systems with access limited to the people and services needed to operate RenameClick. Local app preferences, direct-build auth/session material, API keys, model files, preview caches, and workspace data are stored on your device according to the app's local storage behavior.
We retain account and license metadata while you have an active relationship with RenameClick, while it is needed for support or fraud prevention, or as required by law.
9. Your Choices
- Use the built-in local AI model, LM Studio, or Ollama if you want processing to stay local.
- Remove cloud provider API keys from Provider Settings if you do not want to use cloud AI.
- Disable crash reporting in the app settings if you prefer not to share diagnostics.
- Manage or cancel Apple subscriptions through your Apple ID subscription settings.
- Manage or cancel direct-build Polar subscriptions through the billing portal.
- Contact us via Troubleshooting & Support or email support@pithly.app for privacy questions, account deletion, or data deletion requests.
10. Local AI Model Transparency
RenameClick's built-in local inference uses an openly licensed model distributed through Hugging Face. After the one-time model download, the built-in model can analyze supported files without uploading content to RenameClick or a cloud AI provider.
Why local-only processing matters for regulated workflows
For users working with sensitive or regulated data, local-only mode helps confirm that:
- The model runs on the local device.
- No file contents are transmitted externally during local inference.
- The model binaries match a publicly auditable, open-source release.
This transparency can support internal security reviews and compliance assessments when RenameClick is configured for offline-only use.
Disclaimer: RenameClick does not claim HIPAA compliance and does not provide legal or regulatory guarantees. Compliance with HIPAA or other regulations depends on how the software is configured and used by the end user. We recommend consulting with your compliance officer or legal counsel for specific regulatory requirements.