1. Data processed by the product
Input Method Manager reads the current macOS input source name and system identifier to show status and enforce a lock the user chooses to enable. When the user enables Follow Apps, the app also reads the active application name and application identifier locally to match user-created app rules and select the target input source. It does not monitor keystrokes, read typed content, or read content inside the active application.
The app first checks locally whether Squirrel is installed; this check does not require configuration-folder access. Only when a feature needs to read or modify Squirrel configuration, and after folder authorization, does the app read the fixed configuration folder, configuration files, build results, and deployment diagnostics. This data is processed locally.
2. Feedback and in-app notifications
Email addresses, feedback text, and optional screenshots are sent to admin.squirrelset.com only when a user voluntarily submits feedback. A submission also sends the app version and a random installation identifier. A user may attach up to three screenshots totaling no more than 5 MB. The identifier is generated by the app and stored in the local Keychain to deliver a resolution notice to the same installation. It is not a hardware identifier and is not used for cross-app tracking. Optional screenshots are re-encoded on the server to remove removable image metadata.
Feedback notifications work differently across versions. Older versions without a feedback-notification on/off control register a random installation identifier and app version with the feedback service and check for replies when the app starts or the notifications view opens. This happens independently of the basic usage analytics choice. In versions with that control, simply opening the tool does not create or register a feedback identity for a new user; a successful feedback submission enables notifications. While enabled, opening the tool or its notifications view uses the existing random identifier and authentication secret to check for replies, without registering the installation again. Users can turn notifications off in that view; requests already sent cannot be recalled. After upgrading from an older version to one with that control, users must explicitly enable notifications to continue viewing earlier replies. Existing identities and ticket associations are preserved. Feedback notifications are independent of optional usage analytics.
The website “Send feedback” form sends the email address and feedback text entered by the visitor to the same support console for a reply and resolution. Website feedback does not request or receive an app installation identifier, so it cannot receive in-app notifications.
Feedback data is used to investigate an issue and reply; app feedback can also be used to send a related in-app notice. App and website feedback tickets, plus optional screenshots, are retained for 180 days by default and then removed. Notices are retained until their purpose ends or the user requests deletion.
2.1. Optional basic usage analytics
Share Basic Usage Information is off by default. Only after a user turns it on in Privacy & Scope can a build configured for production use the AppAdmin analytics component to send this app’s launch and foreground active-session records to api.appadmin.cc. Records include timestamps, session IDs, a random installation ID, app and analytics component versions, macOS version, the desktop device category, and counts or status showing discarded cached records and incomplete record history. The installation ID is separate from the feedback-notification ID. It is not a computer serial number or hardware identifier and is not used for cross-app tracking.
A foreground active session only describes periods when this tool is the active app. It does not measure time spent using an input method or typing. Running in the background, automatically switching input sources, or showing the floating toolbar does not by itself count as foreground usage. This macOS integration does not include crash, performance, or hang reports. It does not send typed content, document text, configuration, dictionaries, or information about other apps.
Without a connection, pending records may be stored on this Mac and sent when a connection returns. Users can turn this option off at any time. Turning it off stops collection and clears unsent records; requests already sent cannot be recalled. Input source management, Squirrel configuration, and feedback continue to work. Development, automated-test, and internal acceptance builds do not send data to the production analytics project.
2.2. App updates
In versions that provide update checks, the app periodically checks Apple’s public store lookup service at itunes.apple.com for a new version when the app starts or returns to the foreground. Users can also check manually. The check uses this app’s store ID and store region; it does not send typed content, configuration, feedback records, or the feedback identity. A failed check does not affect normal use. When an update is available, users can visit the App Store themselves; the app does not download or install updates automatically.
3. Data we do not collect
We do not upload typed input, active app names or identifiers, personal dictionaries, Squirrel configuration files, app rules, backup files, or deployment diagnostics. The feedback feature does not automatically attach any of that content. We do not include advertising or cross-app tracking. Basic usage analytics follows the opt-in and withdrawal rules in section 2.1.
4. Local storage
The basic usage analytics choice, its separate random installation ID and unsent records, plus language preferences, the input source automation mode, the lock target, app names and identifiers plus target input sources in app rules, the Squirrel folder security bookmark, configuration backups, deployment diagnostics, and the random feedback-notification identity may be stored locally. Users can stop automatic switching, remove app rules, or manage related data through the product interface. Removing the Keychain item or resetting the system may change the feedback identity.
This website stores only a language explicitly selected by the visitor and a dismissed language suggestion in the current browser. These preferences keep the selected language and prevent repeated prompts. They are not uploaded or used to identify the visitor, and clearing website data removes them.
5. Website data
This website is hosted by infrastructure providers. To maintain security and availability, servers and the CDN may process access IP addresses, request times, browser types, and error logs according to standard industry practice. We do not use these logs to create personal profiles or sell personal information.
6. Children’s privacy
Input Method Manager is a general-purpose input method management and configuration utility. It is not directed specifically to children and does not intentionally collect children’s personal information.
7. Policy changes
If the product adds network features or begins processing new categories of data, we will update this policy before enabling those features and explain the changes where appropriate.
8. Contact and privacy requests
For questions about this policy, local data, feedback, or website-log processing, email [email protected]. To request deletion of feedback data, provide the email address used for the feedback and an approximate submission date. We cannot access, export, or delete configuration, dictionaries, or typed content that a user has not voluntarily submitted; users can delete local content through the product interface or macOS file-management tools.