Protez Pass Privacy Policy (United States)
Date of establishment: November 9, 2026 / Version of this Policy: 1.0.0 (applies from App version 1.0.0)
Protez, Inc. (the “Company”) complies with the Act on the Protection of Personal Information of Japan (the “APPI”) and other applicable laws and regulations, and handles users’ information in accordance with this Privacy Policy (this “Policy”), with respect to the password generation and management app “Protez Pass” that the Company provides.
Protez Pass is designed so that the Company does not receive users’ information. This Policy explains what the app does not collect, what is processed inside the user’s device, and the information the Company collects as an exception (information relating to inquiries and to website access).
1. Operator information
- Name: Protez, Inc.
- Address: Omori 2596-9, Inzai, Chiba, Japan
- Representative: Representative Director Hiroaki KOBAYASHI
2. Definitions
In this Policy, the following terms have the following meanings.
- The App: The “Protez Pass” application provided by the Company (including the iOS and iPadOS versions and the desktop version (for Windows, macOS or Linux) that the Company provides).
- The Website: The Company’s website that introduces the App (https://pass.protez.jp/consumer) and the Company’s website (https://protez.jp).
- User: A person who uses the App and a person who views the Website.
- Vault Data: Passwords, passphrases, names, login IDs, notes and other records that the user generates or saves in the App, and the encrypted file (the vault) that contains them.
- Personal information, personal data, retained personal data: Have the meanings given in the APPI.
3. Scope of application
- This Policy applies to the use of the App, to viewing the Website (limited to the scope set out in Article 8), and to inquiries to the Company about the App.
- This Policy also applies to the desktop version (for Windows, macOS or Linux) that the Company provides.
- The handling of personal information in the Company’s other products and services is governed by the privacy policy of each product or service (for ProtezAI, the “ProtezAI Privacy Policy”). The handling of information of businesses that contract for Protez Pass for Biz and of their officers and employees is governed by the “Protez Pass for Biz Service Privacy Policy”.
- The handling of information by the apps and third-party services that the user chooses when sending a shared file or a Secure File (Article 5, items 3 and 9) from the App, or when saving a decrypted file (email, messaging, AirDrop, file storage locations and others), and by iCloud and other backup services, is governed by each provider’s privacy policy or equivalent.
4. Information the App does not collect
The App has no function for communicating over HTTP and no function for sending information to the Company. The App’s own communication over the internet is limited to DNS over TLS queries that check whether a newer version is available and whether the Protez Pass Terms of Use or this Policy are to be amended (the destinations and the information sent are set out in Article 11). Once the business verification function (shown in the App as “Verify a Business”) is provided, the App also makes the DNS over TLS queries and the retrieval of the time by NTS that accompany that function (Article 5-2). These communications contain no information that identifies the user. In addition, only while the user has turned on “Allow sync”, the App announces itself on the user’s local network, accepts connections on it only from devices the user has linked (and, while linking, from the device entering the user’s code), and connects directly to them. This communication never goes to the Company and never goes over the internet. The Company does not collect the following information through the App.
- Account information: The App has no account registration mechanism, and does not ask for a name, email address or any other information that identifies the user.
- Vault Data: Vault Data is stored encrypted inside the user’s device and is never sent to the Company. As set out in Article 5, Vault Data leaves the device only through a device-to-device transfer by Bluetooth, sending a shared file, sending pre-shared keys inside a Secure File (Article 5, item 11), sync over the local network with devices the user has linked (up to three in all; Article 5, item 12), or a backup of the user’s own device, each performed by the user’s own operation.
- Biometric and similar information: Authentication by Face ID, Touch ID and the device passcode is performed by the device’s OS. The App receives from the OS only the result of authentication (whether it succeeded) and does not collect face or fingerprint information. Where a security key is used in the desktop version, the App receives from the security key a value used to derive the vault key and uses it only inside the device.
- Usage and device information: The App does not send usage logs, operation history, analytics data, crash reports, advertising identifiers, location information, contacts or other information on the device to the Company or any other third party.
- Content of communications: The App does not route the content of a Bluetooth transfer through the Company’s servers, and the Company does not collect that content.
5. Information processed inside the user’s device
The following information is processed only inside the user’s device, and the Company never collects it.
- The vault: Vault Data is encrypted with a key derived from the master password set by the user (one master password opens every vault) (and, if the user turns on “Also require this device”, a key held on the device) and is stored inside the device. The Company knows neither the master password nor these keys and cannot open the vault. If the user forgets the master password, the Company cannot recover it. If the user sets a new master password by choosing “Forgot master password?”, the existing vaults are archived, not deleted, and each can be opened later with the master password it was made under.
- Transfer by Bluetooth: When the user uses the App’s transfer function, Vault Data is encrypted using the QR code on the screen (transfer code) and a transfer passcode, and sent directly by Bluetooth to a nearby device of the user or of the counterparty. The App uses the device’s camera only to read QR codes, and does not save or send any image it captures.
- Shared files: When the user creates a shared file (.protezpass), its content is encrypted with a passphrase generated by the App and handed to the sending method the user chooses (email, messaging, AirDrop, saving to files, etc.). The provider of the sending method may handle the encrypted file, but cannot read its content without the passphrase.
- Device backups: Vault files may be included, in encrypted form, in an iCloud backup or a backup to a computer that the user has configured (for the desktop version, a backup of that computer). These backups belong to the user, and their handling is governed by the policies of Apple and the other backup providers. However, of the information in item 11, what the App keeps in files outside the vault is excluded from these backups (including Time Machine on a Mac) to the extent the OS allows.
- Saving passwords (iOS): If the user permits it, iOS may save the master password in Apple’s password management function. This saving is an OS function and is governed by Apple’s policies.
- Clipboard: A password, passphrase or other vault item copied by the App is placed on the clipboard with a setting that limits it to use within the device, and is cleared automatically after a set time.
- Checking against leaked passwords: When the master password is created or changed, it is checked, inside the device, against a list of previously leaked passwords (bundled with the App). No information is sent outside for this check.
- Settings: The display language, appearance, generation settings, the Residence (Article 15, paragraph 4) and other settings of the App are stored inside the device.
- Secure Files (.protez): When the user sends a file with the App’s “Exchange Files Securely” function, the App encrypts the file the user picked, inside the device, with a passphrase into a Secure File (.protez) and hands it to the sending method the user chooses. When the user opens a received Secure File in the App, the App decrypts it inside the device with the passphrase and hands the decrypted file, through the OS’s file-saving function, to the location the user chooses. The App does not inspect the content of decrypted files (including checking for malware), and does not send Secure Files, decrypted files or passphrases to the Company. A decrypted file is deleted from the App’s temporary storage after it is handed to the chosen location or when the operation is cancelled.
- Passphrase vault and file passphrases: Passphrases the user creates with the App’s “Set Up and Manage Passphrases” function are stored in the “Passphrase vault”, the passphrases of files the user sends or receives with the “Exchange Files Securely” function in the “File passphrases” vault, and the passphrases of shared files the user sends in the “Share keys” vault, each encrypted inside the device. These vaults open with the master password, like every other vault (and, if the user turned on “Also require this device”, a key held on the device). A vault protected in this way cannot be restored to another device. The Company cannot open these vaults, and their content is never sent to the Company.
- Pre-shared keys: When the user sends a Secure File to a person registered in “Set Up and Manage Passphrases” with “Attach new pre-shared keys” turned on, the App puts single-use keys for later files to that person (“pre-shared keys”) inside the encrypted Secure File. The App stores the pre-shared keys held with each person, encrypted, in the vault; it keeps, in files outside the vault, the identifiers of those keys (no key, name or file content) and a value used to detect that the vault was moved; and it keeps, in the device’s keychain or similar store, a key that is not synchronised and is not moved to another device. Between linked devices, the pre-shared keys are synced as part of the vault (item 12). After the vault is restored from a backup, or moved to another device by a means other than that sync, the pre-shared keys held before may become unusable; in that case new pre-shared keys are handed over with the next file. When the counterparty’s app cannot find a pre-shared key, the App shows 8 groups of numbers in the sent file’s record, and the user may pass them to the counterparty by a method the user chooses. None of this information is sent to the Company.
- Wi-Fi sync: When the user turns on “Allow sync” and links the user’s own devices (up to three in all), the App encrypts, inside the device, the records of the vaults the user has chosen to sync, and sends them directly to, and receives them from, the linked devices on the same local network. The key used for linking is stored only inside each device and is not included in backups. When a record is edited or deleted on one device, the change is made on the linked devices too, and a deleted record is kept on each device for 30 days so that it can be restored. Every kind of vault can be synced, including the passphrase vault and the file passphrases vault with their pre-shared keys; a record the user has excluded from sync is not sent to the linked devices. Sync communication never goes to the Company and never goes over the internet.
- Vault access history: The App records, inside the device, when someone tried to open the vaults and how it ended (such as opened, wrong password or device check not passed), and when an archived vault was deleted, each with the date and time and, where it applies, which vault. The record is encrypted with a key kept only on the device, and can be read in the App’s settings only after the vaults have been opened with the master password. It is never sent to the Company or anyone else, is not synced to linked devices, and is excluded from device backups to the extent the OS allows. It keeps up to 200 entries, and entries the user has already seen are removed once they are older than 90 days. The App has no setting that turns the record off; when the user clears it, a line stating that it was cleared is left in its place.
6. Information the Company collects
The Company collects users’ information only in the following cases.
- Inquiries: When a user makes an inquiry to the Company through the inquiry form or by post (including a Disclosure Request by post), the e-mail address the user sent (on the inquiry form, the address confirmed by a one-time pass), the company name and name (if provided), the kind of inquiry, the subject, the content of the inquiry and other information the user voluntarily provided, for post the sender’s name and address, and the date and time of sending and receipt. The Company also obtains, in receiving inquiry-form submissions, in the automatic checks of Article 16, paragraphs 4 and 5, and in sending its e-mail, a matching value computed from the e-mail address, the number of submissions (including per sending IP address), one-time pass records, records of discards and other records. The kinds, content and retention periods of these records are shown on the information page of the procedure in Article 14, paragraph 3.
- Information on access to the Website: Information within the scope set out in Article 8
- Reports about a business: Once the business verification function is provided, when a user reports a business registered for that function through the web form the Company provides or by post, the email address and name (if provided) that the user sent, the content of the report and its attachments, and the date and time of sending and receipt
The Company does not ask for Vault Data, the master password or the passphrase of a shared file in order to respond to an inquiry. Please do not include these in an inquiry.
7. Purposes of use
- The Company uses the information in Article 6, item 1 only for the purposes of replying to and handling inquiries (including keeping a record of the handling) and of preventing misuse of the inquiry channel.
- The Company uses the information in Article 6, item 2 only for the purposes set out in Article 8, paragraph 2.
- The Company does not use the information it collects for advertising, marketing, analysis of users (profiling) or training of artificial intelligence (AI).
- If the Company changes a purpose of use, it will not change it beyond the scope that is reasonably recognized as related to the purpose before the change, and will notify the individual of, or publicly announce, the purpose after the change.
- The Company uses the information in Article 6, item 3 only to handle the report under Article 8-2 of the “Protez Pass for Biz Service Privacy Policy” (including consulting the police, checking public information and making an enquiry of the business) and to keep a record of that handling. The Company owes the reporter no reply on progress or outcome and, except as required by laws and regulations, does not provide information identifying the reporter to the business.
- The Company’s staff may use artificial intelligence (AI) to prepare a draft reply to an inquiry. Names, e-mail addresses, telephone numbers, postal addresses and other information identifying a person in the inquiry are masked by an automatic process before the text is passed to the AI. A member of the Company’s staff decides whether to reply and what the reply says, and a member of the Company’s staff sends every reply.
8. Information on access to the Website
- The Website is delivered using the service of Cloudflare, Inc. (United States). When a user views the Website (including when a user opens the link to the Company’s website from the App’s settings screen and it is displayed in the browser), the IP address, browser type, URL of the page viewed, referrer and date and time sent from the user’s browser may be recorded on the servers of Cloudflare, Inc. When this link is opened, the App itself does not send information; the browser on the user’s device requests the page.
- The Company views the records in the preceding paragraph only where necessary to handle faults of the Website and to counter unauthorized access and attacks.
- When a user opens a link from the Website to an external site (social media, etc.), the handling of information at the destination is governed by the policy of the operator of the destination.
- The Website contains no analytics tools, advertising tags or embedded social media, and, apart from the check in the next sentence, no other party collects information about a visitor’s online activities over time and across different websites through the Website. The forms on the Website (including the inquiry form) use Cloudflare Turnstile, a service of Cloudflare, Inc., to check that the sender is a person and not an automated program; when a form is shown or sent, the IP address and the information about the browser and device needed for that check are sent from the browser to Cloudflare, Inc., which handles them under its own privacy policy.
9. Provision to third parties, entrustment, and provision to third parties in foreign countries
- Because the Company does not collect users’ information through the App, the Company does not provide users’ personal data to third parties in relation to the App.
- The Company does not provide the information in Article 6 to a third party without the individual’s consent, except where required by law or otherwise permitted by the APPI.
- The Company uses the services of Cloudflare, Inc. (United States) to receive inquiry-form submissions, to send one-time pass e-mail and to deliver the Website, and the services of Amazon Web Services to store inquiries, check them automatically, prepare draft replies and send notices of receipt and replies. The content of inquiries is stored in the Tokyo Region (Japan), and may be processed in the Tokyo, Osaka, Seoul, Singapore, Sydney or Mumbai Region for the automatic checks and for draft replies. Where a foreign provider is used or data is processed in a foreign country, grasping the external environment is governed by Article 12.
10. Roles of the App Store and Apple
- The iOS and iPadOS versions of the App are distributed through the App Store operated by Apple Inc. and its affiliates (“Apple”). Information accompanying the download, purchase and update of the App, the posting of App Store reviews and other use of the App Store is handled by Apple in accordance with Apple’s privacy policy and is not collected by the Company through the App. The desktop version that the Company provides is distributed not through Apple but by download from the Website, and Article 8 applies to viewing that download page.
- The Company may reply to reviews posted on the App Store through functions provided by Apple. The reviewer’s name and the content of the review are displayed on the App Store, and their handling is governed by Apple’s policies.
- The App’s App Store privacy information (privacy label) is stated as “Data Not Collected”.
11. Communications made by the App
- The App’s communication with servers of parties other than the Company is limited to the check for a newer version (item 1) and the check for amendments of the Protez Pass Terms of Use and this Policy (item 2). Once the business verification function is provided, the App also makes the communications accompanying that function (items 3 and 4). Each communication goes directly from the user’s device to the destinations the user has chosen in Settings, and the user can change those destinations in Settings. These communications do not contain the user’s name, telephone number, device identifier or other information that identifies the user. By the nature of the communication, each destination can know the IP address of the user’s device and the date and time of the communication. The handling of information by the operator of each destination is governed by that operator’s privacy policy or equivalent.
- To check whether a newer version of the App is available, the App, at launch and no more often than a set interval, sends by DNS over TLS a query for a name in a DNS zone the Company manages to DNS resolvers (by default, Quad9, operated by Quad9 Foundation, and Cloudflare, operated by Cloudflare, Inc.). The query is the same for every user and contains no version of the App and no device type. The App evaluates the answer inside the device and, if a newer version exists, says so on screen (the query is still made when the notice is turned off). What the Company’s DNS servers receive are queries from DNS resolvers, not queries from the user’s device (depending on the settings of the DNS resolver the user chooses, the query may include information indicating the range of the user’s network). The Company cannot identify a user from this query.
- To check whether the Protez Pass Terms of Use or this Policy are to be amended, the App, at the same time as the check in the preceding item, sends by DNS over TLS a query for another name in a DNS zone the Company manages to the DNS resolvers in the preceding item. The query is the same for every user and contains neither the Residence the user has stated (Article 15, paragraph 4), nor any version of the App, the Terms of Use or this Policy, nor the device type. The App evaluates, inside the device, the version and effective date that the answer gives for the Residence among those given for each country or region, and may say on screen that an amendment is scheduled (Article 15, paragraph 5). What the Company’s DNS servers receive, and that the Company cannot identify a user from this query, are as in the preceding item.
- To obtain Business passes (Article 5-2, paragraph 1) and check their validity, the App sends queries containing the business ID by DNS over TLS to the DNS resolvers in item 1 (only after Article 5-2 takes effect).
- To check the time, the App obtains the time by NTS (Network Time Security) from time servers (by default, those operated by Cloudflare, Inc., the Physikalisch-Technische Bundesanstalt (PTB) and System76, Inc.) (only after Article 5-2 takes effect). This communication contains no business ID.
- Where a destination is specified by host name, the device’s OS looks up that name using the name-resolution settings configured on the device.
- The sync in Article 5, item 12 is communication made directly between the user’s devices on the local network, and is not communication with a server of the Company or of anyone else.
12. Security control measures
The Company takes the following measures, in light of the small amount of information it handles, to prevent leakage, loss or damage of the personal data it holds (mainly the information in Article 6) and for other security control.
- Basic policy: The Company establishes this Policy and complies with applicable laws, regulations and guidelines.
- Organizational security control measures: The Company designates a person responsible for handling personal data and makes clear who handles personal data and with what authority. It establishes procedures for reporting and responding to incidents such as leakage.
- Human security control measures: The Company imposes confidentiality obligations on persons who handle personal data and provides necessary training.
- Physical security control measures: The Company takes measures to prevent theft and loss of devices and electronic media that handle personal data.
- Technical security control measures: Records of inquiries received through the inquiry form can be viewed only by the Company’s staff, from devices the Company has approved. These records are encrypted when stored and in transit, and are deleted automatically at the end of their retention period. The Company takes measures against unauthorized external access, and content discarded under Article 16, paragraphs 4 and 5 is not kept. Letters received by post and their records are kept in a locked file.
- Grasping the external environment: When using the service of a provider in a foreign country, and when personal data is processed in a foreign country (Article 9, paragraph 3), the Company takes security control measures after grasping the system for the protection of personal information in that country (the United States, the Republic of Korea, Singapore, Australia and India).
If a leakage or similar incident involving personal data occurs, the Company responds in accordance with the APPI and other laws that apply.
Vault Data is not under the Company’s control, so its security depends on the App’s encryption and on the user’s management of the device (the device passcode, management of the master password, etc.).
13. Retention period
- The Company keeps an inquiry record for 3 months after it closes the inquiry, and then erases it without delay. The retention periods of the other records that accompany an inquiry (Article 6, item 1) are shown on the information page of the procedure in Article 14, paragraph 3. Records of Disclosure Requests by post are kept for the period that procedure sets.
- The Company keeps the information in Article 6, item 3 only for as long as needed to achieve its purposes of use and then erases it without delay.
- Notwithstanding the preceding two paragraphs, where retention is required by law, the information is kept for that period. The records in Article 8, paragraph 1 held on the hosting provider’s servers are retained for the period that provider determines.
14. Matters concerning retained personal data and requests for disclosure and the like
- The personal data the Company holds in relation to the App is limited to the information in Article 6. Vault Data and other information inside the device are not held by the Company, so the Company cannot respond to requests for their disclosure, correction or deletion. The user can check and change information inside the device by operating the App or the device. A vault that is not archived cannot be deleted inside the App: an unwanted vault is archived and stays on the device until the user deletes it. An archived vault can be deleted inside the App by entering the current master password or, for a vault archived by choosing “Forgot master password?”, the master password it was made under; this deletes only the copy on the device, not a copy in a backup made earlier. A record the user deletes waits 30 days in “Recently deleted” before it is erased. What the App keeps is deleted when the user removes the App or erases the device; on a computer, removing the App usually leaves its data folder, which the user then deletes. On iOS, items the App placed in the Keychain can remain on the device after the App is removed, and are deleted when the device is erased.
- The individual or the individual’s agent may request of the Company, by post, disclosure of retained personal data (including disclosure of records of provision to third parties), its correction or addition, the cessation of its use, and the cessation of its provision to third parties (together, “Disclosure Requests”).
- Please make a Disclosure Request by the method set out in the Procedure for Personal Data Requests (see “Requests about your personal information” on the Company’s inquiry page, https://protez.jp/enquiry). Identity verification, requests by an agent and the way the answer is given are also set out in that Procedure.
- For disclosure, a fee of 1,000 yen per request is charged as set out in that Procedure; no fee is charged for other requests.
- The Company responds to Disclosure Requests without delay. However, in the cases set out in Article 10 of that Procedure (including where responding may seriously hinder the proper conduct of the Company’s business), the Company may decline all or part of a request.
- Inquiry records and the other records in Article 6, item 1 are kept for the purposes in Article 7, paragraph 1, including preventing misuse of the inquiry channel, for the period set out in Article 13, paragraph 1, and are deleted at the end of that period. Records received through the inquiry form are deleted automatically. The Company does not delete or erase these records individually at the request of the individual or of anyone else.
- The purposes of use of retained personal data are as shown in Article 7 and on the information page of the procedure in paragraph 3. The Company gives no individual notice of the purpose of use.
15. Amendment of this Policy
- The Company may amend this Policy. Each version of this Policy is bundled with a version of the App and shows, as its version, the number of the App version with which it was first bundled. An amended Policy is posted on the Website before distribution starts of the version of the App that bundles it. As to use of the App, the version of this Policy bundled with a version of the App describes how that version of the App handles information, also for a user who does not update the App. Where the user has not yet confirmed on a device having read the version of this Policy bundled with the version of the App on that device, the App displays this Policy and asks the user to confirm having read it, as set out in Article 1, paragraph 5 of the Terms of Use. The record of this confirmation is stored on the device only and is sent nowhere. While a vault is stored on the device and that confirmation has not been recorded on the device, the vaults open read-only as set out in Article 1, paragraph 9 of the Terms of Use.
- If the Company adds a function by which the App newly collects information about users, or sends information from the user’s device to the Company or any other third party, the Company posts the amended Policy on the Website before distribution starts of the version of the App that has that function. Where the law requires the individual’s consent, the Company obtains it before the function is used.
- This Policy is written in English, and the English text is the governing text. Translations of this Policy are provided for reference only, and if there is any discrepancy between a translation and the English version, the English version prevails.
- The App displays the privacy policy for the country or region of residence that the user states in the App (the “Residence”). As to use of the App, this Policy applies to users who state the United States as their Residence in the App. The Residence is stored on the device only and is not sent to the Company or anyone else. If the user changes the Residence, the App displays the privacy policy for the new Residence and asks the user to confirm it again.
- In addition to the posting on the Website under paragraph 1, when the App learns through the check in Article 11, paragraph 1, item 2 that an amendment of the privacy policy for the Residence is scheduled, the App may say so on screen. The notice does not prevent use of the App, and whether or not it is shown does not affect the application of the amended Policy. The user’s confirmation is recorded only for a version of this Policy that the App itself has displayed.
- Paragraph 1 concerns use of the App. The provisions of this Policy that concern the Company and the information the Company itself handles outside the App (including the information in Article 6), and requests concerning that information (the introductory paragraphs, Article 1, Article 2, items 2 and 3, Article 3, paragraph 1 (as to viewing the Website and inquiries) and paragraph 3, Articles 6 to 9, Article 10, paragraphs 1 and 2, Articles 12 to 14, Article 15, paragraph 3 and Article 16, so far as they concern those matters), are not tied to a version of the App. For those matters, the privacy policy that the Company posts on the Website for the country or region where the individual lives (where none is posted for that country or region, the privacy policy posted for Japan and other countries and regions) applies from the date the Company sets in the posting, and the current version of those provisions is the one posted on the Website. An amendment that would use information the Company already holds for a purpose not reasonably related to the purpose before the amendment applies to that information only with the individual’s consent where the law requires it.
16. Contact point
- For inquiries and complaints about this Policy and the handling of personal information, please write to the following contact point through the inquiry form or by post. Disclosure Requests follow the procedure in Article 14, paragraph 3.
- Operator: Protez, Inc.
- Contact point: Personal Information Protection Desk
- Inquiry form: https://protez.jp/enquiry
- Post: Protez, Inc., Personal Information Protection Desk, 2596-9 Omori, Inzai, Chiba 270-1327, Japan
- Handling: the inquiry form accepts messages at any time; they are handled on the Company’s business days.
- Complaints and general inquiries may be sent by ordinary post, and no fee is charged. Post can also be used when the inquiry form cannot be used (including when the form has stopped accepting messages for the day).
- The Company endeavours to handle complaints appropriately and promptly. Complaints and general inquiries that pass the automatic checks in the next paragraph and paragraph 5 are read by a member of the Company’s staff. The Company replies only where it judges a reply necessary or the law requires one.
- Messages sent through the inquiry form are checked automatically. A message whose content falls into any of the following categories is discarded automatically, without being read by a person, without notice and without a reply.
- Hateful or discriminatory content
- Insults and harassment
- Sexual content
- Violence and threats
- Content seeking or helping crime or other wrongdoing
- Attempts to manipulate an automated system (prompt attacks)
- Besides the preceding paragraph, messages sent beyond a volume limit, messages sent in a form other than the Company’s inquiry form, and messages that cannot be checked because of a system fault may also be discarded without being read by a person, without notice and without a reply. Inquiries by post are not subject to these checks.
- After a message is sent through the inquiry form, the Company may send a notice of receipt by e-mail automatically. The notice is the same for every message and is not a promise that a member of the Company’s staff will read the message or reply to it.
- Disclosure Requests are not accepted through the inquiry form. A Disclosure Request sent through the inquiry form is not handled and may receive no reply.
- The Company’s e-mail about inquiries is sent from the domains contact.protez.jp and mail.protez.jp. These domains receive no mail. Each reply from the Company contains one link, starting https://www.protez.jp/support/follow-up/, through which one further message about that inquiry can be sent. The link is valid for 30 days and stops working when a newer reply arrives.