Legal
Privacy Policy
- Version
- 1.1
- Effective Date
- August 19, 2026
- Last Updated
- August 19, 2026
This Privacy Policy describes how Site Control Occupancy (“the service”, “we”, “us”) handles information when you use this QR-based area movement and occupancy system. Site Control Occupancy is operated by Kota Miyazaki under the name Miyazaki Industry.
Section 1
Introduction
Site Control Occupancy is a web system used at facilities, construction sites, and similar workplaces. People on site scan a QR code to record that they have moved into an area. Authorized administrators can then see area movement records and current occupancy (how many people are currently recorded in each area).
Site Control Occupancy is operated by Kota Miyazaki under the name Miyazaki Industry. Miyazaki Industry is a brand name. It is not described here as a registered company, and this policy does not list a company registration number, tax number, operator address, or operator phone number.
This policy applies to Site Users who scan QR codes, and to information processed so that administrators can manage occupancy and safety. Administrator accounts are separate from Site User profiles.
Section 2
Information We Collect
We aim to collect only information needed to operate occupancy management, identify returning Site Users, support site safety, and keep the system secure. We do not ask for unnecessary personal information.
Depending on how you use the service, we may collect:
- Name
- Company
- Mobile Number
- User Type (when an administrator records one)
- Current Area
- Movement History
- QR Point used
- Movement date and time
- Browser identification token
- Basic technical information necessary for security and operation, such as limited request metadata or user-agent information associated with a movement record
We do not require government ID numbers, payment card details, or a list of contacts. We do not currently collect GPS coordinates. See Section 6.
Section 3
How We Use Your Information
We use the information described above for the following purposes:
- Identify Site Users
- Remember returning users on the same browser, where storage is available
- Record area movements
- Calculate current occupancy
- Support site safety
- Support emergency response
- Allow authorized administrators to contact users when necessary
- Detect incorrect or suspicious movement records
- Maintain system security
- Improve system reliability
Section 4
Mobile Number
Your Mobile Number is collected because Site Users do not use a password. It helps the service reconnect you to the correct profile if this browser does not remember you.
We may use Mobile Number for:
- Account recovery
- User identification support
- Emergency contact where appropriate
SMS authentication is not currently required. Public users cannot see another user’s full Mobile Number. During account recovery, candidates are shown with a masked number, for example •••• 4567.
Section 5
Browser Identification
After you register, the service may store an identification token in this browser (for example in localStorage or similar browser storage). On a later visit, the service can use that token to recognize you so you do not have to enter your details again.
This identification information is not a smartphone IMEI, serial number, or other hardware identifier issued by the device manufacturer. It is a token created by this service for this browser.
The token can be lost if you delete browser data, use private or incognito browsing, change devices, switch browsers, or block site storage. Agreeing to this Privacy Policy does not guarantee that the browser can save the token. If the token cannot be saved, you may need to use account recovery.
Section 6
Movement and Location Information
This service does not track you with GPS. It records area movement based on the QR Point you scan. A movement is an area-to-area record, for example Ground Floor → B2, or B2 → B3.
Current occupancy is calculated from the area last recorded for each Site User, not from continuous location tracking.
This service does not currently collect GPS or device geolocation coordinates. If GPS or similar location tracking is added in the future, this Privacy Policy will be updated before that feature is used to collect such data.
Section 7
How We Share Information
Site User information is not published to the general public. Other Site Users cannot browse a directory of names, companies, mobile numbers, or movement history.
Authorized administrators may access information only as needed for occupancy management, site operations, safety, emergency response, security, and related administration. Access is controlled by role-based permissions.
We do not sell personal information to third parties or Data Intermediaries.
We disclose personal information to third parties or Data Intermediaries only as needed to achieve the purposes described in Section 3, and only to the extent necessary for those purposes. This includes service operators used to host and run the system. Recipients are required to handle the personal information under appropriate confidentiality obligations.
We may also disclose personal information where disclosure is required by law, and only to the extent required.
Unnecessary sharing is avoided.
Advertising, where enabled, is described in Section 12. It does not involve providing Site User names, mobile numbers, company information, movement records, or browser identification tokens to advertising providers.
Section 8
Data Retention
Site User personal information and movement records will normally be deleted one month after the system ceases to be used for the relevant project or site.
If specific records need to be preserved in connection with an incident, claim, dispute, investigation, legal requirement, or similar legitimate need, only the relevant records may be retained separately for as long as reasonably necessary for that purpose. An incident or similar need is not used as a reason to retain all Site User information for a long period.
Consent records (which policy version you agreed to, and when) are stored separately from movement history so that agreement history can be kept without mixing it into occupancy logs.
Section 9
Data Security
We implement reasonable security measures appropriate to a system of this kind. These may include:
- Authentication for administrator accounts
- Role Based Access Control
- Database access control
- Secure tokens for Site User browser identification
- Row Level Security
- HTTPS
No method of transmission or storage is completely free of risk. We do not promise that information cannot be accessed, disclosed, altered, or destroyed. Please use the service on a trusted device and do not share a remembered browser profile with someone who should not use your identity.
Section 10
User Rights and Requests
Depending on the laws that apply to you, you may have the right to request access to, correction of, or deletion of personal information we hold about you, or to ask a related question. We will consider requests in line with applicable law and operational needs (for example, some records may need to be retained for safety or legal reasons).
To make a request, please use the Contact page.
Section 11
Cookies and Similar Technologies
We may use cookies, localStorage, and other browser storage. These technologies are not all used for the same purpose.
Necessary storage is used to operate the occupancy system. Examples include:
- Site User identification token
- Administrator authentication session
- Security-related storage
- Preferences that are needed for the service to function
Optional / advertising storage is different. If a third-party advertising provider is shown, that provider or its partners may use cookies, similar storage, or advertising identifiers for their own advertising technology. Agreeing to this Privacy Policy and the Terms of Use is not the same as giving advertising-cookie consent. Advertising consent, where required, is handled separately and does not block QR scanning, user identification, Confirm Move, or movement registration.
Clearing browser data, using private browsing, or blocking storage may affect necessary identification even if you have agreed to this policy.
Section 12
Advertising
The service may navigate to a dedicated advertising subdomain after a movement has been recorded, where a 320×50 banner from a third-party advertising provider may be shown on a generic completion page. Advertising scripts are not loaded on the main application origin while a person is entering a name, company, or mobile number, during account recovery, or before Confirm Move has succeeded. Administrator, login, MFA, and API pages do not load advertising scripts. Home, About, How It Works, FAQ, and Resources are selected public informational pages and do not currently load this banner. Contact, Privacy Policy, Terms of Use, Limitations, and error pages also do not load it. Advertising is independent from movement registration and occupancy calculation. You can use the core QR movement features even if a banner is unavailable, blocked, or fails to display.
This service does not provide Site User names, mobile numbers, company information, movement records, current occupancy information, or browser identification tokens to the third-party advertising provider as part of the occupancy application. The advertising page is served from a separate hostname and does not receive those application fields. Advertising networks may still collect technical information through their own scripts, cookies, or similar technologies — for example IP address, user-agent, or advertising identifiers — subject to their policies and to any consent rules that apply in your region.
This service does not use advertising consent as a substitute for Privacy Policy or Terms of Use consent.
If a specific advertising-provider policy URL is published later, it will be added to this section through configuration. Occupancy recording does not depend on advertising being available.
Section 13
Changes to This Privacy Policy
We may update this Privacy Policy from time to time, for example when features change, when retention rules are set, or when legal requirements become clearer. The version number and effective date are shown at the top of this page.
If the current Privacy Policy version is newer than the version you last accepted, the service may ask you to review the updated policy and agree again before you continue with movement confirmation.
Section 14
Contact
Privacy questions may be sent to Kota Miyazaki at fczakimiya.pc@gmail.com.
You can also use the Contact page. Contact details are configured by the operator and may be updated without rewriting this entire policy.
