How Cat Chaos Collects Data
1. Data Collected Through Meta Platform (Oculus/Quest Integration)
When users launch Cat Chaos on Meta Quest, the app interacts with the Meta SDK and Oculus Platform Services to enable authentication, in-app purchases (IAP), and entitlement verification.
The collection process happens automatically through the Meta platform APIs, as required by Meta’s systems for apps that use IAP.
A. Authentication and Account Linking
When a player launches the app, Meta automatically provides a unique Meta Account ID to the app via the platform’s API.
This ID does not include the user’s name or email — it’s a numeric identifier generated by Meta.
Cat Chaos uses this ID only to link the user’s game data to their Meta account so that progress and purchases can be restored across sessions.
Data Collected:
Collected By: Meta Quest SDK (automatically on app launch)
Used For: Player authentication and linking to saved data in PlayFab.
Stored In: PlayFab under the player’s account record.
B. In-App Purchases (IAP)
When a player purchases content (for example, cosmetics or in-game currency):
Meta handles the payment process directly — Cat Chaos never receives financial information such as credit card numbers or payment credentials.
After a successful purchase, Meta sends Cat Chaos a purchase receipt that includes:
This receipt is then sent securely to PlayFab through an HTTPS request for validation and delivery of the purchased item.
Data Collected:
Product ID
Purchase receipt/token
Transaction timestamp
Collected By: Meta Quest IAP SDK
Processed By: PlayFab backend (for validation and ownership tracking)
Used For:
Verifying legitimate purchases
Delivering purchased content
Preventing fraudulent refund or replay attacks
Stored In: PlayFab player record, under “PurchasedItems” or similar data fields.
C. Device and Performance Data
The Meta platform automatically gathers certain non-personal device and performance metrics when the app is running or crashes. This information is accessible to developers through Meta’s performance analytics and optional SDK logging.
Data Collected:
Device model (e.g., Quest 2, Quest 3)
Operating system version
Frame rate and rendering performance
Crash logs and error codes
Collected By: Meta Quest runtime (not manual collection)
Used For: Debugging, optimization, and ensuring compatibility across devices.
Stored In: Meta analytics dashboard (aggregated form) — not tied to personal user data.
2. Data Collected Through Microsoft PlayFab
Cat Chaos uses Microsoft PlayFab, a cloud backend service for Unity games, to handle player accounts, cloud saves, and purchase verification.
When the app starts, it initializes a PlayFab client session linked to the player’s Meta ID.
A. Account Initialization
On first launch, PlayFab generates a PlayFab Player ID, which is a random unique identifier.
This ID is linked to the player’s Meta Account ID but does not contain personally identifiable information (PII).
Data Collected:
Collected By: PlayFab SDK
Used For: Identifying player data in the cloud database.
Stored In: PlayFab user profile table.
B. Gameplay and Progress Data
During gameplay, Cat Chaos periodically syncs progress data to PlayFab. This includes:
Owned cosmetics or unlocked content
Achievements and stats
Player preferences and in-game settings
Currency balance or progression level
These updates happen automatically through PlayFab’s secure API calls, usually when:
Data Collected:
Gameplay stats
Inventory items
Achievement data
Settings/preferences
Collected By: PlayFab SDK (secure HTTPS calls)
Used For: Restoring progress, managing cosmetics, enabling cross-session play.
Stored In: PlayFab player data tables (cloud-hosted on Microsoft Azure).
C. Purchase Verification
When Meta reports a completed transaction:
Cat Chaos forwards the purchase receipt to PlayFab’s Receipt Validation API.
PlayFab contacts Meta’s servers to confirm the receipt is legitimate.
Upon validation, PlayFab adds the purchased item to the user’s account.
Data Collected:
Purchase receipt
Product ID
Player’s PlayFab ID
Used For:
Stored In: PlayFab’s secure transaction history log.
D. Analytics and Device Info
PlayFab collects limited anonymous analytics data for stability and diagnostics:
Region (based on device settings, e.g., “US”, “EU”)
Device model and OS version
Connection type (Wi-Fi, offline)
Collected By: PlayFab Telemetry system
Used For: Aggregate analytics, balancing servers, and improving user experience.
Stored In: PlayFab telemetry tables (aggregated, non-personalized).
All communication between Cat Chaos and PlayFab occurs over HTTPS using encrypted requests.
No sensitive financial information (credit card data, billing addresses) is ever handled by Cat Chaos.
Meta and PlayFab both store data on secure servers compliant with GDPR, CCPA, and ISO/IEC 27001 standards.
Player launches Cat Chaos → Meta assigns Meta Account ID
App connects to PlayFab → PlayFab creates Player ID linked to Meta ID
Player buys an item → Meta sends purchase receipt to app
App sends receipt to PlayFab → PlayFab validates and stores it
Player progress, cosmetics, and stats are synced to PlayFab cloud
Device and performance data is automatically logged by Meta
Cat Chaos does not collect or request:
Personal names, emails, or physical addresses
Microphone, camera, or motion data
User-generated content or text
Location or GPS data
Only the data listed above is collected and used strictly for account functionality, purchase verification, and gameplay features.
To request data deletion, please email: genegarguyman@gmail.com
