LUPERSON

Privacy

Privacy policy for ClipReplace.

Privacy Policy

  • Effective Date: May 7, 2026
  • Last Revised: May 7, 2026

Kazuo Ito (the "Provider") hereby establishes the following Privacy Policy (the "Policy") regarding the handling of user information in the macOS application "ClipReplace" (the "Application").

1. Information Collected or Handled

1-1. Profile and Settings Information

The Application stores the following information on the user's device.

  • Profile names
  • Keywords, replacement strings, input items, display order, and enabled/disabled states of replacement rules
  • Display language of the Application
  • Completion status of the initial onboarding
  • Consent status regarding the Privacy Policy and clipboard use
  • Notification settings
  • Crash report transmission setting
  • Shortcut settings
  • Minimum state information necessary to display billing status and operate the Application

This information is stored mainly in local storage on macOS (including Application Support and UserDefaults).

1-2. Secret Values

Secret values registered in the Application are stored in the macOS Keychain.
The Provider refers to such secret values within the Application only to the extent necessary for ordinary use of the Application.

1-3. Text on the Clipboard

The Application reads text on the clipboard only when the user explicitly executes replacement processing.
The Application does not continuously monitor the clipboard unless the user performs an execution operation.

Text read from the clipboard and the replacement result are, in principle, processed within the user's device.
If the replacement result includes secret values, the Application may apply additional protection to writing that result to the clipboard in order to enhance security. This may include writing that is valid only on that device and automatic deletion after approximately 90 seconds.

1-4. Import and Export Files

The Application may import and export JSON files selected by the user.
If Include Secrets is enabled at the time of export, secret values stored in the Keychain may be included in the output file in plain text.
Such files are saved to the location selected by the user, and subsequent management of them is the user's responsibility.

1-5. Crash Diagnostic Information

The Application sends crash diagnostic information using Google Firebase Crashlytics only when the user has explicitly enabled it.
If crash report transmission is disabled, no automatic transmission to Crashlytics is performed.

Information that may be subject to transmission includes the following.

  • Crash logs
  • Stack traces
  • Device information
  • OS version
  • Application version
  • Diagnostic information to the extent necessary for failure analysis
  • Custom keys set by the Application

Information that the Application sends to Crashlytics as custom keys mainly consists of the following application state information.

  • Display language
  • State of the current screen and settings
  • Onboarding state
  • Clipboard consent state
  • State of notification settings and crash report settings
  • Billing status
  • Number of profiles and number of enabled rules
  • Whether there are unsaved changes
  • Summary of the result of the most recent replacement execution

The Application does not send, as custom keys to Crashlytics, user ID, Analytics data, profile names, profile contents, clipboard contents, or secret values.

Unsent reports generated while crash report transmission is disabled may be temporarily stored on the device.
If the user later enables transmission, they will be sent, and if the Application is restarted while transmission remains disabled, they will be deleted.

2. Purposes of Use of Information

The Provider uses information handled by the Application for the following purposes.

  • Providing the replacement function
  • Saving and restoring profiles, settings, and secret values
  • Providing import and export functions
  • Applying settings such as shortcuts, notifications, and display language
  • Providing the non-consumable In-App Purchase and reflecting entitlement status
  • Investigating defects, improving stability, and responding to failures
  • Responding to user support

3. External Transmission and Third-Party Services

3-1. Google Firebase Crashlytics

The Application uses Google Firebase Crashlytics only when the user has enabled crash report transmission.
In that case, crash diagnostic information may be sent to Google.

Firebase Crashlytics: https://firebase.google.com/docs/crashlytics/ios/customize-crash-reports

3-2. Apple's Billing Infrastructure

The non-consumable In-App Purchase of the Application is provided through Apple's App Store billing infrastructure.
Purchases, billing, refunds, and other settlement-related information are processed in accordance with conditions established by Apple.
The Provider does not obtain Apple's payment information in its entirety.

4. Storage Location and Retention Period of Information

Profiles and various settings of the Application are stored mainly on the user's device.
Secret values are stored in the Keychain.
Such information may be retained until the user deletes it in the Application or deletes the Application and related data.

JSON files exported by the user are stored in the storage location selected by the user.
The Provider does not manage that storage location.

5. User Choices and Management

Users may manage the following by themselves.

  • Adding, editing, and deleting profiles, rules, input values, and secret values
  • Exporting with Include Secrets enabled or disabled
  • Enabling or disabling crash report transmission
  • Uninstalling the Application

6. Minors

If a minor uses the Application, please do so after obtaining the consent of a parent or guardian or other legal representative as necessary.

7. Changes to This Policy

The Provider may change this Policy as necessary.
The revised Policy shall become effective at the time it is published by a method the Provider deems appropriate or on a separately specified effective date.

8. Contact

Contact information for inquiries regarding this Policy is as follows.

Related Document: Terms of Use