Privacy Policy

13. This website (infocloset.jp)

When you browse this website, the web server's access logs temporarily record details such as your IP address, browser information (User-Agent), referrer, and date and time of access. We use these to operate the server reliably and to detect unauthorized access. Our use of analytics tools is as set out in Section 6 of Part 1. The same applies to the web server's access logs when you browse the product websites we operate (such as mumo.infocloset.jp and nyx.infocloset.jp).

14. Inquiry management platform (ContactBox)

Content sent through the inquiry feature of an app we provide (such as MumoStream and NyXGridEncode) is received and stored on the inquiry management platform (ContactBox) that we operate, and is used to address problems and improve features. The items we collect are as follows.

Inquiries we receive are stored on servers under our control, and we keep encrypted backups of that stored data. We use your reply email address solely to respond to your inquiry. To stay aware of incoming inquiries, we may send the content of an inquiry to the email or message-notification services we use. We delete each inquiry 3 years after it was last updated.

15. MumoStream (app and server)

MumoStream is "self-hosted" streaming software. You run the server software on a computer you provide yourself, and you connect to it from the client app to watch media that you own. We do not operate or host any server, and we never hold, collect, or view your account information, media files, or playback history.

15.1 Information the app stores on your device

The client app stores on your device the details of the server it connects to (protocol, host name, and port), the login password (kept in the Keychain on iOS and stored in encrypted form on the device on Android), authentication tokens, your user name, various settings, and any media files you download. None of this is sent anywhere other than the server you connect to.

15.2 Information the app sends to the server

The client app sends authentication information and playback requests to the server you have specified. The destination is the server you specify, not us. Communication supports encryption via TLS (HTTPS). For the information that the server software records, please see Section 17 of this Part.

15.3 In-app purchases

In-app purchases that unlock Pro features (auto-renewing subscriptions and a one-time purchase) are processed through Apple (the App Store) on iOS or Google (Google Play) on Android, and in both cases through the billing-management service RevenueCat. Payment information such as credit card numbers is processed by Apple or Google, and we do not collect or hold it. To manage purchase status, purchase information and a user identifier generated by the app (which does not include your name, email address, or similar details) are sent to RevenueCat. RevenueCat's handling of that data is governed by its own privacy policy.

15.4 Analytics and tracking

The client app does not use any analytics tools or advertising SDKs that track user behavior (such as Firebase Analytics or Crashlytics). We do not collect any information about how you use the app.

15.5 Google Cast

When you cast playback to a TV or other device with Google Cast, the client app sends the URL of the media being played (which includes the address of your server and may include temporary credentials required for playback) and its title to the Cast-enabled device on the same network that you select. The Cast-enabled device retrieves the media directly from your server using a receiver application provided by Google. None of this information is sent to us. The handling of information by the Cast-enabled device and by Google is governed by Google's privacy policy.

16. NyXGridEncode (batch encoder for Windows)

NyXGridEncode is software that converts video files on your Windows PC. Reading, converting, and saving video files all take place on your own device (and on any devices you add to distributed encoding), and neither your video files nor their content is ever sent to us. We have no way of knowing which files you convert. The only connections the software makes to our servers on its own are the license verification described in 16.2 and the update check described in 16.7 (apart from inquiries you choose to send, as described in 16.6). The external notifications described in 16.8 go to the destinations you configure and do not pass through our servers.

16.1 Information stored on your device

NyXGridEncode stores the following on your PC: your settings, such as conversion instructions, output folders, watched folders, the addresses and authentication token used for distributed encoding, user names and passwords for shared paths, and external notification destinations and their credentials; the queue; logs, such as the names and paths of converted files, processing results, and error details; records of completed jobs; records of files already processed from watched folders; records for each distributed encoding agent, such as the agent name, job counts, MAC addresses, and connection and disconnection history; benchmark records; temporary files; and your license registration details. These are kept alongside the executable where that location is writable, and in a dedicated folder under ProgramData where the software has been installed under Program Files (working files for previews are created in the Windows temporary folder only when they cannot be created in that location). Temporary files include fragments of videos being converted in segments and files received for distributed encoding. Passwords for shared paths and the credentials for external notification destinations (access tokens, webhook URLs, and the password for the outgoing mail server) are stored encrypted. A copy of the license registration state is also kept in your user folder and in the registry so that tampering can be detected. None of this is sent to us automatically.

If you choose Help > Save Diagnostics in the app, NyXGridEncode saves logs, your settings (with authentication tokens, shared path passwords, and external notification credentials masked), external tool versions, and environment information (such as your OS type and version, CPU type, and app version) as a ZIP file in a location you specify.

If you export your settings, NyXGridEncode saves the settings you select as a file in a location you specify; the file does not include license registration details or values specific to the device. The file does include the authentication tokens for distributed encoding, shared path passwords, and external notification credentials. The passwords and credentials are encrypted, but they can be used once the file is loaded into NyXGridEncode. Do not keep this file anywhere a third party can read it.

Neither the diagnostics ZIP file nor an exported settings file is sent to us automatically. If you provide logs or diagnostic information to us for support, we use their content solely to address the problem.

16.2 Information sent to our server to verify a license

When you enter a license key for a paid edition or a trial license to register it or to look it up before registering, or when you attach an add-on license, the software sends the following to our license management server (a lookup sends only the license key), and after registration it periodically re-verifies the license whenever it can connect. While it cannot connect, it continues to work for a limited period on the basis of the last stored verification result.

• The license key and the software version
• Summary values used to identify the device (hash values generated separately from the OS identifier, the system drive's serial number, the computer name, and the number of processors, and a hash value generated from them combined; apart from the computer name described below, the underlying values themselves are not sent)
• The license ID (for periodic re-verification after registration, when attaching and detaching add-on licenses, and when deregistering)
• The computer name of the device (so that, when the device limit is reached, you can choose on screen which device to deregister; please bear this in mind if your computer name includes your real name)

How we store and use this information is set out in Section 18. When you use the free edition without a license key, this communication does not take place.

16.3 Downloading external tools

NyXGridEncode does not bundle the external tools it uses for conversion (FFmpeg, NVEncC, QSVEncC, VCEEncC, and libVLC). If you choose to download external tools in the installer (by default, the installer downloads FFmpeg), or request them from the External Tools screen in the app, the software connects directly from your device to the sites that distribute each tool (GitHub and NuGet) to download the files. In addition, whenever the External Tools screen is opened (it opens automatically at startup if FFmpeg cannot be found), the software connects to the same sites to check the latest version of each tool. If checking external tools is enabled under Update Check in the settings (it is enabled by default), the software also connects to the same sites at startup and every 24 hours while running to check the latest version of each installed tool (except when running as an agent for distributed encoding). This traffic does not pass through us, and we are not aware of what you download or when. The operators of these sites may record connection details such as your IP address; their handling of that data is governed by their own privacy policies.

16.4 Distributed encoding (sharing work across devices)

When you use distributed encoding, the devices you provide communicate directly with one another within your own network, exchanging the video files to be converted and the results. To share the work, each device taking part in distributed encoding (an agent) sends the controller device information such as the agent name (the computer name by default), OS, CPU, GPU, and memory details, external tool versions, and the MAC addresses of its network adapters. When you use Wake-on-LAN, the controller device broadcasts a wake-up signal addressed to an agent's MAC address within your network. We are not involved in this communication, and it does not pass through any server of ours. Securing the communication between devices (managing the authentication token and the scope of your network) is your responsibility.

16.5 Analytics and tracking

NyXGridEncode contains no analytics tools that collect usage data, no crash-reporting feature, and no advertising. We do not collect any information about how you use the software.

16.6 Contacting support

Only when you send an inquiry from Help > Support in the app does the software send the following information to our inquiry management platform (ContactBox; see Section 14). Any information added automatically is shown on screen, and your consent is obtained, before anything is sent.

• The type, subject, and content of the inquiry
• A reply email address (only if you enter one)
• Your OS type and version, CPU type, app version, and display language
• Your license ID (only if you have registered a license; it is appended to the end of the content)

We use the license ID to identify the license and purchase record to which your inquiry relates. In all other respects, Section 14 applies.

16.7 Update check and updates

If checking the app is enabled under Update Check in the settings (it is enabled by default), the software retrieves information about the latest version from our official site (nyx.infocloset.jp) at startup and every 24 hours while running. In this communication, the software does not send your license ID, information that identifies your device, or usage information, and the comparison with the latest version takes place on your device. By the nature of the communication, however, our server records the source IP address, the date and time, and the name of the software. We use these records solely to operate the server and to prevent unauthorized access, and we treat them as web server access logs as set out in Section 13. Even if you disable this check in the settings, the software makes the same communication when you choose Help > Check for Updates in the app.

Only when you choose Update Now does the software download the installer from our official site and run it after confirming that its contents match our signature. As above, no information is sent to us in this download.

16.8 External notifications

Only when you enable a destination under External Notifications in the settings does the software send events such as a finished queue, a failed job, a stalled job, or a disconnected agent to the destinations you specify (LINE, Discord, Slack, a webhook URL, or email addresses through the outgoing mail server you specify). All destinations are disabled by default. When you choose Send Test in the settings, the software also sends to the destination you have entered. The content sent consists of the event type, the computer name of the sending device, the date and time, the paths of the job's input and output files, the name of the node that processed the job, the reason for a failure, and agent names. This traffic goes directly from your device to the destination and does not pass through us, and we are not aware that anything was sent or what it contained. The handling of information at each destination is governed by the terms and privacy policy of the operator of that destination.

17. Running self-hosted software yourself

Software we distribute (such as the ContactBox distribution edition and the MumoStream server) runs on the operator's own server. The controller of the data that accumulates is the operator, and we neither hold nor access that data. The operator is responsible for managing the personal information it handles, including establishing a privacy policy for its end users. The handling set out in this section applies in the same way to any software we may distribute in the future, and the operator bears responsibility for managing the data.

17.1 Data handled by each program

The data handled differs depending on the type of self-hosted software. Representative examples are as follows.

• ContactBox (distribution edition): inquiries received from connected apps (message, subject, type, reply email, device information, status, and date and time). The source IP address is not stored. The admin password is stored hashed.
• MumoStream server: account information (user name and hashed password), activity logs (actions taken, source IP address, User-Agent, and date and time), playback history and favorites, and access-permission settings. TLS private keys and the keys related to certificate issuance (ACME) are stored encrypted with AES-256-GCM.

17.2 External transmission

Only when email (SMTP) or LINE notifications are configured in the ContactBox distribution edition is the content of a received inquiry sent to the configured destination. Both are disabled by default.

17.3 The operator's responsibilities

The operator is to do the following.

• To establish and present to end users a privacy policy explaining the information collected and the purposes of use.
• To implement access controls, enable HTTPS, and change the initial password.
• To manage the personal information it handles in accordance with the APPI and other applicable laws, and to set retention periods and a deletion policy.

18. Sales of software licenses and trial licenses

This section covers the handling of information in connection with the software licenses we sell through this website or through the checkout pages we direct you to ("paid licenses"). It applies in the same way to any software we sell in the future. The handling of information for the trial licenses we issue free of charge is set out in 18.8.

18.1 Information we collect

When you purchase a paid license, we collect the following.

• The name, email address, and billing country or region and other address information you enter on the checkout page
• The order details (product, amount, and currency), the date and time of purchase, and the transaction identifier issued by the payment service provider
• The license key we issue (we store a hash of the key, used for verification, and its last four characters; the record of the email that delivered the license key contains the license key in encrypted form), and information used to identify the devices on which the license is activated (an identifier that distinguishes the device, the device's computer name, the software version, the dates and times of activation, the most recent check, and deregistration, and the reason for deregistration)

The checkout page is provided by Stripe, Inc., our payment service provider. Credit card numbers and other payment details are processed by Stripe, and we do not collect or hold them. In transactions with purchasers outside Japan, Link, LLC (United States of America), an affiliate of Stripe, Inc., acts as the seller: it receives payment, issues receipts, and collects and remits the taxes imposed in the purchaser's country or region. In that case, Link, LLC handles the information you enter on the checkout page in its capacity as the seller. The handling of personal information by Stripe and by Link, LLC is governed by their respective privacy policies.

18.2 Purposes of use

• To issue and deliver license keys and to verify that a paid license is valid
• To provide purchase-related support, such as reissuing a license key, deregistering a device, and processing refunds
• To prevent unauthorized copying, sharing, or resale of licenses, and to prevent payment fraud
• To keep transaction records and to fulfill other obligations under applicable law

18.3 Storage and external transmission

The information we collect is stored on the license management server that we operate. To deliver license keys and to contact you about support, we send your email address and the message content to the email-sending service we use. The retention periods are set out in 18.7.

18.4 Information the software sends to our server

Software in which a paid license has been activated sends the following to our license management server in order to verify that the license is valid.

• The license ID and the software version
• The license key (sent when you register a key, look one up before registering, or attach an add-on license)
• Summary values used to identify the device (hash values generated from device information such as the OS identifier, system drive serial number, computer name, and number of processors; the original values are not sent)
• The computer name of the device (so that, when the maximum number of registered devices is reached, you can choose on screen which device to deregister)

When and what each piece of software sends may be set out in its own section of Part 2. For software without its own section, this subsection applies. For device registrations, replacements, and deregistrations, for the attachment and detachment of add-on licenses, and for license key reissues, our license management server records the operation performed, the date and time, and the source IP address, in order to prevent misuse and to keep operational records (IP addresses are stored in encrypted form). These records are deleted together with the records of the license concerned, except that the IP addresses they contain are deleted after the period set out in 18.7. In addition, when the software communicates with the license management server, the web server's access logs record details such as the source IP address and the date and time. We treat these access logs in the same way as the web server access logs described in Section 13. This license-verification communication does not include the content of any files you process.

18.5 Users in the Republic of Korea

For users who reside in the Republic of Korea, we provide a Korean-language document that describes the handling under this section in line with the laws of the Republic of Korea: 개인정보 처리방침 (소프트웨어 라이선스 판매 및 체험판 라이선스)

18.6 Supplementary provisions for specific countries and regions

We are located in Japan and handle information about purchasers of paid licenses in Japan. We transfer the information of purchasers who reside outside Japan to Japan because it is necessary to perform our contract with the purchaser (issuing and verifying licenses and providing support). If a personal data breach occurs, we will notify the competent supervisory authority and, where required, the individuals concerned within the period set by the applicable laws. The following also applies to residents of the countries and regions below.

• Thailand: Under the Personal Data Protection Act, B.E. 2562, this Policy sets out the purposes of use (18.2), storage and external transmission (18.3), and our contact details (Section 12). You may exercise the rights of access, data portability, objection, erasure, restriction and rectification, and may withdraw your consent, through the contact point in Section 12. You may also lodge a complaint with the Personal Data Protection Committee (PDPC).
• Saudi Arabia: Under the Personal Data Protection Law, our legal bases for processing are the performance of our contract with the purchaser, compliance with legal obligations, and our legitimate interest in preventing misuse. You may exercise the rights to be informed, to access, to rectification and to erasure through the contact point in Section 12, and we will, as a rule, respond within 30 days. If you are dissatisfied with how we handle your data, you may lodge a complaint with the Saudi Data and Artificial Intelligence Authority (SDAIA).
• Barbados: Under the Data Protection Act, 2019, you may exercise the rights of access, rectification, erasure and to stop processing through the contact point in Section 12, and may lodge a complaint with the Data Protection Commissioner.

18.7 Retention periods

We keep the information collected under this section for the periods below and delete it once the period ends. Where the law requires us to keep information, we keep it for the period the law sets.

• Paid license information: while the paid license is valid, and for 5 years from the date the paid license is revoked or expires (or, if the paid license record is updated after that, from the date of the last update)
• Trial license information: 1 year from the expiry of the trial license
• Information about purchasers and trial license applicants (such as email address and display language): until all of that person's license records (including trial licenses) and order records have been deleted
• Records used to prevent duplicate issuance and registration of trial licenses: 1 year from the date of the record
• Trial license application information (email address, display language, trial license product applied for, date and time of application, and the IP address used to apply): deleted when the trial license is issued, or, if it is not issued, after the confirmation link expires (24 hours after the application)
• Records of trial license applications we did not accept, as described in 18.8: 90 days from the date of the record
• Temporary records used to limit the number of trial license issuances (source IP addresses converted with a key held only by us into values from which the originals cannot be recovered): deleted within 2 days after the limit period (1 hour) ends
• Records used to count the number of trial licenses issued per day for each source IP address and each email domain (each converted with a key held only by us into a value from which the original cannot be recovered): deleted once 2 days have passed since the date of the record
• Temporary records used to limit the number of license registrations, verifications, and similar operations (values converted from source IP addresses): deleted within 2 days after the limit period ends
• Order records (product, amount, purchase date and time, and transaction identifier): 7 years from the date of the order. While any record of a license issued under that order remains, the order record is kept even after 7 years
• Content of payment notifications received from the payment service provider (such as name, email address, and billing address information): 90 days from receipt
• Information that identifies a device on which a license was activated: 90 days from the date the device is deregistered. Information about devices that have not been deregistered is deleted together with the record of the license
• Records of the operations described in 18.4: deleted together with the record of the license concerned
• IP addresses recorded for the operations described in 18.4 and for trial license issuance operations: 90 days from the date of the record
• Emails sent from our servers (including the license key, in the case of an email that delivered a license key): 90 days from the date of sending. Emails that could not be sent: 90 days from the date of creation
• Records of email addresses, IP addresses, device identifiers, and license IDs whose use we have blocked: until the block is lifted
• Records of unauthorized communications with the license management server and other events requiring review (such as the source IP address and User-Agent, stored in encrypted form): 90 days from the date of the record

18.8 Trial licenses

We issue trial licenses free of charge for the software for which we offer them (such as NyXGridEncode) to those who apply on a product site we operate (such as nyx.infocloset.jp). Trial licenses are issued for each type, such as each software product and edition (each a "trial license product"). When you apply for and use a trial license, we collect the following.

• The email address and display language you provide when applying, the date and time of the application, and the trial license product you apply for
• The source IP address used when you apply for the trial license and when you request its issuance (stored in encrypted form)
• The license key of the trial license we issue (we store a hash of the key, used for verification, and its last four characters; the record of the email that delivered the license key contains the license key in encrypted form), the license ID, the date and time of issue, and the expiry date and time
• Information used to identify the device on which the trial license is registered (the same items as the device information in 18.1)
• Records of applications we did not accept (limited to applications made with disposable email addresses, applications we determine to have been submitted automatically, and applications from email addresses or IP addresses whose use we have blocked; we record the email address you entered, the trial license product applied for, the date and time of the application, the source IP address, and the reason the application was not accepted, and store the email address and IP address in encrypted form)
• Records used to prevent duplicate issuance and registration (your email address, the device identifier, and the hash value of each item among the summary values used to identify the device described in 18.4, each converted with a key held only by us into a value from which the original cannot be recovered, together with the trial license product and license ID of the corresponding trial license, the display language, and the date and time of the record)

Duplicate issuance and registration are assessed separately for each trial license product. Before conversion, the email address used for these records is normalized so that differences in letter case, any part after a "+", and dots in Gmail addresses are ignored. Applications and issuance requests are relayed to our license management server by the product site that received the application, and that product site sends the source IP address to the server when doing so.

We keep the application information (email address, display language, trial license product applied for, date and time of application, and the IP address used to apply) only until the trial license is issued from the link in the confirmation email, and delete it at the time of issue. Once a trial license is issued, we keep the email address and display language as applicant information. The IP address used to request issuance is kept with the issuance record. To limit the number of issuances, we keep as a temporary record a value converted, with a key held only by us, from the source IP address (for IPv6, the upper 64 bits of the address; the same applies throughout this paragraph), and, to count the number of issuances per day, we record values converted in the same way from the source IP address and from the domain of the email address (excluding the domains of major email services). We do not accept applications made with disposable email addresses, applications we determine to have been submitted automatically, or applications from email addresses or IP addresses whose use we have blocked, and we keep records of these applications to investigate and prevent misuse.

We use this information for the purposes below. We do not use the email address collected through a trial license application to send advertising or promotional emails.

• To issue trial licenses and to send the confirmation email, the license key, the notice that a trial license has already been issued, and the notice that a trial license has expired
• To verify that trial licenses are valid, to register and deregister devices, and to reissue license keys
• To prevent the same person from receiving, and the same device from registering, more than one trial license of the same trial license product
• To prevent mass applications and other misuse
• To keep track internally of the issuance of trial licenses (including notifying ourselves of each issuance by email)
• To provide support for trial licenses

18.3 to 18.6 also apply to trial licenses. In those provisions, "paid license" is to be read as "trial license" and "purchaser" as "trial license applicant." The retention periods are set out in 18.7. Persons who reside in the European Union (EU), the European Economic Area (EEA), or the United Kingdom are not eligible to apply for a trial license (see 17.9 of our Terms of Service).