Site policy
Save Data Policy
Save Data & Local File Data Policy
ROMConsole supports account features such as save/load, rolling autosave, private library metadata, achievements, leaderboards and play statistics by storing platform data, not private ROM files.
When a user selects a local ROM or ZIP file, ROMConsole may read the file locally in the browser to identify metadata and generate a SHA-256 hash. The ROM file itself is not uploaded, stored, streamed, linked or distributed by the server.
The hash allows ROMConsole to recognise the same local file again later. It can be used to match save data, rolling autosave data, player stats, achievements, leaderboard activity and private library records to the correct local file. The hash is not the ROM file and cannot recreate the game.
Save data and autosave data may be stored on the server for registered-player account features where the enabled EmulatorJS core supports save-state export. Manual saves and rolling autosaves are account data, not game distribution files.
Rolling autosave is designed to update the latest autosave slot without creating unlimited new autosave rows every minute. Manual saves remain separate where supported.
Some systems, such as Nintendo 64, can create large save-state payloads. Site owners should configure PHP and MySQL/MariaDB limits appropriately for large save states. Recommended settings are documented in the installation and requirements files.
Users remain responsible for the legality of the local files they select. ROMConsole stores save and platform data only; it does not store the copyrighted ROM file itself.
ROMConsole supports account features such as save/load, rolling autosave, private library metadata, achievements, leaderboards and play statistics by storing platform data, not private ROM files.
When a user selects a local ROM or ZIP file, ROMConsole may read the file locally in the browser to identify metadata and generate a SHA-256 hash. The ROM file itself is not uploaded, stored, streamed, linked or distributed by the server.
The hash allows ROMConsole to recognise the same local file again later. It can be used to match save data, rolling autosave data, player stats, achievements, leaderboard activity and private library records to the correct local file. The hash is not the ROM file and cannot recreate the game.
Save data and autosave data may be stored on the server for registered-player account features where the enabled EmulatorJS core supports save-state export. Manual saves and rolling autosaves are account data, not game distribution files.
Rolling autosave is designed to update the latest autosave slot without creating unlimited new autosave rows every minute. Manual saves remain separate where supported.
Some systems, such as Nintendo 64, can create large save-state payloads. Site owners should configure PHP and MySQL/MariaDB limits appropriately for large save states. Recommended settings are documented in the installation and requirements files.
Users remain responsible for the legality of the local files they select. ROMConsole stores save and platform data only; it does not store the copyrighted ROM file itself.