Made by Mizu 日本語
Game overview

Privacy Policy

Jigsaw Cute: Anime Card Puzzle

Scope

This policy describes information handled by Made by Mizu in connection with Jigsaw Cute: Anime Card Puzzle. Last updated: November 15, 2026.

Local game data

Stage progress, unfinished boards, collected artwork, settings, and Good/Bad illustration ratings are saved on your device. No email, password, or social-login account registration is required. Cloud saves are not provided. Illustration ratings and other usage observations are transmitted under the regional measurement choices described below.

Advertising and consent

We use Google AdMob and Google User Messaging Platform (UMP). Supported Android updates include mediation adapters for Unity Ads, Meta Audience Network and Liftoff Monetize (Vungle). The service that actually supplies an ad depends on available inventory, ad configuration, your region and consent state. These services process information for ad delivery, measurement and fraud prevention. The information involved and controls through consent and device settings are explained below and in each service’s policy.

Meta advertising privacy policy · Liftoff Privacy Policy

Advertising services may process and share approximate location inferred from IP addresses; device, OS, and app information; advertising IDs, App Set IDs, or similar identifiers; interactions such as app launches, taps, video views, ad impressions and clicks; diagnostics and performance data; and consent status for advertising, measurement, analytics, and fraud prevention.

Consent messages are shown where applicable. When required, you can change choices through the privacy entry in the game settings. Android settings also provide advertising ID deletion/reset and advertising controls.

Crash diagnostics and analytics

Firebase Crashlytics processes crash logs, stack traces, diagnostic installation identifiers, device/OS/app versions, and limited technical context such as screen, mode, and stage to investigate errors and improve quality. Game save files and support email contents are not sent as crash reports. On Android, crash diagnostics run automatically and do not stop when optional Game Usage Data is off. Supported iOS/iPadOS builds have a separate optional choice on the existing welcome screen and a Crash diagnostics switch in Settings → Support → Data and privacy. This choice starts off. If allowed, at later launches the app automatically sends unsent diagnostic reports temporarily cached on the device, including reports cached before permission, to Firebase Crashlytics. The diagnostic SDK may temporarily keep reports locally while submission is not permitted. Turning this choice off prevents new diagnostic submission handoffs by the app; information already handed to the SDK for submission or received by a service cannot be recalled. This device-specific choice is not copied with game data. It is separate from usage measurement, Apple tracking permission, and diagnostic processing by advertising providers.

The measurement-migration build sends game usage observations to Google Analytics for Firebase and uses daily BigQuery exports for analysis. Previously published builds use our Cloudflare measurement service. This choice is separate from Firebase Crashlytics diagnostics and advertising consent. Google also processes SDK-generated app-instance identifiers, sessions, use time, and device, OS and app information. Supported Android builds also use Tenjin as explained below.

Aggregate demographic analysis

Supported Android builds send the available Android advertising ID to Google Analytics for aggregate age and gender analysis when game usage data is enabled under the existing regional rules and your saved choice. Google signals may associate app usage records with information from Google users who have consented to that association. This can enrich aggregate demographic reports; it does not give Made by Mizu an individual user’s age or gender. Reports may omit or suppress data, and do not cover every user. You can stop game usage collection in the game settings and manage advertising-ID restrictions or deletion in Android settings. We respect those controls. This measurement does not enable personalized advertising or remarketing. We do not add advertising IDs to our custom gameplay-event parameters. Earlier builds without this capability continue to disable GA advertising-ID collection; iOS IDFA/ATT behavior is unchanged. Google processes data under its policies and the property’s retention settings. You can view or delete eligible Google activity in My Activity. See also Google’s Privacy Policy.

Content delivery

The app retrieves game images, delivery information, and reference time for calendar and event availability over HTTPS from Cloudflare services. The device time zone is used locally for Daily dates and rollover; this does not require GPS or location permission. IP addresses, request times, file paths, and network-related technical information may be processed for delivery and security. Game save files are not sent in content download requests.

Payments

This game has no in-app purchases or subscriptions. Made by Mizu does not collect payment card details or purchase receipts for this game.

Support

If you email support, we handle your email address, message, and any screenshots or device information you choose to provide to respond and investigate issues. Please do not include unnecessary personal information or information from other apps.

If you choose to submit a report about a Unity Ads advertisement, Unity may process the submitted report to investigate the advertisement and provide support. This is separate from emailing Made by Mizu.

Third-party processing

We use the services described above for ads, diagnostics, consent, and content delivery. Information may be processed in providers’ locations outside your country. Network communications use HTTPS or other transport encryption. See the providers’ policies:

Retention, deletion, and contact

On Android, clear app data or uninstall to delete local game data. On iOS/iPadOS, use Delete App; Offload App keeps documents and data. This does not delete separate OS or user backups, copies transferred to another device, or exported images and videos. Deleting local data does not delete information already transmitted to third-party services.

Support information is retained as needed for handling inquiries, investigating issues, and required record keeping. Providers retain advertising and diagnostic data under their own policies. Contact support@madebymizu.com with questions about access or deletion. Where SDK identifiers are needed, we will explain available steps within our ability to identify the relevant information.

Website and changes

This website uses the existing site’s Google Analytics and Google Fonts. Providers may process IP addresses, page views, and device/browser information when you visit. Website analytics is separate from the game’s production analytics setting.

We update this policy when features, SDKs, or data practices change and provide notices or consent where required for material changes. This game is intended for ages 13 and older. Age- and region-related advertising and privacy requirements apply. Contact us if you believe information about a child under 13 has been provided.

Game measurement and platform/regional choices

In supported updated Android builds, a separate usage-data prompt is shown only in the prior-consent regions maintained in one common list. Collection begins after permission there, and without that prompt in other identified regions. Unknown regions or failed connections do not automatically enable collection. Earlier refusals and collection stops are preserved; an answered prompt is not repeated merely for a restart, app or SDK update, or notice-number change. In supported builds you can stop or change collection in Usage Data in Settings / Support Center. All game features remain available without measurement. This choice is separate from Terms and advertising consent. Earlier grants are not automatically expanded to the new ad-revenue scope; gameplay and earnings before permission are not backfilled. Older builds retain their version-specific measurement.

In supported iOS builds, usage measurement starts only when you select the optional usage-data choice on the existing first-launch Welcome screen or later enable it in Settings. It is unchecked initially; you can start the game without selecting it. This choice is separate from accepting Terms, advertising consent, and Apple tracking permission. Region alone does not automatically enable usage measurement. Saved explicit answers are retained; an earlier regional default is not treated as your permission. You can stop collection in Settings. Gameplay and ad revenue from before permission are not backfilled. If the choice cannot be saved, usage measurement remains off and you can still play.

A regional check contacts Cloudflare without an installation ID or gameplay records. Cloudflare-derived country information is used for this check, not stored with IP addresses in the measurement database. We do not request GPS or infer country from your language or time zone. Automatic activation on Android is checked at startup, on return to the foreground, and while using the app; unsuccessful checks stop measurement, not play.

We compare usability, return visits, progress, artwork preferences and feature or effect variants statistically. Fields are a random ID for this installation, app version, Android/iOS type, dates, screens and level reached, image IDs, puzzle starts/completions, use time and interruptions, export results and latest Good/Bad ratings. Short foreground intervals support cumulative five- and ten-minute counts, excluding background and earlier time. Profile observations include viewing, editing, achievements and single/all reward claims, equipped icon/theme IDs and explicit share/save/copy outcomes. Video observations include playback controls, preparation/download, initialization, first frame and failure stages. Completion E/G assignment and exposure/Next/exit, and review-prompt trigger/copy/image assignments, displays, actions and store-open outcomes use the same installation ID. Actual review submission or delivery to a share recipient is not observed.

Our custom gameplay events do not contain profile names, shared text, names, email addresses, advertising IDs, precise location, photos, artwork/video contents or game save files. The random installation ID is not linked across reinstalls. The ByteBrew migration build does not send this Google Analytics ID to ByteBrew or join individual records using that shared ID. Advertising-ID handling is described below. We do not sell detailed gameplay observations or use them for behaviorally targeted advertising. Google signals association is described above.

For measurement-migration builds, Google Analytics for Firebase receives and processes usage observations, which Made by Mizu analyzes in BigQuery. Communications are encrypted and processing may take place outside your country. Retention follows Google Analytics retention settings and the applicable service policies. Our current verification-only BigQuery Sandbox has a 60-day table expiry. Identifier-free aggregates may be kept for longer comparisons. Individual records received from older builds on Cloudflare Workers and D1 continue to become eligible for gradual deletion 90 days after receipt. Deletion exactly on day 90, and anonymity of all retained information, are not guaranteed. Existing D1 compact initial-measurement, retention and time state, latest ratings, experiment assignments and replay-control numbers remain for long-term comparisons. These compact states are separate from individual records eligible for deletion after 90 days. Cloudflare continues to provide artwork, video, reference time and regional checks.

Stopping measurement discards the app’s unsent observations and stops new collection. This does not automatically delete or recall records already passed to the SDK or received by a service. SDK identifiers are not recreated on every launch. Contact support@madebymizu.com for access or deletion questions. Network and settings failures do not hold up play, and observations may be lost.

Image export and private cache

Home collection artwork may use short silent looping videos. Album starts with a still image and plays its clip only after you select Play. Album export includes both the illustration and its clip when a clip is available. Profile names, ownership/equipment, achievements and app-open dates are saved locally; explicit Profile card export/share creates a PNG. Acquired collection artwork is retained in app-private storage for the Album. Used normal puzzle images, Daily images unused for a period, and Event images at least three days past the event end are eligible for private-cache cleanup at a safe opportunity. Image cleanup does not revoke level progress, completion records, or access earned through rewarded ads.

Save adds new JPEG images and, where available, MP4 clips through the operating system’s export facility. The app has no feature to enumerate, read back, overwrite, or delete photos after export. Private-cache cleanup does not delete JPEGs saved to Photos or other export destinations. Exported JPEGs may remain after app data is cleared or the app is uninstalled.

Advertising install attribution (Android attribution update)

The ByteBrew migration build measures install attribution and permitted foreground sessions for new Android installations after the update. Devices with evidence of earlier use or restored progress, or an inconclusive migration check, are not registered as new acquisitions. Historical AppMetrica records remain subject to that service's policies. Detailed gameplay observations remain with Google Analytics and are not fully mirrored to ByteBrew. ByteBrew processes SDK identifiers, available advertising IDs, Play install referrer, app/device/OS/session information and connection IP addresses. Android GA advertising-ID handling is described in the aggregate demographics section above. Refusals, regional conditions and device advertising-ID deletion are respected; we do not activate the SDK without the applicable permission or bypass refusal. In supported revenue builds, eligible users under the newly disclosed revenue scope have actual impression revenue in USD, ad format, public ad unit and the available monetization network sent to ByteBrew. Install data, permitted foreground app-open/return sessions and ad-revenue data of eligible users attributed to Unity Ads are shared with that partner for advertising measurement and revenue optimization. Organic installs are not classified as paid acquisitions; complete matching, complete revenue capture or immediate notification is not guaranteed. Purchases, additional crash records, artwork/video contents and save files are not sent to this MMP. Processing may occur abroad, with ByteBrew policies governing retention and deletion. Stopping collection does not automatically recall admitted communications or information already received.

Supported Android builds use Tenjin alongside ByteBrew. This applies to devices that begin using the game with a supported build and are permitted to send usage data. Devices with evidence of earlier use or restored progress are not enrolled as new acquisitions. Tenjin processes SDK identifiers, available advertising IDs, the Play install referrer, app/device/OS and foreground-session information, and connection IP addresses. Where ad-revenue measurement is also permitted, we send actual impression revenue, currency and the public ad unit. AppLovin receives installs and permitted app-open/return information from devices meeting Tenjin's existing measurement conditions regardless of acquisition source, for advertising matching and measurement. This includes eligible organic users, users acquired through other networks and eligible users outside campaign target countries; it does not classify every participant as an AppLovin acquisition. We do not currently forward ad revenue or purchase information from Tenjin to AppLovin. TikTok receives installs and permitted foreground app-open/return sessions from Tenjin-eligible devices regardless of acquisition source, so it can match them against its advertising records. Ad revenue is shared only where that measurement is also permitted. TikTok sharing therefore includes eligible organic users and users acquired through other networks; it does not classify every participant as a TikTok acquisition. The normal Unity Ads measurement integration uses ByteBrew; Tenjin does not forward these records to Unity Ads. Detailed gameplay histories and save files are not sent to Tenjin. Existing refusals and collection stops remain in effect. Processing may occur outside your country; Tenjin's policies govern retention and deletion. Tenjin Privacy Policy

Builds with Tenjin paused do not start the Tenjin SDK or send new install, app-open or ad-revenue records to Tenjin. The explanation above and Tenjin’s policies continue to apply to records sent by earlier supported builds and to continued use of those builds.

On supported new Android installations, we use the Meta App Events SDK to measure installs and app opens while game usage data is enabled. Meta processes SDK identifiers, app and device information, install referrers, available advertising IDs and connection IP addresses to measure Meta ads. This SDK does not receive detailed gameplay, purchases or ad revenue. Regional conditions and device advertising ID restrictions are respected. Your existing usage-data choice is retained and can be changed in Settings.

ByteBrew Privacy Policy · Yandex policy for earlier builds

Related links