Version: 1.4 Last updated: 2026-10-04 Effective: 2026-10-04
Details for the Current Version
This section describes features implemented in document version 1.4, effective October 4, 2026. These specific descriptions take precedence over later hypothetical or general statements such as “if added in the future” or “if available in the current version.” The original character background, naming explanations, statutory user rights, and limits of responsibility remain applicable. Read descriptions of the same subject together with the actual features; do not assume that an unimplemented feature is available.
Local Features Available Now
The app includes virtual pet interactions, prewritten local conversations, map exploration, mini-games, a virtual shop, inventory and collections, farming, travel keepsakes, story reading, plans, and countdowns.
The map is an illustrated world installed with the app, not a location map. Park friends and town characters are software characters, not online players or real contacts. The shop uses in-game coins. There are currently no real-money payments, ticket purchases, in-app purchases, or cash redemption of virtual items. Conversations also use in-game coins: the first chat on a topic costs 25 coins and chatting again costs 2. Coins are tracked only on this device, have no real-world value, and cannot be purchased or redeemed.
The story is original in-app content installed with the app. By default, story interactions must be completed before the reading continues; you can turn on “Skip Story Moments” in Settings. Readers' choices create local reading memories and do not rewrite the story's fixed content. “Reading Impressions” are literary expressions, not personality tests, psychological assessments, or real-world credit judgments. Completing Volume One ends at “To be continued.”
Default Name and Your Chosen Nickname
The virtual puppy’s default name is Huqing, shown as “Huqing” in the English interface. The first-launch welcome screen includes an optional nickname field. Keeping the default or leaving it blank uses the default name. You can also change your puppy’s nickname in My Pup. This is a pet nickname, not an online account username, and you do not need to enter your real name.
Nicknames accept Chinese characters or English letters: up to four Chinese characters or six English letters. Mixed names use the same length validation as the app. After a change, supported interface text, written dialogue, story presentation, and this app’s system reminder presentation use your chosen nickname. Reminder titles and notes you enter stay as written. Renaming does not erase pet, reading, or travel progress, rewrite the fixed story content, or regenerate prerecorded character voices or story recordings. Existing audio may still include the original recorded name. The English interface continues to use the existing Chinese recordings.
Nickname and language preferences stay on your device. The app shares these presentation settings locally with its widget and Live Activity extension through its own App Group; it does not upload them to a developer server. Your nickname may appear on the Lock Screen, Dynamic Island, or supported companion displays.
This document’s explanation of “Huqing,” its name order, creative background, and namesake statements describes the default fictional character. It does not assign that name structure to a nickname you choose or imply participation or permission from a real person with the same name.
Data Actually Saved and Its Purpose
To restore your experience, the app saves the following in its local app sandbox and preferences:
Pet status, bond level, interaction counts, conversation topics and progress, and saved lines;
Map progress, in-game coins, experience, item quantities, decorations, home setup, fields and harvest times, quests and daily reward records, virtual friends, collections, travel stamps, and travel notes;
Dates, fictional locations, pet expressions, and lighting choices for travel keepsakes;
Story chapter and paragraph position, furthest reading progress, completed chapters, interactive events, memories, footprints, reader choices and their timestamps, bookmarks and their timestamps, text size, font, dark reading, and interaction-display preferences;
User-created plan titles, notes, types, due dates, creation dates, completion states, reminder preferences, and local identifiers and processing states needed to maintain notifications, Live Activities, and system timers;
Pet nickname, language preferences, sound, volume, haptic, and motion preferences, plus the accepted document version and acceptance time.
A randomly generated six-letter “permanent device ID” kept in the device Keychain, used only for developer diagnostics. It is not uploaded or used for advertising or tracking, and usually remains after the app is deleted.
This data supports local features and progress restoration; it is not uploaded to a developer server. Reading choices are not used for advertising profiles, and interaction or quest records are not used to profile real people. The app has no online account, advertising, cross-app tracking, developer-operated remote analytics, or online generative AI requests. Because you enter plan titles and notes, please avoid adding identity documents, health or financial details, or other people's private information unrelated to the reminder.
Travel Keepsakes and Device Permissions
Travel photos are in-app keepsakes composed from built-in map scenes, pet expressions, and lighting choices. They currently do not use the camera, record audio, read the system photo library, or save to it. The app stores local card options and timestamps rather than photographs of real scenes. It keeps up to the 30 most recent keepsakes and 40 most recent travel notes.
Story poster: after finishing Volume One, when you tap “Make a Poster and Save to Photos” in “This Volume's Memories,” the app creates an image on this device and requests only the iOS “Add Photos” permission to save it to the system photo library. The app does not read or upload any photos in your library, and declining does not affect other features. Once saved, the poster is managed by you and the system photo library.
Plan Reminders and Three System Controls
Standard notifications: The first time you open Plans, you can choose Full Notifications or Dynamic Island Only. Choosing full notifications or turning on system notifications requests iOS notification authorization when needed. If permission was previously denied, you must change it in Settings. Dynamic Island Only does not request standard notification permission. Standard reminders are scheduled locally and can be disabled in the app or system settings.
Live Activities: Enabled in the app by default; whether they appear still depends on iOS Live Activity settings, the device, and system state. They may show a plan title, part of its notes, and a countdown on the Lock Screen, Dynamic Island, and supported related system surfaces. They are separate from standard notification permission. Local ActivityKit provides them. The app does not register a push token with a developer server or rely on developer-operated remote pushes. The system may limit their number, duration, display, and alerts; permanent display is not promised.
Optional System Clock Mode: Off by default. Only turning it on requests separate alarm and timer authorization, on systems that support AlarmKit. After authorization, some plans use system alarms or timers, with pause, resume, and snooze controls. This authorization is separate from standard notifications. System alarms may alert even in Silent or Focus mode. Turning this mode off attempts to cancel timers it manages and restore applicable standard plan reminders.
System components process plans locally. Titles and notes may be visible to people who can see your Lock Screen or linked devices. You can edit plans, disable the relevant features, or adjust notification previews and permissions in system settings. System and linked-device behavior follows those providers' rules.
What Reminders Can and Cannot Guarantee
Plan reminders are for everyday scheduling. They are not emergency, medical, life-safety, or other services that must guarantee on-time delivery. Notification settings, Focus, scheduled summaries, a powered-off device, battery state, system version, Live Activity limits, and changes to device time may affect display or alerts.
A standard Live Activity shows a due state when its countdown ends. Opening the app clears the relevant due card, while unfinished plans remain in the list. Ending or dismissing a card does not complete the plan. System Clock Mode follows Apple's system timer and alarm behavior. The current app does not guarantee that every Lock Screen or Dynamic Island card will disappear automatically after a specified number of minutes.
AI Assets in the Current Version
Some pet images, maps, scenes, story cover art, and prerecorded character voices were generated, synthesized, or assisted by AI. These files are bundled with the app and displayed or played locally. Using the app does not send your plans, reading choices, device data, or voice to the models used to make those assets.
The app explains that some visuals and character voices were made with AI and are preinstalled local assets. Pet voice settings include a separate synthesized-voice explanation. User dialogue has no audio. Playing the pet's voice does not require the microphone. The voice is not a recording of a real person with the same name, and literary characters do not automatically correspond to real people.
The app currently has no feature for publicly posting user content or exporting images or audio. If posting or exporting generated assets is added later, appropriate labeling and explanations must be updated for the actual use. This section does not obtain advance authorization for unknown processing. Legally required generated-content labels must not be maliciously removed, altered, forged, or hidden.
Audio, Silent Mode, and Story Interactions
The app includes background music, an opening soundtrack, interface and game feedback, puppy dialogue, story interaction sounds, and the dream recording. These are bundled local audio files. Playback does not require microphone access and does not record, identify, or upload your voice. Dialogue uses scripted text and prerecorded audio, not an online AI chat service.
Background music follows the app’s Silent Mode logic, and the opening soundtrack fades in gradually. Puppy dialogue, button sounds, and story audio use a media playback audio session and may remain audible in Ring/Silent mode. System volume, your audio output device, audio interruptions, and the relevant in-app switches still affect playback. The Silent Mode check does not guarantee detection of the hardware switch’s exact state. Check volume and audio settings before using the app in a quiet setting.
Audio settings let you adjust music, character voices, and effects separately, turn off automatic puppy voice playback, and disable story interaction sounds or the dream recording’s audio. Tapping Play in the recording interaction plays a local file; with recording audio disabled, the interaction advances silently. In-app audio is separate from iOS notification and alarm sounds, which follow their own system rules.
Retention, Security, and Local Processing
Local saves generally remain until you delete the relevant records, use Delete Data and Start Over, uninstall the app and remove its data, or the operating system clears, migrates, or restores them. The app keeps up to 30 recent travel cards and 40 recent travel notes. Other records remain locally as supported by each feature. Deleting data in the app does not guarantee removal of operating-system backups or content already displayed on companion devices.
A nickname, reminder note, or reading record may contain personal information depending on its content and context. No upload to a developer server does not mean that no information is processed locally. The app does not provide these records to advertisers or AI providers and has no advertising-identifier tracking, online analytics, third-party network SDKs, or developer-server user profiles. Independent App Store, device backup, and crash diagnostic services follow the relevant platform’s policies.
The app uses the operating system’s sandbox and its own App Group to limit data access. It does not promise additional custom encryption for local saves or recovery after device loss, jailbreaking, unauthorized third-party access, or actual data corruption. Device time and in-app monotonic timing support pet care, reminders, animation, and audio coordination; they do not obtain precise location or create a cross-app identifier.
Story Content and Use
The reading experience includes a fixed built-in story, illustrations, and twenty-one immersive interactions, such as ringing a bell, uncovering soil, chasing and tossing leaves, writing with chalk, turning attendance pages, advancing a simulated clock, picking up a test paper, dragging a desk, pushing open a door, and playing the dream recording. Interactions, game rewards, and reading memories are entertainment and literary expression; they do not affect real-world rights. The story depicts school evaluation, enforced standing, and emotional conflict. These are fictional events, not an endorsement of punishment or harm.
By default, interactions must be completed before reading continues; you may turn on “Skip Story Moments” in Settings or pause reading at any time. Parents or guardians should consider the story’s content and a child’s age and understanding. The app does not provide medical care, psychological diagnosis, or emergency assistance. Character dialogue is not professional advice. In-game coins, items, decorations, and rewards are for use within this app only. There are currently no real-money top-ups, trading, cash withdrawals, redemptions, or paid in-app purchases.
Local features operate on supported systems and devices. Glass materials, Dynamic Island, system alarms, fold layouts, and haptics depend on operating-system and hardware support. An unavailable optional reminder or hardware capability should not block pet care or reading features that do not require it.
Delete Data and Start Over
After a second confirmation, My Pet → Settings → Delete Data & Start Over attempts to stop audio, end this app's Live Activities, cancel its pending and delivered notifications, cancel system alarms and timers it manages, and clear persistent app preferences. This includes pet and chat progress, the map, inventory, coins, fields, quests, travel keepsakes, plans, story reading position, choices, bookmarks, collections, reading preferences, and agreement acceptance records. On success, the app returns to the welcome screen. Continuing requires you to actively accept the documents again.
Deleting progress cannot retract content already heard or displayed, and does not delete bundled images, story text, voice clips, or other app resources. If permissions or system components prevent reminders from being canceled, check their actual system state. If deletion fails, follow the app's message.
This operation does not clear iOS notification, Live Activity, or alarm permission decisions. Accepting the documents again is not a new system authorization. Manage those permissions separately in Settings. The app has no developer-hosted cloud saves or independent progress import, export, or recovery service. System backups, device migration, and linked-device records follow system rules. In-app deletion does not guarantee deletion of those system copies.
Local Controls and Document Acceptance
You can view your pet, inventory, travel cards, story collections, and plans; edit plans and preferences; cancel reminders; remove individual bookmarks; or use the confirmed deletion feature to clear all local progress. There is no developer-server account. The developer cannot use a nonexistent remote dashboard to view, export, or recover data held only on your device.
These local controls and data-structure explanations do not limit your legal rights to information, choice, access, correction, deletion, or withdrawal of consent, and do not replace separate consent where legally required. Accepting document version 1.4 again does not erase old progress or give advance consent to future online, paid, or sensitive-permission features.
Creator, Support, and Privacy Contact
Public creator name: Xiao Ying (ying).
Support and privacy contact: kumaridropdi889@gmail.com. You can contact the creator about app use, nicknames, reminders, data management, or privacy. Send only what is needed to address the issue. Avoid sending entire pet saves, identity documents, passwords, or other people’s information unrelated to your feedback.
Email links in the app open a draft in the mail app you choose. They do not send mail automatically or attach pet saves, reminders, reading records, or device identifiers. Your chosen email service handles mail under its own privacy rules.
If you send an email, the recipient processes the sender address, message, and files you attach only to reply, investigate and resolve your feedback, or address privacy requests as required by law. These records are retained only as needed to handle the matter and meet legal obligations, not for advertising or cross-app tracking. You can request correction or deletion of feedback information you voluntarily submitted by writing to the same address. Information that must legally be retained is handled accordingly. The creator cannot remotely access, delete, or restore saves that have never been uploaded and exist only on your device.
PockiPup Virtual Pet App Privacy Policy
Version: 1.4
Last updated: October 4, 2026
Effective: October 4, 2026
Important Notice
Welcome to PockiPup.
The app values privacy and data security. This Privacy Policy helps you understand processing, permissions, local storage, deletion, and related matters. Read it carefully before first use.
The current version's basic privacy principles are:
The app runs locally.
Core pet features need no app-owned server.
No online app account is required.
No phone number, email, legal name, or identity documents are required for core features.
Pet states and related data generally stay on your device.
Local pet data is not uploaded to developer servers.
No pet-data cloud sync is provided.
User profiles, personalized advertising, and cross-app tracking are not part of core features.
Contacts, precise location, messages, and call logs are not requested merely for unrelated purposes.
Uninstalling, clearing data, or device failure may make local pet data unrecoverable.
“No online connection” and “no upload” refer primarily to the app's own operation and processing.
Store downloads and updates, and system backups, verification, security checks, or other system services, may communicate online under store, operating system, or manufacturer control.
That is not the app actively uploading pet data to its own servers.
Article 1 · Scope of This Policy
This policy covers the current PockiPup version's privacy and data activities.
“App” means PockiPup Virtual Pet App.
“You” means an individual installing, launching, or using it.
“Local data” mainly means on-device data used for pet features.
It explains whether personal information is collected or uploaded, what is saved locally, permissions, deletion, backup effects, ads, profiling, tracking, and other important privacy matters.
A User Agreement and About This App & Terms of Use are also provided.
This policy concerns privacy and data; the User Agreement covers usage rules.
Article 2 · Local Operation
The current version runs locally.
Core pet features run on your device.
No identity verification through an app-owned server is required for entry.
An online account is not necessary for basic features.
Pet states are not stored remotely on app-owned servers.
Daily state changes, interactions, settings, and related data are generally processed on-device.
Installed core local features can generally run offline.
Connecting your device to the internet does not mean the app automatically uploads pet data.
Article 3 · No Online Account
No online app registration is required.
You need not provide a phone number, email, online username, account password, identity number, or legal name for current core features.
No real-name verification is required for them.
There is no server-backed profile page.
There is no online account system for cross-device pet-data sync.
Old data therefore does not automatically appear on a new device through an app account.
Article 4 · No Developer-Server Collection for Core Features
The current version has no developer-operated remote data server for core pet features.
Pet states are not actively uploaded to run them.
The app does not collect entered legal names, phone numbers, emails, or identity details through its own servers.
It creates no server-side behavioral files.
It does not continuously upload actions to analyze personal habits.
It does not remotely aggregate local data for commercial profiling.
Opening a character page or interacting with Huqing does not send that interaction to the developer.
Article 5 · Local Pet Data
The app may read and write on-device data to save pet states. Depending on version and features, it may include:
Current pet state;
Growth or interaction progress;
Unlocked content;
Pet values;
Feature preferences;
Volume or audio settings;
Read or completed local states;
Themes or interface settings;
Local-time states for pet features;
First-launch completion;
Acceptance of the current agreement version;
Other configurations needed for operation.
This mainly lets you continue earlier pet states and settings after closing and reopening the app.
Article 6 · Local Storage Is Not an Upload
Local storage does not mean the developer has obtained or remotely collected data.
Writing to device storage and uploading online to a server are different processes.
Current pet data is mainly local.
Without a server-upload feature, local use alone does not let the developer remotely view pet states.
The installation device and operating system actually hold the data.
Article 7 · Why Local Data Is Used
The main purposes are to:
Save current pet states;
Save game or interaction progress;
Retain your settings;
Restore normal states after relaunch;
Determine first-launch completion;
Record local feature choices;
Keep software working;
Provide a continuous, consistent pet experience.
It is not used for commercial profiling unrelated to pet features.
Article 8 · Where Data Is Stored
Pet data generally stays on the device where you use the app.
Physical storage depends on app design, the operating system, and its storage mechanisms.
The app does not save pet states through developer cloud accounts.
The device may use sandboxing or similar isolation.
Protection also depends on device and system security.
Article 9 · How Long Data Is Kept
Local data usually remains while the app is installed.
Pet states may continue updating during normal use.
In-app reset, delete, or clear actions may change or remove data.
System data clearing may delete it.
Uninstalling may also delete it.
Actual deletion varies by device and system.
Copies in system backups may remain under the system provider's retention rules.
Article 10 · Uninstalling and Deletion
Please note: uninstalling may permanently erase pet data.
Possible causes include:
Uninstalling;
Clearing app data in Settings;
In-app reset;
Factory reset;
Reinstalling or resetting the operating system;
Storage or file-system failure;
System cleanup tools removing app files;
Other device operations that remove local data.
Without a current backup or export feature, recovery of data actually deleted from the device is not guaranteed.
Article 11 · Your Control of Local Data
Change pet states through normal app use.
Reset data through available version-specific features.
Clear it using system app management.
Stop use by uninstalling.
Local core storage gives you direct control through your device.
Understand that clearing or uninstalling may be irreversible.
Article 12 · System Backups
The app offers no developer-owned cloud pet sync.
Systems, manufacturers, or features you enable may offer cloud, full-device, or app-data backups, device migration, restore, or system sync.
If enabled, app data may enter those backups under system or manufacturer mechanisms.
This is not an app upload to app-owned servers.
Contents, location, retention, and deletion follow the system, manufacturer, or cloud provider's privacy rules.
Manage backup features through your device's available settings.
Article 13 · App Stores
Stores may process information when you download, buy, install, or update.
This may include download status, purchases, app versions, or distribution-related device details.
The store or platform handles it under its own rules.
The app cannot promise how a store independently processes data.
Distribution-related processing is not the app collecting pet data.
Article 14 · Operating Systems
The app runs on your device's operating system.
The system may perform security checks, permission management, crash handling, backups, storage and power management, installation verification, and device protection.
The system or manufacturer controls these.
The app cannot control their data rules.
Also review your device and system providers' privacy policies.
Article 15 · Permission Principles
Permissions are used only as related, necessary, and within a minimum scope.
Unnecessary permissions should not be required for unrelated purposes.
Merely displaying a pet does not justify contacts access.
It does not justify reading messages.
It does not justify reading call logs.
It does not justify continuous precise location.
It does not justify turning on the camera or microphone.
Future features that truly need permissions must explain their actual use.
Article 16 · You Control Permissions
Review granted permissions in device settings.
Turn them off or on where the system allows.
Refusal may affect a feature that needs the permission.
It should not unreasonably affect unrelated local core features.
Article 17 · Notification Permission
Local pet reminders, state alerts, or similar current or future features may need system notification permission.
This allows local notifications to appear at appropriate times.
Permission does not mean pet data is uploaded.
Fully local scheduling can be completed on-device.
Turn notifications off in Settings.
You may then miss reminders, while unrelated features generally continue.
Article 18 · Local Storage
The app may use its system-assigned internal storage to save data.
Using that space is not access to every device file.
Saving progress does not justify browsing personal photos, videos, files, or unrelated content.
Any future import or export should access files only when you actively choose that feature and as needed.
Article 19 · Camera
Core pet features generally do not require camera access.
The app does not enable it in unrelated situations merely to run those features.
Future camera-dependent features should request permission when actively used.
You may refuse it.
Article 20 · Microphone
Built-in character or AI audio does not imply microphone use.
Playback and recording are separate features.
Playback alone does not require microphone permission.
Core pet features generally do not require collecting or recording your voice.
Future microphone-dependent features must request permission and explain it when used.
Article 21 · AI Audio and Privacy
Some character voices, narration, alerts, or audio may be generated, synthesized, or assisted by AI.
They may be prerecorded app resources.
Playing them does not mean your voice is being recorded.
Nor does it require uploading your data to an online AI service.
In local mode, bundled audio plays directly on-device.
These notices do not mean the app collects biometrics or voiceprints.
Article 22 · Voiceprints and Biometrics
Core features do not need voiceprint-based identity.
Playing AI audio does not automatically obtain your voiceprint.
Core features do not require face- or fingerprint-identification templates.
System fingerprint or face unlocking is handled by the operating system and security modules under their rules, not by this app collecting biometrics.
Article 23 · Location
Core pet features generally need no precise location.
They do not continuously track your whereabouts.
Movement histories are not part of core features.
Future location features must separately explain their actual purposes and permissions.
Article 24 · Contacts
Core features do not read your contacts.
The app does not read contacts without reason to identify your friends.
It does not search contacts for real people named Huqing because the fictional character may share a name.
No contact-based identity matching links the character to real namesakes.
Article 25 · Photos and Media
Core features generally need no access to all photos or videos.
They do not browse your photo library without reason.
Future image-selection features should use system user-selection mechanisms where possible.
Selecting one file does not authorize unlimited access to unselected files.
Article 26 · Clipboard
The app does not continuously read the clipboard for unrelated purposes.
Any future paste feature must be user-triggered and based on actual need.
Clipboard content should not be used for unrelated profiling or ad tracking.
Article 27 · Advertising
Local core features do not require online advertising profiles.
Interactions are not uploaded to developer servers for personalized ad matching.
Future ads require an updated policy.
Third-party processing for ads must be explained as required by law.
Acceptance now is not advance consent to nonexistent future personalized advertising.
Article 28 · Profiling
Core features do not include remote collection of behavior for developer-server profiles.
Interactions are not used to build remote personal files judging spending capacity, interests, or other commercial traits.
Local logic updating pet states is not server-side commercial profiling.
Article 29 · Cross-App Tracking
Current local features need no cross-app tracking.
Pet features do not actively identify activity in unrelated apps.
Cross-app advertising profiles are not a core feature.
Major future changes require legally appropriate new explanations.
Article 30 · Analytics
Local operation does not require pet usage records uploaded for remote statistics.
The app does not continuously upload individual usage merely to learn daily launch counts.
Future online analytics or crash services require updated notices before activation.
Inactive future analytics are not treated as already authorized.
Article 31 · Crash and Diagnostic Information
Crash handling does not require active pet-data uploads to developer servers.
Systems, stores, or manufacturers may have independent crash diagnostics or quality analysis.
Their settings and policies govern these activities.
This is not automatically direct developer collection of pet data.
Article 32 · Third-Party SDKs and Components
Development may use necessary libraries, open-source components, or system frameworks.
Using code components does not automatically mean online personal-data collection.
Any current or future SDK independently processing personal information online must be explained according to its actual behavior and law.
General wording does not obtain unlimited advance authorization for future third-party collection.
SDKs that change local operation to online processing require a matching policy update.
Article 33 · No Sale of Personal Information
Selling local pet data is not the app's business model.
Using pet features does not lead to sale of your local data.
The app does not earn revenue by selling contacts, precise location, or other unrelated personal information.
Article 34 · No Server-Based Commercial Sharing
Local core pet data is not routinely uploaded to developer servers for commercial sharing with other organizations.
Pet states are not supplied as data for ad companies' profiles.
Pet progress is not given to data brokers for commercial profiling.
Article 35 · Data Transfers
In local mode, there is no developer-server pet-account database to sell or transfer.
Major future product changes involving a change of personal-information controller must follow the law then applicable and the actual circumstances.
This policy is not advance consent to unknown future transfers.
Article 36 · Cross-Border Data
Local core features require no pet-data uploads to domestic or foreign app servers.
There is no current design to send core pet data to foreign developer servers.
Future cross-border personal-data features require reassessment and legal compliance.
Article 37 · Minimum Necessary Information
Process only data reasonably needed for a specific feature.
Technical availability alone is no reason to process unnecessary data.
Features needing no permission should not force extra permissions without reason.
Locally achievable core processing should not automatically upload data merely for convenience.
Future features require reassessment of their actual data needs.
Article 38 · Sensitive Personal Information
Core features generally do not need identity numbers, precise location, financial accounts, health records, or biometrics.
Pet gameplay does not require entering them.
Do not voluntarily save unrelated sensitive data where no feature needs it.
Any future necessary sensitive processing must receive appropriate protection under actual features and law.
Article 39 · Financial Information
Local core features do not require card numbers or bank passwords.
Saving pet progress does not require bank details.
Lawful store purchases may use store or payment-provider processing.
Their rules govern payment data.
A store payment does not automatically give the app full bank passwords or other payment credentials.
Article 40 · Minors' Privacy
The app values minors' personal information and privacy.
Core features do not require real age, identity number, or other identity information.
They do not require minors to upload identity documents.
Minors should use it reasonably for their age and understanding.
Future online features processing minors' information must apply appropriate legal protections.
Obtain guardian consent for protected age groups where law requires it.
Article 41 · No Need to Submit Real Huqing Information
Huqing is a virtual dog.
Its name does not make the app request information about real individuals named Huqing.
Proving the name's origin does not require friends' photos, phone numbers, chats, addresses, or other personal data.
The app does not search contacts for namesakes.
It creates no identity database connecting the fictional pet to real people.
Article 42 · Real People's Privacy
Respect real people's privacy and information rights.
Do not use the app to save or spread others' sensitive data without authorization.
A shared name is no reason to identify or compile information on a real person through the app.
Character settings are not a basis to obtain, distribute, or use namesakes' private information.
Article 43 · Local Acceptance Records
The app may save whether you accepted the current document version to decide if first-launch confirmation is needed again.
This can be a local state value, version, or similar technical record.
It mainly prevents repeating the same confirmation on every launch.
It is not automatically uploaded.
Major changes legally requiring renewed consent may display confirmation again through a version change or other method.
Article 44 · What Agreement Means
On first use, you can open this policy and the User Agreement.
You may choose whether to check “I have read and agree to the User Agreement and Privacy Policy.”
The checkbox must be actively selected by you.
Core access may be prevented before confirmation.
Reading a link is not agreement.
Installation alone is not confirmation.
General policy acceptance does not replace separate consent legally required for particular processing.
Article 45 · Withdrawal and Stopping Use
You may stop using the app.
Uninstall through the operating system.
Delete local data through available device or app controls.
Withdrawing a revocable permission may stop dependent features.
Withdrawal does not invalidate processing lawfully performed beforehand.
After stopping use, uninstalling or clearing data handles the remaining local data.
Article 46 · Access to Local Data
View displayed pet states through the interface.
Direct access to internal files or databases depends on system security.
The app will not deliberately hide an actual remote account to block legal data rights.
There is no current remote account, so no developer-server login is needed to view a personal pet file.
Article 47 · Correcting Local Data
Some pet data is automatically generated virtual state.
Normal use changes those states.
Editing user settings depends on actual features.
This policy does not restrict lawful personal-information rights.
Article 48 · Deleting Local Data
Depending on your device and app features, delete some or all local data by:
Using an in-app reset, if available;
Using system Clear App Data or similar controls;
Uninstalling;
Other system-permitted management methods.
Pet states, progress, and settings may become unrecoverable. Use care.
Article 49 · Security Measures
Security is designed for local operation.
Keeping pet data on-device reduces exposure from unnecessary remote transfers.
Avoid unnecessary server transfers.
Security also relies on system isolation, protections, and your device safety.
Keep your device secure.
Use passcodes, lock-screen authentication, or other protections as needed.
Article 50 · Lost-Device Risks
Loss, theft, or unauthorized possession may affect local data.
The app cannot control physical device security.
Use lock-screen passcodes or system security appropriately.
If the device is unprotected, someone able to use it may also open the app.
Article 51 · Malware and System Risks
Malware, elevated system access, or serious vulnerabilities may create added risks.
These may exceed what a normal app can reasonably control.
Install systems and apps from trustworthy sources where possible.
Avoid unknown, maliciously modified, or code-injected versions of this app.
Article 52 · Unofficial Modified Versions
This policy cannot guarantee modified, cracked, or unknown-source versions retain the original local processing.
Third parties may add network, advertising, tracking, or other code.
This policy describes the corresponding normally released app version only.
Judge unauthorized modifications by their actual behavior.
Article 53 · Network State
An online device does not mean the app itself is online.
Other apps and system services may use the internet concurrently.
Wi-Fi or cellular access does not automatically grant this app other apps' data.
Determine the source of actual communication from actual program behavior.
Article 54 · Updates May Need Internet
Installed core features do not rely on app servers.
Stores normally need internet access to check or download versions.
Distribution services handle downloads.
Update communication is not the app uploading pet states in the background.
Article 55 · Policy Updates
Features, laws, or design changes may require updates.
Wording, spelling, or formatting corrections do not necessarily change processing.
Significant privacy changes—accounts, cloud sync, developer servers, online AI, analytics, advertising, tracking, personal-data uploads, sensitive permissions, or third-party online SDKs—must be reflected in an updated policy.
Obtain renewed consent where required.
Acceptance of the local policy is not advance blanket authorization for all unknown future processing.
Article 56 · Major Privacy Changes
If local operation changes to substantial online personal-data processing, such as account servers or cloud pet sync, explain at least:
Information processed;
Purposes;
Methods;
Retention;
Storage locations;
Third-party disclosure;
Cross-border transfers;
Third-party SDKs;
Deletion options;
How users exercise lawful data rights.
Article 57 · Future Features Are Not Authorized Now
References to future additions only explain protection principles.
They do not mean features currently exist.
They do not give advance authorization to process data for them.
Renewed consent depends on actual future features and then-applicable law.
Article 58 · Independent Third-Party Services
Devices, operating systems, stores, and system cloud services you enable may have their own policies.
This app's policy does not explain independent processing on their behalf.
Review the rules of services you actually use.
Their independent behavior will not be misrepresented as fully controlled by this app.
Article 59 · No Real-Person Data from a Shared Name
Huqing is a virtual dog.
Real people may share that name.
This does not cause the app to automatically search for or locate them, obtain their contacts, photos, voice, address, or social accounts, or create personal files.
There is no design for automatic personal-information matching between the character and real namesakes.
Article 60 · Do Not Upload Others' Information
No current core feature requires personal data uploaded to developer servers.
Using Huqing does not require real friends' details.
Do not misuse program modifications to embed or spread others' private data into inappropriate contexts.
Respect others' lawful privacy and information rights while using your device.
Article 61 · AI Assets Versus Data Processing
Disclosing AI-made audio does not mean the device continually runs an online AI model.
Prerecorded bundled AI audio plays locally like other app resources.
The explanation mainly provides content transparency.
It does not automatically mean recording your voice, analyzing voiceprints, obtaining photos, identifying you, sending data to AI providers, or AI profiling.
Actual features determine any such processing; local core pet features do not require it.
Article 62 · Interactions and Privacy
Feeding, interaction, rest, cleaning, and other actions can update states locally.
A local update does not remotely tell the developer when you acted.
Current operation does not upload every tap to analyze individual habits remotely.
Core features can be used without a remote behavioral file.
Article 63 · Time Information
Some states need the device's current date or time.
Using it for local calculation is not precise-location collection.
Local logic may calculate pet states or date changes.
This does not automatically report usage times to developer servers.
Article 64 · Device Information
Operation necessarily uses basic technical states such as screen dimensions, runtime environment, or app version supplied by the system.
Local use for correct display and operation is not a server upload.
Unique device identifiers are not needlessly collected remotely for commercial profiles.
Future necessary remote device processing requires a matching policy update.
Article 65 · Unique Identifiers
Local core features generally do not need server-side advertising identifiers for profiles.
Advertising IDs are not needlessly uploaded merely to recognize the same person.
Future advertising or attribution requires separate actual explanations.
The app creates and stores a randomly generated six-letter “permanent device ID” in the device Keychain, used only for developer diagnostics. It contains no name, phone number, advertising identifier, or other personal information. It stays on this device (Keychain access is set to “this device only”), is not uploaded to any developer server, and is not used for advertising, profiling, or cross-app tracking. Because Keychain items can remain after an app is deleted, the ID usually stays the same after reinstalling the app. The developer learns it only if you read it out and send it, for example when reporting a problem. It is shown before the version number on the About page.
Article 66 · Cookies and Web Tracking
Core features are local, not developer web-account services.
Cookies are not currently used to build developer-server behavioral profiles for core features.
Third-party pages opened through systems or stores may have independent data rules.
This policy does not guarantee third-party web behavior.
Article 67 · Automated Decisions
Ordinary local program logic may select animations, states, or interaction results.
This is primarily entertainment.
The app does not currently use server-side profiles for significant decisions affecting real-world rights.
A pet appearing happy or sad is not a credit, employment, education, financial, or other important real-world assessment of you.
Article 68 · Personalized Pet States
Local interactions may change pet states.
This personalization mainly affects game or pet states.
It is not commercial personalized-recommendation profiling.
A pet responding more closely to your local interactions does not automatically upload your personal data.
Article 69 · Privacy Principles
The app follows these principles:
Lawfulness;
Legitimacy;
Necessity;
Good faith;
Clear purpose;
Minimum scope;
Informed users;
User choice;
Local processing first;
No unjustified processing unrelated to features;
No unlawful exclusion of statutory rights by agreement.
Article 70 · Your Legal Rights
Within applicable law, you have rights to know, decide, limit, or refuse processing of personal information.
Data held only on-device and not uploaded can generally be managed directly through the app or device.
This policy does not exclude lawful personal-information rights.
Article 71 · Rights Without a Remote Account
There is no current developer-server account database, so some usual online profile-query scenarios do not exist.
The developer cannot remotely edit or delete on-device pet states through a nonexistent account dashboard.
Use actual local app or system management capabilities.
This is a difference in local data structure, not a restriction of information rights.
Article 72 · Irreversible Deletion
Thoroughly deleted data may have no developer-server copy.
Accidental deletion without a system or other app-provided backup may therefore be unrecoverable.
Local operation reduces remote retention but makes preserving device data more important.
Confirm carefully before clearing data or uninstalling.
Article 73 · Anonymous Information
Information that cannot identify a person or be restored to identify them may have a different legal status from personal information.
This concept will not be used to hide actual personal-data processing.
Classification depends on actual content and processing.
Article 74 · Legal Requirements
Applicable personal information, data security, and consumer protection laws must be followed.
New mandatory data-processing requirements must be met within their actual scope.
This policy does not exclude mandatory protection.
Article 75 · Interpretation
“No online connection” mainly means core features do not rely on app-owned servers or actively upload pet data through them.
It does not guarantee the entire device never communicates online.
Stores, systems, manufacturers, and other installed software may have independent network activity.
“Local data” is mainly saved and processed on-device.
“Third party” means another product or service provider independent of the app's operating entity.
Article 76 · Legal Effect
Interpret this policy according to actual processing.
Update descriptions promptly when features change.
Privacy wording must not hide actual undisclosed processing.
Disclaimers do not exclude nonwaivable liability.
An invalid clause does not automatically invalidate other independent lawful terms.
Article 77 · Relationship to the User Agreement
On first entry, open each document separately.
The agreement mainly covers usage rules.
This policy mainly covers data and privacy.
After reading both, freely choose whether to check “I have read and agree to the User Agreement and Privacy Policy.”
Without active selection, installation or opening alone is not confirmation.
Article 78 · Relationship to About This App & Terms of Use
About This App may also show About This App & Terms of Use.
It explains Huqing, its name origin, AI sounds, local operation, and other information.
This policy gives fuller data and privacy details.
For specific processing questions, read it together with actual behavior first.
Article 79 · Final Privacy Statement
To avoid ambiguity:
The current app is a local virtual pet app.
Core features need no app-owned servers.
No online app account is required.
No developer-server pet cloud sync is provided.
Pet states and related data generally stay on-device.
Core pet data is not actively uploaded to developer servers.
The name Huqing does not cause collection of real namesakes' information.
Some sounds use AI production, but playback is not recording or collecting your voice.
AI playback alone requires no microphone permission.
Online commercial profiling is not a core feature.
Cross-app tracking is not a core feature.
Core features do not unjustifiably read contacts, messages, call logs, or precise location.
Uninstalling, clearing data, or damage may make local data unrecoverable.
System backups, migration, store downloads, and security services are not app server uploads.
Future accounts, sync, online AI, analytics, ads, or other online personal-data features require matching policy updates and lawful notice or consent.
Article 80 · Privacy in Plain Language
Your pet runs on your device.
Its data mostly stays there.
No app account is needed.
Pet states need not be uploaded to developer servers.
There are no developer cloud pet saves.
Some sounds were made with AI, but are prerecorded content—not the app listening to you.
Uninstalling or clearing data may make pet data unrecoverable.
System backups, store downloads, and system services follow their providers' own rules.
Article 81 · Final Review
Before checking “I have read and agree to the User Agreement and Privacy Policy,” confirm that you understand:
This is a local virtual pet app;
No online app account is required;
Pet data is mainly saved on-device;
No developer-server cloud sync is provided;
Uninstalling may erase pet data;
Some sounds may use AI generation, synthesis, or assistance;
Playing AI sounds is not recording your voice;
Stores and operating systems are independent environments;
You may freely choose whether to accept and continue.
Privacy at a Glance
Operation: On-device
App account: Not required
Developer servers: Not used by core features
Pet cloud sync: None
Pet data: Generally local
Developer remote access to pet states: Not provided
Online profiles: Not used by core features
Cross-app tracking: Not used by core features
Contacts: Not needed by core features
Precise location: Not needed by core features
Microphone: Not needed for built-in AI audio
AI sounds: Some may be generated, synthesized, or assisted by AI
Deletion: Available app controls, system data clearing, or uninstalling
Cloud backups: No developer sync; system-provided backups are separate
After reading and understanding this Privacy Policy, choose freely whether to accept it and continue using PockiPup.
Home Screen and Lock Screen Widgets
Version 3.4 adds native Apple WidgetKit widgets: Plan Countdown, Your Desk Buddy, Daily Care, Pick Up Your Story, and Adventure Passport. They support the relevant Home Screen sizes and selected Lock Screen layouts. You choose whether to add or remove them in the system widget gallery; the app does not place widgets on your Home Screen automatically.
To show this content, the app stores a limited, read-only display copy in its on-device App Group: nickname and language; pet stats and their update time; bond and level; IDs, titles, types, start and due dates, and paused time remaining for unfinished plans; the current chapter title and reading percentage; visited-place stamps, coin and item counts, and farm harvest times. It does not include plan notes, the full story text, reading choices, photos, or recordings, and it is not uploaded to a developer server. Personal save content is not published before the agreement confirmation is complete.
Home Screen, Lock Screen, StandBy, and other supported system views may display this content. Anyone who can see your device screen may also see it. In Me → Home Screen Widgets, you can turn off plan titles in widgets; widgets then show “Plan” instead. This setting does not change existing notification or Live Activity content settings. Removing a widget does not delete app progress.
iOS schedules widget refreshes. Countdown digits use the system timer; content refreshes may be delayed, and pet stats are display estimates based on the local save. Widgets do not continuously run games, play audio, or replace due-time notifications. Tapping opens the relevant app page; it does not automatically feed the pet, spend coins, complete a plan, or change a reading choice.
Delete All Data and Start Over removes the shared display copy and requests a widget refresh. The system may briefly retain an old rendered snapshot until its next refresh. The app cannot immediately erase every view already cached by the system or displayed on another device.
Version 3.5 also adds Days to Go and Important Days, sharing IDs, titles, Gregorian dates, categories, repeat rules, and pin status. Date reminder settings and notes are not included in the display copy. Configuration can select a particular day or follow pinned and nearby dates. The system manages clear glass; the app does not read wallpaper. The title visibility switch hides both plan and important-day titles.
Days to Go and Important Dates
Version 3.5 adds Days to Go within Plans. You can save birthdays, anniversaries, trips, goals, and other dates; count calendar days ahead or behind; categorize, pin, search, sort, repeat yearly or monthly, edit, and delete them. Dates are saved as Gregorian year, month, and day and counted using calendar days in the device’s current time zone, with today as day 0. February 29 uses February 28 in non-leap years; shorter months use their last day.
IDs, names, notes, dates, categories, repeat rules, pin status, reminder preferences, reminder times, advance-reminder days, and creation times stay on this device. The feature does not read or write system calendars, contacts, birthday records, or Reminders and does not connect to the internet. Respect other people’s privacy when entering their birthdays or anniversaries. Using this feature does not require submitting identification or contact details.
You may choose a reminder on the day and an additional reminder 1, 3, or 7 days before. Date reminders reuse the app’s existing system notification preference and permission. Without notification permission, dates can still be saved and shown in widgets. The feature does not automatically request calendar, contacts, or extra Live Activity permission, and does not turn every distant date into an ongoing Live Activity. It currently does not provide long-term Days to Go countdowns in Dynamic Island.
Repeating reminders use a bounded rolling queue: local notifications are scheduled for the next occurrence and up to three later occurrences. When system notification slots are limited, the nearest reminders take priority. Later reminders are replenished when you reopen the app. Already scheduled notifications can be delivered while the app is closed, but unscheduled future reminders cannot be guaranteed if you do not open the app for a long time. Reopening reschedules them for the device’s current time zone. If you change time zones without reopening, previously scheduled reminders follow their previous schedule. Silent mode, Focus, permission, and notification settings can affect their appearance or sound.
The Days to Go and Important Days widgets share limited, read-only date-display data: IDs, titles, dates, categories, repeat rules, and pin status. They do not share date notes or reminder settings. Widget configuration lets you choose an event or automatically follow pinned and nearby days, and select clear glass or soft cream. The actual transparent Home Screen glass follows system clear or tinted appearance settings. The app cannot force a system appearance or read your wallpaper. The title visibility switch applies to both plans and important days. iOS schedules date updates, which may be delayed. Deleting a day cancels its pending reminders and updates its display copy. Delete All Data also clears these saves.