MGWD

Effective Date: October 21, 2026

1. Introduction

This Privacy Policy explains how Splashwash processes information when you play the game on the Meta Horizon platform, use its online multiplayer and social features, 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 mgwdgames@gmail.com.

Splashwash is a virtual reality game focused on cleaning, collecting trash, repairing objects, and restoring locations. It does not require you to create a separate Splashwash account. Meta platform features use Meta's online services, including optional in-app purchases, friend invites and presence, the Daily Job leaderboard, store rating prompts, and Meta's In-App Analytics. Online multiplayer uses Epic Online Services (EOS), provided by Epic Games, for player authentication, creating and joining lobbies, and establishing peer-to-peer connections, including connections routed through EOS relay servers.

We do not operate our own backend that stores player profiles, Meta account records, Meta purchase records, leaderboard records, or analytics records. However, the game processes information on your device, sends information to Meta and EOS where needed for their services, and exchanges information with other players during multiplayer sessions. The absence of a developer-operated backend does not mean that no information is transmitted or stored by service providers.

2. Personal Data and Online Features

2.1. Meta User ID

Splashwash accesses the signed-in user's Meta Horizon User ID through the Meta Platform SDK. This is a unique identifier associated with the user's Meta account; it is not the user's real name.

The game uses this identifier to identify the current platform user and associate platform operations, profile information, purchase checks, and content entitlements with the correct account. This includes verifying and restoring eligible purchased content, maintaining continuity of platform-related functionality across sessions, recognising your own entry on the Daily Job leaderboard (section 2.10), and the Meta social features described in sections 2.9 and 2.12.

The Meta User ID is also used for EOS authentication as explained in section 2.6. We do not use it for advertising, marketing, behavioural profiling, or cross-app tracking. Meta's In-App Analytics, which is provided by Meta on its platform, is described in section 2.11.

2.2. User Age Group

On Meta Quest, Splashwash requests the user's age category through Meta's User Age Group / Get Age Category API during platform initialisation. This may indicate a child, teen, adult, or unavailable age category.

The game uses this information to comply with Meta's age-group requirements and to determine whether age-specific platform requirements or restrictions apply. For accounts in the child category, rooms are private by default, the game does not show interrupting store offers or rating requests, and Daily Job times are not posted to the leaderboard (section 2.10). The category may also appear in local diagnostic logs as described in section 3. Splashwash does not receive an exact date of birth through this API and does not independently request an 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 through the Meta Platform SDK. Depending on what Meta makes available and the feature being used, this may include:

your display name or username;
your Meta profile picture or profile-image URL;
profile information necessary to identify the current platform user within Splashwash.

This information is used to identify the signed-in user and, where applicable, display their identity within platform-connected parts of the game. Your display name may be included in multiplayer lobby information and shown to other players, included in invitations and presence information as described in section 2.9, and shown next to your time on the Daily Job leaderboard as described in section 2.10.

We do not use Meta profile information for advertising, marketing, behavioural profiling, data brokerage, or tracking across unrelated applications. We do not operate a developer backend that stores Meta user profiles. EOS processing of multiplayer identifiers and lobby information is described below.

2.4. In-App Purchases

Splashwash supports optional purchases of digital content or features through Meta's in-app purchase system, such as cosmetic items, packs, premium biomes, and the Pro License, in versions where these purchases are available.

The game processes information returned by Meta's purchase services, which may include product identifiers or SKUs, prices, purchase identifiers where provided, purchase results, ownership information, and content entitlements.

We use this information to identify purchasable content, show prices and offers, initiate checkout requested by you, determine whether a purchase succeeded, unlock purchased content or functionality, verify ownership, and restore eligible purchases.

Minimal information indicating which content or features are unlocked, and which offers have already been shown to you, may be stored locally on your device where needed to provide access and to limit how often offers appear.

Payments are processed through Meta's checkout system. Splashwash does not receive or store payment-card numbers, bank-account information, or payment authentication credentials. This integration does not give Splashwash information about purchases made in unrelated applications. We do not operate a developer-managed transaction database.

2.5. Information We Do Not Request or Use

Splashwash does not request access to your contacts, photos, files, or location. Access to the people you are connected with on Meta (Followers) is used only to show your friends' Daily Job times as described in section 2.10, and the invite panel described in section 2.9 is shown by Meta's own system interface.

We do not record voice chat or collect camera recordings for developer use. Live microphone processing for voice chat is described in section 2.8.

We do not collect information for personalised advertising, behavioural advertising, marketing profiling, data brokerage, or cross-app tracking. The game does not include third-party advertising services. Apart from Meta's In-App Analytics described in section 2.11, it does not include analytics services.

2.6. Epic Online Services Authentication

Splashwash uses the EOS Connect service to authenticate players for online functionality. The game sends your Meta User ID and a sign-in proof supplied by Meta to EOS so that EOS can verify the platform user and create or retrieve an EOS Product User ID for Splashwash.

The EOS Product User ID is a pseudonymous player identifier. It is not your real name, but it can be associated with your platform account and used to recognise you across sessions. It should not be understood as fully anonymous information.

You do not need to create or sign in to an Epic Games account to use this integration. Splashwash does not receive your Meta password.

If Meta sign-in is temporarily unavailable, Splashwash may use EOS device-based authentication instead. For that process, the game provides the device model and a display name, and EOS creates or uses a device-based identifier. This identifier is used for game authentication, not advertising.

2.7. Lobbies, Peer-to-Peer Connections, and Multiplayer Data

EOS enables the game to create, find, join, and leave multiplayer lobbies and establish connections between participating players. One participating player's device acts as the session host. Connections first attempt a direct peer-to-peer connection and may use an EOS relay if a direct connection cannot be established. A relay server forwards traffic between the connected devices.

Information processed for these features includes:

player and connection identifiers, including the EOS Product User ID;
display names used in multiplayer;
lobby identifiers, membership, and information needed to identify and join a session;
lobby attributes such as the room name and code, selected map or location, host display name, player count, public/private setting, and protocol-version information needed to match compatible players;
IP addresses and technical connection information needed to establish, route, and maintain multiplayer connections;
live gameplay information needed to keep the session synchronised, such as avatar poses and cosmetic choices, head and hand or controller movements, object positions, tool actions, readiness and host status, connection-quality information, and the state of cleaning, collection, repair, or restoration activities;
live voice audio when microphone access and voice transmission are enabled, as described in section 2.8.

Lobby information is processed by EOS. Live gameplay and voice data are exchanged between players' devices using the game's multiplayer networking, including through the device acting as host. Depending on the connection, this traffic may travel directly between devices or through EOS relay servers. When you are in an online room, the room's lobby identifier is also shared with Meta as described in section 2.9.

If a direct peer-to-peer connection is used, your IP address may be visible to the devices of players connected to you. Relay routing can avoid exposing your IP address to another player's device, but EOS still processes network information needed to provide the connection.

These features are used to provide online play, not advertising or behavioural profiling. EOS lobbies and relays do not, by themselves, mean that we operate a cloud database of your saved game progress.

2.8. Microphone and Peer-to-Peer Voice Chat

Splashwash offers live voice chat between players in the same multiplayer session. The game requests microphone permission for this feature. You can refuse or revoke microphone access in your headset settings and continue playing without transmitting your voice.

When microphone access and voice transmission are enabled, audio is captured temporarily and transmitted through the game's peer-to-peer multiplayer connections. The device hosting the session forwards voice packets to the other participants for playback. If a connection uses an EOS relay, the relay forwards the voice traffic as part of the multiplayer traffic. Splashwash does not use a separate Epic Voice/RTC service for this voice chat.

We do not record or retain voice chat audio. Temporary capture, transmission, and playback buffers are used to provide the live conversation. Other participants can hear what you say, so information you choose to disclose over voice is shared with them.

You can mute your microphone and mute other players locally using the game's voice controls.

2.9. Friend Invites, Presence, and Deep Linking (Meta Group Presence)

While you are in an online Splashwash room, the game tells Meta's Group Presence service that you are in that room so that your friends can join you and you can invite them. The information sent to Meta is:

the in-app destination (a Splashwash crew room);
the room's lobby identifier (the EOS lobby ID), used by Meta as the session identifier;
whether the room can still be joined (for example, whether it is full);
a short message used to find the room, containing the room code and the host's display name.

When you leave the room, the game clears this information. Meta may show your presence in Splashwash to people you are connected with, according to your Meta account and privacy settings, and may list you as someone they recently played with.

When you choose to invite friends, Meta shows its own invite panel. The list of people you can invite is provided and displayed by Meta; the game does not receive that list or your contacts. Meta delivers the invitations you send.

When you accept an invitation or choose to join a friend from Meta's interface, Meta starts Splashwash (or notifies the running game) with the destination, the room's lobby identifier, and the message described above (deep linking). The game uses this only to bring you into that room. It may report to Meta whether joining succeeded or failed (for example, because the room was full), which Meta uses for its launch statistics. If you are in a single-player job when you accept an invitation, your progress is saved before you join.

2.10. Daily Job and Leaderboards

The Daily Job is a single-player map that is the same for all players each day. When you finish it, Splashwash records your best time for that day on your device and, in store versions of the game, posts it to a Meta Platform leaderboard. The leaderboard entry contains your Meta User ID, a score that encodes the day and your time, the time of the entry, and technical information identifying the game version and the day's map, used so that only comparable results are ranked together. Meta stores the entry and associates it with your Meta profile.

Other Splashwash players who view the Daily Job board can see the day's top times with the players' display names or usernames. Your own position is shown to you. If the Followers permission is available, the game also asks Meta for the day's times of people you are connected with who play Splashwash, and shows their names and times to you. The game does not store your follower list.

Each player has one entry on the leaderboard. A later result replaces the earlier one, and we may remove entries or reset the leaderboard. The leaderboard is not shown outside the game. Times from accounts in Meta's child age group are not posted, and the game does not post times from development or test versions.

2.11. Meta In-App Analytics

Splashwash uses Meta's In-App Analytics feature to understand, in aggregate, how the game is played and where it can be improved. While you play, the game sends events through the Meta Platform SDK, for example: the game started, the tutorial started or finished, a job started, finished, or was left (with the biome, map size, solo or multiplayer mode, minutes played, or progress percentage), menus and store screens opened, offers shown, opened, closed, or bought, purchase results, free trials used, invites opened or sent, Daily Job finishes, and rating prompts shown or answered. Each event consists of an event name and a single number, such as a count, a duration, a percentage, a coin amount, or a price. Events do not contain free text, voice, or messages.

Meta processes these events under its own terms and policies and provides us with statistics based on them in its developer dashboard. We do not receive a separate copy of the events and do not combine them with information from other sources. Meta may disable this feature for some accounts.

2.12. Ratings and Reviews

After you have played a few jobs, Splashwash may ask once (and once more later if you choose "Maybe later") whether you would like to rate the game. The game asks Meta whether its rating window can be shown to you and, if so, opens Meta's own rating and review interface. Otherwise, it shows instructions for rating the game in the Meta Horizon app. Your rating and any review are submitted to Meta and published under Meta's policies; we can see published reviews and the overall store rating like any other visitor. The game stores on your device only whether and when it asked you and your answer, and how many jobs you have played. No reward is offered for a rating, and the request is not shown to accounts in Meta's child age group.

3. Device Processing, Multiplayer Synchronisation, and Local Storage

XR Input Data

Splashwash temporarily processes headset and motion-controller information needed to operate the virtual reality experience. This may include headset and controller position and orientation, controller input, tracking status, and temporary interaction information.

This information enables gameplay, object interactions, cleaning and vacuuming tools, trash collection, repairs and restoration, tracking checks, and haptic and interaction feedback.

During multiplayer, the movement and interaction information needed to represent your actions and synchronise the session is also transmitted to other participants through the connections described in section 2.7. This multiplayer information is therefore not processed exclusively on your own device.

We do not intentionally record XR input for profiling or upload an XR movement history to a developer-operated backend.

Local Game Data

Splashwash stores gameplay information locally so that it can remember progress and preferences. Depending on the game version, this may include:

game and map progress, completed objectives, and cleaned or restored areas;
Daily Job progress, best times, streak of days played, and a result waiting to be posted while you are offline;
coins, unlocked content, free trials used, and which offers or rating requests have been shown;
gameplay settings;
accessibility and comfort preferences;
haptics and audio settings.

Local save files are stored in the application's local storage unless backed up by Meta's platform services. During multiplayer, relevant gameplay state is shared with other participants to run the session and may be reflected in local progress saved by the game.

Local Purchase-Related Data

The game may retain minimal local information indicating which purchased content or features are available or unlocked. This is separate from Meta's payment, transaction, and store records.

Meta Cloud Backup

We do not operate our own cloud-save service. Where Meta's system-level Cloud Backup is enabled for Splashwash and the user, Meta may back up eligible local application data. These backups are managed through Meta's systems and policies.

Local Diagnostic Logs

The game and its networking components generate local diagnostic messages to help identify platform, authentication, connection, store, and microphone errors. These messages can include technical session information and the age category returned by Meta. The game also keeps a small local store log file recording store refreshes, product availability, and the steps of purchases you start, without payment details. These logs do not contain voice recordings.

We do not operate a developer service that automatically collects these local logs. If you choose to send diagnostic information to us for support, we process it as support correspondence under section 5.

4. Purposes and Legal Bases of Processing

We process the information described in this policy to:

operate Splashwash, its VR controls, and its cleaning, collection, repair, and restoration mechanics;
save and restore progress and preferences;
identify and authenticate the signed-in platform user;
retrieve and display relevant Meta profile information;
provide Meta platform features and verify or restore eligible in-app purchases;
provide access to purchased or unlocked content;
determine whether age-related Meta requirements or restrictions apply;
create, find, and join multiplayer lobbies, and let friends find, join, and invite each other through Meta;
establish and maintain multiplayer connections, including relay connections;
synchronise players, objects, and shared gameplay;
provide live voice chat when enabled;
provide the Daily Job and its leaderboard, including friends' times where available;
understand, in aggregate, how the game is used through Meta's In-App Analytics;
offer the option to rate the game;
diagnose platform, networking, store, and microphone issues;
respond to support, privacy, and data-deletion requests.

We do not use this information for advertising, marketing profiling, behavioural profiling, cross-app tracking, selling personal information, or data-broker activities.

Where the GDPR or similar laws require a legal basis, we rely on:

Performance of a contract: processing necessary to provide the game and requested features, including account authentication, multiplayer networking, friend invites and joining, the Daily Job leaderboard, and purchase entitlements.
Legitimate interests: processing necessary to operate, maintain, and improve the service, including aggregated usage statistics through Meta's In-App Analytics, addressing technical issues, protecting its security, and responding to enquiries, where those interests are not overridden by your rights.
Legal obligations: processing necessary to comply with applicable law and respond to valid legal or privacy-rights requests.
Consent, where required: including optional microphone processing where consent is the applicable legal basis. You can stop voice transmission or revoke microphone access. Withdrawing consent does not affect the lawfulness of processing before withdrawal.

Information required for authentication, multiplayer connections, or the leaderboard is necessary to provide those online features. If it cannot be processed, the affected features may not work. Microphone access is optional for gameplay.

5. Information You Provide When Contacting Us

If you contact us by email, we receive your email address and information you voluntarily include, such as a technical issue, purchase reference, diagnostic log, support enquiry, privacy request, or deletion request.

We use this information to respond to and resolve your enquiry and comply with applicable legal or platform requirements. Support correspondence is not used for advertising or marketing.

Correspondence is processed through our email service provider, Google (Gmail). This is separate from the game's multiplayer services and does not constitute a gameplay or player-account backend.

Please do not send passwords, full payment-card information, authentication tokens, or unnecessary sensitive information by email.

6. Data Retention

XR input and live multiplayer state: processed temporarily for gameplay, representation of player actions, and session synchronisation. We do not maintain a developer-operated archive of movement or multiplayer traffic. Saved progress or world state is handled as local game data below.
Voice audio: processed in temporary capture, network, and playback buffers for live voice chat. We do not retain recordings of conversations.
Meta User ID and profile information: processed for relevant platform operations, EOS authentication, multiplayer identity, invites, and the leaderboard. We do not operate our own server-side Meta profile database. This does not remove the EOS retention described below.
Age-category information: processed during relevant Meta requests and age-related checks. We do not intentionally retain the category in a developer-operated backend.
Presence and invitation information: kept by Meta while you are in an online room and cleared by the game when you leave; Meta determines how long it keeps related records, such as invitations and recently-played-with lists.
Daily Job leaderboard entries: kept by Meta until replaced by a later result of yours, removed by us, or the leaderboard is reset. You can ask us to remove your entry (section 9).
In-App Analytics events: processed and retained by Meta under its policies; we only see the resulting statistics.
Local diagnostic logs: retained in device or platform log storage according to the relevant system's log-buffer, rotation, and clearing behaviour, or in the game's local store log file until it is replaced or you clear the application's data. Logs you send to us are retained under the support-correspondence criteria below.
EOS player identifiers and account associations: may persist beyond a game session so that EOS can authenticate and recognise the same player on later visits. They are not automatically erased when you leave a lobby, close the game, or uninstall it. They are retained for as long as needed to support the player's use of the online service, subject to applicable deletion requests and legal requirements. See section 9 for how to request deletion.
Lobby data: processed by EOS while needed to operate and manage the lobby. Closing a lobby ends its active use, but does not necessarily erase all associated service records or technical logs immediately.
EOS connection and operational records: any records retained by Epic for service operation, security, troubleshooting, or legal requirements are governed by the applicable EOS service terms and, where Epic acts as an independent controller, its privacy policy. We do not set a separate fixed retention period for Epic's independently controlled records.
Purchase information: processed as needed for ownership and purchase checks. Minimal local unlock information may remain as needed to provide access.
Local game data: retained until you clear the application's stored data or uninstall it, subject to any separate Meta backup and restoration.
Meta Cloud Backup: retained separately under Meta's policies and controls where enabled.
Support correspondence: retained only as long as reasonably necessary to resolve the enquiry, handle follow-up issues or disputes, and meet legal obligations.

Meta independently determines retention of the account, profile, payment, transaction, platform, presence, invitation, review, analytics, and backup information it controls.

7. Disclosure, Service Providers, and International Processing

We do not sell or rent personal information or disclose Splashwash player information to advertisers, advertising networks, data brokers, or behavioural analytics providers.

Epic Online Services

Epic Games provides EOS authentication, lobbies, and peer-to-peer networking, including relay infrastructure. EOS processes the relevant authentication information, player identifiers, display names, lobby information, and network data described in section 2. When a connection is relayed, multiplayer traffic, including live voice packets, passes through the relay.

EOS Game Services process information to provide the integrated services. See the EOS Trust Statement. For processing where Epic acts as an independent controller, see the Epic Games Privacy Policy.

Other Players

Players participating in your multiplayer session receive the information needed to display your multiplayer identity, represent your avatar and actions, synchronise gameplay, and play your voice when you transmit it. Their devices, including the device acting as host, also process the player identifiers and connection information needed for the session.

The normal in-game lobby list shows information such as the room name, host display name, map or location, and player count. Lobby attributes, including room codes and member display names, are also shared through EOS lobby discovery and lookup. A room being omitted from the normal public list does not make its lobby metadata confidential: that metadata can still be discoverable by other game clients through EOS queries. Direct peer-to-peer IP visibility is described in section 2.7.

People you are connected with on Meta may see that you are in a Splashwash room and join it, as described in section 2.9. Players who view the Daily Job board can see the display names and times of the day's top players, and your friends can see your time, as described in section 2.10.

Email Provider and Legal Disclosures

Support correspondence is processed by Google through Gmail. See the Google Privacy Policy.

We may disclose information where required by applicable law, regulation, court order, or other valid legal process.

International Processing

Meta, Epic, and Google operate internationally. Information may be processed outside your country of residence, including in the United States. Information about the international-transfer safeguards used by these providers is available in their privacy notices. Where required by applicable law, transfers must be covered by an applicable adequacy decision or appropriate safeguards, such as standard contractual clauses. You can contact us for information about safeguards applicable to transfers made on our behalf.

8. Security Measures

We use reasonable technical and organisational safeguards appropriate to the information processed by Splashwash. These include limiting processing to information needed for the described functions, storing local data within application storage where appropriate, and limiting access to support correspondence and service-management tools.

Meta account, profile, purchase, presence, invitation, leaderboard, rating, and analytics operations use Meta's platform services. Multiplayer authentication, lobbies, and network connections use EOS and the game's networking components.

Splashwash does not collect your Meta account password, payment-card numbers, bank-account credentials, or payment authentication information. The sign-in proof described in section 2.6 is used to verify your platform identity.

No method of storage, transmission, or electronic processing can guarantee absolute security.

9. Your Choices, Data Deletion, and Other Rights

To request access, correction, deletion, or information about personal information under our control, including information processed through EOS on our behalf and your Daily Job leaderboard entry, email mgwdgames@gmail.com. You may use the subject line "Splashwash Privacy Request".

We will respond without undue delay and within the period required by applicable law. Where the GDPR applies, this is generally within one month; if an extension is legally permitted and necessary, we will explain it within that initial period.

We may request only information reasonably needed to verify your identity and locate the relevant records. You may include your Meta Horizon username to help us start the enquiry, but we may need an additional account or player identifier. Do not send your password or sign-in tokens.

EOS-Related Data

You can ask us to access or delete Splashwash-related data held through EOS, including relevant player identifiers and account associations. We will use the available EOS tools or work with Epic to process a valid request within the scope of our control and applicable law.

Some EOS identity associations may be shared across products within a developer organisation. If a request would affect access to another game, we will explain the scope before carrying out that action. Deleting only data for one game does not necessarily remove all associated identity records.

Deleting EOS-related data does not delete your Meta account or Meta purchase records. If you later use online features again, the game may create or re-establish the records needed to provide them. For information independently controlled by Epic, we will explain how to contact Epic through its privacy channels where appropriate.

Leaderboard, Presence, and Invitations

You can ask us to remove your Daily Job leaderboard entry. If you play the Daily Job again, a new entry may be created. Your presence in a Splashwash room is cleared when you leave the room; you can also control who sees your activity in your Meta account and privacy settings. Invitations, followers, and recently-played-with lists are managed through Meta.

Ratings and Analytics

Ratings and reviews you submit are managed through Meta's store and review tools. In-App Analytics events are processed by Meta; requests about them should be submitted through Meta's privacy controls, and we will help where we can.

Local Device Data

You can remove locally stored Splashwash information by clearing the application's storage through your device settings where available or uninstalling the game. This removes local progress, preferences, Daily Job records, and locally retained unlock information from that device. We cannot remotely erase files stored only on your device.

Device or platform diagnostic logs may be managed separately from application storage and remain until the relevant system rotates or clears them. Uninstalling the game does not necessarily clear those logs.

Clearing local data or uninstalling Splashwash does not itself delete data held by EOS, Meta, or other service providers.

Meta Cloud Backup

Deleting local data or uninstalling the game does not necessarily delete Meta-managed backups. Use Meta's Cloud Backup controls to manage applicable backups. An existing backup may restore local data when Splashwash is reinstalled.

Meta Account, Profile, and Purchase Records

Clearing local Splashwash data does not delete your Meta account, profile, store purchase history, or Meta-managed purchase and entitlement records. Purchased content may become available again after reinstallation when the game retrieves your current entitlements.

Requests about information independently controlled by Meta should be submitted through Meta's privacy, account, or support controls.

Microphone and Multiplayer Choices

You can refuse or revoke microphone permission in headset settings, mute your microphone in game, or mute other players locally. You can leave a multiplayer session to stop participating in that session. These choices do not automatically delete records already held by service providers.

Other Rights

Depending on applicable law, you may have rights to access, correction, deletion, restriction, objection, data portability, withdrawal of consent where processing relies on consent, and complaints to a competent data-protection authority.

Where we do not hold or control the information concerned, we will explain this and, where possible, identify the appropriate way to manage or delete it.

10. Children and Age-Appropriate Use

Access to Splashwash and its online features is subject to the application's selected Meta age group, Meta account requirements, applicable parental controls, and applicable law.

The category returned by Meta's Get Age Category API is used for the purposes described in section 2.2, including determining whether age-specific platform requirements or restrictions apply. For accounts in the child category, rooms are private by default, the game does not show interrupting store offers or rating requests, and Daily Job times are not posted to the leaderboard. Presence and invitations follow the controls Meta applies to the account. Age-category information is not used for advertising, marketing, behavioural profiling, or analytics.

Multiplayer features involve sharing the session information described in this policy with other players, and voice chat transmits microphone audio when enabled. Parents or guardians may contact us with privacy questions or requests relating to their child, including requests concerning information processed through the game's online services.

11. Changes to This Privacy Policy

We may update this policy to reflect changes to Splashwash, its multiplayer and social services, Meta or EOS requirements, applicable law, or our data practices. The updated version will include a new Effective Date. Where required by law, we will provide additional notice of material changes.

12. Contact Us

For questions, privacy requests, deletion requests, or security concerns relating to Splashwash, contact:

MGWD Email: mgwdgames@gmail.com

MGWD is the studio name of Marcin Gwóźdź, an independent developer based in Poland, who is the data controller for the processing described in this policy and can be contacted at mgwdgames@gmail.com.