Privacy policy

Updated: October 30, 2026 (Version 2026-10-30.1)

Qiaole is provided by 河南巧了智能科技有限公司 (Henan Qiaole Intelligent Technology Co., Ltd., “we”) to help friends discover opportunities to meet. This privacy policy describes how we process your personal information and how you can manage it.

We value your privacy and take security measures required by applicable law. We process personal information only with an applicable legal basis: information necessary to provide registration, sign-in and services you request; information such as location after obtaining the relevant consent; and information necessary to fulfil applicable legal obligations. Accepting this policy does not grant every system permission or authorize background location or other activities requiring separate consent.

Operator: 河南巧了智能科技有限公司 (Henan Qiaole Intelligent Technology Co., Ltd.)
Privacy contact: qiaolezhinengkeji@126.com
Use this email for questions or privacy requests. You can also delete your account in the app under Me → Delete account.

1. How we collect and use personal information

1.1 Device permissions: user_grant permissions in the HarmonyOS package

user_grant means a permission that requires your explicit approval in the system permission prompt. To help friends discover opportunities to meet, the HarmonyOS package requests the following two location permissions. Location is processed only after separate consent to location processing, the relevant system permission grants, and enabling availability while the app is in the foreground.

The current HarmonyOS app does not read contacts, identity documents, faces, calendars, photo libraries, recordings or browsing history, and does not automatically read the clipboard. Choosing to copy a UID, friend code or invitation code only writes that selected content to the system clipboard. Data export uses the system file picker to save to a location you choose without requesting access to other files. Please do not include unrelated sensitive information in chat or reports.

1.2 Categories of personal information and processing scope

We process the following information according to the services you actually use, such as sign-in, friend management, discovering opportunities to meet, invitations, chat and customer support. Where separate consent or a system permission is required, it is requested before the relevant feature is enabled. Listing a category does not mean that all information in it is collected or that it is all collected in the background.

1.3 Processing details by feature

This policy covers features actually offered across different platforms. Availability depends on your version; mentioning a feature does not cause information to be collected when it is unavailable. The current native HarmonyOS app mainly processes the phone number, nickname, invitation code, account and friend identifiers, friend list and distance settings, invitation responses, chat text and report descriptions you provide, together with necessary session, network, language and time-zone information. It processes location only after you enable availability as explained below.

Beta invitations: to limit server load, new accounts receive 3 single-use invitation codes. The server stores the codes, usage status and invitation relationships. Anyone with a valid code can view the inviter's nickname or display name; the inviter can view the new user's nickname. This does not automatically add friends or expose either person's private list. Deleting the inviter's account deletes their codes. A used place is not returned when the invited person deletes their account.

Operations and fault statistics: the server records user identifiers, active dates and the time of the latest successful request to count distinct daily users. It also keeps daily totals for registrations, deletions, requests, errors and response times. These statistics are retained long term and exclude request bodies, exact locations and friend lists. Operational statistics show aggregates; administrators may also handle safety reports you submit. Account deletion removes linked activity details; counts that contain no identity remain long term.

2. Location and reminders

Location and reminders on iOS and Android

In versions supporting continuous sensing, only after you select “Until I pause”, separately consent to background location processing and grant system location permission does Qiaole start continuous location with the app open, to discover opportunities to meet friends. iOS and Android then use system location events to attempt updates approximately once a minute, including while locked or using other apps. iOS shows a location indicator; Android shows an ongoing notification and uses a wake lock while its location service is running. This uses more battery. Signals, battery restrictions and connectivity affect updates; a valid fix every minute is not guaranteed. The server records whether you consented to continuous background location, the policy version and time. Older consent never automatically starts this mode. After force-quitting, system termination or restarting, reopen Qiaole and confirm again to resume.

Timed sensing retains its previous rules: iOS attempts updates once a minute in the foreground and stops sampling in the background; Android attempts updates every minute in the foreground and hourly in the background. Older iOS versions without continuous background sensing also sample only in the foreground. HarmonyOS currently remains foreground-only as described in section 1.1. Pausing, withdrawing consent or signing out stops local location updates; pausing or withdrawing consent also clears the current server location. You may revoke system location permission in Settings. Only the latest automatically sampled location is kept, expiring after approximately 5 minutes; no route history is recorded. Continuous sensing does not automatically share coordinates with friends.

A match occurs only when both people have added each other and both fresh locations meet their individual distance conditions. In the foreground, the app refreshes matches and plays enabled sounds. With notification permission, iOS uses Apple push for new encounters, received invitations, accepted invitations, Thinking of You and new chat messages. Notifications use fixed text and contain no friend names, distances, locations or shared content; declined invitations do not trigger push. Encounter notifications follow your daily reminder limit. Outside an enabled meeting time window they are delivered quietly to Notification Center. The server rechecks blocking, muting and withdrawal before sending; you can also disable notifications in system settings. System push and background location are separate mechanisms: stopping location does not necessarily disable message notifications. Without continuous sensing, or if background location is interrupted, the last location expires after approximately 5 minutes and cannot generate new matches. Android remote push is not currently connected. Ordinary encounters do not show coordinates; one-sided choices and distance settings are private. See Each Other requires both people to separately consent to that location-sharing session.

3. Display and third-party services

You may send feedback by email to the contact above. We process the contact details and description you provide to respond and investigate. Do not send passwords or unrelated sensitive information. Android in-app updates download an APK to the app's private cache, verify it and request installation through the system. You must allow the installation source and confirm; installation is never silent. Updates do not read your other files.

Adding by phone number or WeChat ID is off by default; existing explicit settings are preserved. You can enable it or share a replaceable private friend code with people you trust. A person who successfully adds you through a method you permit sees your nickname; match and invitation participants see each other's nicknames and relevant events. We do not sell personal information and currently include no advertising or behavioral analytics SDK.

For mainland Chinese numbers, Alibaba Cloud Number Authentication (Alibaba Cloud Computing Co., Ltd.) generates, sends and checks SMS codes. For other countries or regions enabled by the operator, Twilio Verify (Twilio) may be used. Availability follows the regions actually offered on the registration screen; not every number can necessarily receive messages. To verify a number, we send the number with country calling code and the code you enter to the relevant provider. We do not generate or store verification codes. Providers process the information necessary for sending and checking under their own privacy rules; see the Twilio privacy notice.

Apple Push Notification service (APNs, Apple Inc.) delivers iOS lock-screen notifications. We send Apple the phone's push token and fixed reminder text, without nicknames, locations or shared content. Apple's processing is governed by the Apple privacy policy.

The current service connects over HTTPS to Alibaba Cloud servers in mainland China; Caddy on the server handles encrypted connections. The current API domain uses DNS resolution and does not proxy business requests through Cloudflare HTTPS proxy or Tunnel. This description does not apply to historical domains or older network routes. On iOS and Android, geolocator calls system location, flutter_secure_storage stores local sign-in information, and the system browser opens download and policy pages. The native HarmonyOS app uses system Location Kit for location, Asset Store to securely store sign-in tokens, the system file picker for data exports, and bundled offline policy text displayed in the app. Language settings are stored in local preferences. Relevant system and browser privacy rules also apply to their processing.

4. Retention, security and account deletion

Storage location: Qiaole's server-side account and service data are stored on servers in mainland China. Processing by SMS, Apple push and maps you choose is described in the relevant sections. Retention depends on the type of data, service purpose and your deletion actions. There is no blanket fixed thirty-year retention period for all personal data; the specific rules follow.

Account and list data remain until you delete them or your account. Encounters, invitations, plans and feedback are retained long term; the home screen still shows the latest 30 days, and retention does not extend validity. You may export history you are entitled to view. Safety reports, including reason, description, relevant accounts and responses, are retained long term for manual review and appeals. The account database also records current consent state and the time and policy version of consent or withdrawal events; these are deleted with your account. Sign-in sessions last 7 days. Public network connections use HTTPS, and the server processes location for matching. The service does not provide end-to-end encryption.

After you confirm Me → Delete account, the live service immediately deletes your account details, all device sessions, related entries in both parties' lists, matches, invitations, targeted shares and responses, chat messages, meeting places and current in-memory location. This cannot be undone and does not delete your WeChat account. Your current phone clears sign-in information and that account's reminder records. Old tokens on other devices can no longer access the service.

Database backups rotate on a daily schedule with at most the latest 7 copies retained. Account data in old backups is not erased immediately by online account deletion; it is removed through rotation. Delayed backup jobs may delay removal. Backups are not used for live matching. Restoring a backup requires the latest privacy-operation records from the same installation, replaying account and content deletion and withdrawal, and invalidating old sessions and sharing permissions. Without those records, safe restoration cannot be assured and the production database must not be directly overwritten.

5. Your choices and rights

You can view and correct editable account details, export data you are entitled to access, delete supported content, withdraw consent and delete your account in the app. In HarmonyOS, privacy and safety controls are accessible from Me, and location permissions can be managed in system settings. Withdrawal stops the relevant subsequent processing and does not affect processing previously performed with that consent. For other access, copying, correction, deletion, explanation or privacy requests, email qiaolezhinengkeji@126.com. We will verify only the information necessary to establish your identity and request and handle it under applicable law. We will not ask you to send passwords or verification codes in chat.

If you disagree with our response, you may contact us again at that email, complain to a competent personal-information protection authority or bring a claim before a court with jurisdiction under applicable law.

You can view your profile, adjust a friend's distance, remove friends, pause availability, turn off sound, sign out, revoke system location permission or delete your account. Without location you can still sign in and manage your list but cannot provide a fresh location for matching. Do not use someone else's WeChat ID to impersonate them.

6. Policy updates

We update this page and its date when features or processing change. Where new permissions are needed, we request system authorization before enabling the feature. The service is for people aged 18 or older and requires your declaration. Phone verification is not identity or age verification; we currently have no independent age-verification mechanism.

Availability and private settings

You can enable availability from 10 minutes, set a custom duration up to 365 days, or keep it on until you pause manually. We save your last duration choice privately. Expiry stops new matches but keeps your list. Keeping availability on requires explicit confirmation and does not remove background restrictions or the separate time limit on location sharing. You can set meeting windows, temporarily pause an individual friend, or disable adding by phone or WeChat ID. Pausing, temporary pauses, one-sided choices and notes are private. You can replace your private friend code; the old one stops working while existing list entries remain. Holding a code does not verify identity.

Unaccepted invitations expire after two hours. Declining is not disclosed to the sender, and there are no read receipts. After acceptance, both people can voluntarily enter an activity, time and public meeting place visible only to the participants. We do not automatically share precise location. Avoid unnecessary sensitive information such as a home address.

Answering “Did you meet this time?” is optional and can be skipped. Answers are not shown to friends. The operations dashboard shows aggregate counts, without respondent identities, meeting places or conversations. Plans and answers remain with the invitation long term; account deletion removes related relationships and invitations. SMS phone verification is connected; WeChat identity verification and Android remote push are not.

Safety, consent and data controls

Me → Settings and help → Safety and privacy provides separate agreement and precise-location confirmations, immediate pause, withdrawal, block and unblock, report receipts and personal data export. Refusing location or withdrawing consent still permits data management, reports and account deletion. Location is processed on the server to judge distance. Only separate mutual consent in See Each Other allows location at the agreed precision to be shown to the selected friend. An encounter notification may still let someone infer you are nearby. Rate limits on distance changes reduce but cannot eliminate inference risks.

Blocking stops future encounters, invitations, shares and location sharing between you and removes the person from your list. Unblocking does not add them again. We send no blocking notification, but changes in interaction may be noticed. Reporting does not automatically block or notify the reported person. Operators can see your submission, account identifiers and handling records. Do not provide passwords, identity documents or precise locations. Reports are not emergency assistance: contact local police in an emergency (110 in mainland China). Send additional material or appeals to the privacy email with the receipt number.

Clearing history hides only your previous encounter and invitation lists, not the other person's records. Records that another participant remains entitled to view are retained long term. Export includes only your visible data, including fixed meeting places deliberately sent in chat; it excludes password hashes, tokens, another person's live location and private settings. Account deletion removes your reports and related block records. Reports already submitted by others lose the target-account link; if their free text still contains your personal information, contact the privacy email for review.

This policy does not claim that cross-border processing assessments have been completed. The current API connects directly to mainland Chinese servers; iOS notifications use Apple push. The operator must verify actual processing locations and applicable cross-border obligations and complete assessments or adjust network routes before public promotion.

Thinking of You and See Each Other

In Thinking of You, you select recipients from your list to send text, HTTPS links and optional responses. Each recipient sees your nickname and that copy's content, not other recipients. There are no read receipts, and bookmarks and muting are private. Content, links, responses and bookmarks are retained long term without timed deletion. Removing something from your own list does not delete what another person received. Blocking hides old shares in both directions; unblocking does not restore them. Account deletion removes related shares and responses. With notification permission, iOS shows a fixed “A friend thought of you” message without the sender or content; muted friends do not trigger alerts. Android alerts only in the foreground.

See Each Other can start from an eligible encounter in the last 30 days, and also supports accepted invitations created within 24 hours. For each session, both people separately choose approximate or precise location and 30 minutes or 2 hours. Viewing requires mutual consent and fresh locations from both. Ending, pausing, withdrawing, blocking or expiry by either person stops sharing for both; restarting requires fresh consent from both. Approximate location is processed on the server using an approximately 0.02-degree grid, sending only its center and roughly 2 km area. Expired or insufficiently accurate locations are hidden. No movement history is kept; automatically sampled coordinates stay in memory. The session's precision, duration, time and version are saved with business records, but retention never reactivates expired or withdrawn consent.

A friend may screenshot or record a location they have seen; withdrawal cannot retrieve information already disclosed. External links are not automatically fetched. After you tap and confirm, the system browser opens the destination, whose operator processes the visit. Selecting and confirming an external map sends the currently shared coordinates (only the grid center for approximate sharing) to OpenStreetMap through the browser. That page does not synchronize with withdrawal or updates in Qiaole; see the OpenStreetMap privacy policy. You can use other Qiaole features without opening external maps.

Chat after matching, meeting places and navigation

People who encountered each other within 30 days, still mutually retain each other and have not blocked each other can chat one to one. There is no online, typing or read status. The server stores message text, sender, recipient, time and request deduplication records. Chat and deliberately sent fixed places are retained long term, without the former 30-day or 500-message deletion limits; the interface loads pages. Clearing your own records does not remove received messages for the other person. Blocking or removing ends contact; adding again does not restore old chat. Account deletion removes related conversation messages. iOS alerts contain fixed text without names, messages or places. Each chat can be muted. Android has no remote background alerts. Transport uses HTTPS without end-to-end encryption.

You can deliberately send the precise current location obtained for that action, or an HTTPS place-sharing link from Amap, Baidu, Tencent, Apple or Google Maps. Separate confirmation is required before sending. The fixed place name, coordinates or link becomes a saved message that both people can export, unlike automatic location samples that are not persisted. Sending a place does not enable live sharing. Recipients may screenshot or save it; clearing or withdrawal cannot recover information already seen. Avoid unnecessary sensitive places such as private homes.

When both people separately consent to live sharing and keep its page open, the current client attempts sampling about every 10 seconds. Display stops if location is older than 30 seconds, insufficiently accurate or sharing ends. Leaving the page or backgrounding stops fast sampling and returns to normal location rules. System, permission and network limits still apply; continuous real-time tracking is not guaranteed. Expiry, pausing availability, withdrawal or blocking stops sharing for both.

When you choose navigation, an authorized precise location or fixed meeting place is sent to your chosen Amap, Apple or Google Maps. Google navigation uses a standard HTTPS link with destination coordinates and walking or driving mode and can open in a maps app or browser. A map link in a location card is handled by its corresponding Amap, Baidu, Tencent, Apple or Google service. Qiaole does not automatically visit or resolve it. Only a snapshot is passed on your action; third-party navigation does not track Qiaole's updates or withdrawals. Each provider's privacy policy applies, including the Google privacy policy. Availability depends on region, network and installed apps. Approximate location cannot be used for precise navigation.

Trips, memories and feedback (October 8, 2026)

Future trips contain only the country or region, city, dates and recipients you enter. Overlaps appear only with mutual authorization and overlapping dates. We do not collect a travel trail. Trips remain long term but stop participating in new overlap notices after they end; you can delete and withdraw them at any time.

Memories are private by default. You may invite one friend to save a shared memory; they can view text and photos only after accepting, and either person can leave sharing. You can delete your own record or delete it with your account. Images are compressed on the client, then the server validates JPEG content, bounds decoded dimensions and re-encodes pixels to remove EXIF, location and comment metadata from new uploads. Images are stored in a protected, separate media table in the database, not distributed on the public download site.

Feedback may include one screenshot and optional version and operating-system diagnostics for operators. Diagnostics are off by default, and feedback is retained long term. Do not upload passwords, verification codes or someone else's private information. Story applications are saved after your confirmation, including original text, application number, two authorizations, authorization changes and review results. You can then choose to email more details. Publicity and targeted-sharing authorizations are independent and off by default. New story applications earn invitations based on content: one for text and one more for a photo, regardless of publicity or sharing consent. Earlier applications follow their original rules. Without publicity consent, content is used only for review and separately authorized targeted sharing. Targeted sharing requires a friend's code and operator review; a button does not send automatically, and sharing does not affect invitation quantity. Applications remain long term. You can withdraw consent or delete an application in My story applications. Withdrawal stops future publicity and sharing; contact operators separately about deleting emails already sent.

The camera is used only for scanning codes; photo-library access reads only the image you choose. You voluntarily enable meeting reminders, which the system may delay. Offline devices cannot learn that someone cancelled or rescheduled; reconnect in the app to sync. Exported calendar copies need manual import and updates. Android vendor remote push is not enabled; background delivery is not promised.

Long-term retention and access audit (October 8, 2026, revision 1)

Business data is not automatically deleted after fixed numbers of days. Your deliberate deletion, account deletion and withdrawal of sharing remain effective. Retention does not grant publicity or model-training rights. Automatic location samples, verification codes and expired sign-in tokens do not enter long-term content archives. The recovery-protection ledger contains only random account or object identifiers, operation types and times, without deleted content, to prevent old backups from restoring deleted information. Administrator reads of statistics and story archives and review actions record access time and action type. There is currently a shared administrator key rather than individual operator identities. Long-term operation event statistics contain only dates, fixed event names and counts, without content or location.

Policy version confirmation (October 11, 2026)

We save the actual policy version you confirm and do not treat an earlier confirmation as agreement to a newer version. After an update, you need to read and confirm it again before enabling features that require current authorization. Older clients can still sign in and manage or delete their data. Feedback, reports and history are paginated so you can read older records.

Language, time zone and region (October 17, 2026)

You can choose Chinese, English or the system language. Your interface-language choice stays on the device. After sign-in, the effective Chinese or English language is also saved as an account preference for system messages and push notifications. The request language is used for service text and does not translate your chats, names or other user content. At sign-in and on returning to the foreground, the app synchronizes the device's IANA time-zone name and current UTC offset. The server saves them as account preferences for meeting windows and local calendar-date checks for trips and memories; the offset is a fallback when a zone name is unavailable. Changing zones does not rewrite saved timestamps, and confirmed meeting reminders stay tied to the actual instant.

A phone's country calling code is used for number normalization and routing to an enabled SMS service. Trip country or region prevents matches between same-named cities in different countries. Older trips with no country retain their original China interpretation. Language or region choice does not change where server data is stored. Daily SMS limits and daily/monthly invitation reward accounting use Beijing time (UTC+8), regardless of device time zone. Existing account-preference and trip retention and deletion rules apply.

Service data is still stored in mainland China. International SMS, Apple push and third-party maps you deliberately select may process transmitted information in other regions. English pages or international number support do not mean that launch, cross-border or other compliance assessments are complete for any country or region. The operator must complete the necessary assessments and service configuration for the regions actually enabled.

Invitations and participation rewards (October 11, 2026)

Check-in counts once per Beijing-time day. Seven cumulative days earn one invitation; they need not be consecutive. After both people voluntarily confirm a meeting, each earns one invitation, limited to once per pair per month. A story for that meeting earns one and a photo one more. Each person can earn at most 5 automatic invitations per month; activities beyond the limit can be recorded but do not receive later back-payment. The initial 3 and manually reviewed grants are outside that limit. We save check-in dates, meeting confirmations, reward source, quantity and issue time to prevent duplicate claims. The same story cannot claim through both automatic and manual routes. Deleting content does not reset eligibility; deduplication identifiers are deleted with the account.

Stories and photos are private by default and used for targeted sharing or de-identified publicity only after your separate authorization. The two choices are independent and rewards do not depend on consent. Photos need not show faces, and we collect no extra location to prove a meeting. Mutual confirmation is a voluntary record, not platform verification of a real-world meeting. There are no public rankings or reward prompts sent to friends.