NameSense1. Scope
This policy applies to NameSense for Mac distributed through the Mac App Store or namesense.app, this website, 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 and pseudonymous purchase ID
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. 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.
In the Mac App Store edition, Pro is an optional non-consumable in-app purchase processed by Apple StoreKit. Apple handles payment details; NameSense does not receive your full card or bank details. The app uses verified Apple transactions to unlock Pro and provides Restore Purchases in Settings. Purchase records and the pseudonymous User ID are synchronized with RevenueCat for entitlement validation and related operational analytics. App Store purchases may also be recognized by the separate Direct edition; Updated editions that support Waffo can recognize valid Waffo Pro access under the same Purchase ID in both distributions; older versions may not support this. Orders, payments, and refunds remain with their original channel.
An updated Direct edition that supports Waffo opens checkout from the app and links the pseudonymous Purchase ID to the order. Waffo hosts checkout and processes the email, billing, payment-instrument, and tax information needed for payment. The NameSense backend on Cloudflare Workers creates orders, verifies payment and refund notifications, and updates Pro access through RevenueCat. Its ledger stores the Purchase ID, order/payment/refund references, amounts, currency, and processing state, but not the payment email or full payment-instrument details; webhook processing may receive additional order information supplied by the provider. Cloudflare may process IP addresses and request times for network delivery, security, and diagnostics. This flow receives no file content or AI API keys. Older email-arranged orders continue under the conditions confirmed at purchase; never email full card numbers or bank login credentials.
Direct build updates
Only the Direct edition uses Sparkle to check for and install signed updates. The Mac App Store edition receives updates through Apple and contains no Sparkle updater. 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.
3. What we do not collect
- The app does not create or require a NameSense account or ask for your name, phone number, or precise location; a bank or payment service used for a Direct transfer may process payer information 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 interactions; language selection is reflected in the URL. It also uses Cloudflare Web Analytics for aggregate, cookieless measurement that does not identify visitors across sites. Optional analytics follows the visitor’s region: in the EEA, the United Kingdom and Switzerland, Google Analytics loads only when you explicitly allow it; elsewhere the same scope is on by default and can be turned off under Privacy settings in the footer. While it is off, no website analytics data is sent to Google.
Optional website analytics
Where prior consent is required, Google Analytics processes public page paths, language, limited button placements, example actions and campaign labels only after you allow it; elsewhere the same scope is on by default and can be declined at any time under Privacy settings in the footer. We do not send file contents, filenames, clipboard contents, email messages, API keys or arbitrary full query strings. Download clicks do not prove installation; contact actions do not prove email delivery.
Cloudflare Web Analytics uses no cookie or local storage identifier and reports only aggregate pages, referring countries and page performance. It runs in every region and does not depend on the analytics switch above, but a Global Privacy Control signal turns it off.
Website analytics is not linked to app first use, renaming or purchase outcomes. Operational app analytics and source linking have been retired; updated editions no longer provide this analytics switch. We send no app usage, activation, purchase or refund attribution events to Google. Purchase verification, refunds and Pro access continue as described above. We do not enable advertising personalization, Google Signals or cross-company advertising tracking.
Website choices and analytics cookies last up to 180 days. Campaign labels remain in the current tab and expire after 30 minutes of inactivity. Decline through footer Privacy settings to immediately stop website analytics and clear controlled cookies and campaign data. We never replay pre-consent activity; withdrawal does not automatically delete data already received by Google. Withdrawal receipts saved in the browser by the former source-linking flow are used only to unlink old associations, retained for at most 60 days and deleted after successful withdrawal. They do not create new app analytics associations. Google handles received data under its Privacy Policy. Declining or withdrawing does not affect downloading, renaming, purchases or Pro entitlements.
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, banking or payment services, Sparkle, AI providers, and hosting
NameSense uses Apple-provided macOS, App Sandbox, file-picker, and iCloud Keychain capabilities. Mac App Store purchases and restoration are handled by Apple StoreKit under Apple’s privacy policy. Purchase entitlements are processed by RevenueCat; web payments in updated Direct editions are handled by Waffo with a backend on Cloudflare; historical manual payments remain with the original seller and its bank or payment service; 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 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 Apple purchase records or transaction and accounting records that the receiving bank, payment service, or operator must retain by law. App Store users can restore an eligible Apple purchase through Restore Purchases; requests concerning Apple-held personal data can be made through Apple’s privacy portal. These parties may retain necessary records for tax, accounting, refunds, fraud prevention, disputes, or other legal duties. Exercise independent privacy rights through the relevant provider. If the only pseudonymous link is deleted, Direct access may require manual verification of the original payment record before restoration.
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. 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.