Play
Select stickers to choose a layer, turn it, and work toward a solved cube. Adjust your view with rotation rings, zoom, undo and reset.

A cube puzzle for Meta Quest
Solve a classic 3x3 cube in virtual reality, or discover how it works one layer at a time.
Made by Ernest Namdar.

Select stickers to choose a layer, turn it, and work toward a solved cube. Adjust your view with rotation rings, zoom, undo and reset.
Watch stickers move on a live circular graph. Try Easy, Medium, Hard or N-hop scrambles, and ask the offline solver for its best next move.
Play with Touch controllers or bare-hand tracking. Point and trigger, or pinch, to select stickers and activate controls.
Inside The Cube
Screenshots rendered from the actual game. Open any image to view it at full resolution.
Support
For questions, feedback, technical support or privacy requests, contact Ernest Namdar.
me@ernestnamdar.comYour headset model, app version and a description of what happened help diagnose an issue. Share a screenshot if useful.
The Cube has no in-app account, advertisements, in-app purchases or multiplayer. Puzzle solving runs on your headset.
Your information
Effective October 15, 2026 · Developer: Ernest Namdar (Khashayar Namdar, Canada)
The Cube is a standalone virtual-reality cube puzzle for Meta Quest. This policy explains how information is handled when you use the app.
Cube state, moves, timer, selections and solver computations are processed on your headset. Controller poses, headset poses, hand joints and pinch input are used transiently to render the scene and control the puzzle. The developer does not operate a server that receives this tracking data, and The Cube does not record hand/headset movement histories or send them to the developer.
The Cube collects and processes Meta platform data through Meta's Platform SDK to provide the following limited app functions. Processing can take place even when the developer does not store a copy of the data.
User ID (USER_ID): The Cube has access to Meta's User ID platform feature as a required dependency of the User Age Group API. Meta's platform integration processes the account's app-scoped user identifier to associate platform requests with the signed-in account. The app also uses Meta's entitlement service to check whether that account is entitled to launch The Cube. The gameplay code does not separately retrieve a user ID, build a user profile, or write a user ID to app logs or developer databases.
User Age Group (USER_AGE): The app requests the signed-in user's age category from Meta once per session after platform initialization, as required for its mixed-age audience. The category may identify a child, teen, adult, or unknown age group; it is not an exact date of birth. The request supports Meta's mixed-age platform requirements. All age categories receive the same puzzle without social features, multiplayer, ads or in-app purchases. The app does not use the result for profiling or advertising, and failure to retrieve a category does not block gameplay.
The app does not send user IDs, age categories or tracking data to a developer-operated server or outside data processor. Meta receives and processes information needed to perform the platform requests and may process account, purchase, device and SDK diagnostic information under its own policies. The app does not request your Meta username, profile photo, friends list or email for gameplay. Meta's own privacy policy applies to Meta services: Meta Quest privacy policy.
The app writes operational messages to the device's diagnostic log, including tracking availability, selected controls and ownership-check outcomes. The developer does not automatically collect those logs or run a separate analytics service. If you voluntarily send a diagnostic log or email for support, Ernest Namdar uses it to diagnose and respond to your issue. Please avoid sending passwords or unnecessary personal information.
The Cube has no advertisements, in-app purchases, in-app account registration, multiplayer or user-generated content. Purchases are handled by the Meta Horizon Store; the app does not receive payment-card details. The developer does not sell personal information.
User Age Group responses are processed transiently for the session request and are not saved by the gameplay code. The gameplay code does not persist or log User ID or User Age Group data, and the developer has no database of these values. Transient gameplay and tracking information is held in app memory during use. Closing the app clears the gameplay session state; installed app data can be removed through headset settings or by uninstalling the app. Meta may retain its own account, transaction and platform-service records under Meta's policies.
To request access, correction or deletion of any personal data held by the developer—including any User ID or User Age Group information you believe is held and any support correspondence you provided—email me@ernestnamdar.comwith the subject "The Cube - Data deletion request". Describe the request and the email address used to contact support; do not send your password, payment details or identity documents. Khashayar Namdar (known as Ernest Namdar) will review and respond to the request, delete applicable developer-held personal data when requested unless retention is legally required, and explain if no matching data is held. The app's lack of a developer database does not prevent you from making a request. Meta-account and purchase records are controlled by Meta; requests to delete those records must also be directed to Meta through its account/privacy tools.
The app requests Meta's age category once per session for its mixed-age audience. All age categories receive the same puzzle without social features, advertisements or multiplayer. The app does not retain or log the returned age category or transmit it to the developer. Failure to retrieve age information does not block gameplay. The Cube must be used in accordance with Meta's account age requirements and the app's store age rating. It does not include a separate registration flow or ask users to provide their age or other personal details.
The developer may update this policy when the app's data practices change. The current version and effective date will be published at the app's privacy-policy URL.