SendHop Privacy Policy — iOS Global
Version 1.1.0; effective date: 2026-10-05. Applies to the ios / global release.
Developer: Beijing Chenghan Bowen Education Technology Co., Ltd. Privacy contact: contact@chenghanbowen.com. Package identifier: com.devmate.sendhop.global.
1. Core transfers and local data
SendHop transfers files between nearby devices on the same Wi-Fi or hotspot. No app account or file cloud drive is required. Selected contents, names, sizes and types, and local addresses, device display information and public keys needed for connections, are processed by your chosen peer. In-app device contacts are not the system address book. Device profiles, contacts and transfer history are stored locally. Recipients control saved copies; deleting local history does not delete peer files.
Native transfers use TLS. Browser guest receiving uses local-network HTTP and does not offer equivalent transport encryption. Use trusted networks, verify recipients and do not publicly share receiving links or QR codes. This version does not provide Bluetooth file transfer.
2. Remote pages, voluntary feedback and first-party promotion
Opening legal or feedback pages connects to our HTTPS services, which receive IP address, User-Agent, request time and page parameters. The SendHop H5 entry supplies only product code, platform, region and locale; it does not automatically attach an installation identifier, device details, app version or account. Voluntary feedback text and contact details are used for support; no app account is required. If an attachment control is offered and you choose to upload, feedback storage uses Beijing Alibaba Cloud OSS and an RDS primary in Beijing; this does not mean that every copy, log, backup, or processor is in Beijing. Feedback and support records are retained as necessary for service, security, legal obligations and handling requests; there is no fixed automatic deletion period. Contact the privacy address in this policy for access, correction or deletion requests.
First-party promotion configuration and events are separate network flows. They may include product, platform, region, channel, locale, package, version, installation instance, placement/material identifiers and technical impression, click, redirect or skip results, not transferred files or recipients. The local installation instance is not assigned as a third-party analytics account identity.
3. Advertising, analytics, diagnostics and choices
Production ads, behavioral analytics and automatic crash collection default to off in this version. Optional features can be enabled only when app configuration permits, an applicable lawful basis exists and in-app and relevant system/ad consent requirements are met; ATT or advertising consent does not replace analytics consent. Withdrawal follows the privacy-choice flow below: it stops new advertising requests and disables optional analytics/diagnostics controlled by the app; it does not mean that all SDKs or previously processed data automatically stop or are deleted.
The app does not actively submit transferred file contents, names, absolute paths, contact identities, public keys, QR payloads, session tokens or network endpoints to advertising, analytics or diagnostic services. Optional analytics concerns non-content events such as generic pages, lifecycle and technical outcomes. Automatic crash information may contain exception text, paths or endpoints; automatic diagnostics defaults to off and is controlled by the app's privacy choice and independent diagnostic configuration.
TopOn service entities and processing
The TopOn advertising-services policy dated 2026-07-10 assigns U.S. citizens and entities organized under U.S. law to Ascent Pro Technology Limited, and other cases to TOPON PTE. LTD., subject also to applicable service agreements. This identifies TopOn itself, not every indirect component's recipient.
TopOn describes IP, device/ad identifiers, device/network/app information, ad interactions, diagnostics and consent information for mediation, measurement and anti-fraud. Actual processing depends on version, configuration and applicable choices; not every listed field is collected by this app. TopOn names Singapore and the United States as primary processing locations, with possible other partner locations. Its general retention is up to two years from collection, subject to necessity and legal/contractual obligations. This is not a universal deletion deadline for app feedback or other SDKs. TopOn privacy requests: privacy@toponad.net.
Privacy Choices and Withdrawal
Use the app's Privacy Choices/Privacy Management entry in Settings to review or make a choice. If you previously gave explicit consent, confirm “Withdraw Privacy Consent” before switching to Basic Services; canceling that confirmation leaves the existing choice unchanged. Choosing again requires your explicit consent before the optional features can resume. Withdrawal cancels current ad preparation and pending presentation; it does not replay prior ad requests or impressions. It stops new advertising requests and disables optional analytics and diagnostics controlled by the app; basic transfers and other basic features remain available. SDK base instances, consent-management components, system diagnostics, or vendor-automatic behavior may still exist or run; this does not mean all SDKs automatically stop and is not a guarantee of zero SDK activity before consent. Withdrawal does not affect processing already lawfully completed and does not automatically delete submitted feedback, transfer history, or peer copies.
The app's main privacy choice is separate from advertising-privacy choices. UMP appears only where applicable and when the required conditions are met; it is not a universal global prompt and does not replace the main privacy choice. On iOS, ATT applies only to cross-app tracking/IDFA where applicable and does not replace the app-level privacy, analytics, or diagnostic choice.
4. Third-party services in this shell
These services support the purposes listed below; processing is subject to app configuration, your privacy choices and applicable legal requirements. Provider policies do not replace this app's notices and consent.
| Component | Entity and official source | Purpose, data and current limits |
|---|---|---|
| Firebase Analytics / Crashlytics | Google; privacy information | Analytics: non-content events. Crashlytics: installation identifiers, device details and crash/exception traces. Collection defaults off; subject to app privacy choices and independent diagnostic configuration. |
| TopOn mediation / ADX | U.S. citizens/entities organized under U.S. law: Ascent Pro Technology Limited; other cases: TOPON PTE. LTD.; see the rule above and policy | IP, device/ad identifiers, device/network/app details, ad interactions and diagnostics for mediation, delivery, measurement and anti-fraud; controlled by app privacy choices and ad configuration, off by default. TopOn may work with affiliates and service partners described in its policy; privacy-request contacts are provided above. |
| Pangle Global | Official regional entity/policy mapping: Pangle policy map; the applicable entity varies by region and is not a single global Bytedance entity | IP-derived region, device/ad identifiers, app and ad interactions for ads and anti-fraud. Off by default, with no app-initiated ad requests; enablement requires the app-level privacy choice, applicable advertising/system consent and release configuration, and withdrawal stops new requests. |
| AdMob / Google Mobile Ads | Google; policy | IP, ad interactions, diagnostics and available identifiers for ads, measurement and invalid-traffic prevention. TopOn route only; off. |
| Google UMP | Google; consent management | Applicable ad consent states and privacy choices, not Analytics/Crashlytics permission. Users manage the app-level choice through the app's Privacy Choices entry; UMP appears only where applicable and does not replace that choice. |
Standard Firebase startup may exist without enabling Analytics/Crashlytics collection. Global excludes domestic Umeng and GroMore. Google may process data on global infrastructure; other ad partners use regional policies. Global data is not assumed stored only in China.
The iOS version covered by this policy uses the Pangle advertising module without the optional App Events module. Advertising services may still process the advertising data described in this policy under applicable consent and configuration.
5. Permissions and system capabilities
Local network/Bonjour, system document selection/sharing and photo saving are used. Camera access is limited to scanning where required by the system, not bulk library scanning. Global ATT concerns cross-app tracking/IDFA; denial does not permit identifier-based bypass. You can manage system permissions and tracking choices in iOS Settings.
6. Storage, rights and security
Information is kept only as needed for the disclosed purposes and applicable obligations. Use system permissions and the in-app privacy entry to manage choices. Contact contact@chenghanbowen.com for access, correction, deletion or consent withdrawal. Withdrawal does not automatically erase submitted feedback or peer copies; uninstalling does not guarantee immediate cloud deletion. Providers may process data under their policies. We do not promise that all data stays on-device or that non-personalized ads process no data.
SendHop is not designed specifically for children. Minors should use it with guardian guidance. Contact us about minors' information. Material policy or processing changes require appropriate notices and renewed consent checks.