SoloBox

Privacy Policy

中文

Version: V1.2 Last updated: September 5, 2026 Effective: September 5, 2026

Chengdu Tianfen Technology Co., Ltd. (成都天份科技有限公司, "we," "us," or "our") operates SoloBox. We value the security of your personal information and privacy and process personal information in accordance with applicable laws and regulations of China.

Translation notice

This English version is provided for convenience. If it differs from the Chinese original, the Chinese version will prevail to the extent permitted by applicable law.

Key summary

SoloBox provides digital file storage, secure notes, Sentinel Protocol, and Time Capsule features. We do not read your contacts, precise location, SMS messages, or call records for advertising profiles. Beneficiary email addresses and telephone numbers are entered by you and are not read from your device contacts.

Please pay particular attention

Recovery phrases, private keys, unlock credentials, uploaded files, and secure notes may constitute sensitive personal information. The file upload flow in version 1.0.1 should not be understood as providing end-to-end encryption by default. Files may be uploaded in their original form to our servers and IPFS storage providers. You should consider a file protected by the corresponding encryption only when the app expressly indicates that encryption is enabled and you properly safeguard the key.

IPFS uses content addressing. After a file is copied or cached by a third-party node, unpinning it from our node or Pinata may not remove every third-party copy. Do not upload state secrets, unlawful content, or another person's information that you have no right to process.

1. How We Collect and Use Personal Information

1.1 Creating, restoring, and unlocking a vault

When you create or restore a vault, we process your recovery phrase, random salt, key-derivation parameters, recovery-phrase verification digest, vault identifier, and access token to identify the vault, restore access, and authenticate requests. The recovery phrase is transmitted to the server over an encrypted transport channel to calculate a verification digest. The business database stores the verification digest rather than the recovery phrase in plaintext.

Private keys, PINs, pattern passwords, master passwords, and recovery phrases are stored locally according to platform capabilities. iOS primarily uses the system Keychain, while Android private keys are wrapped with Android Keystore. On Android, the recovery phrase and some unlock credentials may be stored in app-private storage; hardware-backed encryption cannot be guaranteed on every device and operating-system version. Biometric unlocking is performed by the operating system. We receive only success, failure, or error status and do not obtain fingerprint or facial templates.

1.2 Files, thumbnails, and secure notes

When you upload, organize, preview, download, or delete files, we process the content you actively select together with the file name, folder path, file size, file type, thumbnails, content digest, CID, upload-task identifier, upload status, and creation time. Small and medium preview images are generated on the device for images and videos. Video source files, thumbnails, and upload queues may be cached locally for preview or resumable transfers.

When you create a secure note, we process the title, body, attachments, and related metadata that you provide to store and display the note. The current version does not guarantee end-to-end encryption by default for uploaded files or secure notes.

1.3 Sentinel Protocol and Time Capsule

When you use Sentinel Protocol, Inheritance Guard, or Time Capsule, we process the protocol or capsule name, linked files, beneficiary or notification-recipient email addresses, telephone numbers with country/region codes, trigger period, check-in time, delivery date, time zone, claim period, notes, and settings to save rules, calculate timing, display status, and execute notifications or delivery when the configured conditions are met.

Before providing another person's email address or telephone number, you must ensure that you have a lawful basis for processing it and have explained the purpose to that person. Do not provide third-party personal information unrelated to the feature.

1.4 Operations, security, and troubleshooting

To provide network connectivity, authentication, compatibility, and troubleshooting, we and the DCloud App Engine may process IP address, network type, device brand and model, operating system and version, screen parameters, language, time zone, app name, package name, app version, anonymous device identifiers, launch time, memory usage, request time, API status, and crash stack. We do not use this information for targeted advertising.

Android device and Wi-Fi information read by this app: After you agree to this Privacy Policy, when the app runs and queries device or network status, its embedded runtime components automatically invoke Android system interfaces to read the device MAC address, Wi-Fi network name (SSID), and Wi-Fi connection state. The MAC address supports device identification and runtime compatibility checks. The SSID and Wi-Fi connection state identify the current network connection, check network availability, and help troubleshoot upload, download, and connection failures. A MAC address identifies a network interface; an SSID is the name of the current Wi-Fi network. Access is limited by the operating-system version and system restrictions; fields that the system does not permit are not obtained. This describes the app invoking system interfaces and does not mean these fields are submitted as DCloud engine analytics data.

1.5 Push notifications

The current Android package includes the Getui Message Push SDK for Android (com.igexin.sdk), developed by Daily Interactive Co., Ltd. (每日互动股份有限公司). After you agree to this Privacy Policy, during initialization, push registration, and push-channel maintenance, the SDK automatically invokes system interfaces to collect device platform, manufacturer, brand, model, operating system and version, app information, OAID, AndroidID, IP address, carrier information, DHCP, Wi-Fi connection information (including the Wi-Fi network name, SSID, and the Wi-Fi access-point identifier, BSSID), and push-client identifiers. The SSID is the Wi-Fi network name; the BSSID is the MAC address of the Wi-Fi access point. This device and network information is used to generate and recognize the push-target identifier (CID) and device identifier (GID), establish and maintain push connections, deliver service notifications accurately, and troubleshoot push failures, not for targeted advertising. The SDK processes information needed for push registration and message delivery through its service interfaces; see the Getui Privacy Policy for its processing rules. Fields that the system does not permit are not obtained.

Push-related components also include the Mobile Intelligent Terminal Supplementary Device Identification System Unified Calling SDK (com.bun.miitmdid), developed by the China Academy of Information and Communications Technology. Its purpose, scope, and processing method are described separately in the next section. We initialize push components only after obtaining your consent. You may disable notification permission in system settings.

1.6 Express disclosure of the Mobile Intelligent Terminal Supplementary Device Identification System Unified Calling SDK

SDK name: Mobile Intelligent Terminal Supplementary Device Identification System Unified Calling SDK (com.bun.miitmdid)

Developer: China Academy of Information and Communications Technology

Purpose: To obtain open anonymous device identifiers for push-channel identification, message delivery, related security, and troubleshooting.

Trigger: Only after you agree to this Privacy Policy, when the app initializes push-notification capabilities and invokes the SDK interface.

Information that may be processed: Device manufacturer, model, brand, network operator name, app package name and signature information or the corresponding app-store APPID, as well as OAID, VAID, and AAID.

Method and retention: According to the SDK's official policy, the SDK itself does not request device permissions. The relevant information is used only for local determination, is not stored or transmitted over the network by the SDK, and is destroyed immediately after the interface operation is completed.

SDK privacy policy: https://www.msa-alliance.cn/col.jsp?id=122

1.7 Customer support and complaints

When you contact us by email, we process your email address, message content, attachments, and communication records to verify identity and handle inquiries, complaints, personal-information rights requests, and security incidents.

2. Sensitive Personal Information

Sensitive personal information involved in SoloBox may include recovery phrases, private keys, PINs, pattern passwords, master passwords, biometric verification results, and identity documents, financial accounts, health information, movement tracks, information about minors, or other sensitive information contained in uploaded content. We process such information only to the extent necessary for features that you actively choose. Processing sensitive personal information may create heightened risks to personal safety, property, or dignity. Upload cautiously and safeguard your recovery phrase and unlock credentials.

3. Device Permissions

Permission or system capabilityUse caseMay you refuse?
Access to photos, images, videos, audio, and filesAllows you to select files for upload, generate thumbnails, cache, and preview. We do not enumerate all files when you have not selected them.Yes. You will be unable to select the corresponding files.
Write to photo librarySaves an image or video that you actively download to the system photo library.Yes. You will be unable to save it to the photo library.
Camera and flashlightTakes photos and scans QR codes.Yes. Features that do not rely on the camera remain available.
Fingerprint, Face ID, or system biometricsPerforms local identity verification and unlocking. Templates are managed by the operating system; SoloBox receives only the verification result.Yes. You may use another unlock method.
Network, Wi-Fi state, and network switchingReads Wi-Fi connection state and SSID to check connectivity and troubleshoot upload/download connections; the Getui SDK also reads the access-point identifier BSSID to establish and maintain its push channel. Device MAC-address processing is described in section 1.4.Required for online services. You may stop network communication by disabling network access.
Notifications, vibration, and wake lockReceives service notifications, reports task status, and maintains necessary upload or download tasks.Notifications may be disabled, but messages may not arrive promptly.
Device stateThe distribution configuration includes device-state access that may be used by the runtime or push components for compatibility and channel identification. Business code does not read call content.You may manage it in system settings. Some push or compatibility capabilities may be affected.
Clipboard write accessWrites the recovery phrase only when you tap Copy and attempts to clear it after a delay. It is not used to read clipboard content.Yes. You may record it manually.

You may manage permissions under Settings > Apps > SoloBox > Permissions on your device. Withdrawal does not affect processing lawfully performed before withdrawal.

4. Entrusted Processing, Sharing, Transfer, and Public Disclosure

We do not sell your personal information. To provide runtime, push, and storage functions, we may provide the minimum necessary information to entrusted service providers, including DCloud, Message Push SDK for Android, the Mobile Intelligent Terminal Supplementary Device Identification System Unified Calling SDK, Pinata, and public IPFS gateways. The specific recipients, purposes, information types, and links are listed in the Third-Party Information Sharing List.

Except in the following circumstances, we will not provide your personal information to another personal information processor:

If a merger, division, dissolution, bankruptcy, or similar event results in a transfer of personal information, we will inform you of the recipient's name and contact details and require the recipient to remain bound by this Policy. If the purpose or method of processing changes, consent will be obtained again as required by law.

5. Cross-Border Processing

Cross-border risk notice

Pinata, some public IPFS gateways, and Google Fonts may be operated by entities or servers outside the People's Republic of China. When related features are used, file content, thumbnails, CIDs, file names, IP addresses, User Agents, and request times may be processed by overseas recipients. Before providing personal information overseas, we will inform you as required by law of the recipient, purpose, method, type of information, and method for exercising rights, and obtain separate consent through an independent prompt or other appropriate means. Personal information should not be provided overseas until the applicable legal conditions have been satisfied.

6. Storage Location, Retention, and Deletion

Business databases and logs directly controlled by us are, in principle, stored within the People's Republic of China. The storage location of data involving Pinata, public IPFS gateways, or Google Fonts may vary with the service provider's network nodes.

We retain information for the shortest period necessary to achieve the relevant purpose. Vault and protocol data are generally retained until you delete them or terminate the service. Trash files remain until you permanently delete them or they are cleared under product rules. Upload chunks are deleted after merging, cancellation, or the applicable cleanup period. Customer-support records are retained as necessary to handle requests and comply with legal obligations. When a retention period expires, we delete or anonymize the information unless otherwise required by law.

Data copied, pinned, or cached by other IPFS nodes may be outside our control. We can delete business indexes and unpin data from nodes that we own or control, but cannot guarantee removal of every third-party copy.

7. How We Protect Information

We use measures such as HTTPS/TLS transmission, access-token authentication, access controls, log auditing, backups, and security-incident response. We endeavor to store private keys using platform capabilities such as the system Keychain or Keystore. However, local-storage strength varies by platform, and the current version does not guarantee by default that uploaded files are end-to-end encrypted ciphertext.

No internet or distributed-storage system is absolutely secure. If personal information is or may be leaked, altered, or lost, we will take remedial measures as required by law, notify you by app notice, email, announcement, or another appropriate means, and report to the competent authorities where legally required.

8. Your Personal Information Rights

Within the scope prescribed by law, you have the right to be informed, decide, restrict or refuse processing, access, copy, correct, supplement, and delete personal information, withdraw consent, and request an explanation of processing rules. You may manage files, trash, protocols, and permissions in the app, or email support@solobox.com.cn to submit a request.

To protect your vault and the rights of others, we may first verify your identity. We generally respond within 15 business days. Deleting the app removes local data only and is not the same as deleting server data. To terminate the vault service and delete server data, use the applicable in-app function or contact us at the address above.

9. Protection of Minors

SoloBox is primarily intended for adults with full civil capacity. Users under 18 should use it only after a guardian has read and agreed to this Policy and the Minor Protection Rules. A child under 14 must obtain guardian consent before using the service. If we discover that children's personal information has been processed without valid guardian consent, we will delete it or take other legally required measures.

10. Updates to This Policy

We may update this Policy when business features, processing methods, third-party services, or laws and regulations change. Material changes will be prominently presented through an in-app prompt, notification, or website announcement, and we will obtain consent again where required by law. Previous versions will be archived as appropriate.

11. Contact Us

Personal information processor: Chengdu Tianfen Technology Co., Ltd. (成都天份科技有限公司)

Registered address: No. 1, 15th Floor, Unit 1, Building 3, No. 10 Keyuan 2nd Road, Chengdu High-Tech Zone, Chengdu, Sichuan, China

Privacy contact: support@solobox.com.cn

Website: https://www.solobox.com.cn