Privacy Policy

1. Who we are and what this covers

This policy describes how Daiki Hirose (“we”, “us”) handles your information in the app Nap Pile (Japanese name すやぽん, the “App”). The App is a puzzle game in which you stack sleepy animals on a bed to merge them.

2. Information stored on your device

The App has no account registration. The following information is stored on your device. Information used for analytics, purchases and advertising consent is also processed through external services as described in Sections 3 and 4:

• Game progress (scores, best records, daily streak including rest days and daily gifts received, the collection, how many games you played today, Snooze growth and sleep-talk records, favorite and accessory choices, nicknames you set, Today’s challenge stamps and milestone rewards received, and the score, duration and similar figures of a game in progress (used to record games you quit partway))
• A copy of a game’s figures, such as the score and Shards, taken when a revive offer (the screen that asks whether to keep playing or end the game) appears (used so that a game left with the offer still showing when the App closed can be counted as a finished game — in your play counts, best records, Shards and similar records — on a later launch)
• Your in-game wallet (Shard balance, tools, purchased or unlocked themes and music, and treats you have given)
• Settings (sound, haptics, language, theme and its material, reminder time, whether you have answered the question about how you found the App, etc.)
• Your advertising consent choices (Section 4)
• Markers for ad requests whose result has not yet been fully sent (the request identifier, the placement and whether the ad started showing; used to send, on a later launch, a request whose result had not been fully sent when the App closed, as described in Section 3)

A copy of the wallet is also kept in the device keychain so it can survive reinstalling the App on the same device. The App also stores in the keychain a random identifier used only on your device so that Snooze growth is counted once per game. This identifier is not sent to any external service and does not move to another device. The App does not sync the entire wallet to an external service. Wallet information sent for analytics and purchase and grant records are described in Section 3.

The daily reminder is a local notification created on your device and is off by default. No push notification server is used to deliver it. When analytics is enabled, information about notification permission, settings, time (hour only) and launches from reminders is sent as described in Section 3.

3. Information processed through third-party services

The App uses the services below. Each provider processes the information described below and connection information such as IP addresses under its own privacy policy.

• Apple Inc.: payment processing through the App Store. We do not receive payment details such as card numbers; Apple handles them.
• RevenueCat, Inc.: verifying and restoring in-app purchases. Processes an anonymous app user ID, transaction and receipt data, purchase status and technical information such as device and OS details, and maintains records of Shards granted through purchases. This does not sync the entire wallet, including Shards earned through play or spent in the App. To aggregate advertising revenue, it also receives ad events (loading, display, clicks and load failures, placement, format, ad unit ID, impression ID, revenue amount, currency and revenue precision) tied to the same anonymous ID. It also shares a randomly generated per-device identifier from PostHog with RevenueCat so that purchase records can be matched against PostHog analytics. We do not share it while “Share usage data” is turned off. When you turn it off, the App requests deletion of this RevenueCat attribute and stops sending new identifier links. Previously sent data is not deleted. If the attribute is absent, RevenueCat may use its anonymous app user ID for its PostHog integration. This setting does not stop RevenueCat’s purchase verification, restoration, grant records or server-to-server purchase events.
• Unity Technologies SF (Unity LevelPlay / Unity Ads): serving and measuring ads. Through its mediation, ads from Unity Ads and from advertising partners participating in its ad exchange may be shown. Processes the advertising identifier, ad impression and click information, and device information. See Section 4.
• InMobi Pte. Ltd. (InMobi CMP / Choice): collecting and recording advertising consent for users in the EEA, the UK and Switzerland, and providing privacy settings for US state laws. Stores the consent state on your device under the IAB Transparency & Consent Framework (TCF) and passes it to advertising providers. US choices use GPP. The SDK also communicates to retrieve configuration and support consent management.
• PostHog Inc.: usage analytics and troubleshooting to improve the game. The following information is sent with a randomly generated per-device identifier and session identifiers:
  • App launches and updates, moves to the foreground or background (including the kind of screen that was showing when the App moved to the background and, during the tutorial, the tutorial step), first launch date, your optional answer, asked when you first use the App, about how you found the App (a multiple-choice answer with no free-text field and the fact that the question was shown, including choosing “Skip”; the answer or skipped choice is also saved once to the analytics profile for that identifier), launches from reminders, and tutorial starts, progress, exits, completion and rewards
  • Play counts, scores and best records, game duration and reason for ending, drops, merges, highest tier, bears born and vanished, chains, Shards earned and their breakdown, tool use and stock, revive methods, new records, discoveries and daily streak, and records of games you quit partway (how the game was left — you left the game screen, or the App closed during play — and the score, duration, drops and highest tier up to that point; if the App closed, this is sent on a later launch, usually the next one. A game left with a revive offer still showing when the App closed may be counted as a finished game on a later launch (usually the next one). When it is counted, its record may be sent then — the same items as a normal game end, such as the score, plus the number of days from the day the game was started to the day it was counted — together with a record of completing Today’s challenge, if it was completed as a result. When it is not counted, it is sent as a game you quit partway, with the kind of reason it was not counted)
  • When a daily streak breaks, the streak length and the gap since your last play; use of rest days (the date rested and the streak length); taps on the “Today’s gift” row (whether it was already received, whether it is a bonus day, and the day count); views of the gift sheet (the one that opens automatically on the home screen and “Streak rewards”; what opened it — automatically or a tap on the row — the day count and that day’s gift helper character) and how it was closed (×, button or swipe); and completing Today’s challenge (the challenge and the number of stamps collected) and receiving milestone rewards (the milestone and the kind of reward)
  • Reaching the play limit and the action chosen, where a pass offer was opened, products purchased (including the Rainy Window theme), purchase attempts and results (including the time from start to result and, when a purchase fails, the type of error), restore results, the store price and currency of the Nap Pass, Shard Pouch, or paid theme or appearance (material), sent when you start a purchase and with its result (including cancelled and failed attempts), shop tabs viewed, and tools, themes or music bought with Shards, their price and the balance after purchase
  • Pass status and plan, Shards granted by the pass when they are reflected (plan and amount), selected themes and music, music previews, number of themes owned, the theme material (such as felt) you selected and the one being shown, the number of Felt Themes and similar themes owned, whether you chose “Use it” or “Later” on the “A gift for you” card, and Shard balance (rounded to the nearest 100 in ongoing status updates; purchases made with Shards include the exact balance after purchase)
  • Snooze (character growth): the character chosen after a game, the EXP gained, its level and level-ups, how it was chosen (the number of candidates, whether it was a fallback pick, whether it was that day’s gift helper, whether it was a special moment, whether it is a favorite), marking a favorite, saving a nickname (only the character’s ID — the text of the name you type is never sent), putting on or taking off an accessory, taps on the cards shown after a game (card type, level and whether it was the first sleep-talk), opening a picture book and where it was opened from, and giving a treat (the character’s ID, the EXP gained, the level after the treat and the approximate range of your Shard balance after it — never the exact balance)
  • Changes to sound, volume, haptics, guide line, language and analytics settings; tutorial completion; notification permission, settings and time (hour only); where sharing was initiated and its result; the kinds of content on the share card (the kind of title, the kind of line, and whether the golden ring appears — never the title or line text, the score or names); when sharing succeeds, the share destination (the name iOS’s share sheet returns for the type of destination); successfully sharing a picture book and its destination; collection views and discovery counts; Records views, the number of days with records and where Records was opened from; views of reward notices and their type; and configuration loading results
  • Views and actions in first-time guidance and the home updates list; album views and the number of collected photos; the character and level of a viewed or shared album photo and the sharing result (not the photo itself)
  • Ad requests, results (including the error type and message when an ad fails to load or show; a request whose result had not been fully sent when the App closed is sent on a later launch, usually the next one, and may be sent more than once) and placements; the name of the ad network that served the ad, as returned by the ad SDK
  • How each ad display went (how it ended; whether signals that the ad started showing, was rewarded and was closed were received from the ad SDK; the time from request to result, until the ad started showing, and while it was shown; how many times and for how long the App was not in the foreground between asking to show the ad and the result; and the App’s state, such as foreground or background, when the result was decided); an identifier the App creates for each ad request (made from the time of the request and a counter for that launch; it contains nothing that identifies a device or a person); signals received from the ad SDK after the result was decided (the kinds of signals, the time since the result was decided, what ended the wait for further signals, and that ad’s placement, result and how it ended); free grants given when a video could not be loaded, and their result; views of the double-Shards offer (the amount offered and the total after receiving it); where consent screens were opened, whether GDPR applies and whether a response has been recorded (the App does not send consent strings to PostHog)
  • App and SDK names and versions, build number, device model, manufacturer and type, OS and version, screen size, whether the device is an emulator, your device’s time zone and language/region settings (e.g. Asia/Tokyo, ja-JP; read from your device settings, not estimated from your IP address), and event and sending times and identifiers. SDK launch events may include the URL that opened the App
  • Diagnostic information about unhandled JavaScript errors, rejected promises and errors that occur while displaying a screen, including error type, message, severity, location and call history (stack traces)

  In addition, we receive purchase-related events from RevenueCat — purchases (including Shard Pouches and paid themes and appearances), renewals, cancellations, cancellation reversals, expirations, billing issues, and changes between subscription plans (product ID, amount and currency, timestamp, transaction ID, store, etc.) — tied to the identifier above or to your anonymous RevenueCat ID. This transfer happens from RevenueCat’s servers and occurs regardless of your “Share usage data” setting.

  Analytics does not ask you to enter your name, email address or phone number, and the App does not link those details or the advertising identifier to the random identifier. It does not collect precise location such as GPS. We disable PostHog’s region estimation from IP addresses for information sent directly by the App; however, purchase events delivered by RevenueCat may include region information based on RevenueCat’s server location. Connection information such as IP addresses is processed when communicating with the service.

  You can stop new usage and error records in Settings under “Share usage data” (on by default). Information recorded before you turned it off may still be sent, and communication to retrieve SDK configuration may still occur. Turning it off does not delete information already sent (Section 6).

• Cloudflare, Inc.: delivering a configuration file we operate. Your IP address and similar connection data are processed transiently when it is fetched.

• Apple Privacy Policy
• RevenueCat Privacy Policy
• Unity Privacy Policy
• InMobi Privacy Policy
• PostHog Privacy Policy
• Cloudflare Privacy Policy

4. Advertising and consent

1. Ads you will see: video ads you choose to watch by tapping a button (revive, extra plays, double shards, shop) and at most one full-screen ad per day. Full-screen ads never appear during play and are not shown to Nap Pass subscribers. Stopping a video ad early has no penalty.
2. iOS tracking permission (ATT): For a newly installed App, iOS asks whether the App may use the advertising identifier (IDFA) after an explanation when you start your first regular game after completing or skipping the three-step tutorial. For people who have already finished the tutorial and update from an earlier version without having answered, it asks when Home first appears. If iOS has already recorded a choice or restricts the prompt, it is not shown again. If you allow it, advertising providers may use the identifier to show ads matched to your interests. If you decline, the identifier is not collected and you only see ads that are not based on your interests. Your choice does not change what you can play, and you can change it at any time in iOS Settings.
3. Users in the EEA, the UK and Switzerland: before the first ad, InMobi CMP (Choice) shows a consent screen asking for your consent to the use of information for advertising. You can change your choices at any time from “Privacy settings” in the App’s settings.
4. Users in certain US states: where state law applies, “Privacy settings” in the App’s settings lets you opt out of the sale or sharing of personal information. We ourselves never sell or share your personal information.
5. Ad content: the ad content rating is set to be suitable for all audiences.

5. Information we do not collect

When you choose to save a share card, picture-book image or bundled album photo through the iOS share sheet, iOS may ask for permission to add the generated image to your photo library. The App does not request permission to read the photo library and does not read your photos. The App does not ask you to register your name, email address or phone number and has no feature that reads your contacts, photos, health data or browsing history in other apps or websites. If you contact us, we receive your email address and the content of your request. The App does not collect precise location such as GPS. Advertising providers may, however, infer approximate location such as your country or region from your IP address (Sections 3 and 4). Usage analytics and crash reports go through PostHog (Section 3); these include usage, device information and error messages associated with a random identifier. You can stop new records in Settings. There is no account registration, cloud sync of the entire progress and wallet, or push notification.

6. Retention and deletion

Ordinary App storage is removed when you delete the App, but the wallet copy in the keychain and the on-device identifier used for Snooze (Section 2) may remain after reinstalling on the same device. Deleting the App therefore does not erase all information. The App has no feature that syncs the entire progress and wallet to another device. Purchase and grant records and analytics already sent are retained by external services separately from local storage. If you would like the purchase records tied to your anonymous RevenueCat ID, or the usage data tied to your random PostHog identifier, deleted, contact us (Section 10) and we will request the deletion. Information processed by Apple, Unity, InMobi, RevenueCat, Cloudflare and PostHog is governed by their policies and applicable law.

7. Your rights

The App is available worldwide. If you are in the EEA, the UK or another jurisdiction with similar laws, you may have the right to access, correct, delete, restrict or object to the processing of your information and to data portability. You can exercise these rights through the contact in Section 10. Our legal bases are: performance of a contract for purchases; your consent for interest-based advertising; our legitimate interests for fraud prevention and for basic ad delivery where permitted; and our legitimate interests for usage analytics (new usage records from the App can be stopped in Settings; RevenueCat’s server-side purchase processing is described in Section 3). You can withdraw consent at any time (Section 4). You also have the right to lodge a complaint with the supervisory authority in your country or region.

International transfers: Apple, RevenueCat, Unity, InMobi, Cloudflare and PostHog may process information outside your country, including in the United States and Japan. We rely on the safeguards each provider maintains.

8. Children

The App is not directed to children under 13, and we do not knowingly collect personal information from children under 13. If you are a parent or guardian and believe we have collected information from your child, please contact us (Section 10).

9. Changes

We may update this policy from time to time. Material changes will be announced on this page or by other appropriate means.

10. Contact

Please contact us at dhirose.business@gmail.com.