Privacy Policy

Version: v1.0 Effective Date: 2026-03-24 Updated: 2026-03-24 Welcome to Craving Cat. This Privacy Policy is written against the current codebase. It explains what stays on your device, what is sent only when you choose to send it, and what we do not collect. 1. Developer and scope Developer type: Individual developer (non-corporate) Contact: landingfeather@163.com This policy applies to the Craving Cat iOS / iPadOS app, its related Screen Time extensions, and the standalone legal pages for this product. 2. What we do not do by default 1. We do not require account registration or sign-in. 2. We do not integrate ads SDKs, analytics SDKs, or App Tracking Transparency-based tracking. 3. We do not upload your Screen Time authorization status, protected app list, app-usage duration, trigger history, exemption history, or local protection rules. 4. We do not read the content of other apps, messages, searches, keyboard input, photos, contacts, location, microphone, or camera data. 3. Information processed locally on your device 1. Screen Time authorization and protection state After you actively grant permission, the app stores the minimum local state needed to run protection features, including: - Screen Time / Family Controls authorization status; - whether protection is enabled; - the most recent threshold trigger time and event name; - the most recent shield-button outcome, such as “Put it down for now” or “Allow a little more.” 2. Protected targets and rule settings The protected targets and rules you choose in the iOS system picker are used only for on-device functionality and extension sync. They may include: - the apps you select and the related system-provided tokens; - when available from the system, the app display name and bundle identifier; - daily limits, session limits, and exemption durations; - temporary exemption state. The current build is centered on app-level protection. If you also select categories or web domains in Apple’s picker, those choices may still be stored locally to preserve your setup, even though category- or web-domain-based blocking is not the main active path in the current build. 3. Local interface and trial state The app also stores a small amount of local state, such as: - display language; - whether the home tutorial has been seen; - the start and end timestamps of the 7-day intro trial. Trial timestamps are kept in local preferences and secure storage / keychain to reduce accidental loss. 4. Feedback draft queue and send-attempt history If you write feedback and sending fails, the draft may remain on your device until the app retries later. The app also stores short-term send-attempt timestamps locally for rate limiting and retry control. 4. Network use and third parties 1. Feedback submissions Under the current code, the only confirmed feature-specific network request is when you choose to send feedback to the developer’s feedback service. The request contains only: - the feedback text you chose to submit; and - the app identifier "com.flowthemoment.cravingcat". We do not attach your protected app list, Screen Time duration, trigger history, rule configuration, or Apple account details to that feedback request. If sending fails, the feedback may stay on your device first and retry later. 2. Apple system services and App Store If you use trial, purchase, or restore-purchase features, billing and transaction handling are performed by Apple / the App Store. The app reads only the local transaction state needed to determine whether trial, monthly access, or lifetime access is available to you. We do not directly receive your Apple ID, bank card number, or full payment credentials. 3. Font loading notice The current code uses the google_fonts package for typography. According to that package’s documentation, if matching font files are not bundled into the app, font files may be fetched over the network and cached on the device. We do not use this for advertising, profiling, or behavior analytics; however, from a strict code-review perspective, this means the current build may make font-file requests in addition to feedback sending. If the app later switches to fully bundled local fonts, this policy will be updated accordingly. 4. Third-party services currently involved - Apple: Screen Time / Family Controls / DeviceActivity / ManagedSettings / StoreKit / App Store - Supabase: only for receiving feedback text that you actively submit - Google Fonts mechanism: only if the current build has not bundled the used font files locally 5. iOS parental-control / Screen Time permissions 1. The current code requests authorization with AuthorizationCenter.shared.requestAuthorization(for: .individual), which is designed for self-directed use on your own compatible device. 2. Apple describes the Screen Time APIs as privacy-preserving. We do not upload the apps you choose, the websites you visit, or the time you spend in those apps or websites to our servers. 3. Craving Cat is not a remote surveillance service and does not provide a way for us to read another person’s usage history from our server. 6. Retention and deletion 1. Local data stays on your device until you change settings, stop protection, clear app data, or uninstall the app. 2. Feedback you choose to send may remain in the developer’s feedback system for as long as reasonably needed to review product issues, improve the app, or process your request. 3. If you want already-submitted feedback deleted, contact us by email. Because we do not run a user-account system, we may need enough information from you to locate the relevant feedback entry. 7. Your choices and rights Subject to applicable law, you may: - revoke or stop system authorization; - change or delete local protection settings; - stop using the app and remove local data from your device; - contact us to ask about, access, or request deletion of feedback you voluntarily submitted. 8. Minors The app is designed for self-directed use on the user’s own device. If a minor uses the app, guardian guidance is recommended. Do not use the app to manage or collect data from another person’s device without proper authorization. 9. Policy updates If a later version adds account systems, cloud sync, crash analytics, ads, broader network features, or new payment flows, we will update this policy before those features are made available.