YurAri LLC. (“we,” “us,” or “our”) explains below how the Hitomise app (“the App”) handles information.
1. Information handled by the App
Users can create and edit message card text, short labels, icons, colors, display order, and Widget Set names, layouts, and card assignments. The App stores these items, App settings, and information used to recover Widget configuration data on the device. Card text and other user-entered content may contain information about the user or another person. Please choose what you enter.
The “Write now” feature stores the text being entered as a draft on the device. When enabled, the App also stores up to five recent messages that were shown. This history setting is on by default. Search terms are used to filter cards stored on the device but are not saved as an App search history.
The App stores the Full version purchase status, the time it was checked, and the source store locally so that it can use the purchase status. Apple or Google handles account and transaction information needed for payment and purchases under its own terms and privacy information.
2. Storage and Widgets
Cards, Widget Sets, settings, drafts, and recent message history are stored in the App’s local data area. Some purchase status information is stored in the device’s local preferences. The App has no user account feature or synchronization server operated by us. The current App code contains no process that sends card text or short labels to a server operated by us.
The Home Screen Widget uses display information stored in an area shared between the App and its Widget on the device. This includes the Widget Set name, card association information, short labels, icons, and colors. The Widget snapshot is designed not to include the full card text. Short labels and other displayed information may be visible to anyone who can see the device’s Home Screen.
3. Network use, purchases, and third parties
Ordinary features such as creating, editing, searching, and showing cards and using “Write now” use data stored on the device. The current code contains no process that sends card text to a server operated by us, no account synchronization operated by us, and no operator-integrated advertising, behavioral analytics, or dedicated crash-reporting service. The App code also contains no process that writes message text, short labels, drafts, history, or search terms to App logs.
The App uses Apple App Store or Google Play purchase features to check product information, make Full version or supporter purchases, and restore purchases, and it communicates with the applicable store. The Android Google Play Billing Library includes Google’s logging transport. Billing events sent through this path may contain billing API results and timing, technical information about the App, Android/device and network, and a random value generated for a BillingClient instance. The public materials and network observation in this audit did not establish when or which events are actually sent, all event fields, or Google’s retention period. The App’s purchase calls do not pass card text, short labels, or Quick Text text. The App does not access payment card details; Google Play handles them directly. For the stores’ handling, see Apple’s App Store privacy information and Google’s Privacy Policy.
4. Permissions and file selection
The App code was not found to request access to the camera, microphone, location, contacts, or photo library for ordinary use. Saving or loading a backup uses the operating system’s file picker, which accesses the file and destination selected by the user. If the selected destination is provided by a cloud storage or other service, that provider’s terms and privacy information also apply to the file.
5. Backups and restore
An App-created “.hitomise” backup is a JSON file. It contains card text and labels, display settings, Widget Sets, App settings, and, when present, information used to recover invalid Widget configuration. It does not contain the “Write now” draft, recent message history, or the locally cached purchase status. The App does not apply its own encryption to backup files.
The user chooses where to save the backup in the operating system’s file picker. Restoring replaces the current cards, Widget Sets, and settings with the contents of the selected backup. Immediately before replacement, the App creates a recovery copy containing the pre-restore data in a private area of the App. The App has no screen for deleting this recovery copy on its own; a later restore replaces the same file.
When device operating system backup is enabled, the App’s data may be included according to the operating system’s behavior and settings. We do not control the destination, retention, or deletion of operating system backups. Copies in user-created files or operating system backups are not removed when data is edited or deleted inside the App.
6. Retention, deletion, and controls
Cards and Widget Sets remain in local storage until the user edits or deletes them in the App, or removes the App’s data from the device. Settings remain until changed. A “Write now” draft remains until changed or replaced with empty text using the clear action. Recent message history is limited to five items. Turning off history in Settings also deletes the saved history.
The locally cached purchase status remains while the App’s data remains on the device. Apple or Google determines the retention and deletion of purchase records and account information. The user manages manual backup files at the chosen destination. A pre-restore recovery copy may remain until it is replaced by a later restore or the App’s data is removed from the device. Manage copies in operating system backups through the device or backup service settings.
The App has no user account or card storage on a server operated by us. Cards and related items can be edited or deleted individually in the App. For privacy questions, contact us below.
7. Information security
The current implementation contains no App-specific encryption for the card database or manual backup files. Please use your device’s screen lock and operating system protections, and manage the security of backup destinations. Take particular care with short labels shown in Widgets and with where backup files are saved.
8. Changes to this policy
If the App’s features or information handling changes, we will update this policy on this page. The revised policy applies from the date it is posted.
