Most tests run locally in your browser. We do not upload microphone or camera content.

Privacy Policy

How Micstest handles permissions, local processing, cookies, and limited data

Last updatedApril 4, 2026

Effective dateApril 4, 2026

Operator

Micstest is not presented here as a corporation. The public author information in this repository identifies the service as run by a named individual.

Operating entity	Tom Mcfly, operating Micstest
Status	Operated by an independent developer / individual creator
Contact email	[email protected]
Country or region	United States
Jurisdiction note	Please send privacy or legal notices by email first

What We Collect

Micstest is designed so device testing happens in your browser whenever possible. Separate site features such as analytics, comments, feedback, and cookies may still process limited data.

We may collect

Basic request and security logs such as IP address, user agent, referrer, and timestamps
Page-view and usage analytics through Umami and Google Analytics
A persistent user_sign cookie used to associate likes, dislikes, and feedback with the same browser
Optional feedback or contact details you submit, such as your email address, topic, and message
Public comments you choose to post, including display name, topic, and comment text

We do not collect

Microphone recordings uploaded to our servers
Webcam video uploaded to our servers
Uploaded diagnostic media files as part of normal testing
Account profile data or passwords, because there is no account system
Bluetooth, geolocation, or motion sensor readings stored on our servers as part of routine tool use

When you run microphone, camera, geolocation, Bluetooth, notification, or motion tests, the live stream or sensor reading is handled in the browser session unless you separately submit information to us.

Permissions

Browser permissions are requested only when you open a matching tool and actively start a test. Denying a permission may limit that tool, but it does not block the rest of the site.

Microphone permission

Why it is needed: To capture live audio for the microphone tester and local recording preview.Used in: /micUploaded to server?: No. Audio stays in your browser unless you choose to download it locally.How to revoke: Remove microphone access in your browser site settings or operating-system privacy settings.

Camera permission

Why it is needed: To preview your webcam, measure image characteristics, and take local snapshots.Used in: /cameraUploaded to server?: No. Camera frames are processed locally in the browser.How to revoke: Remove camera access in your browser site settings or operating-system privacy settings.

Notifications permission

Why it is needed: To test page notifications and service-worker notifications.Used in: /notificationUploaded to server?: No. The site sends test notifications locally through the browser.How to revoke: Block notifications in your browser site settings and, if needed, in system notification settings.

Geolocation permission

Why it is needed: To read your current location for the geolocation test and watch-position demo.Used in: /geolocationUploaded to server?: No. Coordinates are shown in the browser and not uploaded by the site during normal use.How to revoke: Remove location access in browser site settings or system location controls.

Bluetooth permission

Why it is needed: To discover nearby compatible Bluetooth devices and inspect local GATT services.Used in: /bluetoothUploaded to server?: No. Device discovery and interaction stay in the browser session.How to revoke: Disconnect the device and clear site permissions in the browser when your browser exposes that control.

Motion / Sensor permission

Why it is needed: To read motion and orientation events for sensor diagnostics on supported devices.Used in: /device-sensorUploaded to server?: No. Sensor readings are displayed locally in the page.How to revoke: Turn off sensor access in browser or device settings. On some iOS devices, deny or reset motion/orientation permission.

Cookies & Analytics

The testing tools themselves do not need cookies to process microphone or camera content, but the website does use limited cookies and third-party scripts at the site level.

Micstest sets a persistent first-party user_sign cookie to reduce duplicate likes/dislikes and to associate feedback records with the same browser.
The site loads Umami and Google Analytics for traffic and usage measurement. The current codebase does not attach account IDs, microphone recordings, or webcam media to those analytics calls.
The current Google Analytics snippet in the repository does not show a custom IP-anonymization flag. Provider-side processing rules may still apply under Google policies.
The site also loads an Ezoic privacy/consent script and Google AdSense advertising script. Depending on your region, browser, and consent state, those providers may use cookies or similar identifiers.
You can clear cookies, block third-party scripts, use browser privacy controls, or adjust any consent choices shown to you by the site or its providers.

Third-Party Services

Current production code in this repository loads or links to the following third-party services.

Category	Provider or service	Purpose	Data note
CDN / script delivery	cloud.umami.is, www.googletagmanager.com, g.ezodn.com, cdnjs.buymeacoffee.com, pagead2.googlesyndication.com	Delivers analytics, consent, support-widget, and advertising scripts.	Those providers may receive standard request metadata when their scripts load.
Analytics	Umami; Google Analytics	Measures traffic, page views, and high-level site usage.	The repository does not show custom personal identifiers attached to analytics events.
Advertising / consent	Google AdSense; Ezoic CMP	Handles advertising delivery and consent-management prompts where applicable.	Cookie and identifier behavior may depend on region and consent state.
Error monitoring	None detected in current production code	No dedicated third-party error monitoring script is currently loaded.	If this changes, this policy should be updated.
Embedded links and support widgets	Buy Me a Coffee widget; external links to Reddit, Instagram, and X	Lets you support the creator or open third-party sites by choice.	Those services apply their own privacy practices after their widget loads or you click out.

Your Rights

If you want to access, correct, or delete personal data you submitted through comments or feedback, contact us by email.

Email privacy requests to [email protected].
For deletion requests, include the page URL, approximate date, and the email address, display name, or message content you used so we can locate the record.
If you are asking about microphone, camera, Bluetooth, geolocation, or motion data, note that those test streams are normally not uploaded to our servers, so there is usually no server-side media file to delete.
You can also report privacy concerns or suspected data issues at [email protected].
We aim to respond within 7 to 14 business days.