Privacy Policy for Splashwash
Effective Date: September 22, 2026
1. Introduction
This Privacy Policy explains how Splashwash processes information when you play the game on the Meta Horizon platform or contact us for support.
Splashwash is provided by MGWD ("we", "us", or "the developer"), the controller responsible for the processing described in this policy. You can contact us at marcingwozdz94@gmail.com.
Splashwash is a virtual reality game focused on cleaning, collecting trash, repairing objects, and restoring locations. Its core gameplay does not require a separate Splashwash account. Versions supporting Meta platform features or optional in-app purchases may use Meta's online services for those features.
We do not operate a backend that collects or stores player profiles, gameplay activity, Meta account records, or Meta purchase records. However, Splashwash accesses and processes limited Meta platform information as described below.
Processing within the application does not necessarily mean that this information is uploaded to a developer-operated server.
2. Personal Data and Meta Platform Features
2.1. User ID
Splashwash accesses the signed-in user's Meta Horizon User ID through the Meta Platform SDK.
The User ID is a unique identifier associated with the user's Meta account for platform purposes. It is not the user's real name.
Splashwash uses the User ID to identify the current platform user when accessing Meta platform features and to associate relevant platform operations, profile information, purchase checks, and content entitlements with the correct account.
This may include:
identifying the signed-in Meta user;
retrieving applicable Meta profile information;
verifying purchased content or features;
restoring eligible purchased content;
maintaining continuity of platform-related functionality across sessions.
We do not use the User ID for advertising, marketing, behavioural profiling, analytics, or cross-app tracking.
2.2. User Age Group
Where required by Meta's platform policies or enabled for the application, Splashwash accesses the user's age category using Meta's User Age Group / Get Age Category API.
The result provides an age category associated with the user's Meta account, such as child, teen, adult, or an indication that age information is unavailable.
Splashwash does not receive the user's exact date of birth through this API.
The age-category information is used to comply with Meta's age-group requirements and to determine whether age-specific platform requirements or restrictions apply to the user.
Splashwash does not independently request the user's exact age, date of birth, or identity documents through the game.
Age-category information is not used for advertising, marketing, behavioural profiling, or analytics.
2.3. User Profile
Splashwash accesses limited profile information associated with the signed-in Meta Horizon user through Meta's Platform SDK.
Depending on the information made available by Meta and the platform feature being used, this may include:
the user's display name or username;
the user's Meta profile picture or profile-image URL;
profile information necessary to identify the current platform user within Splashwash.
Splashwash uses this information to identify the signed-in user and, where applicable, display the user's Meta identity or profile information within platform-connected parts of the application.
Profile information may also be used together with the User ID when providing Meta platform functionality associated with the current user.
Splashwash does not use Meta profile information for:
advertising;
marketing;
behavioural profiling;
analytics;
data brokerage;
tracking users across unrelated applications.
We do not operate a developer backend that stores Meta user profiles.
2.4. In-App Purchases
Splashwash supports optional purchases of digital content or features through Meta's in-app purchase system in versions where these purchases are available.
To provide in-app purchase functionality, Splashwash processes information returned by Meta's purchase services.
This may include:
product identifiers or SKUs;
purchase identifiers where provided;
purchase results;
ownership information;
entitlement information indicating whether the current Meta account has access to purchased Splashwash content or features.
Splashwash uses this information to:
display or identify purchasable content;
initiate checkout requested by the user;
determine whether a purchase was successfully completed;
unlock purchased digital content or functionality;
verify ownership of purchased content;
restore eligible purchases.
Minimal information indicating which content or features are unlocked may be stored locally on the device where necessary to provide access to purchased content.
Payments are processed through Meta's checkout system. Splashwash does not receive or store payment-card numbers, bank-account information, or payment authentication credentials.
Splashwash does not receive information about purchases made in unrelated applications through this integration.
2.5. Information We Do Not Request or Use
Splashwash does not request access to the user's followers, contacts, or social relationships unless a future version of the application explicitly introduces a feature requiring such access and this Privacy Policy is updated accordingly.
Splashwash does not collect microphone recordings or camera recordings for developer use.
Splashwash does not collect information for personalised advertising, behavioural advertising, marketing profiling, data brokerage, or cross-app tracking.
The game does not include third-party advertising or behavioural analytics services.
3. Information Processed Locally on the Device
XR Input Data
Splashwash temporarily processes headset and motion-controller information necessary to operate the virtual reality experience.
This may include:
headset position and orientation;
motion-controller position and orientation;
controller input;
controller tracking status;
temporary interaction information required for gameplay.
This information is used to:
control gameplay;
interact with objects;
operate cleaning tools;
operate vacuuming or similar mechanics;
collect trash;
repair or restore objects;
determine controller tracking;
provide haptic and interaction feedback.
XR input information is processed temporarily during gameplay.
We do not intentionally record this information for profiling purposes or upload it to a developer-operated backend.
Local Game Data
Splashwash stores certain gameplay information locally on the user's device so the game can remember progress and preferences.
Depending on the game version, this may include:
game progress;
completed objectives;
map progress;
cleaned or restored areas;
unlocked content;
gameplay settings;
accessibility preferences;
comfort settings;
haptics settings;
audio settings.
This information remains within the application's local storage unless separately backed up by Meta's platform services.
Local Purchase-Related Data
Splashwash may retain minimal local information indicating which purchased content or features are available or unlocked.
This information is separate from Meta's payment, transaction, and store records.
We do not operate a developer-managed transaction database.
Meta Cloud Backup
We do not operate our own cloud-save service.
Where Meta's system-level Cloud Backup functionality is enabled for Splashwash and the user, Meta may independently back up eligible local application data.
Those backups are controlled through Meta's systems and policies rather than through a developer-operated Splashwash backend.
4. Purposes of Processing
We process the information described in this Privacy Policy only as necessary to:
operate Splashwash and its virtual reality controls;
enable interaction with objects and environments;
operate cleaning, collection, repair, and restoration mechanics;
save and restore game progress and preferences;
identify the signed-in Meta platform user;
retrieve and display limited Meta profile information where required by platform-connected functionality;
provide Meta platform features;
provide, verify, and restore eligible in-app purchases;
determine whether age-related Meta platform requirements or restrictions apply;
provide access to purchased or unlocked content;
respond to support or privacy requests.
We do not use the information described in this policy for:
advertising;
personalised advertising;
marketing profiling;
behavioural profiling;
cross-app tracking;
selling personal information;
data-broker activities.
Where applicable law requires a legal basis for processing, we rely on processing necessary to provide the game and functionality requested by the user, legitimate interests in operating and maintaining the service where those interests are not overridden by user rights, compliance with applicable legal obligations, and consent where legally required.
5. Information You Provide When Contacting Us
If you contact us by email, we receive your email address and any information that you voluntarily include in your message.
This may include:
a description of a technical issue;
information relating to an in-app purchase;
a purchase reference;
a privacy request;
a data-deletion request.
We use this information only to respond to and resolve the enquiry and to comply with applicable legal or platform requirements.
Support correspondence is not used for advertising or marketing.
Support correspondence is processed through our email service provider, Google (Gmail).
This is separate from Splashwash gameplay processing and does not constitute a gameplay or player-account backend.
Please do not send passwords, full payment-card information, or unnecessary sensitive information by email.
6. Data Retention
XR input data: processed temporarily while necessary for gameplay and normally discarded when no longer required or when the application closes.
User ID: processed during relevant Meta platform operations and game sessions. Splashwash does not intentionally store the User ID in a developer-operated backend.
User Age Group: processed during relevant Meta platform requests. Splashwash does not intentionally retain the age-category value in a developer-operated backend.
User Profile: profile information received from Meta is processed as necessary to provide the platform-connected functionality described in this policy. Splashwash does not operate a server-side database of Meta user profiles.
Purchase information: purchase and entitlement responses are processed as needed to complete ownership and purchase checks. Minimal local information indicating that content is unlocked may remain on the device as necessary to provide access.
Local game data: retained on the user's device until the user clears the application's stored data or uninstalls the application.
Meta Cloud Backup: Meta-managed backup data, where enabled, may remain separately under Meta's policies and controls.
Support correspondence: retained only for as long as reasonably necessary to respond to the enquiry, handle follow-up issues, resolve disputes, or comply with applicable legal obligations.
Meta independently determines retention of account, profile, transaction, payment, platform, and backup information controlled by Meta.
7. Disclosure and Sharing
We do not sell or rent personal information.
We do not disclose Splashwash player information to advertisers, advertising networks, data brokers, or behavioural analytics providers.
Splashwash communicates with Meta's platform services as necessary to provide the user identity, age-category, profile, entitlement, and purchase functionality described in this Privacy Policy.
Meta independently processes information required to operate:
Meta accounts;
Meta Horizon profiles;
Meta Horizon Store;
payment systems;
purchases and entitlements;
platform services;
device services;
cloud backups.
Meta's processing is governed by Meta's applicable privacy policies and terms.
Support correspondence voluntarily sent to us is processed through our email service provider.
We may disclose information where required by applicable law, regulation, court order, or other valid legal process.
8. Security Measures
We use reasonable technical and organisational safeguards appropriate to the limited information processed by Splashwash.
These measures include limiting processing to information required for game or platform functionality, storing local information within application storage where appropriate, and limiting access to support correspondence.
Meta account, profile, and purchase operations use Meta's platform services.
Splashwash does not collect Meta account passwords, payment-card numbers, bank-account credentials, or payment authentication information.
No method of storage, transmission, or electronic processing can be guaranteed to provide absolute security.
9. Data Deletion and Your Rights
To request deletion, correction, access, or information relating to personal information under our control, contact:
marcingwozdz94@gmail.com
You may use the subject line:
Splashwash Privacy Request
We will respond without undue delay and within any time period required by applicable law.
Where necessary, we may request only the information reasonably required to verify and process the request.
Where we do not hold the information concerned, we will explain this and, where possible, identify the appropriate method for managing or deleting the information.
Local Device Data
To remove locally stored Splashwash information, users can clear the application's storage through the device settings or uninstall the application.
This removes locally stored progress, preferences, and locally retained unlock information from that device.
Because this information exists only on the user's device, we cannot remotely erase it.
Meta Cloud Backup
Deleting local Splashwash data or uninstalling the application does not necessarily delete backups controlled independently by Meta.
Where a Meta Cloud Backup exists, users should use Meta's Cloud Backup management controls to remove applicable backups.
An existing backup may restore local application data when Splashwash is reinstalled.
Meta Account, Profile, and Purchase Records
Clearing Splashwash's local data does not delete the user's Meta account, Meta profile, Meta Horizon Store purchase history, or Meta-managed purchase and entitlement records.
Purchased Splashwash content may become available again after reinstalling the application when the game retrieves the account's current entitlement information from Meta.
Requests relating to Meta account data, Meta profile information, transaction records, or other information independently controlled by Meta should be submitted through Meta's privacy, account, or support controls.
Depending on applicable law, users may also have rights relating to access, correction, deletion, restriction, objection, data portability, and complaints to an applicable data-protection authority.
10. Children and Age-Appropriate Use
Access to Splashwash and its Meta platform functionality is subject to the application's selected Meta age group, Meta account requirements, applicable parental controls, and applicable law.
Where Splashwash uses Meta's Get Age Category API, the returned category is used only for the purposes described in this Privacy Policy, including compliance with Meta age-group requirements and determining whether age-specific platform restrictions apply.
We do not use age-category information for advertising, marketing, behavioural profiling, or analytics.
Parents or guardians may contact us regarding privacy questions or requests relating to their child where applicable.
11. Changes to This Privacy Policy
We may update this Privacy Policy to reflect changes to Splashwash, Meta platform requirements, applicable legal requirements, or our data practices.
When changes are made, the updated version will include a new Effective Date.
Where required by applicable law, we will provide additional notice regarding material changes.
12. Contact Us
For questions, privacy requests, deletion requests, or security concerns relating to Splashwash, contact:
Marcin Gwóźdź
Email: marcingwozdz94@gmail.com