Privacy Policy

1. Who runs this service

For anything about this policy, contact us at info@yuge-zao.com or through the feedback form on this site.

2. What we collect

This service has no accounts and no sign-in. Ordinary browsing never asks for your name, address or phone number. The feedback form lets you optionally add your name and email address alongside your message. What we collect is the following.

Device identifiers such as cookies, and the records of how the service is used, are handled with the care due to information that may relate to an identifiable person under Japanese data protection law.

The identifiers are random strings only. They are not derived from any characteristic of your device, and we do not use fingerprinting.

3. What we do not store

None of the following is kept as usage data.

• Your precise latitude and longitude — it is used only inside your browser to work out distances to restaurants, and is never sent to our servers.
• Your IP address as part of our own usage data — we may use it momentarily to deal with excessive request volume, but it is not kept as usage data.
• The raw User-Agent string — only the four-value device type derived from it is stored.
• The public code in a QR code’s URL — which placement it was is recorded as an internal identifier instead.
• Your enquiry message, name or email — these are never part of usage data. They are stored separately as an enquiry.

Note that serving this site and displaying the map involve outside providers, which may handle the IP address and similar connection information inherent in those requests. See the External Transmission page for details.

4. Why we use it

1. Running and displaying the service — opening status, distances to restaurants, language switching
2. Understanding which features and paths are actually used, so we can improve them
3. Understanding which placements’ QR codes are being used, including reporting back to venues and listed restaurants
4. Responding to enquiries and contacting you where needed
5. Investigating faults and dealing with abuse or excessive request volume

We do not use any of it for advertising, behavioural ad targeting, or profiling, and we have not built the means to do so.

5. Location

Location is the easiest part to misread, so there is a separate page about it. In short:

• Your device location is requested only when you press “Use my location” and allow it in your browser’s own permission prompt.
• Once obtained, it is used inside your browser to calculate distances. It is not sent to our servers and not stored.
• If you arrived from a QR code, the pre-registered position of the venue where that QR is installed is used as the starting point for distances. That is not your device location.

6. Arriving from a QR code

QR codes placed at accommodations, stations, tourist information, the bus terminal and member restaurants each carry a different code. To understand which placement people arrive from, we record an internal identifier, the type of placement, and — for a restaurant’s own QR — which restaurant it belongs to.

The public code that appears in the QR’s URL, and the coordinates of the placement itself, are not stored as usage data.

QR codes are put up in public, so many different people scan the same one. What is recorded is which printed code someone came through — not a measurement of where they were when they scanned it.

7. What you type into the feedback form

A category and a message are required; your name and email address are optional. Without an email address we have no way to reply.

We use what you send to respond, to contact you where necessary, and to deal with abuse. Your message, name and email are never included in usage data.

8. Sending to outside services

Displaying the map causes your browser to contact a map data provider. Which providers, when, and what may travel with those requests is listed on the External Transmission page.

This service contains no advertising or analytics tags or SDKs from other companies. Usage records are received by this service itself and stored in our own database.

9. How long we keep things

Clearing cookies in your browser detaches the identifiers immediately. If you would like an enquiry deleted, contact us at the address above.

10. Keeping it safe

• Traffic between your browser and this service uses HTTPS.
• The cookies used for usage records cannot be read by JavaScript.
• The database has row-level access control enabled, so public pages can only read what is meant to be public.
• The restaurant management screens and our own admin screens are not reachable by ordinary visitors.

11. Sharing with others

We never sell what we collect. We do not share it with third parties except in the following cases.

• Where required by law
• Where it is necessary to protect someone’s life, safety or property and consent is impractical to obtain
• Where a provider handles it on our behalf to run the service — for example our hosting provider or map data provider — under appropriate supervision

We may report to venues and listed restaurants how much their placement’s QR code is being used. Those reports are aggregate figures only; they never include browser identifiers, session identifiers, or any other identifier that could follow an individual visitor.

12. Requests about your personal data

If you would like to be told the purpose of use of your retained personal data, or to request its disclosure, correction, addition, deletion, suspension of use, erasure, or suspension of provision to third parties, contact us at info@yuge-zao.com.

We will verify that the request comes from you and respond in accordance with the law. We will explain the steps and the identity check needed when you get in touch.

13. Changes to this policy

If what we collect or which outside services we use changes, we will update this page. We will say so on the service itself for anything significant.

14. Contact

For questions about this policy or about how we handle personal information, contact Yuge Inc. at info@yuge-zao.com.