Bot: A Small Life · 흰새우랩 (White Shrimp Lab)
Privacy Policy
This policy applies to White Shrimp Lab's Bot: A Small Life app and Bot information pages. Versions offering optional Apple/Google login use the shared Workshop login service. Effective November 9, 2026. This English translation preserves the existing policy.
iOS versions with purchases use a payment SDK for purchases and restoration. iOS 1.0 and the free Android edition do not initialize it. Existing transaction, entitlement and deletion-recovery records and server-side deletion checks are separate.
1. Information and purposes
- Age: an on-device, secure-storage self-confirmation of being 14 or older. No birth date or identity document is requested.
- Access: random account/Bot identifiers, server hashes of device credentials and a public Bot number for access, progress/purchase linking and request recovery. IDFV is used by versions with the payment SDK.
- Optional login: Apple/Google identifiers and email, names/profile-photo URLs supplied by the provider, authentication sessions, the link between the shared login and game owner, consent version/time and encrypted recovery information. These restore the same game and purchase entitlements; different games are not automatically merged.
- Game progress: birth, visits, interactions and death events, time zone, generations, relationships, habits, places, names, backgrounds and records to calculate life and provide records/decorations.
- Purchases: product, transaction and original-transaction identifiers, store/environment, purchase, refund, entitlement and verification times for verification, restoration, refunds and duplicate-grant prevention. Purchase metrics apply to versions with the payment SDK.
- Deletion/recovery: request numbers, hashes of codes/credentials, policy copies, processing/verification/completion states and times for deletion and request recovery.
- Support: sender email, correspondence, voluntarily supplied device/app details and minimum verification evidence for support and rights requests.
- Technical data: IP/access/error logs, city/country-level approximate location inferred from IP, technical device/app and crash information for delivery, security and diagnosis.
Guests do not need to log in. A login link is created only after reviewing the notice and consenting. The game does not store Apple/Google passwords or request card numbers. Random identifiers remain linked to progress and purchases, so this processing is not described as anonymous.
2. Collection and public information
We process information through app use, server requests, purchase-service verification, explicit deletion requests and support messages. The app does not implement tracking across other companies' apps or websites for advertising.
No public ranking is currently operated, and user-entered Bot names are not published. Public tip totals include valid production purchases and exclude tests/refunds. Device secrets and full private life records are not published. Accounts with deletion requests are hidden from public lists.
The device stores session, last-state, purchase and deletion-recovery information. This web guide does not collect deletion credentials or send deletion requests. Do not put recovery credentials in URLs or email. Recovery codes introduced in 1.1 are generated/displayed on-device, not newly stored on the server; keep them like passwords.
3. Retention and disposal
- Game data: retained during use. Ordinary access/public exposure is blocked after a deletion request; game and device-recovery items are cleaned up after purchase-service checks.
- Login links: retained while used to access the game. Bot deletion removes this game's link and encrypted recovery information. An active linked account is not automatically deleted merely because web signup is unfinished.
- Minimum legal transaction records: where applicable, contract/cancellation and payment/supply records are kept for five years from the event; consumer complaint/dispute records for three years after closure. This does not mean all game data is kept for five years.
- Ordinary support: deleted 90 days after closure, except necessary records for an actual dispute or separate legal duty.
- Deletion-status recovery/duplicate prevention: minimum necessary records remain while the purpose continues and are disposed of when it ends and no separate basis remains. Hashing does not make records anonymous or justify indefinite retention.
- Logs/backups: processed for necessary delivery/security/recovery periods under provider schedules, deletion instructions, contract termination and legal exceptions. Active-data deletion and backup/log cleanup may not finish simultaneously.
Electronic files are deleted to make recovery difficult; paper records are shredded. Legal retention is managed separately by purpose, records, start and end date. A code's 15-minute validity is not the deletion deadline for all data.
4. Processing services and international transfers
The existing Korean policy discloses necessary overseas processing/storage under Article 28-8(1)(3)(a) of Korea's Personal Information Protection Act. The listed subprocessor scope depends on features; it does not mean every item is sent to every provider.
- Supabase Pte. Ltd. / Supabase, Inc.
- The primary DB and corresponding backups are in Seoul, Korea. Support/operations include Singapore and the US; listed configuration/feature-flag subprocessors include Hungary. The provider describes log storage in EU data centers without a specific country. Account/authentication hashes, game, minimum transactions, deletion recovery and technical/security logs support storage, API delivery and incident response. Transmission is by HTTPS during app/API use and event handling, with necessary support access. Retention follows service/item purposes or earlier deletion instructions. The DPA's deletion after the 30-day return period at contract termination is separate from individual account deletion. Contact: privacy@supabase.io. Locations · DPA/subprocessors.
- RevenueCat, Inc.
- Processing includes US AWS and listed US subprocessors; AB180 for Korean customer support is in Korea. Versions with the SDK send account identifiers, IDFV, purchases, entitlements, refunds and necessary technical information for verification, restoration, refunds and purchase metrics. HTTPS transmission starts at SDK initialization, before any purchase, and during purchase/restoration. Free 1.0 does not use these SDK transfers. When handling deletion, the server can check whether an existing purchase customer exists and verify cleanup by HTTPS GET. Records are kept as needed for the purchase service and cleaned up on customer-deletion requests, subject to backup and legal-retention exceptions; immediate deletion of all internal copies is not guaranteed. Contact: compliance@revenuecat.com. Privacy · DPA.
- Vercel Inc.
- Listed processing includes main US facilities and subprocessors in the US (hosting/security/logs), Spain (analytics) and UK (support), as applicable to features. This is not a guarantee of individual transit countries or a fixed storage region. Web IP/request/error/technical records support delivery, security and diagnosis. Login/account callbacks use one-time authentication codes, identifiers, email and session cookies for authentication, session continuity and user requests. The deletion guide does not collect device secrets or recovery codes. Requests use HTTPS. Customer data follows deletion functions/instructions during service and reasonable processing periods after contract termination, with separate legal exceptions and service-log purposes. Contact: privacy@vercel.com. DPA · Subprocessors.
- Google LLC / personal Gmail
- Support email uses the consumer policy's worldwide server scope. Published locations include the US, Taiwan, Japan, Singapore, Ireland, Netherlands, Denmark, Finland, Germany, Belgium, UK, Uruguay and Chile; this is not a complete fixed location list for a personal Gmail account or a Workspace region guarantee. Sender/reply addresses, correspondence and minimum app/device information are processed on receipt/reply for support and rights requests. Operator web access uses HTTPS; email delivery follows Google's mail process. Operator copies, including sent mail, attachments and trash, are deleted 90 days after ordinary support closure; Google's active/backup deletion schedules and legal/security exceptions are separate. Contact: googlekrsupport@google.com. Privacy · Locations · Retention.
Optional Apple/Google login authenticates on the provider's screen. Identifiers, email (including Apple relay addresses), supplied name/photo URLs and authentication results pass to Supabase's shared login service. Providers handle their own accounts/security records under their policies. Game deletion does not delete their accounts or all provider records. Specific authentication-request countries or immediate deletion are not guaranteed. Apple login privacy · Google privacy.
Linked official disclosures describe published processing scope, not all internal routes or immediate disposal of every copy. Apple separately processes App Store purchases/refunds and accounts; game deletion does not remove Apple's statutory records.
5. Rights and verification
Contact us for access, correction, deletion, restriction, withdrawal of consent, objections or an explanation of international processing/transfer refusal. We explain applicable legal limitations and procedures. Representative requests require lawful authority and minimum verification. Help remains available without app access; public Bot/order details alone do not authorize deletion. We do not accept passwords or device/recovery secrets by email.
Refusing processing needed for progress or purchase verification may limit the corresponding feature. Hosting/CDN processing occurs when opening web pages. Email support is optional and not needed for ordinary play. Transfer refusal/deletion does not automatically cancel or refund purchases.
To close the shared login account, use Login Account Management with your Apple/Google login. Delete linked Bot data in the app first. Bot deletion does not automatically close other Workshop services.
흰새우랩 (White Shrimp Lab) · Support and privacy contact
baegsu100@gmail.comPlease include your device, OS and app version, when the issue occurred, the message shown and what you tried. For purchase issues, include the product name and store.
Do not send passwords, recovery codes, device secrets, deletion codes or card details. Do not attach original receipts to your first message. We will explain the minimum evidence and a safe verification method if needed. Opening an email link does not send a request.
Korean privacy assistance: KISA and Personal Information Dispute Mediation Committee.
6. Protection and age
We use authentication hashes, access restrictions, secure on-device recovery storage, limited operational permissions, encrypted transport and secret masking. Confirmed security incidents follow applicable notice/reporting duties.
The game is for ages 14 and over. The app stores a self-confirmation only in secure device storage before service use, without birth dates, identity documents or a parental-consent procedure. Under-14s may not use it; users/guardians can request rights concerning information already processed. The App Store content rating is separate from this service age requirement.
7. Effective date and history
Effective November 9, 2026. Material changes follow applicable notice or consent requirements and appear here. The November 9 revision added optional Apple/Google login, game links, encrypted recovery, consent records and the distinction between game deletion and shared-account closure. Guest play and existing progress/purchases remained available.
October 31 clarified purchases/payment SDK from 1.1 and recovery codes without changing processing categories, purposes, retention or providers. October 27 clarified that no public ranking is operated and user-entered Bot names are not published. The original policy took effect October 26, 2026.