Consignment Note Privacy Policy

01

Introduction

Hiro App Works (hereinafter “we”) provides the iOS app “Consignment Note” (hereinafter “the App”). This policy explains how user information is handled in the App based on its current implementation.

The App is used to manage consignment-sale products, inventory, sales, and settlements on an iPhone. Account registration and login are not required, and the App has no screens for entering a name, address, telephone number, email address, or similar information in order to use it. However, users may voluntarily enter text such as product names, notes, and sales location names.

02

Information handled in the app

Business data entered or created in the App is stored, in principle, in the App’s database (SQLite) and storage. The main contents are as follows.

• Product information: Product name, optional management number / product number, sale price, initial at-home inventory, notes, registration date and time, discontinued status, and information about where product photos are stored
• Sales location information: Sales location name, fee method, rate, and amount, notes, and location-use end status
• Inventory and sales history: Details of deliveries, items brought home, sales, inventory adjustments, and cancellations; quantities, record dates, snapshots of prices at the time of sale, and notes
• Settlement information: Applicable period, sales, fees, transfer fees, expected deposit amount, actual deposit amount, difference, settlement status, and itemized details by product
• Settings and operation history: Settings for automatic suggestions and recording methods, and operation history relating to products, sales locations, and settlements

03

Information sent to external services

The App does not have a dedicated server or general cloud synchronization. However, when API keys are enabled in the distribution settings, the App uses the following external services. Information sent to external services is limited to the extent necessary to provide each service.

04

In-app purchases

The App’s Pro features are based on non-consumable in-app purchases through the iOS App Store. Apple processes the payment, and RevenueCat assists with checking the purchase status and Pro entitlements in the App. The App does not have a process for obtaining or storing payment-method information such as credit card numbers entered on Apple’s payment screen.

The App does not save purchase status, the RevenueCat customer ID, or analytics event history in the App’s SQLite data or manual backups. If a purchase or restore fails or is cancelled, the App does not treat it as successful.

05

Analytics information

The “Analytics” screen in the App aggregates sales history saved on the user’s device and displays the results within the App. The business data itself shown on this screen, such as sales, number of items sold, sales rate, expected proceeds, and rankings, is not sent to PostHog.

As described in the preceding section, the App sends fixed events and limited categorical values to PostHog to aggregate whether features were used and the status of purchase flows. Even when PostHog is unavailable, product saving, inventory, sales, settlement, and purchase processing continue, and errors from the analytics SDK do not propagate to the App’s save processing.

06

Product photos

To register a product photo, users select one from the photo library or take a photo with the camera. The selected or captured image is converted to JPEG in the App, saved in the App’s Documents area with the long side limited to a maximum of 1,200 pixels and with a configured compression quality, and only information about its storage location within the App is recorded in SQLite, not the image itself.

The App is not implemented to send product photos to RevenueCat or PostHog, or to upload them to our servers. When a photo is deleted from the App, the photo file managed by the App is also deleted. However, copies of photos that users have saved elsewhere through backup or sharing may remain at those destinations.

07

CSV files

For bulk product registration, the App reads a CSV file selected by the user in the iOS file picker. It supports UTF-8, including files with a BOM, and does not read files larger than 10 MiB. The CSV contents are parsed and checked within the App. If the user confirms registration, product information and initial at-home inventory are saved to SQLite. The App does not upload the CSV to an external server dedicated to CSV files or save it in a CSV-specific table.

The App deletes the temporary Cache copy created when the file is selected after the reading process is complete. When exporting a CSV template, the App opens the iOS share sheet and passes the file to the destination selected by the user. The handling of destinations selected by the user, such as Files and iCloud Drive, follows the settings and policies of those services.

08

Backup and restore

Backups in the App are not automatic; they are a manual feature that the user explicitly runs from the settings screen. A backup contains a JSON file combining the SQLite data covered by the feature, including products, sales locations, inventory history, sales history, settlements, settings, and operation history, with product photos in JPEG Base64 format.

The created JSON file is temporarily placed in the App’s Cache and then passed through the iOS share sheet to a destination selected by the user. The App does not automatically upload it to our servers, iCloud, or any other cloud service. If the user selects Files, iCloud Drive, email, or another sharing destination, the file is passed to that service at that time.

During restore, the App validates the JSON file selected by the user and, after explicit confirmation, replaces the existing data and photos in the App. Purchase status and Product Analytics status are not included in backups. Because backups saved at a sharing destination are not subject to deletion by the App, users should delete them from the destination themselves when they are no longer needed.

09

Provision to third parties

We have not built a feature into the App to provide users’ business data to third parties for advertising or sales purposes. The App also has no feature for collecting or selling account information as a list.

However, information necessary for their respective purposes is passed to RevenueCat for purchase management, PostHog for usage analytics, the App Store for payment and purchase processing, and destinations selected by the user through sharing. This is done within the scope described in “Information sent to external services,” and the terms and privacy policies of each service apply. Except where required by law or in similar cases, we do not independently provide information to third parties beyond the above.

10

Data management

The App’s business data is stored on the device, and there is no mechanism for us to directly view it during ordinary use of the App. The App has no account-based cloud synchronization or feature for automatically requesting that we delete data.

Products, sales locations, and transactions with history are not physically deleted through ordinary operations in order to maintain the consistency of that history; instead, they are managed using statuses such as discontinued, no longer in use, or cancelled. Product photos can be deleted from the product-editing screen. When the App is deleted from a device, data in the App’s storage is handled according to iOS app deletion, but backups and CSV files that users have exported to Files or elsewhere must be deleted separately.

The retention period and deletion methods for information handled by RevenueCat and PostHog follow the policies of those services. For questions about external services or this policy, please contact us at the address below.

11

Changes to this Privacy Policy

We may revise this policy in response to changes in the App’s features, the external services it uses, applicable laws, or operations. If there are important changes, we will notify users in a way that can be recognized on this page or in the App. The revised policy applies from the time it is posted on this page.

12

Contact

When contacting us, please avoid including more personal information or business data than necessary, such as product names or the contents of backups, in your email.