Are U OK (心连心) Privacy Policy

This English version is a translation provided for reference only. The Chinese version (《心连心隐私政策》) is the authoritative text; if there is any inconsistency between the two versions, the Chinese version prevails.

Effective date: 2026-10-20

Last updated: 2026-10-26

Summary (please read first)

• Who processes your information: The developer 张世博 (Zhang Shibo) (the "Developer" or "I"), contact email aruokok@163.com.
• Where it is stored: On Alibaba Cloud servers located within the People's Republic of China (Beijing). The Developer does not provide your personal information outside China (for exceptions, see Part 4, item (2)).
• Why it is collected: Only to provide the core function of "scheduled check-ins to say you are safe, notifying your family members when you are overdue, and emergency help", plus the extended features you choose to use.
• What the Developer does not do: No advertising, analytics or personalized recommendation SDKs are integrated; your contacts, call logs, SMS and app list are not read; no user profiles are built; personal information is not sold.
• Sensitive personal information: Precise location (only when you turn on "Share location" or send an emergency help request) and photos (only when you actively upload an avatar or a check-in photo); step counts (read only when you turn on "Activity care" and give separate consent, compared only on your phone; only the last movement time is uploaded). Fingerprint and face are verified locally on the device, and the Developer cannot obtain them.
• Your rights: In the App you can view, correct and delete information, withdraw authorizations and delete your account at any time; for other requests, email the Developer, who will reply within 15 working days.

Introduction

"心连心" (English name "Are U OK"; the "App" or the "Service") is a scheduled check-in tool for letting your family know you are safe, developed and operated independently by 张世博 (Zhang Shibo). The Developer processes your personal information lawfully, properly, only as necessary and in good faith, in accordance with the Personal Information Protection Law of the People's Republic of China (《中华人民共和国个人信息保护法》), the Cybersecurity Law of the People's Republic of China (《中华人民共和国网络安全法》), the Data Security Law of the People's Republic of China (《中华人民共和国数据安全法》), the Regulations on Network Data Security Management (《网络数据安全管理条例》) and related national standards.

This policy applies to the Android and iOS versions of the App and to the accompanying server-side services (website https://www.auokok.cn , ICP filing number: 陇ICP备2026010042号). Please read this policy carefully before using the Service, especially the terms shown in bold. Where sensitive personal information is processed, the Developer will ask for your separate consent when you turn on the corresponding feature. By tapping "Agree" in the pop-up at first launch, you agree that the Developer may process your personal information as described in this policy; if you tap "Disagree", the Developer will not collect any of your personal information.

This policy covers: 1. How the Developer collects and uses your personal information; 2. Use of device permissions; 3. Entrusted processing, sharing, transfer and public disclosure; 4. Storage and protection; 5. Your rights; 6. Account deletion; 7. Protection of minors; 8. Updates to this policy; 9. How to contact the Developer. Attachments: "List of Personal Information Collected" (《个人信息收集清单》) and "List of Third-Party Information Sharing" (《第三方信息共享清单》).

1. How the Developer collects and uses your personal information

The basic business function of the App is: you check in to say you are safe on a schedule you set yourself; if you have still not checked in after the deadline, the App first reminds you, and after the grace period ends it notifies the family members you added in advance whose link is active; plus emergency help (SOS). The personal information necessary for the basic business function is: account information (email address, mobile number or third-party account identifier), check-in records and check-in settings, and family relationships. All other features are extended business functions; if you do not use them or refuse to provide the corresponding information, the basic business function is not affected.

(1) Registration and sign-in

1. Email registration and sign-in: You need to provide an email address and set a password, and the Developer sends a verification code to that email address. Sending a verification code and some sign-in scenarios require entering an image captcha. The server stores only a one-way Argon2-hashed digest of your password, never the password itself.
2. Sign-in mobile number (optional, when the Developer turns this feature on): You can link a mainland China mobile number to sign in, register or recover your password with "mobile number + SMS verification code". SMS verification codes are sent and verified by Alibaba Cloud Computing Co., Ltd.'s Phone Number Verification Service (SMS verification), to which the Developer provides the mobile number. Your sign-in mobile number is visible only to you; other users can enter your sign-in mobile number to send you a family invitation, and the invitation takes effect only after you confirm it; the inviter cannot see your number. To prevent abuse of verification codes, the Developer records a salted hash of the mobile number, a hash of the request IP, the purpose of sending and the result (the verification code is not stored, and the number in plain text is not stored in this record).
3. Account ID: At registration the system randomly generates an 8-digit "OK ID" for you, which family members use to add each other.
4. Sign-in state and device information: The Developer issues sign-in tokens and records the brief device information reported by the client (device model, operating system type and version, App version, no more than 128 characters), the client platform type (Android/iOS/HarmonyOS) and the interface language, in order to keep you signed in, show you your signed-in devices, send notifications in your language and determine which features the client supports.

(2) Profile (all optional)

1. Nickname, avatar, time zone: Your nickname and avatar are shown to your family members and appear in invitations, check-in updates, alert notifications and emails. The avatar is cropped and compressed on your device before upload. If you do not provide them, a default nickname and default avatar are used.
2. Contact phone: Shown only to the family members you added (whose link is active); its only purpose is to let them open the system dialer to call you. The Developer does not verify it, and it is not used for sign-in, SMS or marketing.
3. Gender, year of birth: Visible only to you (the App shows your age from it; your exact birthday is not collected); not shown to other users and not used for marketing or profiling. When troubleshooting in the operations console, the Developer can see gender and age (the year of birth is not shown).
4. Linking or changing an email address: The Developer sends a 6-digit verification code to the new email address (valid for 10 minutes; at most 1 per minute and 5 per day per account), and the address is saved only after verification succeeds. For accounts that sign in with email and password, changing the email changes the sign-in email, and a notice is sent to the old address.

(3) Check-ins (basic business function)

1. Check-in records: The check-in time and how you checked in (in the App, from the home-screen widget, from an email link, etc.).
2. Mood, note and photo (optional): A mood/daily-life status, a note of up to 200 characters, or one photo. These are visible to your active family members, so please share carefully.
3. Check-in settings: The check-in interval, reminder time before the deadline, grace period, guarding switch, do-not-disturb periods, etc., used to calculate deadlines and to send reminders and alerts on time.
4. Check-in alarm (local reminder): The check-in reminders you set are triggered on your phone by the system alarm/scheduled notification, and the reminder times are stored on your phone.

(4) Overdue reminders and family alerts (basic business function)

1. Adding family members: You can add family members by OK ID, QR code, registered email address or (once available) sign-in mobile number, or enter the name, email address and relationship of someone who does not use the App. Adding an App user (by OK ID, QR code or mobile number) takes effect immediately, without the other person's confirmation: you are choosing to share your own information with them, so they immediately receive your check-in updates, overdue alerts and emergency help requests and can see your check-in status and records. They are told that you added them as family and can choose to share back with you, or remove themselves from your family list. They do not automatically share their information with you; you can see their check-ins only after they add you too. For a family member added by email address only, the Developer sends a confirmation email to that address, and alerts are sent only after the recipient confirms; the recipient can accept or ignore it. Before adding someone or entering their contact details, you should obtain their consent. When another user adds you as family, you receive the information above from them; if you do not want it, you can remove yourself from their family list from the prompt on the Family tab or on their details page, after which they need your confirmation to add you again. To prevent abuse, the number of App users each user can add as family per day is limited.
2. Alert content: When you are overdue and the grace period has ended, the Developer notifies your active family members by in-app message, system push notification and/or email. The content includes your nickname, your last check-in time and your overdue status; if you turned on "Share location", it also includes your last reported location (latitude/longitude, accuracy, time) and map links generated from it. After you check in, your family members receive a "checked in safe" notice.
3. Do not disturb: After you set do-not-disturb periods, reminders and check-in updates are not sent during those periods, and overdue alerts and "checked in safe" notices are postponed until the period ends; emergency help is not affected by do not disturb.
4. Acknowledging receipt: Family members can tap "Got it" on an alert or emergency help request; the Developer records who acknowledged it, when and through which channel, and shows this to you and that family member. This record does not change how alerts are sent.
5. Reminding you: Before the deadline and after you become overdue, the Developer reminds you to check in by in-app message, system notification, push and/or email.

(5) Location (extended feature; sensitive personal information)

Only after you actively turn on "Share location" and grant location permission does the App obtain your device's precise or approximate location when you check in (and, while enabled, as needed) and upload it. The server keeps only the most recent location and does not keep a track or history; this location is included only in overdue alerts sent to your family members. When you turn off "Share location", the server immediately deletes the saved location. Locations included in overdue alert and SOS messages (coordinates, map links and text addresses) are automatically removed from those messages 7 days after they are sent.

Emergency help (SOS): When you actively send an emergency help request, whether or not "Share location" is on, the App tries once to obtain your current precise location and sends it with the request to your active family members. The location is preferably converted into a text address (such as "a road in a district of a city") on the device by the phone operating system's geocoding service; if the device cannot convert it and the Developer has enabled server-side conversion, the Developer's server sends the coordinates of that request (without your account, nickname or any other information) to the AMap Open Platform reverse-geocoding service to obtain a text address. The text address, coordinates, accuracy and map links are sent to your active family members by in-app message, system push and email; the text address is kept with that SOS record and is not displayed in the operations console.

(6) Activity care (extended feature; sensitive personal information)

Only after you actively turn on "Activity care", give your separate consent and grant the "Physical activity" permission (currently offered only in the Android version, and only when your check-in cycle is longer than 8 hours) does the App read the cumulative step count recorded by your phone's system step counter. Step counts are compared only on your phone to see whether they changed, and are never uploaded to the server. About once an hour (and when the App or background guard is running and detects new movement), the App uploads to the server the time it last detected movement (a change in step count) and the time of the check, to tell whether you haven't moved for a long time within the detection period you set (by default 08:00–22:00 every day).

1. Purpose: If you haven't moved for a total of 4 hours within the detection period, you are first reminded by push / system notification to check in. If you still haven't checked in or moved 30 minutes later, the Developer sends your active family members a gentle care note (such as "hasn't moved for more than 4 hours; you may want to check that they're OK"), at most once per check-in cycle. The care note contains no step count, location or other information. If reports stop because your phone is off or offline, no care note is sent (the regular overdue alert still applies).
2. Information kept on the server: the Activity care switch and detection period, the last movement time, the time of the most recent report, and when care notes were sent. Step counts, movement tracks and history are not stored; only the latest movement time is kept.
3. How to turn it off: You can turn it off at any time in "Settings → Check-in & guarding → Activity care". When you turn it off, the server immediately deletes the uploaded movement time and care status, and the App stops reading the step counter and clears its local records. You can also revoke the "Physical activity" permission in system settings. Not turning on Activity care does not affect check-ins or other features.

(7) Family interaction (extended feature)

1. Family members you added (whose link is active) can see your check-in records (including mood, note and photo) and guarding status; once they add you too, you can see theirs.
2. The current version of the App (the Android version, including the Huawei AppGallery version and the version downloaded from the official website; and the iOS version) does not offer chat (text, image or voice messages) and does not request the microphone permission. Chat messages created in earlier versions (Android official-website direct-install version 0.11.28 and earlier) are still kept as described in Part 4, and you can delete them by deleting your account or contacting the Developer; the Developer does not display any chat content or media content in the operations console.
3. Images: Avatars and check-in photos are first compressed on the device; the server re-encodes them as JPEG and generates thumbnails, removing all EXIF metadata (including GPS shooting location and device model). Check-in photos can be accessed only after signing in, and only by you and the family members allowed to view your check-in records. Uploaded files not referenced within 24 hours are deleted automatically.
4. Reporting: You can choose "Report" in the top-right corner of a family member's detail page, select a reason and report illegal or non-compliant content or harassment to the Developer by email (the email is pre-filled with the reported user's nickname, OK ID and account ID), or report as described in Part 9. The Developer will verify the report within 15 working days, handle it in accordance with the law and keep the reporter's information confidential.

(8) Security verification (extended feature)

1. Fingerprint/face sign-in and check-in verification: Verification is performed entirely and locally by the device's operating system; the Developer does not collect and cannot obtain your fingerprint, face or other biometric information. When enabled, the server generates a random key for that device and stores only its hash; all device keys are invalidated after you change or reset your password.
2. Check-in passcode: If the device has no usable fingerprint/face, you can set a check-in passcode, which is stored only on your device as a salted hash and is not uploaded to the server.

(9) Push messages and notifications

1. Huawei Push (Android version, only on devices that support HMS Core): After you sign in, the App requests a push token from Huawei Push Kit and uploads it to the server; when you need to be notified, the Developer sends the notification title and summary (which may include a family member's nickname, check-in updates or alert prompts) to Huawei's push servers for delivery to your device. The Huawei Push Kit SDK processes app information, device information and network information under its own rules (see the "List of Third-Party Information Sharing"). The App does not initialize push or request a token before you agree to this policy and sign in.
2. Other devices: The App syncs with the server periodically through its own foreground service and issues local notifications; for this you may need to allow notifications, background running, auto-start on boot and ignoring battery optimization.
3. You can turn off notifications by category in the App under "Settings → Notifications", or turn off notification permission in system settings. If you do, you may not receive check-in reminders and family alerts in time, which may prevent the App from achieving its core purpose.

(10) SMS notifications (not currently offered)

The App does not currently send alerts or emergency help notifications to family members by SMS, and does not collect family members' mobile numbers or provide them to SMS providers for this purpose. If this is offered in the future, the Developer will update this policy and notify you prominently in the App.

(11) Subscriptions and payment (not currently offered)

1. The App does not currently offer subscription purchases; no subscription entry is shown in the App, no payment SDKs such as Alipay or WeChat Pay are integrated, and no payment information is collected. Check-ins, overdue alerts (push + email) and emergency help are free forever.
2. The subscription badge next to an avatar (if any) is shown by the server based on existing entitlements and does not involve any new collection of information.
3. If subscriptions are offered in the future, the Developer will update this policy, publish a "Subscription Service Agreement" (《订阅服务协议》) and "Auto-Renewal Service Rules" (《自动续费服务规则》), and obtain your consent before you purchase.

(12) Inviting friends, points and redemption codes (when the Developer turns these on)

• Install ID: An identifier randomly generated on your device (the App does not read device identifiers such as IMEI, OAID or Android ID), submitted at registration, when entering an invite code and at mobile-number sign-in. The server stores only a salted hash of it, which, together with the likewise salted hash of the registration IP, is used only to limit the number of registrations from the same device/network and to detect reward abuse.
• Invite relationships, points ledger, redemption records: The relationship between inviter and invitee, qualification and claim status, and risk flags; the type, amount, balance, time and expiry time of points changes; the redemption time, the entitlement granted and a salted hash of the request IP. An inviter can see only an invitee's nickname, registration date and status. See the "Invite and Points Rules" (《邀请与积分规则》) for the rules.

(13) Information needed to keep the Service secure

When processing requests, the server obtains network logs such as the IP address, request time, endpoint and result, used for rate limiting, anti-abuse, troubleshooting and fulfilling the statutory obligation to retain logs. Image captchas and email/SMS verification codes are kept only briefly and deleted automatically when they expire.

Checking for updates (only the Android version downloaded from the official website): The Android version is offered through two channels, Huawei AppGallery and the official website (www.auokok.cn), with the same features. For the Huawei AppGallery version, upgrades are handled by the app store; the App does not check for updates, does not download installation packages and does not request the "request to uninstall apps" permission. The official-website version requests the latest version information from the official website when you tap "About → Check for updates" and the first time you open the App each day (producing only the network logs described above, without submitting account information), and a new version is downloaded and installed through the browser only after you confirm. Version information and installation packages are provided by the Developer's download server located in Hong Kong, China (886423.xyz, accelerated by the Cloudflare content delivery network); that server receives your device's IP address and request information (such as browser identifiers like device model and system version) only during transmission, does not receive account information, does not keep access logs and does not store any user data. The official website also offers a domestic backup download link (https://www.auokok.cn/download/cn/areuok-latest.apk ).

(14) Operations console

The Developer uses an operations console for customer support, risk control and account management; only the Developer can sign in to it (account + password + one-time passcode). The console does not display message content, images/voice, check-in photos or precise locations; it shows only necessary information such as account data, counts and times.

(15) Information the Developer does not collect

The App does not integrate any advertising, analytics or personalized recommendation SDK, does not read your contacts, call logs, SMS or app list, does not request the phone-call permission, and does not build user profiles or send targeted push messages.

Scan (Android version): The App uses the Huawei Scan Kit SDK (Huawei Software Technologies Co., Ltd.) to recognize family members' QR codes. Camera frames and images you choose from your album are recognized only on the device; to keep the SDK running stably, the SDK processes call information, network information, app information and device information in accordance with its privacy statement, stored within the People's Republic of China (see the "List of Third-Party Information Sharing"). On non-Huawei devices with HMS Core installed, the SDK may launch HMS Core to use its recognition model. The iOS version does not offer Scan.

(16) Exceptions to consent

Under laws and regulations, your personal information may be processed without your consent in the following circumstances: where necessary to conclude or perform a contract to which you are a party; where necessary to perform statutory duties or obligations; where necessary to respond to a public health emergency or to protect a natural person's life, health and property in an emergency; where personal information you have made public or that has otherwise been lawfully made public is processed within a reasonable scope; and other circumstances provided by laws and administrative regulations.

2. How device permissions are used

The following permissions are requested only when you use the corresponding feature (their purpose is explained at the time of the request). You can refuse, or turn them off at any time in system settings; this affects only the corresponding feature.

The App does not request permissions such as microphone, read phone state, contacts, call logs, SMS, storage (read/write all files) or getting the app list. The Huawei AppGallery version does not request the "request to uninstall apps" permission and does not check for the old version.

The permissions used by the iOS version (notifications, location, camera, photos, Face ID) serve the same purposes as in the table above. The iOS version does not offer Activity care and does not read motion and fitness data.

3. Entrusted processing, sharing, transfer and public disclosure

(1) Entrusted processing and third-party services

The Developer provides the service providers below only with the minimum information necessary for the corresponding purpose, and requires them to take security measures and not to use it for other purposes. For the complete list (including SDK names, the information processed and links to privacy policies), see the "List of Third-Party Information Sharing".

1. Alibaba Cloud Computing Co., Ltd.: Cloud servers (Beijing) used to run the Service and store data; (when enabled) the Phone Number Verification Service to send sign-in verification codes; (when enabled) the SMS service to send SMS notifications.
2. NetEase (Hangzhou) Network Co., Ltd. · 163 Mail SMTP service: Sends verification-code, family confirmation, reminder, alert and renewal reminder emails. Involves recipient email addresses and email content (which may include your nickname, last check-in time, location when enabled, and the coordinates and text address of an SOS).
3. Huawei Software Technologies Co., Ltd. · Huawei Push Kit (Android version, HMS devices): Push token, notification title and summary; the SDK processes app information, device information and network information.
4. Huawei Software Technologies Co., Ltd. · Huawei Scan Kit SDK (Android version "Scan"): Images you actively submit (recognized on the device), sensor information (acceleration, light, used on the device); to run stably, the SDK processes call information, network information, app information and device information (stored in China).
5. Beijing AutoNavi Tuqiang Technology Co., Ltd. · AMap Open Platform reverse geocoding (only for SOS, when the device cannot convert the location and the Developer has enabled it): The coordinates of that single request.
6. Device operating system capabilities: Location, geocoding, biometrics, camera, image picker, system alarms, etc. are provided by the device maker and subject to its privacy policy (on devices with Google Play services installed, location is obtained through the Google Play services location API).
7. Map links: The map links (AMap) in alerts are generated by the Developer from the coordinates; the Developer does not send your information to the map provider, but when family members open a link, the coordinates are passed to the corresponding map provider.

(2) Sharing with your family members

The core function of the Service requires sharing your information with the family members you actively added whose link is active (adding an App user takes effect immediately; family added by email only must confirm): nickname, avatar, OK ID, contact phone (if entered), check-in records (including mood, note and photo), guarding status, the messages between you (created in earlier versions), your last check-in time and (if enabled) last location in alerts, SOS location and address, (if Activity care is on) the care note sent when you haven't moved for a long time, "Got it" acknowledgement records, and the badge showing whether you are a subscriber. You can remove a family member at any time to stop sharing; when another user adds you as family, you can also remove yourself from their family list at any time to stop receiving their information.

(3) Transfer

The Developer does not transfer your personal information. If it needs to be transferred because of a merger, division, dissolution, declaration of bankruptcy or transfer of business, the Developer will tell you the recipient's name and contact details and require the recipient to continue to comply with this policy; if the recipient changes the purpose or method of processing, it will obtain your consent again.

(4) Public disclosure

The Developer does not publicly disclose your personal information unless you give separate consent or it is required by laws and regulations, litigation, arbitration or a mandatory request of a competent government authority.

4. Storing and protecting your personal information

(1) Storage location

Your personal information is stored on Alibaba Cloud servers located within the People's Republic of China (Beijing), and backups are also kept in the domestic environment where those servers are located.

(2) No provision outside China

The Developer does not provide your personal information outside the People's Republic of China. Please note the following situations that arise from choices made by you or your family members: if a family member's email address you entered is provided by an overseas email service provider, emails are delivered through that provider; when family members open a map link, the coordinates are passed to the corresponding map provider; when the Android version downloaded from the official website checks for updates or downloads an installation package, the request is handled by the download server located in Hong Kong, China (see Part 1, item (13)), involving only network request information such as the device IP address and no account information or other personal information, and that server does not keep access logs. If the Developer genuinely needs to provide personal information outside China in the future, it will inform you and obtain your separate consent in accordance with the law, and complete the statutory procedures such as a security assessment, standard contract or certification.

(3) Retention period

The Developer keeps your personal information only for the shortest period necessary to achieve the purposes, and deletes or anonymizes it after that period (unless laws and regulations provide otherwise):

(4) Security measures

1. All traffic between the client and the server is encrypted with HTTPS (TLS).
2. Passwords are stored as one-way Argon2id hashes; sign-in tokens, device keys, confirmation links and the like are generated as random values, and the server keeps only the necessary hashes; payment channel credentials are stored encrypted.
3. Check-in photos (and chat media from earlier versions) can be accessed only after signing in, with access controlled by relationship; avatars use random, unguessable addresses; EXIF/GPS is removed from uploaded images.
4. Sign-in, verification-code and similar endpoints are protected by image captchas and rate limits.
5. Only the Developer can access the servers, which use key-based login, brute-force protection and a firewall; the operations console requires a one-time passcode.

If a personal information security incident unfortunately occurs, the Developer will, in accordance with laws and regulations, promptly inform you of the incident, its possible impact, the measures taken or to be taken and suggestions for protecting yourself, and report it to the competent authorities as required.

5. Your rights

1. Access and copy: You can view your profile, check-in records and family list in the App. If you need a copy, you can request one by email, and the Developer will provide it as an electronic file after verifying your identity.
2. Correction and supplement: You can change your nickname, avatar, time zone, contact phone, gender, year of birth, email, password and check-in settings under "Settings" and "Personal info".
3. Deletion: You can remove family members, your avatar, contact phone, etc., and turn off "Share location" (the location is then deleted). In the circumstances provided by law, you can also ask the Developer to delete your information.
4. Withdrawing consent: You can turn off system permissions, "Share location", fingerprint authentication, notification categories or guarding. Withdrawal does not affect processing carried out before the withdrawal.
5. Deleting your account: See Part 6.
6. Explanation and personal information portability (where the conditions set by the national cyberspace authority are met).

Except for matters you can handle yourself in the App, please make requests as described in Part 9. For security, the Developer may first need to verify your identity, and will reply within 15 working days; in principle, no fee is charged for reasonable requests.

6. Account deletion

1. You can delete your account yourself at any time in the App under "Settings → Privacy & Security → Delete account" or at the bottom of the "Personal info" page (after verifying your sign-in password or another sign-in method and confirming a second time). If you cannot do it yourself, you can email aruokok@163.com from your registered email address to request deletion, and the Developer will process it within 15 working days after verification.
2. After deletion, the Developer immediately deletes your account and related personal information, and it cannot be recovered, including account data, check-in records and moods/notes/photos, chat messages from earlier versions (including conversations with you on the other party's device), uploaded images and voice, location, family relationships, alert records, tokens and device keys; copies in backups are overwritten through rotation within 7 days. Transaction records that laws and regulations require to be kept are handled as described in Part 4.
3. After deletion, any existing subscription entitlements (if any) end.
4. After deletion, users who had you as a family member lose their link with you; if they then have no active family members, their guarding stays on and the App reminds them to add family.

7. Protection of minors' personal information (including the Children's Personal Information Protection Rules)

1. The Service is intended mainly for adults (including people living alone who need to report that they are safe, older people and their families). Minors under 18 should read this policy accompanied by a guardian and use the Service only after obtaining the guardian's consent.
2. Children under 14 must register for and use the App with their guardian's consent and accompaniment. The registration page has a checkbox "I am at least 14 years old, or have obtained my guardian's consent"; children's personal information is processed in accordance with the "Children's Personal Information Protection Rules" below.

Children's Personal Information Protection Rules

In accordance with the Personal Information Protection Law of the People's Republic of China (《中华人民共和国个人信息保护法》), the Provisions on the Online Protection of Children's Personal Information (《儿童个人信息网络保护规定》), the Regulations on the Online Protection of Minors (《未成年人网络保护条例》) and Article 21 of the Regulations on Network Data Security Management (《网络数据安全管理条例》), the Developer has established these rules specifically for the personal information of children under 14 ("children"); where these rules are inconsistent with other parts of this policy, these rules prevail.

1. Guardian consent: Before a child registers or uses the App, the guardian must read this policy and these rules, and the guardian ticks the consent box (or the child ticks it accompanied by the guardian). If the Developer finds that it has collected a child's personal information without the guardian's consent, it will delete it as soon as possible.
2. Minimal collection: Only the information necessary for check-ins to say they are safe is processed: account information (email or mobile number, OK ID, nickname), check-in records and check-in settings, and family relationships. Avatar, contact phone, gender, year of birth and check-in mood/note/photo are all optional; location sharing is off by default, and guardians are advised to turn it on for children only when needed. The App does not offer chat or subscription purchases, does not integrate advertising or analytics SDKs, and does not profile children or send them targeted push messages.
3. Visibility: A child's check-in records and similar information are visible only to family members the child has added; guardians are advised to be the child's family member themselves and to check the child's family list regularly.
4. Purpose of use: Children's personal information is used only for check-ins to say they are safe, overdue reminders and family alerts, and emergency help as described in Part 1 of this policy, and not for any other purpose.
5. Entrusted processing and sharing: Information is provided only to the necessary service providers as described in Part 3 (such as cloud services, email, push and the scan SDK), which are required to process it in accordance with the requirements for protecting children's personal information; children's personal information is not shared with, transferred to or publicly disclosed to other third parties, unless laws provide otherwise or the guardian's separate consent is obtained.
6. Storage and security: Children's personal information is stored in China, for the same retention periods as in Part 4 and no longer than necessary to achieve the purposes; the Developer takes measures such as encrypted transmission and access control, and in the event of a security incident will inform the guardian and report to the competent authorities as required.
7. Guardians' rights: Guardians can, on the child's behalf, access, copy, correct and delete the child's personal information, withdraw consent or delete the account; they can do so in the App or contact the Developer as described in Part 9, and the Developer will process the request within 15 working days after verifying the guardianship.
8. Contact: The Developer is personally responsible for matters relating to the protection of children's personal information; see Part 9 for contact details.

8. Updates to this policy

The Developer may update this policy because of changes in laws and regulations or adjustments to features. After an update, it will be published in the App and on the official website, and the "Last updated" date will be changed. For material changes (substantial changes to the purposes or methods of processing, the types of personal information or third-party sharing), the Developer will notify you prominently in the App, such as with a pop-up, and obtain your consent again where necessary. Previous versions can be requested from the Developer by email.

9. How to contact the Developer

The personal information processor of the App is 张世博 (Zhang Shibo). If you have any questions, comments, complaints, reports or requests about this policy or personal information protection, you can contact the Developer as follows:

• Developer: 张世博 (Zhang Shibo)
• Email: aruokok@163.com
• Website: https://www.auokok.cn

The Developer will reply within 15 working days after receiving your email and verifying your identity. If you are not satisfied with the reply, or believe that the Developer's processing of personal information has harmed your lawful rights and interests, you can complain to or report to the cyberspace, telecommunications, public security, market regulation or other competent authorities, or file a lawsuit with a people's court having jurisdiction.

---

Attachment 1: "List of Personal Information Collected" (《个人信息收集清单》) (collected-info-list.md)Attachment 2: "List of Third-Party Information Sharing" (《第三方信息共享清单》) (third-party-list.md)