Privacy Policy

This English translation is provided for convenience. If there is any discrepancy, the Japanese version prevails. Japanese version: プライバシーポリシー

Handling of Photos (Key Points)

Registered photos of people, clothing images and generated results are stored only on your device.
Images are sent only when you execute a generation, via our server (Google Cloud Platform), to generative AI (the OpenAI API provided by OpenAI, or, as a backup, the Gemini API provided by Google LLC). Images are sent to OpenAI only if, in addition, you have given consent on a confirmation screen shown once in the App before first use (see Section 3 for details of the destinations).
Images sent are processed in memory on our server and then discarded immediately; they are not stored. They are not recorded in our database either.
When you execute a generation, you are treated as having consented to this sending (generation is not possible without sending).
We do not obtain your name or email address. Even if you optionally use “Sign in with Google” in the Android version, we use only the account identifier among the information received from Google, and we neither use nor store your name or email address (Section 2).
We do not engage in any ad delivery or behavioral tracking.
In the Android version, we use Google components (ML Kit and MediaPipe) to check the person in photos and the category of clothing on your device. Images are not sent off the device for this, but these components may send performance metrics to Google (Section 3-8).

* Because images are sent to Google or OpenAI at the time of generation, we do not claim that “images never leave your device.” We describe the actual behavior accurately.

The TryOn Operations Team (“we”, “us” or “our”) establishes this Privacy Policy (the “Policy”) as set out below with respect to the handling of personal information and user information in the application “TryOn” (the version for iPhone distributed on the App Store (the “iOS version”) and the version for Android distributed on Google Play (the “Android version”); collectively, the “App”).

Unless “iOS version” or “Android version” is specified, this Policy applies to both. References to versions (such as “version 2.2 and later”) refer to versions of the iOS version. The Android version has been available since version 2.4.0, and statements about “version 2.4 or later” apply to it.

1. Business Information

Business name: TryOn Operations Team
Contact for personal information protection: kaiseiota0620@gmail.com

2. Information We Obtain

The information we obtain is as follows.

Type of information	Details	How obtained
Account identifier	If you use the App without signing in: an identifier that our server calculates from an identification code the App creates on your device (the code itself is not stored; see Section 3-9 for how the code is handled). If you optionally sign in through Sign in with Apple in the iOS version: a user identifier specific to the App, issued by Apple. If you optionally sign in through “Sign in with Google” in the Android version: the account identifier issued by Google (the “sub” contained in the Google ID token). The ID token may contain your name and email address, but we handle the ID token only in memory while verifying it to authenticate you, and do not use anything other than the identifier, nor store it or write it to logs. In every case, we do not store your name or email address. An Apple account and a Google account are treated as separate accounts.	Created on the device when you start using the App / provided by Apple (iOS version) or Google (Android version) when you sign in
Credit and plan information	Number of remaining credits, subscribed plan, plan expiration date, whether free credits have been granted, and creation and update dates and times	Recorded in the course of using the Service
Generation request records	Request ID, number of credits consumed, processing status (success / failure and refunded), type of failure, and date and time. These records do not include the images themselves or any features derived from the images.	Recorded when a generation is executed
Purchase information	iOS version: Transaction ID issued by Apple (including the original transaction ID of a subscription, used when you restore purchases to confirm which account the plan belongs to), purchased product ID, number of credits granted, and date and time. Android version: the purchase token and order number issued by Google Play, purchased product ID (subscription ID or product ID), number of credits granted, and date and time. The purchase token is used to verify and acknowledge the purchase, to process notifications such as subscription renewals, cancellations and refunds, and, when you restore purchases, to confirm which account the plan belongs to. Purchases are acknowledged by our server. In both cases, to confirm which account a purchase belongs to, a per-account code (a value that does not include your name or similar information) is passed to the App Store or Google Play at the time of purchase. Payment information such as credit card numbers is not passed to us.	At the time of purchase through the App Store or Google Play (for the Android version, subscription renewals, cancellations, refunds and the like are also received through notifications from Google Play)
Pro plan usage	Monthly number of generations and amount of use (version 2.3 or later; Pro plan subscribers only). This is recorded in association with an irreversibly converted value, not the account identifier itself. In addition, the amount of use on the current day (Japan time) is recorded in the account to apply the limit.	Recorded when a generation is performed
Image data	Photos of people and clothing images (described in detail in Section 3)	Received temporarily, only when a generation is executed
Body information and garment measurements (optional)	Only if you use the size check (version 2.4 or later): the height, weight, usual clothing size and body measurements (shoulder width, bust, waist, hips, inseam) you enter, and the garment sizes and measurements (described in Section 3-5). Entering them is optional.	Received temporarily, only when a generation or Fit Report using the size check is executed (stored on your device)
Style Profile photos and results (optional)	Only if you use the personal color, body type or measurement analysis (version 2.4 or later): the photos you choose (a face photo or full-body photos), your answers to the body type questions, your height, and the results (described in Section 3-7). The analysis is optional.	Received temporarily, only when an analysis is executed (results are stored on your device)
Server access logs	Records of the App’s connections to our server (IP address, User-Agent, date and time, etc.). These are used only to operate the server and prevent abuse, and are not used to estimate your location or identify you.	Recorded automatically by our server (Google Cloud) during communication (automatically deleted after 30 days)

3. Handling of Image Data

Because it relates to the core function of the App, we explain the handling of images separately.

3-1. Storage on Your Device

The photos of people you register, the clothing images you import, the generated try-on images and Fit Report images are stored only on your device, in an area dedicated to the App, and are not stored on our server. They cannot be accessed by other apps.

iOS version: they are protected so that they cannot be read while the device is locked, and are excluded from iCloud backup.
Android version: they are excluded from Android cloud backup and from device-to-device data transfer (such as copying when you change devices).

3-2. Sending to Our Server and to the Gemini API

Only when you execute a try-on generation are your photos of people and clothing images sent to our server (Google Cloud Platform, region in Japan). For Standard quality in version 2.1 and earlier of the App, and in version 2.2 and later when the OpenAI API is temporarily unavailable, they are sent from there to “Gemini API”, a generative AI service provided by Google LLC (for other destinations, see Section 3-2-2). Executing a generation presupposes consent to this sending. Generation cannot be performed without sending.

Google LLC handles the data as follows.

We use the paid API, and under Google’s terms, the images sent are not used to train Google’s AI models.
However, Google may temporarily retain data sent to the API for the period specified in its policies, for purposes such as abuse monitoring.
Processing by Google may take place on servers outside Japan (such as in the United States).
For details, please see the Gemini API Terms of Service and the Google Privacy Policy.

3-2-2. Sending to the OpenAI API

In the following cases, your photos of people and clothing images are sent via our server to the “OpenAI API” provided by OpenAI (the image generation model GPT Image and the image-reading model GPT). Images are sent to the OpenAI API only if, in addition to the consent given by executing a generation (Section 3-2), you have reviewed the destination and given consent on a confirmation screen shown once in the App before first use.

When generating try-on images in version 2.2 and later of the App (all generations)
When generating with “High Quality” selected in version 2.1 of the App
When creating a Fit Report (似合う診断レポート; version 2.2 and later). For the diagnosis, in addition to Registered Photos, try-on images and images of the clothing tried on, images of clothing saved in your wardrobe (up to 12 items) are also sent

In version 2.2 and later, when the OpenAI API is temporarily unavailable, generation may be performed as a backup using the Gemini API described in Section 3-2.

Under OpenAI’s terms, data sent to the API is not used to train OpenAI’s models.
However, OpenAI may retain data sent to the API for up to 30 days for abuse monitoring.
Processing by OpenAI takes place on servers outside Japan (such as in the United States).
For details, please see the OpenAI Services Agreement and the OpenAI Privacy Policy.

3-3. Disposal of Images Sent

Our server only processes the images it receives in memory and does not write them to disk or to any storage service. Images are discarded immediately after processing is completed. Only the metadata described in Section 2 is recorded in our database. Neither image data nor any part of it is output to logs.

3-4. How to Delete

Images on your device are deleted when you retake or delete photos in the App, or when you uninstall the App. Because no images are stored on our server, there is no need to request deletion of images on the server side.

3-5. Body Information and Garment Measurements (Size Check, Optional)

If you use the size check (version 2.4 or later), the height, weight, usual clothing size and body measurements you enter are stored only on your device (in the Keychain in the iOS version, and in an area dedicated to the App encrypted with an Android Keystore key in the Android version) and are not synchronized to other devices. Garment sizes and measurements are stored on your device together with try-on results and your clothes.
They are sent to our server, together with the images, only when you run a generation or Fit Report that uses the size check. Our server uses them only to calculate the size check, neither stores them nor writes them to logs, and discards them as soon as processing is complete.
To the contractors that generate images and diagnoses (Sections 3-2 and 3-2-2), we send only the visual description calculated on our server (for example, "the hem falls around the knee") and the height and size labels, as text. Your weight and body measurements themselves are not sent to these contractors.
You can delete the body information you entered at any time from My Studio in the App. It is also deleted when you delete your account. All other features of the Service are available without entering it.

3-6. Closet Item Details and Reading Shared Product Pages

The details you record for items in your Closet (name, brand, price, store, product page URL, size, color, material, season, purchase date, notes and status; version 2.4 or later; entering them is optional) are stored only on your device and are not sent to our server.
When you share a page, such as an online store's product page, to the App, the product information published on that page (product name, brand, price, currency, site name, color and material) is read on your device and filled into the details automatically. To fill in items that could not be read, the App may access the shared page directly from your device. Neither the content nor the URL of the page is sent to our server.
You can also choose not to save a shared item to your Closet. In that case, the item's image and details are deleted from your device after the try-on. Items and details you save can be deleted from your Closet at any time.

3-7. Style Profile Analysis (Personal Color, Body Type, Measurements; Optional)

Only when you run a personal color, body type or measurement analysis (version 2.4 or later; 1 credit each), the photos you choose, your answers to the body type questions (choices only) and your height are sent via our server to the analysis provider (OpenAI; Section 3-2-2). Our server neither stores nor logs the photos, answers or results, and discards them immediately after the analysis.
The results (your best colors, body type, estimated body measurements, etc.) are stored only on your device (as in Section 3-5, in the Keychain in the iOS version and in an area encrypted with an Android Keystore key in the Android version) and are not synchronized to other devices. To show which photo each result is based on, a reduced copy of the photos used for the analysis is also stored only on your device (in the same area as Section 3-1). This copy is deleted when you run the analysis again or delete the result.
When you run a Fit Report, a summary of the saved results (your personal color type and the names of your best and difficult colors, your body type and its flattering and unflattering shapes, and the name of your body shape) is sent as text via our server to the provider for scoring and comments. The estimated body measurement values are not sent.
The estimated body measurements are added to the body information for the size check (Section 3-5) only if you choose to. Values you have already entered do not change unless you choose to replace them.
You can delete the results at any time from "Style Profile" in the App. They are also deleted when you delete your account. All other features of the Service are available without the analysis.
The analysis is an AI estimate and is not a substitute for a professional consultation.

3-8. On-Device Image Checks (Android Version)

The Android version uses components provided by Google LLC that run on your device. It uses ML Kit to estimate the category of clothing (tops, shoes, etc.) from shared clothing images, and MediaPipe to check, for example, that only one person appears in a photo you register.
These checks are performed only on your device, and images are not sent off the device for them. (Images are sent at the time of generation as described in Sections 3-2 and 3-2-2.)
However, these components may send Google metrics for measuring their performance and usage (such as processing time, device model, OS version, App version, error types and a per-installation identifier). These do not include the photos themselves. We do not receive these metrics. Their handling by Google is governed by the ML Kit data disclosure and the Google Privacy Policy.

3-9. Storage of the Identification Code (Google Block Store)

The identification code used to let you use the App without signing in (Section 2) is created by the App on your device and stored only on your device. In the iOS version it is stored in the device’s Keychain and is not synchronized to other devices. In the Android version it is encrypted with an Android Keystore key and stored in an area dedicated to the App.
In the Android version, so that you can continue with the same account after deleting and reinstalling the App, a copy of this code is kept in Block Store, part of Google Play services. The copy is stored only on that device and is not sent to cloud backup. On devices where Google Play services are unavailable, the copy cannot be kept, and reinstalling creates a new account.
When you delete your account, both the code on the device and the copy in Block Store are deleted.

4. Purposes of Use

We use the information we obtain only for the following purposes:

To provide the Service, namely the generation of try-on images
To manage remaining credits and to prevent double charging and double deduction
To verify purchases and grant credits
To prevent unauthorized use and to operate the Service stably
To respond to inquiries

We do not use the information we obtain for ad delivery, behavioral targeting or profiling. Nor do we track users across other companies’ services.

5. Provision to Third Parties

We do not provide your information to third parties except as required by laws and regulations. However, to the extent necessary to provide the Service, we entrust the handling of information to the following businesses.

Contractor	Information entrusted	Purpose
Google LLC (Gemini API)	Photos of people, clothing images	Generation of try-on images. The Google Privacy Policy and the Gemini API Terms of Service apply.
OpenAI (OpenAI API)	Photos of people and clothing images (all generations in version 2.2 and later, and when High Quality is selected in version 2.1). When creating a Fit Report (version 2.2 and later), additionally try-on images and images of clothing saved in your wardrobe (up to 12 items)	Generation of try-on images and creation of Fit Reports. The OpenAI Privacy Policy and the OpenAI Services Agreement apply.
Google LLC (Google Cloud Platform)	The metadata described in Section 2	Operation of servers and the database (stored in a region in Japan)
Apple Inc. (iOS version)	Authentication information, purchase information	Processing of login and payments. Handling by Apple is governed by the Apple Privacy Policy.
Google LLC (Google Play and Sign in with Google; Android version)	Authentication information (if you sign in with Google), purchase information (purchase token, per-account code)	Processing of login and payments, verification and acknowledgement of purchases, and processing of subscription notifications. Handling by Google is governed by the Google Privacy Policy.
Google LLC (ML Kit and MediaPipe; Android version)	Performance and usage metrics of the components (Section 3-8; no images)	Provision and improvement of the on-device components. Sent directly from the components to Google; we do not receive them.

In connection with the entrustment above, information may be processed outside Japan (such as in the United States). In selecting contractors, we confirm that appropriate security control measures are in place.

6. Retention Period

Image data: Not stored on our server (Section 3). Data on your device is retained until you delete it.
Generation request records: Automatically deleted once 30 days have passed from the date of recording.
Account information, credit information and purchase information: Retained while the account is active and for any period required by law. If you request deletion, we delete it through the procedure in Section 8.
Information that remains after account deletion: To prevent the same purchase from being granted twice, purchase records (transaction ID or order number, product, number of credits granted, and date and time) are retained without a fixed period after their link to your account has been removed. For details, see Deleting Your Account and Data.
Server access logs: Automatically deleted once 30 days have passed from the date of recording.

7. Security Control Measures

All communications are encrypted using HTTPS.
API keys for generative AI are not included in the App itself and are managed as secrets on the server side.
Reading from and writing to the database is restricted so that it can be performed only from our server.
Images on your device are stored in an area dedicated to the App so that other apps cannot read them. In the iOS version, the operating system’s data protection features are applied so that they cannot be read while the device is locked. In the Android version, body information, Style Profile results and the identification code are encrypted with an Android Keystore key.
Our operations do not output image data or authentication tokens to logs.

8. Your Rights and Procedures

You may request disclosure, correction, suspension of use and erasure of your information held by us.

Account deletion can be completed within the App (both the iOS and Android versions): Settings → “Delete Account”. Your credits, plan and records on the server, and the photos and generated results on your device, are all deleted. The steps, what is deleted and what remains, and how to make a request after deleting the App are described on the Deleting Your Account and Data page.
Other requests and questions: kaiseiota0620@gmail.com

We will respond within a reasonable period, to the extent we can verify your identity. Please note that deleting your account causes any remaining credits to expire. Deleting your account also does not automatically cancel App Store or Google Play subscriptions. This contact point can also be accessed from the App’s settings screen.

8-2. Consent

Consent to this Policy is obtained as follows.

By starting to use the App (tapping “Start Free” at the end of the onboarding; in version 2.2 or earlier, logging in with Sign in with Apple), you are deemed to have consented to this Policy.
With respect to the sending of images described in Section 3, you are deemed to have consented by executing a generation (including the creation of a Fit Report).
With respect to sending to the OpenAI API, your consent is additionally obtained on a confirmation screen shown once in the App before first use (Section 3-2-2).

In particular, “sending of images at the time of generation” in Section 3 is central to the Service, and if you do not consent to it, the generation features cannot be used. You may withdraw your consent at any time by deleting your account, and we will not obtain any new information after withdrawal.

9. Minors

The Service prohibits the use of images that show any person under 18 years of age. We do not knowingly collect information from children under 13 years of age. If a parent or guardian becomes aware that their child has provided information to us, please contact us at the contact point in Section 8. We will delete it promptly.

10. About This Website

This website is hosted on GitHub Pages (GitHub, Inc.). GitHub may collect access logs (such as IP addresses) in order to provide its services. For details, please see the GitHub General Privacy Statement. We do not use access analytics tools or advertising cookies on this website.

11. Changes to This Policy

We may revise this Policy in response to changes in laws and regulations or in the content of the Service. If we make a significant change, we will announce it in advance in the App or on this website. The revised Policy takes effect when it is posted on this website.

12. Contact

Business name: TryOn Operations Team
Contact: kaiseiota0620@gmail.com