Findu Privacy Policy — End-to-End Location Encryption

1. Introduction

Operator identity: The App Findu (Findu.co, the “App”) is developed by Zhong Ming (应用研发方, application developer) and operated by Zhong Ming (应用运营方, application operator). “We”, “us”, and “our company” in this Policy refer to the above developer and operator, Zhong Ming.

This Privacy Policy explains how we collect, use, store, share, and protect your information, and the rights you have.

Highlight: the App offers optional end-to-end location encryption. You may enable keys and turn on “Encrypt uploads” so new locations are stored as ciphertext. Then the server and operators cannot learn your plaintext coordinates; decryption happens only on your device and authorized friends’ devices. See Section 2.

Using the App means you have read and agree to this Policy. If you disagree, stop using the App. During registration or login, we ask you to check agreement to this Policy and the Terms of Service.

Questions? Contact us at root@obaby.org.cn, QQ: 382291381, or QQ Group: 462214191.

Encryption

2. Highlight: End-to-End Location Encryption

To strengthen location privacy, the App provides end-to-end encryption (configure under Me → Location Encryption):

1) Enable keys: create a device keypair and data encryption key (DEK) on your device. You can decrypt friends’ encrypted locations and distribute sealed DEKs to authorized friends. Uploads may still be plaintext by default.

2) Encrypt uploads: a separate switch. When on, new coordinates are written as ciphertext; the server stores ciphertext and necessary metadata only and cannot recover plaintext lat/lon. When off, new points remain plaintext (older plaintext history stays plaintext and is not auto-encrypted).

3) Recovery key: only for you to restore keys after device change or data wipe — not for friends. The server stores a backup wrapped with your recovery key and cannot unwrap it or recover the key. If it is lost and the device has no keys, encrypted traces cannot be decrypted.

4) Friend decryption: both sides enable keys, you grant location permission, and DEK sharing is completed. Friends unwrap the DEK with their private key and decrypt locally; they never receive your recovery key.

5) Your controls: turn off encrypted uploads or disable keys anytime (disabling keys also turns off encrypted uploads); clear all historical coordinates; dangerous key-replacement actions require extra confirmation and may purge old ciphertext.

We encourage encrypted uploads when you need stronger privacy; use is optional and under your control.

3. Information We Collect

Account information: username, email, password (stored encrypted), nickname, avatar, and account identifiers for authentication and profile display. If you sign in with Apple, Weibo, or QQ, we also collect the platform identifiers (such as OpenID, UnionID, and authorization credentials) and any nickname, avatar, or email you authorize, to create or bind a Findu account.

Location information: when location is enabled, we may collect geographic coordinates, report time, and accuracy for friend location and history features. If “Encrypt uploads” is on, new coordinates are stored as ciphertext and we cannot read plaintext location; otherwise they are stored in plaintext. You may disable location/reporting anytime.

Encryption metadata: if you enable location encryption, we may store public keys, wrapped key backups, algorithm identifiers, encrypt-upload flags, and sealed DEK packages for authorized friends. These materials support encryption/decryption and do not contain readable plaintext coordinates.

Friendships and location data: friendships, groups, requests, and the location cards you choose to share, used for friend management and location sharing.

Device and logs: to keep the service secure and stable and to provide push notifications and operations analysis, we and our partners collect: device model, OS version; device identifiers (IMEI, Android ID, OAID, IDFA, DEVICE_ID, IMSI, device MAC address); network information (IP address, network type, carrier, Wi‑Fi connection info, Wi‑Fi SSID, Wi‑Fi BSSID); installed app list; push client ID (e.g. CID); request time; and crash/exception logs. Android ID, OAID, device MAC address, Wi‑Fi SSID and Wi‑Fi BSSID are mainly read by push and device-identifier SDKs to generate push targets and keep delivery/network stable. Collection method: the App and third-party SDKs call system APIs. Purpose: push, security, troubleshooting, and operations analysis. Scope: limited to the purposes in this Policy.

Payment and order data: when you purchase in-app subscriptions or products, order ID, payment channel, amount, and transaction status may be processed (payment account details are handled by the payment provider).

Information you provide: avatars, profile details, and feedback sent to support.

4. How We Use Information

To provide core features: friend location, traces, messaging, notifications, and location encryption.

For authentication, security, fraud prevention, customer support, updates, and troubleshooting.

Within your authorization, to show your location or profile to friends with viewing permission; for encrypted locations, we only relay ciphertext and sealed key packages — decryption happens on devices.

We do not sell your personal information, and we will not use it for unrelated advertising without your consent. We will not attempt to break your end-to-end location ciphertext.

5. Sharing & Disclosure

Except as below, we will not share your personal information with third parties without your consent:

(1) with your explicit consent; (2) with necessary vendors for maps, push, messaging, or payments to deliver features (see Section 12); (3) to comply with law or lawful authority requests; (4) in a merger/acquisition with continued protection as required by law.

To provide push notifications, we share necessary device and network information with Getui Push (Zhejiang Daily Interactive Network Technology Co., Ltd. / Daily Interactive Co., Ltd.), including: OAID, Android ID, device MAC address, Wi‑Fi SSID, Wi‑Fi BSSID, device platform/OEM/brand/model and OS version, and carrier information; and, when the system allows, IMEI, IMSI, IP address, and cell information. This is used to generate the push target ID (CID) and device ID (GID) so friend requests, system notices, and offline chat alerts can be delivered accurately, and is not used for unrelated purposes. The Mobile Smart Terminal Supplementary Device Identifier Unified Calling SDK reads OAID, manufacturer, model, brand, carrier name, and app package name so the push channel can identify the device. Sharing method: after you agree to this Policy, the SDK reads data via system APIs and transmits it to the vendor’s servers.

Your location is visible only to friends/group members you allow; we do not publish your live location to unrelated third parties. For coordinates uploaded encrypted, we cannot provide plaintext location to third parties.

6. Location & Sensitive Data

Location is sensitive personal information. We process it only as needed for location sharing, and provide controls to stop reporting, manage visibility, and use end-to-end encryption.

Share location carefully. You may ask friends to stop viewing or remove the friendship. Keep your recovery key safe and grant location access only to trusted friends.

7. Storage & Security

We retain personal information only as long as needed for the purposes in this Policy and as required by law.

Uploaded files such as avatars are stored on our controlled local server storage by default.

Location data: plaintext and ciphertext points may coexist; new points after enabling encrypted uploads are stored as ciphertext. We use access controls, transport encryption (e.g. HTTPS), and end-to-end encryption where applicable. No internet system is perfectly secure — keep credentials and recovery keys safe.

8. Your Rights

You may access and correct your profile, manage privacy/location settings and location encryption options, and exercise rights such as access, correction, deletion, and withdrawal of consent via the App or email.

You may clear all historical coordinates (plaintext and ciphertext) in the App, or disable keys/encrypted uploads. Note that losing the recovery key may make encrypted data unrecoverable.

Where permitted by law, you may request account deletion. The methods, identity verification, and legal consequences are described in Section 9 (Account Deletion Rules).

9. Account Deletion Rules

The App provides account registration, login, and deletion. You may request deletion of your Findu account in any of the following ways:

1) In-app deletion (recommended): After signing in, go to Me → Advanced Settings → Delete Account, read the consequences, and enter your current password to verify identity. You may also tap “Request account deletion” on the in-app Privacy Policy page to complete the same flow.

2) Email: Send mail to root@obaby.org.cn with the subject “Account deletion”, and include your username and registered email (or the bound Apple / Weibo / QQ identifier) so we can verify ownership. After verification, we will complete deletion within 15 business days and notify you by email.

3) Online support: Contact us via QQ: 382291381 or QQ Group: 462214191, state that you wish to delete the account, and complete identity verification. Processing time is the same as item 2.

Consequences: Submitting a deletion request means you forgo unused virtual benefits on the account. Paid subscriptions that are still in term remain until they expire naturally; deletion itself does not trigger new charges. After deletion, the account is immediately deactivated and cannot be used to sign in; the username and email are released for re-registration; third-party login bindings are removed.

We will stop providing the Service and delete or anonymize related personal data. Information that must be retained by law (such as orders, invoices, and dispute records) will be kept separately for the legally required period and then deleted or anonymized. License keys previously bound to the deleted account cannot be redeemed on another account. Account deletion cannot be undone; please consider carefully before proceeding.

10. Children

We recommend minors use the Service under guardian guidance. Guardians should help minors understand this Policy and consent before personal information is submitted.

11. DCloud Data Collection

This product is built with DCloud uni-app (5+ App/Wap2App). During runtime it needs to collect your device unique identifiers (IMEI/android ID/DEVICE_ID/IDFA, SIM IMSI, OAID) to provide statistical analysis, and uses app launch data and exception/error logs to improve performance and user experience. For details, see the DCloud App Engine Privacy Policy: https://dcloud.io/license/appprivacy.html

To continuously improve the app and provide statistical reports, the runtime collects data such as app launch time and exception/error logs, which include device unique identifiers.

DCloud has obtained China’s Classified Protection of Cybersecurity Level 3 certification (certificate no. 11010813802-20001) to safeguard related data.

DCloud is not a big-data company. The data it collects is used to provide analytics for developers and to continuously improve the product, and does not include personal privacy information.

12. Third-Party Services

DCloud uni-app engine data collection is described in Section 11. To provide maps, system location, push notifications, messaging, camera/mic, in-app purchases, and third-party sign-in, the App integrates the third-party SDKs/services below. Those parties process data under their own policies. This Policy covers only information we collect and process. The list reflects current integrations and will be updated when they change. Note: E2EE key generation/encryption/decryption runs on your device; map/location SDKs may see system location when permission is granted, but coordinates written to our servers after encrypted upload are ciphertext. In the App you can switch the map basemap under Advanced Settings between Tianditu and OpenFreeMap (MapLibre), independent of language settings. Advanced navigation is a separate feature you launch explicitly; it uses the AMap (AutoNavi) navigation SDK and completes AMap privacy compliance settings before initializing. Except for capabilities required to launch the App, we initialize third-party SDKs that collect personal information (including Getui Push and the Mobile Smart Terminal Supplementary Device Identifier Unified Calling SDK) only after you tap Agree on this Privacy Policy. Before you tap Agree, those SDKs will not call system APIs to obtain your personal or device information.

(5) Mobile Smart Terminal Supplementary Device Identifier Unified Calling SDK (MSA OAID) | Provider: Mobile Security Alliance and OEMs | Package: com.bun.miitmdid | Purpose: obtain anonymous device identifier OAID for push device recognition and channel stability | Method: after you agree to this Policy, the SDK reads via system/OEM APIs | Personal information collected: OAID, manufacturer, model, brand, carrier name, app package name | Info: http://www.msa-alliance.cn/col.jsp?id=122

(6) Getui Push (UniPush 2.0) | Provider: Zhejiang Daily Interactive Network Technology Co., Ltd. (Daily Interactive Co., Ltd.) | Package: com.igexin.push | Purpose: friend requests, system notices, offline chat alerts; generate push target ID (CID) and device ID (GID) for accurate delivery and device recognition | Method: after you agree to this Policy, the SDK reads via system APIs and transmits to Getui servers | Personal information collected: device platform, OEM, brand, model and OS version, OAID, Android ID, device MAC address, Wi‑Fi connection info, Wi‑Fi SSID, Wi‑Fi BSSID, DHCP, carrier, IP address; and when authorized or permitted by the system, IMEI, GAID, serial number, IMSI, ICCID, cell information; may also involve push client ID (CID), location-related data, installed app list, stored files | Policy: https://docs.getui.com/privacy/

(8) Huawei HMS Push | Provider: Huawei | Package: com.huawei.hms | Purpose: offline delivery on Huawei devices | May involve: device info, installed apps, network info | Policy: https://developer.huawei.com/consumer/cn/doc/development/HMSCore-Guides/sdk-data-security-0000001050042177

(13) System Geolocation | Provider: Android/iOS system location | Purpose: friend location, traces, maps, location messages | May involve: precise/coarse location, network state | You may revoke location permission in system settings anytime.

(14) Tianditu (National Platform for Common Geospatial Information Services) | Provider: NGCC / Tianditu Open Platform | Purpose: map tiles, geocoding/reverse geocoding, place picking | May involve: network info for map requests, coordinates and search keywords | Site: https://www.tianditu.gov.cn/

(15) MapLibre GL JS + OpenFreeMap | Provider: MapLibre open-source community / OpenFreeMap | Purpose: map tiles when you choose the overseas basemap | May involve: network info and viewport coordinates for tile requests | Info: https://maplibre.org/ , https://openfreemap.org/

(16) OpenIM SDK | Provider: OpenIM (client SDK; messaging backend self-hosted by us) | Purpose: IM, group chat, conversation sync | May involve: account IDs, device/network info, message content and media (stored on servers we control) | Site: https://www.openim.io/ Docs: https://docs.openim.io/

(17) Apple In-App Purchase | Provider: Apple Inc. | Purpose: iOS subscriptions/purchases and receipt validation | May involve: transaction IDs, product info, payment-necessary account/device data processed by Apple | Policy: https://www.apple.com/legal/privacy/

(19) Sign in with Apple | Provider: Apple Inc. | Purpose: register/sign in to Findu with an Apple account | May involve: Apple user identifier (sub/OpenID), email (including Hide My Email), name (first authorization only) | Policy: https://www.apple.com/legal/privacy/

(20) Weibo Open Platform Login | Provider: Beijing Weimeng Chuangke Network Technology Co., Ltd. | Purpose: register/sign in to Findu with a Weibo account | May involve: Weibo user ID, nickname, avatar, and public profile within the granted scope | Policy: https://weibo.com/signup/v5/privacy

(21) QQ Connect Login | Provider: Tencent | Purpose: register/sign in to Findu with a QQ account | May involve: OpenID, UnionID, nickname, avatar, and public profile within the granted scope | Policy: https://wiki.connect.qq.com/qq%e4%ba%92%e8%81%94sdk%e9%9a%90%e7%a7%81%e4%bf%9d%e6%8a%a4%e5%a3%b0%e6%98%8e

(22) AMap Navigation SDK (AMap Navi / Navi-3DMap-Location-Search) | Provider: AutoNavi Software Co., Ltd. (affiliate of Alibaba Group) | Package: com.amap.api | Purpose: when you explicitly start AMap navigation, to provide map display, route planning (drive/walk/ride), and real-time turn-by-turn voice navigation (turn prompts, lane guidance, speed-camera alerts, off-route recalculation) | Personal information collected: (1) location (latitude/longitude, heading, speed for routing and live guidance; coordinates stored internally by Findu in WGS84 are converted to GCJ-02 on your device before being passed in, and our plaintext location records are not uploaded); (2) device information (model, OS version, screen and network environment, device identifiers); (3) network information (IP address, network type, Wi-Fi connection info, cell information); (4) app package name and version, plus anonymous navigation statistics and crash logs | Collection method: only while you actively use the feature, the SDK calls system location APIs and transmits data to AutoNavi servers over HTTPS; the SDK is not initialized when the feature is unused | Scope: map and navigation services only, not for advertising | Compliance: the SDK requires updatePrivacyShow / updatePrivacyAgree to be called before any navigation manager is instantiated, which the App does during initialization | Policy: https://lbs.amap.com/pages/privacy/

Note: Camera, microphone, photo library, barcode, video player, and local database mainly use system APIs for media, voice, scanning, and caching. We request permissions only when you use those features. Vendor push SDKs are typically active only on matching OEM devices with offline channels configured. Fastjson is used only for local parsing and does not collect or upload personal information. Apple / Weibo / QQ login SDKs are used only after you tap the corresponding sign-in method and complete authorization.

13. Changes

We may update this Policy. If changes materially reduce your rights, we will notify you before they take effect via the website, in-app notice, or email. Continued use means acceptance of the updated Policy.

14. Contact

The application developer (应用研发方) and application operator (应用运营方) of this App are both Zhong Ming.

For questions, complaints, suggestions, or account deletion requests about this Privacy Policy, email root@obaby.org.cn or contact us via QQ: 382291381 / QQ Group: 462214191.