Privacy Policy

Last updated: 30 October 2026

This page explains how information is handled when you visit gbax-emulator.com, contact GBAx or use its browser player. For privacy questions or requests, contact support@gbax-emulator.com.

Visiting the website

Your browser sends technical information needed to request pages and files, including an IP address, browser information and the requested URL. Hosting, delivery and security services may process request logs to deliver the website, diagnose faults and prevent abuse. Their logs are separate from the GBAx contact form and browser saves.

Contact messages

The contact form asks for your name, email address, enquiry topic and message. We use this information to receive your enquiry, reply and follow up on the issue. Messages are delivered to our support mailbox through the website’s email service. The GBAx plugin does not save a separate copy of your message in the WordPress database.

To reduce abuse, the form uses a security token, an empty spam-detection field and temporary request counters. Counter keys are derived from your IP address and email using a keyed hash; the counters expire one hour after the latest accepted attempt. The plugin does not put your raw IP address or message in those counters. Hosting and email services may keep separate operational logs.

Email correspondence is retained while needed to handle and follow up on the enquiry. You can ask us about access, correction or deletion of information you sent. We may need enough information to verify that the request relates to you; we will explain any information that must be retained. Deleted messages may remain in service backups until those backups expire.

Game files, saves and favourites

When you choose a local game file, the browser player reads it on your device. The GBAx website plugin does not upload that selected file to WordPress. The player can keep game saves and settings in browser storage. Favourites are also stored locally in your browser rather than in a GBAx website account.

Clearing site data, changing browsers, using private browsing or removing browser storage can remove this progress. Export saves before clearing data. Browser settings let you inspect and remove stored site data; the favourite button can also remove a saved favourite.

Third-party requests and links

The browser player uses EmulatorJS and loads its player code and emulation files from the configured player host when needed. Catalogue games with an online file configured request that file from its host. These requests disclose normal connection information to the relevant host. Desktop downloads and source links lead to GitHub, which handles those requests under its own policies.

Other external sites, including game information sources, operate independently. Review their privacy information when you follow a link or use their services. A local game staying on your device does not mean the page makes no network requests.

Cookies, analytics and advertising

GBAx does not currently use Google Analytics or display advertising. WordPress may use cookies for sign-in and account sessions where applicable; the browser player and favourites use local storage as described above. The contact form does not add a marketing subscription or send a tracking identifier to an advertising service.

If analytics or advertising is introduced, we will update this page to identify the services, purposes and visitor choices and configure any required consent controls before enabling them.

Your choices and contacting us

You can browse without submitting a message, choose not to start the browser player, and clear local site data through your browser. To ask about information associated with a support enquiry, email support@gbax-emulator.com. Please do not send passwords, payment details, identity documents or game files through the contact form.

My Library and browser save backups

My Library keeps recent games, estimated active playtime, collections and backup files on this browser. It uses local storage and IndexedDB, not a GBAx account or cloud synchronisation. Catalogue game IDs in your library are sent to this website to retrieve public game titles and artwork; local filenames, game contents and save contents are not uploaded by this feature.

SHA-256 fingerprints of game and core bytes are computed locally to check backup compatibility. GBAx keeps up to two rolling in-game-save backups per game, plus manually created, imported and pre-restore safety backups. You can download or delete individual backups in My Library, clear history separately, or remove all site storage through your browser settings. Persistent storage is optional and depends on your browser granting the request; it does not prevent you from clearing site data.