Your media remains in the browser.

Microphone and camera access

Access begins only after you choose to start a relevant test and approve the browser permission. Audio samples and camera frames are analyzed or displayed inside the current browser tab. They are not transmitted to our server, recorded, or stored by MeterSee.

Device information

After permission, the browser may reveal labels and settings for locally connected media devices. The current tools use that information only in the page to identify the active device and show capture settings. It is not uploaded by the diagnostic code.

Local diagnostic reports

Pre-call reports are assembled inside the browser and downloaded directly as PDF files. MeterSee does not receive a copy. The report can contain browser details and media-device labels, so the tool provides an option to hide device names before testing and exporting.

Computer slowdown check

The quick computer check measures short-lived browser responsiveness, a local Web Worker calculation, WebGL availability, and small requests to MeterSee. The optional deep check runs only after three explicit confirmations, including a physical-safety confirmation, and can briefly use up to four Web Workers, a 32 MiB memory buffer, 16 MiB of temporary IndexedDB origin storage, and a seven-second WebGL 2 workload. After the storage phase, the tool attempts to close and delete its uniquely named test database. When a storage result is available, the report indicates whether deletion was confirmed. An interrupted check or a closed tab should not be taken as confirmation of deletion.

System readings and symptoms are typed or selected by you. Diagnostic logic and PDF generation run in the browser; MeterSee does not upload the answers, deep-check measurements, or receive a copy of the report. Even with consent, the page cannot enumerate installed applications, processes, files, registry entries, malware, drive-health data, temperatures, or physical memory use.

Connection screening

The Call Quality and Pre-Meeting tools can send a short sequence of small HTTPS requests to a MeterSee asset and time the responses in your browser. Standard hosting logs may therefore receive the same request metadata described below. The timing summary remains in the current tab and is not submitted as a diagnostic report. The check does not upload microphone audio, camera frames, files, or router information and does not connect to Zoom, Teams, or Google Meet on your behalf.

Advertising and cookies

MeterSee intends to use Google AdSense, subject to approval. Advertising stays off until the site advertising switch is enabled and a consent platform reports explicit device-storage consent for Google. Allowing analytics does not enable advertising. If the consent signal is missing or incomplete, the site does not load AdSense or show ad slots.

When advertising is enabled with the required choices, third-party vendors including Google may use cookies, web beacons, IP addresses or similar technologies to serve and measure ads, including ads based on prior visits to this or other websites.

Google's use of advertising cookies enables it and its partners to serve ads to users based on their visit to MeterSee and/or other sites across the Internet. You can learn more about how Google handles user information by reading How Google uses information from sites or apps that use our services.

Users may opt out of personalized advertising at any time by visiting Google Ads Settings. Alternatively, you can opt out of a third-party vendor's use of cookies for personalized advertising by visiting www.aboutads.info.

Personalized advertising in the EEA, United Kingdom and Switzerland requires a Google-certified consent platform. Advertising choices belong to that platform, separately from the analytics controls. Withdrawing an active advertising consent reloads the page to stop previously loaded ad code; requests already sent cannot be recalled. MeterSee does not send microphone audio, camera frames, key presses, mouse events, or test results to Google AdSense.

Optional analytics

MeterSee uses a separate Google Analytics 4 property, measurement ID G-D4V5Z43128, to understand aggregate page use and improve the diagnostics. Analytics is not loaded unless you choose “Allow analytics.” If you decline, the Google Analytics script is not loaded. The setting is stored in your browser and can be changed with the “Privacy choices” control.

Analytics is configured without Google signals or advertising personalization. MeterSee does not send microphone audio, camera frames, key presses, pointer events, device-test inputs, device-test results, or locally generated PDF reports to Google Analytics.

You can withdraw analytics consent through Privacy choices. MeterSee then disables further GA measurement, removes its analytics script and deletes accessible GA cookies. This does not undo earlier requests or delete data already held by Google. If browser storage is unavailable, your choice applies to the current page and may not be remembered on the next visit.

Site delivery and performance

Cloudflare delivers and protects this website. Production pages can also load its Web Analytics performance beacon, independently of the optional Google Analytics control. This beacon measures page visits and loading performance. Cloudflare describes Web Analytics as a cookie-free service. MeterSee diagnostic code does not submit media, test inputs or results to it. See Cloudflare Web Analytics documentation.

Server logs and contact

Hosting and security providers may process standard request metadata such as IP address, user agent, requested URL, and time for delivery, abuse prevention, and troubleshooting. Contact messages will be used to answer the request and maintain necessary records.