←  Home 日本語

Privacy Policy

Software: Mimicry (macOS) · Last updated: 2026-07-09

This privacy policy explains how Mimicry (the "Software") handles user information. The Software is an HTTP/HTTPS proxy tool for iOS/Android app developers, used to locally intercept and mock the traffic between simulators, emulators, and real devices that the developer manages, all on the developer's own Mac. The Software is developed and distributed by Kusumoto Masahiro (the "Developer").

1. Personal information we collect

The Software itself does not collect, store, or transmit any personal information about the user. It contains no analytics SDKs, advertising SDKs, crash reporters, or other third-party trackers. However, only when you use the cloud publish feature (see "3. About the cloud publish feature"; a free tier is available), some information is sent externally for publish configuration, license verification, and payment processing. See "3. About the cloud publish feature" and "4. License verification and payments" for details.

2. Handling of traffic logs and recording data

Regarding traffic interception and mocking—the core features of the Software—captured data is handled as follows.

  • Traffic logs are held only in the app's memory, up to a fixed number of entries, and are never transmitted externally. They are cleared when the app quits and are not persisted to disk.
  • Files saved by the recording feature (Time Travel mock) are stored only in the app's dedicated folder on the user's own Mac. They are never uploaded to the Developer's or any third party's servers.
  • User data such as mock rules and project settings is likewise stored only on the user's own Mac. The exception is when you choose to publish via the cloud publish feature described in the next section.

3. About the cloud publish feature

The Software includes a feature (the cloud publish feature) that temporarily publishes mock rules to the internet so they can be accessed directly from real devices outside your LAN, external beta testers, CI environments, and so on. It can be used as a free tier without a license key; adding a license key enables more concurrent publishes, longer publish durations, and the use of custom domains (see the cloud publish page for details). Only when the user explicitly chooses to use this feature is the following information sent to and stored on servers operated by the Developer on Cloudflare.

  • The mock rules of the project selected for publishing (URL patterns, response contents, etc.)
  • Project name and project ID
  • The list of IP addresses allowed to access it (if configured)
  • The custom domain name used for the publish URL (if configured)
  • An instanceId that identifies the device. If a license key is registered, the license key is also sent (it is not sent when using the free tier).

Published mock rules become accessible to any third party who knows the issued publish URL (which contains a hard-to-guess token). Publishing can be stopped (disabled) at any time by the user; even if not stopped manually, it expires automatically after 24 hours on the free tier, or after 7 days when a license key is registered. Unless you use this feature, mock rules are never sent outside the Software.

4. License verification and payments

The cloud publish feature can be used on the free tier, but a license key is required to expand the number of concurrent publishes and the publish duration. Purchasing and paying for a license key takes place on a checkout screen provided by the payment processor Polar (Polar Software Inc.), and payment information such as credit card details and email address is handled by Polar. The Developer does not directly obtain or store this payment information. To verify the validity of a license key, the Software sends the license key and the instanceId to servers operated by the Developer on Cloudflare. This information is used solely for license management purposes.

5. Scope of traffic interception

The Software intercepts only the traffic between the iOS simulators, Android emulators, real devices, and browsers that the user manages, and the external API servers they communicate with. It provides no feature to intercept third parties' traffic or to relay traffic between third parties. The proxy runs locally on the user's own Mac and targets only communication with the user's own development devices.

6. Automatic update feature

To check for new versions, the Software periodically sends HTTP requests to GitHub Releases (kusumotoa/mimicry-releases). These requests do not contain any information that identifies the user.

7. About the local REST API

For CLI integration, the Software provides a REST API bound only to 127.0.0.1 (the loopback address). It cannot be accessed from external networks, and validation of the Host/Origin headers also rejects calls from anywhere other than the local machine.

8. About certificate installation

To inspect HTTPS traffic, and only when the user explicitly allows it, the Software installs a certificate into the trusted root certificate store of the user's own simulator or real device. This certificate does not affect any device other than the development device that the Software is analyzing.

9. Provision to third parties

Because the Software itself does not collect the user's personal information or traffic data, no provision to third parties occurs in normal use. However, only when you use the cloud publish feature, some information is processed through the payment processor Polar and the infrastructure of Cloudflare, Inc., as described in "3. About the cloud publish feature" and "4. License verification and payments".

10. Cookies and tracking technologies

The Software is a native macOS app and does not use cookies or other tracking technologies. For the payment checkout screen of the cloud publish feature (provided by Polar), Polar's own privacy policy applies.

11. Disclaimer

The Software itself is provided free of charge on an as-is basis. For the cloud publish feature as well (both the free tier and license-key expansions), the Developer does not warrant its operation and is not liable for any damages arising from use of the Software. Use against production environments or traffic containing confidential information is not recommended.

12. Changes to this policy

If this privacy policy is changed, the updated version will be posted on this page and the last-updated date will be revised.

13. Contact

For inquiries about this privacy policy, please contact us at the following.