PAAN Co., Ltd. ("we", "us", or "our") provides MENU-PAAN, a multilingual restaurant-menu translation service for diners; RESTO-PAAN, a menu-management and multilingual translation service for restaurant owners; and other services we provide now or may provide in the future (together, "our Services"). This Privacy and Data Policy ("Policy") explains how we handle personal data and user information in connection with our Services, in compliance with Japan's Act on the Protection of Personal Information ("APPI"), the EU/UK General Data Protection Regulation ("GDPR") where applicable, and other applicable laws.
This Policy applies to all of our Services in common. Where a matter is specific to a particular service, that is stated expressly. This English edition is a reference translation; the Japanese edition prevails in case of any discrepancy (Section 15).
| Entity | PAAN Co., Ltd. |
|---|---|
| Representative | Rokusaburo Inui, Representative Director |
| Address | 3-5-20 Nakameguro, Meguro-ku, Tokyo 153-0061, Japan |
| Data protection manager | Rokusaburo Inui, Representative Director |
| Contact point | https://www.paan.co.jp/contact |
We may collect the following information in providing our Services.
Email address, display name, password and other credentials. Where you register via external authentication (SSO) with an Apple ID or Google account, the identifier and email address provided to us by that provider. Profile avatar (initials, icon, or an image you set). Your account and avatar are used in common across our Services (MENU-PAAN, RESTO-PAAN, etc.) and are therefore shared between those services for the same account.
Dish names, descriptions, prices, currencies, sections, menu images, dish images, tags and similar content that you upload to our Services by entry, photograph or other means, together with derived data our Services generate from it automatically (OCR, AI translation, reference information, keyword extraction), such as translated dish names, descriptions and prices. This content is stored so that you can refer to it in your history, and you can view and delete it through the features provided in our Services.
Purchase and billing information where you buy a paid plan or paid feature. Card numbers and other payment-instrument details are handled by Apple or Google (in-app purchase) or by our payment processor; we do not hold card numbers ourselves.
Access timestamps, operation and usage history, usage status such as translations and item credits used and plans held, device, OS and browser information, IP address (anonymised for analysis), and identifiers stored in cookies and local storage. To send you notices, we store your device's notification ID. This includes records of how far you progress through screens in our Services (step-by-step records such as launching the app, starting a translation and viewing the pricing screen) and records of errors that occur while you use our Services (the nature of the error, the screen on which it occurred, device and browser information and, if you are signed in, your user identifier). To prevent unauthorised use and excessive automated access, where a translation feature (such as service phrases or communicating ingredients to avoid) is used from the customer-facing (guest) screens of RESTO-PAAN, we record a value derived from the user’s IP address in a form from which the IP address cannot be restored, together with the identifier of the restaurant concerned, the type of feature, the date of use and the number of uses (the IP address itself and the content of any text entered are not included in this record). Where RESTO-PAAN is tried without registration, to prevent repeated use from the same device or connection, we record the device identifier and the IP address converted into a form from which they cannot be restored (hash values).
Language setting, currency setting, display settings such as text size and theme, country of stay/residence/origin, year of birth, gender; and ingredients you would rather avoid, dining preferences and similar information.
Your approximate location at the time of a menu translation, collected only where you have granted permission on your device. To resolve a place name (country, region, municipality, district), we transmit the location coordinates we obtain to a map service provider (Google Maps Platform) on the web version, and on the iOS and Android apps we query the place-name resolution function provided by the device’s operating system (provided by the operating-system provider, such as Apple or Google). The place names we store are limited to country, region, municipality and district level; we do not store street-level or other detailed addresses. The location data we store and analyse is rounded to a grid of roughly one square kilometre and does not identify a precise address or your home. Resolved place names are used to display translation results and for the statistical analysis described below. In addition, on completion of a menu translation we may collect the original dish names on the menu together with the rounded grid reference, in a form that does not include your name, email address or the like (the user identifier is one-way hashed). Translation results, prices, descriptions, preferences, order contents and images are not included in this data. We use it for statistical analysis of dish and menu trends by area ("PAAN-DATA").
Where you use the nearby restaurant search, and only where you have granted permission on your device, we transmit your location coordinates at that moment to a map service provider (Google Maps Platform / Places) to find restaurants nearby. These coordinates are used only for that search and we do not store them.
Whether or not you have granted location permission, when you translate a menu we collect your device's time zone setting and (on Android devices) the country of the mobile network you are connected to, and use them to estimate the country in which you are using the Service and for statistical analysis. We do not use this information to estimate your location more precisely than the country. In addition, to display a default travel destination (the country of the menu), when you open the camera screen we estimate the country in which you are using the Service from the IP address of your connection. This estimate is limited to country level, and we do not store the IP address or the estimated country for this purpose (the country you confirm as your destination is stored as part of your translation history).
Where you register a restaurant name on a translation result, we obtain the identifier, name and address of the restaurant selected from the candidates offered by a map service provider (Google Maps Platform / Places) and store them together with the history of that translation. In that case, we separately accumulate the information on that restaurant, the translation result for that menu (including dish names, descriptions and prices), the cuisine genre and the rounded grid reference and place name described above, with the user identifier one-way hashed, for the analysis of menu trends by restaurant and by area. The statement above that certain items “are not included in this data” does not apply to this accumulation associated with registering a restaurant name. Where you enter a restaurant name freely without selecting it from the candidates, this accumulation does not take place.
Where you use the sharing feature, a share URL containing a hard-to-guess string is issued for that translation result. Anyone who knows the URL can view that translation result (dish names, prices, restaurant name, approximate area, etc.) without logging in. A share URL can no longer be viewed once the period we specify (currently 90 days) has elapsed since it was issued or since the sharing operation was last performed. If you perform the sharing operation again for the same translation result, that period is extended with the same URL. Even after it can no longer be viewed, the information for sharing may remain on our servers until you delete your account or data. The share URL does not include cautions, preferences or profile information. Note that deleting an item from your history does not automatically invalidate a share URL that has already been issued. To stop sharing, please contact the point in Section 1.
Order-related actions in the app (adding to candidates, showing to staff, payment, etc.) and order history (dishes selected, quantities, approximate amounts), information you save such as memorable dishes and short notes, and any ratings or feedback you give on translation results (optional). Where you translate a photo selected from your photo library, the date and time the photo was taken and its time zone as recorded in the photo (used to display the date and time in your history). On the iOS app, where a photo records the place it was taken, the device may query Apple’s map service with the location coordinates solely to determine the time zone of that place. We do not obtain or store those location coordinates.
Where you scan a store code or QR code to import a published menu from a partner restaurant (a restaurant using RESTO-PAAN, etc.), the identifier of that restaurant and the imported menu content (translated text, etc.). The menu text is stored as it stood at the time of import. Dish images are displayed by reference (link) to the image provided by the partner restaurant; we do not copy or store them.
In the MENU-PAAN apps, when use without registration (guest use) begins and when a sign-up bonus is granted, in order to confirm that the use comes from a genuine device and app and to prevent the same bonus from being received more than once, we obtain the identifier assigned to the device for each app vendor (identifierForVendor on iOS, ANDROID_ID on Android) and information for confirming the authenticity of the device (a token issued by Apple’s DeviceCheck or Google’s Play Integrity). We send that token to Apple or Google and receive the result of the check; we do not store the token itself, only a value for matching (a one-way hash). On iOS, information indicating whether guest use has begun and whether a sign-up bonus has been granted for the same device may be recorded with and referred to at Apple through Apple’s DeviceCheck mechanism. This information is not used to deliver advertising.
Information showing through which route you started using MENU-PAAN. On the web version, we obtain the route marker attached to the URL of your first visit (the value of src or utm_source) or the host name of the referring site. On the iOS app, to confirm whether the installation came via Apple’s advertising (Apple Ads), information issued by Apple on the device is sent from the device to Apple, and we obtain the campaign and keyword identification numbers of the advert received from Apple. On the Android app, we obtain the install referrer information provided by Google Play (the route marker and whether the installation came via Google Ads). We store this information, on the first occasion only, in association with your account (or, for guest use, the record of that use). We do not obtain advertising identifiers (IDFA, advertising ID) for this purpose.
Restaurant name, category and genre, contact details, location and map information (place data and addresses obtained through Google Maps Platform / Places), store code, restaurant logo and other images the restaurant registers for publication to its guests.
Tax rate and tax treatment, service charge, cover charge and other display and billing settings.
Information a guest voluntarily enters in the viewing and ordering-support features of RESTO-PAAN in order to communicate it to restaurant staff, such as ingredients they would rather avoid. Where a guest selects that they have an allergy or that they need to avoid even trace amounts, that selection is merely displayed as a set sentence on the guest’s device, and we do not store it. Text entered is sent to the AI services in Section 6 for translation into the restaurant’s language. We do not link that text to information that identifies the guest, and do not store it except where it is held temporarily for translation processing.
We also record views of the customer-facing screens (date, menu, display language, device type), dish selections, use of links to reviews, and ordering operations (date and time, display language, dishes, quantities, amounts) in a form that does not identify the guest, and use these records to provide statistics to restaurants and to improve our Services.
Where you apply for the RESTO-PAAN menu registration service: the restaurant name, the name of the person in charge, telephone number, email address, the address to which the information card is to be sent, and materials you send us for registration such as menus (photographs, PDFs, paper documents, etc.) and images such as logos.
We use information that constitutes personal data for the following purposes.
Where the GDPR applies, we process personal data on the following legal bases: (a) performance of a contract with you (providing the Service you request); (b) your consent (e.g., optional profile and preference data, analytics cookies (if introduced), approximate location, marketing) — which you may withdraw at any time; (c) our legitimate interests (securing and improving our Services, preventing fraud, training and improving models on data we hold, and statistical analysis using non-identifying data), balanced against your rights; and (d) compliance with a legal obligation.
We operate and develop several services, including in the food and dining field. We may use information obtained or generated through one service (in particular menu and dish data such as dish names, descriptions, prices, images, tags and automatically generated keywords, and translations of it) to provide, improve and develop other services we operate or may provide in the future, and may integrate it for those purposes.
All of these are operated by the same entity (PAAN Co., Ltd.), so such use does not constitute provision to a third party. We handle the data in accordance with this Policy when using it across our Services.
We use the following external services and infrastructure to provide our Services and may transmit and store information with them as necessary. Their handling of information is governed by each provider's own terms.
The “reference images” feature of our Services opens, only when you operate that feature, the image search page of a search service provided by a third party (DuckDuckGo) in the in-app browser or a new tab, using the dish name (including the restaurant name, where one has been registered) as the search term. In that case, the search term and your device’s IP address, browser information and the like are sent directly from your device to the provider of that search service. We do not include information that identifies your account or information on your preferences in the search term. The handling of information by that search service is governed by its provider’s terms.
We do not provide personal data to third parties without your prior consent, except:
We may outsource all or part of the handling of personal data to the extent necessary to achieve the purposes of use, and we exercise necessary and appropriate supervision over such processors.
Our principal database and storage infrastructure (Supabase) is located in Japan (Tokyo region).
By contrast, among the external services in Section 6, the AI services, authentication and hosting infrastructure may be provided by companies located outside Japan, including the United States, and personal data may therefore be stored on or transmitted to servers of companies abroad. Where we provide personal data to a third party in a foreign country, we take the information-provision and other measures required by the APPI. Where the GDPR applies, transfers outside the EEA/UK are made on the basis of appropriate safeguards such as the European Commission's standard contractual clauses. Information on data protection regimes in each country is available from the Personal Information Protection Commission of Japan and similar authorities.
Our Services use cookies and browser local storage to keep you signed in, remember display settings, cache dictionaries and screen content, and understand usage. You can disable these in your browser settings, but some features of our Services (such as staying signed in) may then be unavailable.
As at the last-updated date of this Policy, we do not use Google Analytics or any other third-party analytics cookies in MENU-PAAN. If we introduce them in future, we will amend this Policy in advance and will use analytics cookies only where you have given your consent.
On the RESTO-PAAN website (the restopaan.com home page, its language versions, and the news, video and press pages), we use the Google Ads tag provided by Google LLC to measure the effectiveness of our advertising. When you view these pages, information is transmitted from your device as follows.
This transmission takes place only when you view the website pages listed above. It does not take place in the RESTO-PAAN owner app (the web version and the smartphone apps), or on the menu screens that customers open from a QR code or similar. We do not send information that directly identifies individuals, such as names or email addresses, to Google LLC.
The use of Google Fonts to display typefaces on those screens is as described in Section 6.
To understand how our websites are viewed (the public pages of menupaan.com, restopaan.com and paan.co.jp, such as the introductory, pricing and news pages), we record on our own servers the page viewed, the display language, the referrer, the code indicating the source of the visit (utm_source), taps on certain buttons on the page, views of materials we distribute, the country (estimated from the IP address), the type of device and operating system, and the date and time of viewing. This measurement does not use cookies or local storage. We do not store the IP address itself; to remove duplicates within the same day, we store a value converted from the IP address in a form that cannot be restored and that differs each day. Codes indicating the source of a visit include those attached to links in emails and other communications we send, and we may thereby learn which recipient of our communications viewed the site. We use these records for statistical analysis of how the sites are viewed, to understand responses to our communications and to detect unauthorised access.
We take organisational, personnel, physical and technical measures that are necessary and appropriate to prevent leakage, loss or damage of the information we handle, including encryption in transit (HTTPS / TLS), least-privilege and row-level access control on the database, hashed storage of credentials, and a design that does not store payment details on our servers. Where we use infrastructure provided by companies in foreign countries (including the United States), we take these measures with an understanding of the personal-data protection regimes of those countries.
We retain information for the period necessary to achieve the purposes of use and, when it is no longer needed, erase or anonymise it by appropriate means. You may request deletion of your account and related data through the account-deletion feature in our Services or through our contact point. On withdrawal we promptly delete your personal data, except the information listed below (deletion of stored images may take several days after the withdrawal procedure). (1) Information we are required by law to retain (transaction records, etc.). (2) The minimum information necessary to prevent the same free bonus from being obtained more than once and other unauthorised use (a value converted from your email address in a form that cannot be restored, a value identifying the device that received the bonus, and the date and time it was granted). We do not use this information for any purpose other than the above. (3) Statistical information processed so as not to identify individuals. Where you withdraw from only one of MENU-PAAN and RESTO-PAAN and keep your account, your account information (email address, credentials and profile avatar) is retained until the account itself is deleted.
Where you delete history (translation results, order history, etc.), that history ceases to be accessible in our Services at the time of the deletion and is then physically deleted from our servers within 90 days at the latest. However, the processing records we create to process translations (including the translation result, a copy of the settings applied at the time of translation such as language and ingredients to avoid, the approximate location grid, the processing date and time, and the app version used) are retained after the history is deleted for as long as the account exists, for investigating defects, managing usage and preventing unauthorised use, and are deleted on withdrawal. Photographs of menus are deleted once 30 days have elapsed since the translation was completed.
Information on applications for the menu registration service (restaurant name, name of the person in charge, telephone number, email address, delivery address, materials received, confirmation materials, and records of our logging in to the account on the user’s behalf) is retained, even after the application is cancelled or the registration service is completed, for three years from the date of completion of the registration service or cancellation of the application, in order to respond to enquiries and requests for corrections, to keep records of transactions and to fulfil legal obligations, and is erased thereafter. This information is not erased automatically when you delete your account for the Service. If you wish it to be erased, please contact the point in Section 1.
You may request notification of the purpose of use, disclosure, correction, addition, deletion, suspension of use, erasure, and suspension of third-party provision of your personal data. Where the GDPR applies, you also have the rights of access, rectification, erasure, restriction, data portability, and objection, and the right to withdraw consent at any time. To exercise these rights, contact us at the point in Section 1. We will verify your identity and respond without undue delay in accordance with law. If you are in the EEA/UK, you also have the right to lodge a complaint with your local data protection supervisory authority.
Our Services are intended for users aged 13 and over. We do not knowingly collect personal data from persons under 13. We do not have a procedure for verifying age at registration, but if we learn that we have collected personal data from a person under 13, we will delete it promptly.
We may amend this Policy in response to changes in law or in our Services. For material changes we will give notice within our Services or on this page; the amended Policy takes effect when posted here.
The Japanese text of this Policy is the authoritative version. Where a translation into English or any other language is prepared for reference and there is any discrepancy between the Japanese version and the translation, the Japanese version prevails.
For enquiries or complaints regarding this Policy or the handling of personal data, contact us at the point in Section 1.