Skip to main content

🔐 Browser Permission Check

Last review datePlatforms researched
2026-02-26Chrome 133, Safari 18, Firefox 135
No Data Collected

This page runs entirely in your browser. No permission results or personal data are collected, stored, or sent to any server.

What is this?​

When a website asks for permission to access your camera, microphone, or location — what exactly does it get? This interactive tool lets you trigger real browser permission prompts and see exactly what data becomes available.

Each card also explains how native apps handle the same permission differently.

Try it yourself​

Click Request Access on any card below to trigger the browser's permission prompt and see what data it returns.

📍

Geolocation

Your precise GPS coordinates (latitude, longitude, altitude).

Native app difference: Native apps can track your location in the background 24/7, even when the app is closed. Web apps can only access location while the tab is open and active.
📷

Camera

Access to your device camera for photos and video.

Native app difference: Native apps retain camera permission permanently once granted. Web apps must re-prompt per session, and the browser shows a visible recording indicator.
🎙️

Microphone

Access to your device microphone for audio recording.

Native app difference: Native apps can record audio in the background without a visible indicator on older OS versions. Browsers always show a recording indicator and stop access when the tab is closed.
🔔

Notifications

Permission to send push notifications to your device.

Native app difference: Native apps often enable notifications by default during installation. Web apps must explicitly ask, and users can revoke at any time from browser settings.
📋

Clipboard Read

Read the contents of your system clipboard. Safari allows clipboard reads on any user click without a prompt — Chrome and Firefox require explicit permission.

Native app difference: Older native apps could silently read your clipboard on every app open (e.g. TikTok was caught doing this). Modern iOS/Android now alert users. Chrome/Firefox require explicit permission, but Safari allows reads on any user gesture without prompting.

Key takeaways​

AspectWeb AppNative App
Permission promptEvery time (per session/site)Once, then remembered forever
Visual indicatorsBrowser shows recording/location iconsOS-level indicators (newer OS only)
Background accessNot possible — stops when tab closesCan run in background indefinitely
RevocationEasy via browser settings per siteBuried in OS settings per app
ScopeLimited to what the API returnsFull hardware access, raw sensor data
tip

If you denied a permission and want to try again, you'll need to reset it in your browser's site settings (click the lock icon in the address bar).

Reference​

ResourceDescription
Permissions APIMDN documentation on querying and managing browser permissions
Geolocation APIMDN documentation on the browser Geolocation API
MediaDevices APIMDN documentation on accessing camera and microphone
Notifications APIMDN documentation on the browser Notifications API
Clipboard APIMDN documentation on the browser Clipboard API