Effective date: October 17, 2026
Last updated: October 10, 2026
Protection disclosures clarified: October 16, 2026 (the October 17, 2026 effective date above is unchanged)
This is the English version of the Blanky Privacy Policy. If the Korean version (https://blanky.kr/blanky/privacy/) and this version differ, the Korean version prevails.
This policy applies to all Blanky apps below. Items that differ by platform are marked [macOS] or [Windows].
The app works without sign-up or login and does not collect identity information such as your name, email address, or phone number.
Limited information is sent outside your device only in the cases listed in §3.
If you choose, you can connect your own Google account to see your Google Calendar events. The Google user data involved is described separately in §3 (f) and §13. The developer runs no server and does not receive this data.
| Item | Purpose | Where it is kept | Sent outside |
|---|---|---|---|
| CPU, memory, disk, battery, and network usage | System monitoring display | Live values are processed in memory only. [macOS] Recent averages are written to the app group storage on the device for the widget | No |
| Local IP address, network interface names, battery cycle count and temperature | On-screen display | Memory only | No |
| Times when the device entered high or low load | Pet reactions | [Windows] pet_state.json on the device | No |
| Pet status (hunger, mood, energy, growth stage), inventory | Pet raising | Local files on the device | No |
| Character settings, app settings, language | Keeping your settings | Local files and settings storage on the device | No |
| Character images you import (GIF, PNG) and their file names | Showing custom characters | Local folder on the device | No |
| Purchase and trial status (tier, trial start date, install date) | Enabling paid features | Local file on the device (premium.json) | No |
| Payment processing | In-app purchases | Managed by [macOS] Apple App Store and [Windows] Microsoft Store | §3 (c) |
| Promo code string | Checking codes and preventing reuse | Google Firestore managed by the developer | §3 (a) |
| Random per-device identifier | Preventing promo code reuse | [macOS] Settings storage on the device and Google Firestore | §3 (a) |
| Error diagnostics | Finding the cause of errors | [Windows] Sentry, only if you consent | §3 (b) |
| Error log file | Checking problems | Local file on the device | No |
| Whether you consented to crash reports | Remembering your choice | [Windows] Settings file on the device | No |
| List of desktop file names | [macOS] Auto food search (§6) | Memory only; file contents are never read | No |
| Launch at login setting | Your choice | [macOS] Login items, [Windows] registry | No |
| Google account connection (refresh token) | Keeping the Google Calendar connection | [macOS] Keychain, [Windows] the current user's Credential Manager (persisted on the local device) | To Google only (§3 (f)) |
| Google Calendar event data (fields used by the app: ID, title, start and end time, and all-day status) | Showing upcoming events, event reminders, overlap notices | The app manages its event list in memory and does not write titles to its schedule file. See §14 for system notifications and macOS networking caches | To Google only (§3 (f)) |
| Events you confirm to add (title, date, time) | Adding events to your Google Calendar | Written to your Google Calendar. App event-list and notification handling is described above and in §14 | To Google only (§3 (f)) |
| Gmail message subject, sender, preview, and message ID (only in versions that offer the Gmail feature and only if you turn it on) | Finding events in mail | Mail content is not written to the schedule file; message IDs are kept in schedule.json on the device so the app does not ask twice | To Google only (§3 (f)) |
| Schedule feature settings, markers for reminders already shown (event ID and start time), list of granted permissions | Not showing the same reminder twice | schedule.json on the device | No |
The app communicates with outside services only in the following cases.
(a) When you use a promo code — Google Firestore (United States)
When you enter a promo code and confirm, the code is sent to Google Firestore managed by the developer to check whether it is valid. If it is valid, the fact of use and the time of use are recorded.
[macOS] To prevent reuse, a random per-device identifier is recorded together. This identifier is randomly generated and is not linked to identity information such as your name or email address.
[Windows] A new one-time value is recorded each time, so the device is not identified.
This happens only when you enter a code; nothing is sent periodically or automatically.
(b) Error diagnostics — Sentry (United States) · [Windows] only · off by default
Only if you consent, when the app quits unexpectedly, the error message and location (stack trace), the runtime environment (operating system and list of installed components), and the app version are sent.
Consent is asked on first launch, is off by default, and can be turned off at any time from the tray menu.
Names, email addresses, and payment information are not sent, and your user account name and computer name are removed before sending.
No usage history or behavioral statistics are collected. [macOS] versions do not have this feature.
(c) In-app purchases — Apple App Store / Microsoft Store
The app communicates with each store when you buy or restore purchases. [macOS] When the app starts, it automatically checks whether you have already purchased an item. Payment method information is managed by each store and the developer cannot access it.
(d) When you tap a link
If you tap the support link (ko-fi.com), the external site opens in your default browser. The app does not add your information, but your IP address and similar information are passed to that site in the process of connecting.
(e) When you share
[macOS] When you share a pet image, the image file and text are delivered to the destination you choose (Mail, Messages, AirDrop, etc.). You choose the destination yourself.
(f) When you connect your Google account — Google LLC (United States)
When you click "Connect Google Calendar" in the app, you sign in to Google and grant permission in your browser.
After that, the app communicates directly from your device with Google APIs (oauth2.googleapis.com, www.googleapis.com, gmail.googleapis.com) over HTTPS. This calendar integration has no developer-operated relay or calendar-storage server. See §14 for operating-system notification and cache handling, and §3 (b) for optional Windows error diagnostics.
Other than (a)–(f) above, the app sends nothing automatically. No advertising SDKs or behavioral analytics tools are used.
| Recipient | Country | When and how | Items | Purpose | Retention |
|---|---|---|---|---|---|
| Google LLC (Firestore) | United States | HTTPS when you enter a promo code | Code string, time of use, [macOS] random per-device identifier | Checking codes and preventing reuse | Until the purpose of code management is fulfilled |
| Functional Software, Inc. (Sentry) | United States | [Windows] HTTPS when an error occurs, only with consent | Error message and location, runtime environment, app version, source IP | Finding and fixing the cause of errors | Per Sentry's retention policy (up to 90 days) |
| Apple Inc. / Microsoft Corporation | United States | When buying or restoring purchases | Product identifier, entitlement information | Payment and purchase verification | Per each company's policy |
The Google account connection (§3 (f)) is an exchange directly between your own Google account and your device; the developer does not receive and pass on the information.
You may refuse international transfers. (a) does not happen if you do not use promo codes, (b) does not happen if you do not consent or turn it off from the tray menu, and (c) does not happen if you do not use in-app purchases.
The developer does not sell your personal information or provide it to third parties for marketing.
The companies in §4 are processors that handle information only as needed to provide the service.
When this feature is on, the pet periodically checks the list of file names on your desktop to find food and moves the target files to the Trash. Files you drag onto the pet are also moved to the Trash.
Data on your device is kept while you use the app and is stored in the following locations.
~/Library/Application Support/Blanky/, ~/Library/Group Containers/%APPDATA%\Blanky\, error logs in the temporary folder, registry HKCU\Software\Blanky⚠️ Deleting the app does not automatically remove the data and settings in these locations.
To remove them completely, delete these folders and registry entries yourself.
Data recorded outside your device is limited to promo code usage records (code, time of use, [macOS] random per-device identifier) and is destroyed once the purpose of code management is fulfilled. To request deletion, contact us at §10.
When you disconnect your Google account connection with "Disconnect" in the app, the app performs removal of the locally stored refresh token and account records in schedule.json (reminder markers, message IDs, granted permissions) and asks Google to revoke access. Events you added remain in your Google Calendar. This procedure does not clear previously delivered system notifications or network caches; these are managed according to operating-system behavior and response cache directives. Before uninstalling the app, you can disconnect in the app or remove access on your Google Account's third-party connections page.
You may request access to, correction, deletion, or suspension of processing of your personal information.
You can delete on-device data yourself in the locations in §7, and we will delete promo code usage records upon request at §10. To verify your identity, we may ask for the code you used.
[Windows] Consent to crash reports can be withdrawn at any time from the tray menu.
You can disconnect your Google account at any time with "Disconnect" in the app's Settings tab or from your Google Account's third-party connections page (https://myaccount.google.com/connections).
The app is not directed at children and does not knowingly collect personal information from children under 14 (under 13 in regions where COPPA applies, such as the United States).
Send privacy questions and requests for access or deletion to the email above.
If you need counseling or want to report a privacy violation, you can contact the following Korean agencies.
October 16, 2026: Clarified the existing Google user data protection mechanisms and corrected the descriptions of app storage and operating-system handling (§2, §3 (f), §7, §13, §14). This clarification does not add permissions or change app behavior. The previously announced October 17, 2026 effective date remains unchanged.
The latest version of this policy is available at the addresses below.
When this policy changes, we update the changes and effective date in this document and announce them at the addresses above and through the app's distribution channels 7 days before they take effect.
Blanky's use and transfer to any other app of information received from Google APIs will adhere to Google API Services User Data Policy, including the Limited Use requirements.
When you connect your Google account, Blanky applies the following safeguards.
This page is the English version of the privacy policy bundled with the app. Contact: blanky@blanky.kr