Privacy Policy

1. Scope

This Policy applies to Video Poker Instant (Meta App ID 3839625092741356), the official Minimum Studio website at home.minimumstudio.net (the “Website”), and any retained support, transaction, or legal records from the discontinued Big Hand Slots service (Meta App ID 865792457400425). It does not replace the privacy notices of Meta, an app store, a payment provider, an operating-system provider, or another third-party platform.

2. Information We Handle

2.1 Video Poker Instant

Build 609 is a testing-only review candidate that uses Instant Games SDK 7. It uses the player's app-scoped Instant Games identifier to associate the player with the same gameplay account across sessions. The identifier is sent to the Minimum Studio game backend as the gameplay account key, and the game derives a pseudonymous, app-specific Player-… label from it. The raw identifier is not displayed. Build 609 also uses FBInstant.player.getDataAsync() and FBInstant.player.setDataAsync() to restore and save game preferences and launch state through Meta Player Data.

Build 609 does not call FBInstant.player.getName() or FBInstant.player.getPhoto(). It does not use data or functionality governed by gaming_profile, gaming_user_locale, gaming_user_picture, user_friends, email, or pages_messaging. Meta's native launch container separately presents its own platform-level name and profile-picture disclosure. Any locale or country values sent by Build 609 are fixed application constants and are not obtained from the player's Meta profile or device location.

Where Meta supports FBInstant.player.getConnectedPlayersAsync(), Build 609 uses only the connected-player count to calculate and display a Social Bonus. It does not use the user_friends permission or a Facebook friend list, and it does not display connected-player identifiers, names, or profile photos. Only the derived reward quantity is sent to the game backend when a player claims the Social Bonus.

The App creates gameplay and account information associated with the app-scoped player identifier. This may include level, virtual-currency balance, gameplay progress, preferences, purchase status and receipts, social or invitation activity, and security or diagnostic records. Build 609 stores game-account information in the Minimum Studio game backend and preferences in Meta Player Data. Its legacy ranking and tournament interfaces are unavailable, it does not connect to the legacy Google Firebase Realtime Database for gameplay data, and it contains no call to the retired Messenger webhook. Minimum Studio does not receive full payment-card details.

Production Build 594 remains the unchanged legacy release. It has received and may continue to process app-scoped player identifiers, player names, profile photos, locale, ranking and tournament information and uses legacy Google Firebase systems. It also contains an obsolete call attempt to a Minimum Studio-controlled Messenger event endpoint; that endpoint has been decommissioned and no longer processes events. Historical profile fields are not read by Build 609. Migration to Zero Permissions and verified deletion or irreversible de-identification of historical profile fields will be handled separately after the Term 7.a review.

2.2 Big Hand Slots

Big Hand Slots has ended service and no longer initiates new gameplay data processing. Minimum Studio continues to accept privacy and deletion requests concerning any retained support, transaction, or legal records. Information held independently by Meta, an app store, or another platform remains subject to that provider's own privacy controls and notices.

2.3 Website analytics

The Website processes limited usage and technical information, including:

• random visitor and session identifiers;
• page title, page path, host name, and time of access;
• browser language, referring host, screen size, and general device type;
• links selected, the section containing the link, and the destination domain; and
• technical information processed by Google Analytics and Firebase, which may include online identifiers, browser or device information, and general geographic information derived from an IP address.

The random Website visitor identifier is stored in local storage, and the session identifier is stored in session storage. Minimum Studio does not ask users to enter a name, account name, or email address for Website analytics.

2.4 Support communications

If you contact us, we receive the email address and any information you choose to include in your message. Please do not send passwords, full payment-card numbers, government identifiers, or other unnecessary sensitive information.

3. How We Use Information

We use the information described above to:

• identify returning players and provide access to gameplay accounts;
• save and synchronize gameplay progress, balances, preferences, and purchase status;
• calculate and display a Social Bonus from the number of connected players, where Meta supports that API;
• provide invitation and sharing dialogs without placing player identifiers in shared content;
• operate the controlled migration from, and retirement of, legacy ranking, tournament, profile-display, context, and Messenger features;
• operate, maintain, secure, analyze, and improve the Website and our games;
• understand aggregate page usage and outbound link activity;
• deliver purchased content and verify transaction status where necessary;
• respond to support, privacy, and deletion requests; and
• comply with law, enforce our rights, and prevent abuse or security incidents.

4. Third-Party Services

Build 609, the testing-only review candidate, relies on Meta Platforms for the Instant Games SDK, player storage, supported connected-player, invitation and sharing features, payments, ads, analytics events, and game delivery, and on Amazon Web Services (AWS) for the game backend. It does not initialize or connect to the legacy Video Poker Firebase Realtime Database and contains no call or endpoint for the retired Messenger webhook. The legacy production build contains an obsolete call attempt to that decommissioned endpoint, which no longer operates. Historical records may remain in legacy systems pending deletion verification, but they are not read or used by Build 609. These service providers process information on Minimum Studio's behalf or independently under their applicable terms and privacy notices.

The discontinued Big Hand Slots service may have relied on app stores, console platforms, operating-system providers, and payment processors. The Website may rely on Google Analytics and Google Firebase. Those providers may independently process account, device, transaction, network, or usage information under their own notices and terms. The Firebase service used for Website analytics is separate from the retired Video Poker gameplay database.

5. Sharing and Sale

Minimum Studio does not sell Platform Data or personal information and does not share it for cross-context behavioral advertising. Build 609 sends the player's app-scoped identifier, necessary game-account information, a derived Player-… pseudonym, blank photo and email fields, and fixed application locale and country constants to the game backend. It does not send any Meta-provided name, profile photo, email address, Meta locale, or Facebook friend-list data to AWS or Google Firebase. The pseudonym and fixed constants are not derived from the user's Meta profile. Information may also be disclosed when required by law, to protect users or our legal rights, or as part of a corporate transaction subject to appropriate safeguards.

6. Retention

Video Poker Instant game-account information is retained only while needed to operate and secure the App, maintain legitimate gameplay and transaction records, resolve disputes, or comply with law. Historical player names and profile photos created by the legacy version remain pending verified deletion and are not used by Build 609. They will be deleted or irreversibly de-identified in accordance with Meta's requirements after the migration safeguards are verified. When other Platform Data is no longer necessary, when a verified user requests deletion, when Meta requests deletion, or when deletion is required by law, Minimum Studio deletes or irreversibly de-identifies the associated records as soon as reasonably possible and generally within 120 days, unless retention is permitted or required by applicable terms or law.

Website analytics is retained only for as long as reasonably necessary to understand and secure the Website, and old records may be deleted or aggregated. A visitor identifier remains in the user's browser until local storage is cleared; a session identifier normally expires with the browser session. Support communications are kept only while needed to resolve a request, maintain reasonable business records, or comply with law.

7. Security

We use reasonable administrative and technical measures designed to protect information against unauthorized access, alteration, disclosure, or loss. No method of transmission or storage is completely secure, so absolute security cannot be guaranteed.

8. Your Choices and Rights

You may clear browser local storage, session storage, or cookies and use browser controls that limit analytics. Depending on your location, you may also have rights to request access, correction, deletion, restriction, objection, or a copy of information associated with you. Send requests to team@minimumstudio.net. We may need limited information to verify and complete a request.

Instructions specific to deletion requests are available on our Data Deletion Instructions page.

9. Children's Privacy

Minimum Studio does not knowingly collect personal information from children beyond the information needed to operate the applicable platform game. If a parent or guardian believes that a child has provided personal information to us, please contact us so that we can review and delete it where appropriate.

10. International Processing

Third-party providers may process information in countries other than the user's country. Where required, we use appropriate safeguards for international processing and rely on the safeguards offered by our service providers.

11. Changes to This Policy

We may update this Policy to reflect changes to our services, providers, or legal obligations. The last-updated date at the top of this page will be updated when a revision is published.

12. Contact

Minimum Studio Corp. (주식회사 미니멈스튜디오)
Chief Executive Officer: Kim Hyuna (김현아)
Business Registration No.: 786-86-02557
City Center, Room 201, 20 Daedeok-daero 512beon-gil, Yuseong-gu,
Daejeon, Republic of Korea
Email: team@minimumstudio.net