Privacy Policy

1. Scope

This policy covers NearDock (named “近链” in Simplified Chinese) for iOS, iPadOS and macOS, local browser connections hosted by the app, and this public policy website. The personal information controller is independent developer qinghong meng (“we”), reachable at a617257112@163.com.

NearDock lets nearby devices exchange messages and files. Its core features require no developer account and do not rely on our cloud servers to relay or store your chats, photos, videos or files. Information you choose to send is processed by the receiving device; this does not mean it is collected by a developer server.

2. Information processed

Discovery and connections

To find and identify nearby devices, the app exchanges device names, device types, locally generated and stored discovery identifiers and network information needed to connect over the local network or Bluetooth. You can choose a device name; otherwise the app uses a name available from the system or a default. Nearby devices may see discovery information before pairing. Avoid including personal information in your device name.

Native connections process public-key identities, verification codes and trust records to verify connections and recognize previously contacted devices. The local identity private key is stored in the system Keychain.

Content you send and receive

The app processes text, links, photos, videos and files that you type, select, drag, forward or share through the system, along with content received from the other device. Records may include file names, types, sizes, checksums, message identifiers, timestamps, transfer states, previews and attachment copies. The app does not automatically remove original EXIF, location or other file metadata. Check files before sharing.

Local settings and records

To restore conversations and transfers, the app stores chat history, conversation and device records, attachments, partial files, necessary deduplication identifiers, trust records, and settings such as device name and language on your device. It uses its own storage and does not read system contacts as its conversation list.

Umeng+ startup analytics, crash diagnostics and hang monitoring

The iOS and iPadOS apps integrate Umeng+ to understand app launches, investigate crashes and hangs, and improve stability after you consent. The following applies only to iOS / iPadOS versions that integrate and enable these services. Updating this policy does not introduce reporting into versions without that integration. The macOS app does not integrate Umeng+ and does not perform the Umeng+ startup analytics, crash reporting or hang reporting described here.

• Startup analytics: The Umeng+ Mobile Analytics SDK (U-App) processes launch times, launch counts and session duration, together with app and SDK versions, device model, operating system version, device or app identifiers (such as IDFV where available or an SDK-generated identifier), IP address and network type, to produce launch and activity statistics. IP addresses are also used to infer coarse location, such as country, province or city, for geographic distribution statistics.
• Crash diagnostics and hang monitoring: The Umeng+ Application Performance Monitoring SDK (U-APM) processes crash time, exception type, error information, call stacks, hang performance information and relevant device, system, app version and runtime information to locate issues, assess their impact and verify fixes.

The SDKs collect this information on the device and send it over the internet to Umeng+ services. We can access statistics, crash reports and hang reports through its developer platform. These reports should not be understood as fully anonymous data. Available fields depend on the operating system and integration settings for each platform. If the purposes or scope change, we will update our notice and obtain any legally required consent.

This integration is for startup analytics, crash diagnostics and hang monitoring only, not advertising or advertising attribution. We will not deliberately submit chat text, photos, videos, transferred file contents, identity private keys or browser access credentials as analytics events or custom diagnostic content. Error information may include runtime context such as file paths. We limit unnecessary logs and custom fields to avoid including unrelated personal information.

Local diagnostics and support

The app and operating system may also produce local connection, file-access and error diagnostic logs. If you email support, we receive the address, explanation, screenshots and attachments you provide, for handling your request and necessary follow-up. Do not include unrelated private files or browser access links.

3. Transfers and browser connections

Native device connections use identity verification and verification-code confirmation to establish encrypted sessions. Check the code on both devices and confirm the intended peer when first connecting. Once connected, text can arrive directly and attachments between native devices can be queued for automatic reception.

HTTPS uses a locally generated, self-signed certificate. Your browser may display a trust warning. You can compare its SHA-256 fingerprint with the host screen; the app does not change system certificate trust settings for you. A failed HTTPS start does not automatically fall back to HTTP.

A complete browser link or QR code contains a temporary access credential. Anyone holding it can enter that browser conversation without another host confirmation. Share it only with the intended device and close the entry when finished. The webpage stores connection identity and resume information in browser session storage (sessionStorage). Downloaded files are managed separately by the browser and the selected storage location. Closing an entry does not delete files already saved by the recipient.

4. Permissions and system services

• Local network and Bluetooth: Used to discover and connect nearby devices and host local browser entries. Denying a permission limits the corresponding connection method.
• Photos and videos: On iOS, the app requests photo read access when needed to process selected local media and supports limited access offered by the system. If you decline read access, you can still try sending through the system picker. Saving an image or video to Photos requests add access.
• Files and folders: Used to read files you select or drag in and save files to your chosen location or the macOS Downloads folder. The system may request permission for the relevant location.
• System sharing: The iOS share extension temporarily saves selected content and its target conversation in a local shared container. The main app imports and sends it when opened, then removes the processed pending batch.

You can review or revoke permissions in system settings. If a selected item is still in iCloud, the system may download it over the internet, subject to Apple services and your settings. Opening this policy website contacts a web server; enabled Umeng+ startup analytics, crash diagnostics and hang monitoring also send relevant information over the internet. Offline core transfers do not mean that these system services, analytics and diagnostics services or external webpages never use the internet.

5. Storage, security and deletion

Chat history is primarily stored in local data files, and attachments in the app’s own directories. The current app does not add application-level encryption for all stored history and attachments. Protect your device with its passcode and system security features. System backups, device migration and copies you export are governed by the relevant system or service settings. The app has no developer-operated cloud chat backup or sync service.

Local records remain available for reviewing, reconnecting and resuming transfers. You can manage them with the app’s deletion and storage tools:

• Delete a message or conversation: Removes the associated local records and attachments. Some minimal deduplication identifiers or trusted identity records may remain, including to prevent deleted messages from reappearing. Deleting a conversation does not clear every device identity.
• Clean files: Removes local attachment, temporary and preview copies for the selected conversation while retaining text, the conversation and records such as file names. Cleaned attachments can no longer be previewed or retried from the original record; select the source again or ask the other device to resend.
• Limits: Deletion and cleanup do not recall content on the recipient’s device or remove your originals, exported or separately saved files, system backups or copies in other apps. Uninstalling also does not guarantee removal of all such copies or system Keychain items.

We cannot view, restore or remotely delete chat data held only on your device. Support correspondence is retained only as needed to handle requests and meet necessary legal obligations, then deleted or anonymized when no longer needed.

Submitted startup analytics, crash reports and hang reports are processed and stored by Umeng+ services, separately from local conversation records. We retain relevant information only as long as needed for the stated purposes and legal obligations, and manage it in accordance with service settings and the Umeng+ privacy policy, deleting or anonymizing it when no longer needed. Deleting local conversations, cleaning files or uninstalling does not automatically delete submitted information. Contact us as described in Section 7 to exercise your rights. No storage or transfer method guarantees absolute security.

6. This website and third parties

Umeng+ SDK details

• Service provider: 友盟同欣（北京）科技有限公司 (Umeng Tongxin (Beijing) Technology Co., Ltd.).
• SDK names and purposes: Umeng+ Mobile Analytics SDK (U-App) for startup analytics; Umeng+ Application Performance Monitoring SDK (U-APM) for crash diagnostics and hang monitoring.
• Component included in U-APM: Yueying SDK, provided by 广州市动景计算机科技有限公司, supports crash and hang performance monitoring. Its handling of relevant device, network, timestamp, app and diagnostic information is described in the Yueying SDK privacy policy.
• Processing and information types: SDKs embedded in the app collect and transmit the analytics, device, network, crash diagnostic and hang performance information listed in Section 2 to the service provider.
• Third-party privacy policy: The Umeng+ privacy policy describes its processing rules and rights contact channels.

This policy website and other services

This website provides public documents without login, advertising or analytics scripts, and does not actively set tracking cookies. Serving a page requires processing the IP address and request information. Routine access or error logs may record request time, path, response status and browser information to deliver pages, troubleshoot problems and maintain security. These records are managed for necessary periods and applicable requirements.

Apple’s permissions, Photos, iCloud, App Store and browser services, and other apps you choose as share targets, process information under their own policies. We do not sell your personal information or use chat content for advertising, and the app has no feature that centrally uploads chats for the developer to view. Recipients you choose can separately save and use what you send or forward. Choose recipients carefully.

7. Choices and younger users

You can change your device name, pause discovery, disconnect conversations, close browser entries, manage local records and revoke permissions in system settings. Pausing discovery does not disconnect established sessions; disconnect or close an entry to end communication. For relevant personal information we actually process through support email, website operation or the analytics and diagnostics services described above, contact us to request access, correction, a copy or deletion. We handle requests under applicable law and verify identity only as necessary.

In versions integrating Umeng+, we explain the relevant processing rules and obtain your consent before enabling these analytics and diagnostics services. Startup analytics, crash diagnostics and hang monitoring are not necessary for device discovery, messaging or file transfers. You can email us to request withdrawal of consent, cessation of the relevant processing or deletion of reports. We will explain the process for your app version and, where needed, help you submit a request to Umeng+. Withdrawal does not affect lawful processing already carried out on the basis of consent, and information may still be retained where required by law. Publication of this policy does not itself constitute your consent.

NearDock is not specifically designed for children. Minors should use it with a parent or guardian’s guidance about recipients, content and browser links. Do not send another person’s personal information or private files without lawful authority. Contact us if you believe we have improperly handled a minor’s information.

8. Updates and contact

We may update this policy as features or information practices change, showing the new date and providing an appropriate notice for significant changes. Additional permissions or legally required consent for new features must be handled through the relevant process; this policy does not replace system permission authorization.

Privacy questions and rights requests: a617257112@163.com. Mention NearDock and briefly describe your request. You do not need to send complete conversations or private attachments.