Are Browser Games Safe? What to Look For
A game running in a browser tab is one of the more tightly fenced pieces of software on a computer. It can draw, play sound and remember its own progress. It cannot open files on its own, install anything or look at other websites, and the few sensitive things it could reach all sit behind a prompt the player has to accept. When browser gaming goes wrong, the problem is almost always the site wrapped around the game, not the game.
What a game in a tab can and can't do
| Freely | With a prompt | Never |
|---|---|---|
| Draw, animate, play sound | Camera | Open files by itself |
| Save progress for its own site | Microphone | Install programs |
| Read taps, keys and gamepads | Location | Read other sites' data |
| Vibrate a phone | Notifications | Change system settings |
The last column rests on how browsers are built. Chrome, for example, has put documents from different sites into separate processes by default since Chrome 67 on desktop, a design called Site Isolation that makes it much harder for one site to steal data from another. The middle column is the permission system: MDN's documentation lists the camera, the microphone, geolocation and notifications among the features that need the person's agreement first.
A game has no honest reason to ask for any of the four. A prompt for the camera or location while trying to play a puzzle game is a reason to say no and close the tab.
Where the real risks are
Most trouble comes from five habits of bad game sites:
- A download to play. A browser game runs in the page. A site that wants an installer, a "player" or a browser extension first is asking for something no browser game needs.
- Fake buttons. Large "Download" or "Play now" buttons inside ad boxes, designed to look like part of the page, lead somewhere else entirely.
- Surprise tabs and redirects. A click that opens an unrequested tab, or a page that jumps to another site, is a sign the site has handed control to someone else's script.
- Sign-ups before playing. A free game that demands an email address, a phone number or a social login before the first level is collecting data, not running a game.
- No padlock. A site without HTTPS sends everything in the open. The padlock doesn't prove a site is honest, but a game site without one in 2026 has skipped the most basic step.
How SalutGames measures up
The live files of all 13 games were checked for this post on 14 October 2026:
No game calls the camera, microphone, location, notification or clipboard features at all, so none of them can trigger a permission prompt. The only device feature some of them use without asking is vibration, for short buzzes on phones. Progress is saved in the browser on the player's own device, under each game's own name, and the save itself stays there. The whole site is served over HTTPS.
For parents and teachers
The checks above take a few seconds on any game site: no download, no permission prompt, no sign-up wall, no surprise tabs, a padlock in the address bar. A site that passes all five is as safe as the browser around it, and modern browsers are built on the assumption that every page might be hostile.
One practical note for school devices: managed Chromebooks often wipe browser data at sign-out, which erases game saves along with everything else. That is the school's setting working as intended, not a problem with the game.
Sources
- The Chromium Projects, Site Isolation
- MDN, Permissions API
- SalutGames: the live files of all 13 games, checked on 14 October 2026
