VIP POP! / PROTOTYPE

Privacy policy

Prototype policy framework · Updated November 2, 2026

What is available now

VIP Pop! is a static browser game. Accounts, advertising, analytics SDKs, payments, photo uploads and paid custom characters are not live. These pages prepare for possible future releases; accepting the demo choices does not activate advertising or upload anything.

Current browser storage and requests

The game saves your personal best in localStorage as vip-pop-best. Stage Tour stores local unlocks, stars, best scores, best remaining time, schema/rules versions and an update timestamp as vip-pop-progress-v1. Stage progress stays separate from the classic best score; unavailable storage falls back to this page’s memory and shows a warning. The local consent demonstration saves your explicit advertising and analytics choices, a schema version and a timestamp as vip-pop-consent-v1. These local values are not sent by the game to a server. We do not currently set advertising cookies. Storage can be cleared in your browser; clearing it removes your saved best, stage progress and choices. If storage is unavailable, choices last only for the page session.

Loading a hosted copy sends ordinary requests to that host. A host may process IP addresses, requested page URLs, browser information and access logs under its own configuration. This repository does not configure hosting access logs or their retention; the operator must disclose its actual hosting setup before a public release. Opening the files locally does not require a game backend.

Planned advertising and consent — not live

If Google AdSense or H5 Games Ads is enabled later, advertising providers may process IP addresses, page URLs, device/browser information, cookies and other identifiers for ad delivery, measurement and related purposes. Optional analytics may process usage events. Providers, purposes, retention criteria and applicable regional rights must be specified before release. Unknown or rejected consent will prevent optional ad and analytics requests under the planned integration.

The current banner is a local UI demonstration, not a certified CMP or a production compliance solution. Before advertising launches in the EEA, UK or Switzerland, it must be replaced with a Google-certified CMP integrated with IAB TCF. Use Privacy choices to review or withdraw the demo choices at any time. Withdrawal changes local settings; it cannot undo processing already performed by a future provider. Applicable US opt-out rights and Global Privacy Control handling must also be implemented before launch.

Planned private custom characters — not live

A future adult-only service would need account email and login state; uploaded photos and cleaned inputs; generated candidates and selected avatars; display names and custom quotes; order IDs, payment status and necessary transaction records; moderation decisions, complaints and security records. Hosting, authentication, payment, storage, AI generation and moderation processors would be identified before launch, along with processing regions, cross-border safeguards and contracts. Photos, emails and quotes must not be placed in URLs, advertising parameters or analytics events. Full card details are intended to stay with a hosted payment provider.

Photos would be used only for the authorized private character workflow, not automatically for marketing or facial identification. The site has no photo-submission UI today. A separate developer-only command-line image PoC sends its chosen test input to the locally configured image-editing provider when explicitly run; visiting this game never invokes that tool. Its provider retention terms have not been established for production.

Proposed retention — implementation pending

The plan proposes deleting original photos, cleaned inputs and intermediates within 24 hours after delivery or rejection, with a seven-day maximum; unselected candidates within 24 hours after selection; and selected assets and quotes while retained by the user. Deletion would disable access immediately and clear online copies within 24 hours. Backups would roll off within at most 30 days. These are proposed targets, not active service guarantees. Order and moderation record retention must be set for applicable tax, dispute and security needs. External processor copies follow their contracts; deleting a site copy does not promise immediate deletion everywhere.

Requests and future changes

Before collecting uploads or accepting payment, the operator must publish its identity, a monitored contact, applicable rights, legal bases, final retention periods and refund/deletion procedures. See Contact for the current contact limitation. Do not submit sensitive data to this prototype. This framework must be updated to match actual services before those services launch.