LATICX
Personal Information Collection List
This list explains the personal information that the LaticX app may collect, use, or process in different feature scenarios. It should be read together with the LaticX Privacy Policy and the Third-Party Information Sharing List.
1. Notes
- LaticX is an AI NAS management app with a local-processing architecture. Your personal files, photos, videos, recordings, documents, and local AI processing content are stored and processed on your NAS locally.
- Cloud services are used for accounts, remote access, cross-network connection, notifications, security operations, analytics, crash diagnostics, and customer feedback.
- The actual data processed may vary depending on your device, operating system version, region, account status, and features you enable.
2. Personal Information Collection and Processing List
| Scenario | Data that may be processed | Cloud upload | Required | Purpose and impact if disabled |
|---|---|---|---|---|
| Account registration, login, and remote access | Phone number, email address, verification code, nickname, avatar, account status, login records, IP address | Yes, for cloud account and security verification | Required for remote access, cross-network connection, and notifications; local device discovery, binding, and offline LAN use do not require a phone number or cloud account | Used to create a cloud account, verify identity, and secure remote access. Without it, you cannot register or log in to a cloud account, or use remote access, cross-network connection, notifications, and other features that depend on a cloud account. This does not affect discovering, binding, or managing a NAS on your local network, or using supported offline features. |
| Device binding and NAS management | Device ID, serial number, device model, firmware version, network status, binding relationship, device operation logs | Local discovery, binding, and LAN management are not uploaded to the cloud. When remote access, a cloud account, or notifications are enabled, only machine and operating status data needed for device services is uploaded. | Required for local device discovery, binding, and NAS management. Remote status synchronization and diagnostics are needed only when related cloud features are enabled. | Used to identify devices, display status, diagnose issues, and maintain service stability. Disabling local device discovery or connection permissions may prevent binding or managing a local device. Not providing a phone number does not affect local device binding. |
| Remote access and WebRTC connection | Account identifier, device ID, signaling information, ICE candidates, network addresses, connection status, relay or tunnel status, necessary access logs | Yes, for establishing and maintaining connections; not stored as cloud file content | Required for remote access and cross-network connection | Used for P2P connection, signaling exchange, network traversal, and fallback relay. Cross-network access will be unavailable if remote access is disabled. |
| File, album, video, recording, and document management | Local file content, file names, paths, thumbnails, indexes, album information, videos, recordings, document content | Not uploaded to the cloud; processed entirely on your NAS locally | Required for local management, search, backup, playback, and organization features | Used to manage files, organize albums, search, back up, and play content on the NAS. You can manage or delete this data on the device. |
| AI assistant, Agent, and knowledge base | Prompts, task context, retrieved snippets, AI results, Agent call records, operation confirmation information | Not uploaded to cloud AI models; processed entirely on your NAS locally | Required for AI assistant, natural language operations, knowledge-base search, and automation tasks | Used to understand requests, retrieve local materials, call NAS features, and return results. AI features will be unavailable if disabled. |
| Cameras and AI recorder card | Camera video, audio, recordings, transcripts, device status, event detection results | Not stored as cloud content or processed by cloud AI. During remote preview, data is transmitted only through the user-initiated connection channel and may pass through relay forwarding where necessary. | Required for camera preview, playback, recording, transcription, and event detection features | Used for live preview, playback, recording management, transcription, and device linkage. Related features will be unavailable if the device or permission is disabled. |
| System permissions | Photos, camera, microphone, notifications, local network, Bluetooth, location, file access permission status and related content | Processed as needed by each feature; permissions are managed by the operating system | Requested only when you use related features | Used for QR-code binding, file selection, album backup, recording, notifications, and device discovery. Denying permissions affects related features. |
| Notifications | Push Token, AAID, RegisterId, APNs Device Token, notification permission status, device model, OS version, notification delivery status | Yes, may be shared with operating system push providers | Required for notification features | Used to send backup completion, device abnormality, remote access, and security alerts. You may not receive timely reminders if notifications are disabled. |
| Analytics and crash diagnostics | Page names, event names, event properties, app version, runtime environment, device model, OS version, crash stack, error logs, anonymous ID or hashed user ID | Yes, only when related services are configured and enabled | Not required for core storage features, but necessary for stability and experience improvement | Used to locate errors, analyze feature usage, and improve product experience. This data is not used to read your local file content. |
| Feedback and customer support | Issue description, contact information, screenshots, screen recordings, logs, device ID, account information, IP address, file paths | Only when you submit feedback or authorize support diagnostics | Not required for core features; missing information may affect troubleshooting | Used to reply to feedback, diagnose issues, handle privacy requests, and improve the product. Avoid uploading sensitive content unrelated to the issue. |
| Security and operations | Access time, operation records, abnormal login records, risk events, network environment information, necessary security logs | Yes, as needed for security operations | Required to protect accounts, devices, networks, and services | Used to prevent unauthorized access, abuse, account compromise, and service issues. Disabling may prevent us from protecting cloud service security. |
3. Local and Cloud Boundaries
- NAS local files, photos, videos, recordings, documents, and local AI processing content are controlled by you. AI assistant, Agent calls, knowledge-base retrieval, and multimodal analysis are processed entirely on your NAS locally and are not uploaded to cloud AI models.
- Remote access, remote preview, or active sharing may transmit related content through a user-initiated connection channel and may pass through relay forwarding where necessary. We do not store it as cloud file content or use it for cloud AI processing, except where required by law or when you actively submit it for feedback.
- Cloud account, remote access, and notification services need to process necessary account identifiers, device identifiers, network connection data, and logs. Local device discovery, binding, and LAN management do not require a phone number or cloud account.
- When P2P connection is unavailable, remote access may use relay or tunnel fallback to maintain connectivity, but this does not change your ownership of local data.
- If we later integrate cloud AI models to process personal data or change personal data processing methods, we will update the relevant policies and obtain necessary authorization where required by applicable law.
4. Updates
We will update this list when LaticX app features, SDKs, permissions, server nodes, or personal information processing methods change, and notify you through in-app pages or other appropriate means.