NameSense1. Scope
This policy applies to the Mac App Store build, the Direct build downloaded from namesense.app, and related support services. NameSense is operated by an independent developer. It explains how the operator and the service providers used for purchase, updates, and support handle information.
2. How NameSense handles information
Files you choose and local processing
When you explicitly choose files or folders through the macOS file picker or by dragging them into NameSense, the app accesses only what is needed to preview, extract content, apply naming rules, and rename the files. When you use local filename parts, that processing happens on your Mac and the file content is not uploaded to servers operated by the NameSense operator.
Optional AI features
If you actively run AI-assisted naming, NameSense shows a data-sharing disclosure and asks for consent before the first request for the relevant provider, endpoint, or filename-sharing scope. After consent, the file content required for that request is sent directly to the AI provider and endpoint you configured. The original filename is included only when you enable that option. The NameSense operator does not receive this content or use it for advertising or training. An AI provider may process or retain requests under its own terms and privacy policy; review those policies before use.
API keys, settings, and AI results
AI API keys you provide are stored in the macOS Keychain. Provider settings, endpoints, models, naming rules, consent records, and app settings are stored on your Mac. To avoid duplicate requests, NameSense may temporarily cache structured AI results locally; the cache expires automatically and is limited in size. NameSense does not sync this local data to servers operated by the NameSense operator.
NameSense Pro, pseudonymous purchase ID, and trial
NameSense does not require an account, email address, or password. To validate and restore Pro access, the app generates a random pseudonymous purchase ID on its first entitlement check, normally at app startup. It contains no name, email address, device serial number, advertising identifier, or file content, and is stored separately from API keys and trial records. When available, the app stores the ID in the synchronizable iCloud Keychain so the same user's Macs may recover the same RevenueCat customer. iCloud Keychain synchronization is an Apple-provided best-effort service, not a NameSense account or guaranteed backup.
The app sends this ID to RevenueCat as the App User ID, together with the purchase record, product, channel, status, and ordinary app/system request information (such as app version, system version, and IP address) needed to validate an entitlement. RevenueCat uses this information for purchase validation, restoration, redemption, fraud prevention, and operational purchase analytics. NameSense disables the RevenueCat SDK's automatic device-identifier collection. The ID is linked to the corresponding purchase profile, but NameSense does not use it for advertising, profiling, or cross-company tracking.
The Mac App Store build offers one-time purchase and restoration only through Apple StoreKit. It contains no Paddle checkout or external purchase link. Apple handles payment, taxes, refunds, and the original transaction record. A verified App Store purchase may be synchronized to RevenueCat and recognized by the Direct build. The Direct build is purchased through Paddle's web checkout and redeemed through RevenueCat. Paddle is the seller/merchant of record and handles payment methods, billing email, taxes, receipts, and refunds. A Paddle purchase unlocks only the Direct build. NameSense does not receive full card details, although the operator may receive limited transaction or buyer information from Paddle or RevenueCat for entitlement delivery, reconciliation, fraud prevention, and support.
The 14-day Pro trial is recorded locally, requires no payment, does not renew, and is not synchronized with the pseudonymous purchase ID.
Direct build updates
Only the Direct build uses Sparkle to check for and install signed updates. It checks automatically every 24 hours and also provides a manual check command. When an update is available, it prompts the user before installation and does not silently replace the app in the background. During a check, it requests an appcast or installer from NameSense's HTTPS update source. The server or host may process ordinary request data such as IP address, request time, app version, macOS version, and processor architecture for update delivery, security, and troubleshooting. The Mac App Store build is updated only by the App Store and does not contain Sparkle.
3. What we do not collect
- NameSense does not create or require an account and does not ask for your name, phone number, or precise location; Paddle may request billing information in the Direct checkout under its own policy.
- NameSense does not upload your files, folders, naming rules, or AI results to servers operated by the NameSense operator.
- NameSense does not use advertising, cross-app tracking, or advertising telemetry. RevenueCat processes only purchase functionality and related operational analytics; update-hosting logs are used only for delivery, security, and diagnostics.
- This website uses JavaScript for navigation and interactive features. It does not use cookies, advertising pixels, or site analytics. Language selection is reflected in the page URL.
4. When you contact us
If you contact us by email, we receive the email address, message, and diagnostic information you choose to send. We use it only to reply, handle support requests, and improve the product. Do not send API keys, passwords, or unnecessary file content. We do not use support messages for advertising.
5. Apple, RevenueCat, Paddle, Sparkle, AI providers, and hosting
NameSense uses Apple-provided macOS, App Sandbox, file-picker, iCloud Keychain, and StoreKit capabilities. Purchase entitlements are processed by RevenueCat; Direct web payments are processed by Paddle; Direct updates use the open-source Sparkle client and NameSense update hosting. AI requests are handled by the third-party provider you choose; a custom endpoint's operator may also process a request. Website and update hosts may process ordinary technical information, such as IP address and request time, for delivery, security, and diagnostics. Each service has its own terms and privacy policy.
6. Retention, deletion, and backups
Rules, caches, consent records, and other local data remain on your Mac until you delete, clear, or reset them in the app or remove the app container. Exported files, backups, and renamed files remain under your control. API keys and trial data are separate Keychain items and may remain after app deletion; delete them through the relevant NameSense settings where available or through macOS Keychain Access.
The pseudonymous purchase ID may survive reinstallation and appear on other devices through iCloud Keychain. Where the app provides a purchase-identity reset/delete control, you can use it to remove the local and synchronizable Keychain item. You may also email support@namesense.app to request de-linking or deletion of operator-controlled pseudonymous NameSense/RevenueCat purchase data or support correspondence. We will first confirm the scope; never send card details, API keys, or file content.
Deleting NameSense/RevenueCat data does not delete transactions held by Apple or Paddle. Apple, Paddle, or RevenueCat may retain records required for tax, accounting, refunds, fraud prevention, disputes, or legal obligations. Exercise independent privacy rights through the relevant provider. After the only pseudonymous link is deleted, Direct access may not be restorable without a valid receipt or redemption path.
7. Security
NameSense relies on macOS App Sandbox, user-selected file authorization, and Keychain protection. You are responsible for protecting your Mac, backups, API keys, and third-party AI service accounts. No local storage or network transmission method can guarantee absolute security.
8. Changes
If NameSense’s data practices change, we will update this page’s effective date and, where appropriate, update the in-app privacy notice and the privacy information in App Store Connect. Material changes will be explained where appropriate.
9. Contact
Questions about this policy, data deletion, or NameSense's privacy practices can be sent to support@namesense.app.