Privacy notice

Anonymous website and Demo usage analysis

To improve the website and Demo, we record viewed pages, entry clicks, successful connection/use/submission/request/contact-delivery milestones, source category, display language, device class and approximate country/region. A random browsing-session identifier uses an HttpOnly, Secure first-party session cookie; a separate random identifier represents a Demo run. These analytics records exclude names, email, phone, IP addresses, precise location and work content. These records also exclude Firebase UIDs and external analytics identifiers. A temporary Demo linkage is server-only. Events expire after 90 days and linkage after 30 days; physical deletion is asynchronous. This analysis is not consent to promotional email.

Scope and contact

This notice covers the LIVE WORK DEMO PC administrator and Mobile worker screens and their related features, provided by AIELcore. Contact livework@aielcore.com.

Information we handle

We handle Session and device registration identifiers, worker names and display languages; work items, work reports, comments, handovers, business notices, daily reports, shifts, business dates and submission status; and photos, files and related information. Depending on the features used, we also handle location, AI insight questions, answers and supporting information, AI translations and images for photo AI.

We process technical logs such as communications and errors, and information used by Firebase Auth and App Check for authentication and app verification. Browsers also store connection recovery information and unsent input.

Purposes and access

We use information to provide the Demo, connect devices, store and display work records, provide relevant translation and AI assistance, prevent misuse, address faults and improve the service. Work records are shared according to Session roles, recipients and permissions. Personal AI history is separate from business reports.

Photos, location and AI

Check rights, people appearing in photos and the content before sending. Image format conversion does not guarantee anonymisation. Location sharing depends on device permission, settings and work status, and is shown only in authorised views. Accuracy and updates depend on devices and connectivity; continuous tracking and immediate updates are not guaranteed.

For AI processing, questions, necessary work information or conversations, and selected photos may be sent to OpenAI. Translations are kept distinct from the original text. Displaying and searching fixed UI and Help does not call AI. AI answers can be incorrect and do not replace official work records or human judgment.

External services

We use Cloudflare for Web delivery; Firebase / Google Cloud, including Auth, App Check and reCAPTCHA, for authentication, app verification, storage and processing; OpenAI for AI; and OpenStreetMap for maps. Map requests convey the displayed area and communication information to the map provider. Google Analytics is also used on the official site and related pages.

Contact email is received in Zoho Mail and also handled at the configured Gmail forwarding destination. The official site contact form uses Cloudflare Turnstile to help prevent abusive submissions. External services process information for their respective functions. Having particular cloud resources in a Japan region does not guarantee that all processing occurs only in Japan, or that external services retain no information.

Extension requests and enquiries

Email may include your email address, optional name and company, feedback, improvement requests, deployment or customisation enquiries, a requestId and a safe Session reference. We use these to review extension requests, contact you, improve the Demo and product, and respond to enquiries. Contacting us is not treated as consent to advertising or newsletters.

Email composition uses your device’s mail app. The Web app does not determine whether email was sent, and sending email does not approve an extension. Do not send secret QR information or authentication tokens.

Access periods, retention and deletion

The preparation period without a P1 participant is 48 hours from Session creation. If S is the first P1 connection time, normal Mobile access lasts 7 days from S. A request before the original deadline and operator approval can extend it once, up to 14 days from S. The PC read-access boundary and the point when the Session becomes eligible for deletion are 30 days from S. These periods use 24-hour days and are separate from business-day changes in Asia/Tokyo.

Work records and photos are subject to Session cleanup. Physical deletion is asynchronous: reaching a deadline or ending a Session does not mean that all deletion finishes immediately. The 180-day AI history period limits normal reading; it is not a guarantee of complete physical deletion after 180 days. AI history and management information, authentication data, logs, email and device data are handled separately from business Session deletion. We do not guarantee a completion date for deletion of all information, including backups.

Your choices and enquiries

Avoid unnecessary personal or confidential information, and do not share QR or connection credentials. Use photos, location sharing and AI only as needed; do not rely on the Demo as the only copy of important records. Clearing browser data does not itself delete server records. For enquiries about access, correction or deletion, contact livework@aielcore.com.