Effective date: 8 October 2026
This policy describes how WEBHOP • Webpage Parkour, developed by Oliver Kearns, handles information when you use the Chrome extension.
WEBHOP turns the current webpage into a pixel parkour game. When you explicitly start a run, it scans rendered webpage elements, creates game platforms, and displays a character and game interface over the page.
WEBHOP operates locally. The extension does not send gameplay information or scanned webpage content to the developer or external servers.
Website content and layout
WEBHOP temporarily accesses rendered text nodes and the positions and dimensions of supported webpage elements, including images, links, buttons, form controls and recognised advertising containers. It uses this information to identify platforms and their gameplay behaviour.
Text is examined to identify rendered lines. Images are treated as rectangular surfaces; their image files are not uploaded or analysed.
This processing can include content displayed on a page where you are signed in. Only activate WEBHOP on pages you are comfortable having it process locally.
Current page information
WEBHOP accesses the current page URL and title. The URL is used to generate a local identifier for personal best records. The page URL and title can also appear in a challenge you choose to copy.
WEBHOP does not access Chrome’s browsing history database or monitor pages you visit when the game is inactive.
Gameplay activity
While active, WEBHOP processes supported gameplay key presses, scroll position, window dimensions and game state. This enables movement, jumping, camera scrolling, collision detection, timing and progress tracking.
It does not maintain a keystroke log or use gameplay activity for advertising, profiling or analytics.
Form fields and credentials
WEBHOP uses the geometry of supported form controls as gameplay surfaces. It does not intentionally read their entered values, passwords, authentication tokens or cookies.