Privacy Policy
Effective & Last Updated: October 1, 2026
LatencyPulse is built with privacy-first engineering. When you perform acoustic latency measurements, your microphone input is analyzed strictly in temporary, volatile local memory (RAM) via your browser's Web Audio API. We do not record, store, or transmit your voice, audio, or acoustic signals to any external server.
This document provides comprehensive transparency regarding our client-side architecture, third-party advertising cookies (including Google AdSense), analytics, and your rights under the GDPR, UK Data Protection Act, and CCPA/CPRA.
- 1. Introduction & Service Scope
- 2. Real-Time Audio & Microphone Data
- 3. Client-Side Local Storage
- 4. Web Analytics & Google Analytics 4
- 5. Third-Party Advertising & Monetization
- 6. Web Telemetry & Server Logs
- 7. Legal Bases for Processing (GDPR)
- 8. California & US State Privacy Rights
- 9. Children's Privacy (COPPA)
- 10. Data Security & Retention
- 11. Contact Information & Amendments
1. Introduction & Service Scope
This Privacy Policy explains how LatencyPulse ("we," "our," or "the Service") handles information when you visit or use our web application located at this domain. LatencyPulse is a specialized browser-based diagnostic utility providing users with tools to estimate and calibrate audio-visual latency, Bluetooth transmission delay, and playback synchronization offsets.
We are dedicated to maintaining the confidentiality, integrity, and security of user information. Because our core benchmarking features operate via client-side W3C Web Audio API standards, we minimize data transmission to the greatest degree feasible under modern web standards.
2. Real-Time Audio & Microphone Processing
LatencyPulse includes an optional diagnostic tool known as the Acoustic Microphone Loopback Auto-Test (Tab 3). To operate this benchmark, your browser will prompt you for explicit permission to access your audio capture device (microphone) via the standardized navigator.mediaDevices.getUserMedia() programming interface.
2.1 Ephemeral Volatile In-Memory Analysis Only
When microphone permission is granted:
- In-Memory Processing: The incoming raw PCM audio stream is routed strictly into an in-memory Web Audio
AudioContextand connected to anAnalyserNodeinside your local browser sandbox. - Transient Peak Detection: The software analyzes numerical sample buffers (
Float32Array) solely to calculate the mathematical arrival timestamp of the generated impulse chirp. - No Audio Recording or Persistence: At no point is your voice, conversation, ambient background sound, or acoustic profile recorded, digitized into audio files (e.g., WAV, MP3, WebM), saved to persistent storage, or retained on your device.
- No Network Transmission: The audio data is never uploaded, streamed, or dispatched across any network socket, WebSocket, API endpoint, or remote server. Processing occurs entirely on your device's CPU and memory.
- Immediate Track Termination: Upon completion of the benchmark pulses, or if you click "Stop" or navigate away, the audio stream tracks are immediately closed via
MediaStreamTrack.stop(), releasing hardware microphone control back to your operating system.
3. Client-Side Local Storage & Session State
To preserve your calibration offset (e.g., your calibrated latency offset in milliseconds) and UI preference selections (such as selected impulse sound effects and sweep speeds), LatencyPulse may use your web browser's local storage mechanisms (localStorage and/or sessionStorage).
This information is stored exclusively on your device, is entirely under your browser's control, and contains no personally identifiable information (PII). You may delete or clear these stored values at any time through your browser's history or cookie clearing settings.
4. Web Analytics & Google Analytics 4 (GA4)
To understand aggregate user traffic patterns, measure popular diagnostic features, and ensure cross-browser performance, LatencyPulse utilizes Google Analytics 4 (GA4), a privacy-conscious web analysis service provided by Google LLC ("Google").
4.1 Scope of Aggregate Statistical Data
Google Analytics uses first-party cookies or pseudonymous client identifiers to compile non-personally identifiable statistical telemetry. This information includes:
- Aggregate page visits, session durations, and user interface engagement flows;
- Referring domain sources (e.g., search engines, referring tech forums);
- Browser engine family, operating system architecture, and screen viewport dimensions;
- Approximate regional geolocation (derived at the city or country level).
4.2 Built-In Privacy Protection & IP Anonymization
- Automatic IP Masking: Under Google Analytics 4 architecture, individual Internet Protocol (IP) addresses are neither logged nor permanently stored on disk. IP addresses are processed transiently at nearest edge nodes solely to resolve general regional geographic metadata and are immediately discarded.
- No Audio or Calibration Tracking: Google Analytics does NOT have access to, nor does it receive or record, your microphone input stream, audio impulse waveforms, or personal latency calibration measurements. All audio analysis remains strictly confined to your local device's volatile RAM memory.
4.3 Google Partner Transparency & User Opt-Out
To learn more about how Google handles analytics telemetry across digital properties, please review Google's official partner policy: How Google uses information from sites or apps that use our services.
Visitors who prefer to exclude their visit data from Google Analytics across all websites may install the official Google Analytics Opt-out Browser Add-on, compatible with all major desktop web browsers.
5. Third-Party Advertising & Future Monetization
Current Operating State: As of the current release, LatencyPulse operates with zero third-party advertising scripts or tracking cookies for its core audio benchmarking features. You can use all diagnostic tools without external advertising trackers.
Prospective Commercial Monetization (Google AdSense Readiness): To support ongoing web infrastructure, server bandwidth, and continuous maintenance, LatencyPulse may implement third-party advertising services (including Google AdSense) or privacy-preserving web analytics. In compliance with Google AdSense Publisher Terms and international data protection laws, this website provides pre-disclosed terms governing ad serving, advertising cookies, and user opt-outs whenever advertising is active:
5.1 Google AdSense & Advertising Cookies (Upon Activation)
- Third-party vendors, including Google LLC, use cookies, device identifiers, and similar technologies to serve advertisements based on a user's prior visits to this website or other websites on the Internet.
- Google's use of advertising cookies enables it and its partners to serve relevant advertisements to users based on their visits to our site and/or other sites across the web.
- These cookies help measure advertising efficacy, prevent fraudulent or invalid clicks, and tailor content to user interests in accordance with Google's publisher policies.
5.2 User Control & Opt-Out Mechanisms
Whenever third-party advertising networks are active, users maintain full legal rights and technical mechanisms to control and opt out of personalized ad targeting:
- Google Ads Settings: You can manage, personalize, or opt out of Google's personalized advertising at any time by visiting the Google Ads Settings portal.
- Industry Opt-Out Portals: You may opt out of personalized advertising cookies from participating advertising networks via the Digital Advertising Alliance (DAA) WebChoices Tool or the Network Advertising Initiative at networkadvertising.org.
- European Users (EDAA): Visitors in the European Union or United Kingdom can manage ad preference cookies through Your Online Choices.
- Browser Controls: Modern web browsers allow you to configure cookie preferences, enable "Global Privacy Control" (GPC) signals, block third-party cookies, or browse in incognito mode.
6. Web Telemetry & Server Logs
When your web browser requests files (HTML, CSS, JS scripts, fonts) from our web servers, standard non-identifying technical server logs are automatically recorded. This data may include:
- Internet Protocol (IP) address (which may be truncated or pseudonymized for privacy);
- Browser client type, version, and rendering engine;
- Operating system architecture;
- Referring Uniform Resource Locator (URL);
- Date, time, and status code of the HTTP request.
This operational logging is processed strictly under legitimate interest to prevent distributed denial-of-service (DDoS) attacks, investigate system errors, detect security vulnerabilities, and ensure infrastructure stability. Server logs are routinely purged.
7. Legal Bases for Processing (GDPR & UK Data Protection)
For individuals residing in the European Economic Area (EEA), United Kingdom, or Switzerland, our processing of data complies with Regulation (EU) 2016/679 (General Data Protection Regulation) and the UK GDPR:
- Functional Execution (Art. 6(1)(b)): Running client-side audio analysis requested directly by your action in the user interface.
- Legitimate Interests (Art. 6(1)(f)): Maintaining server network defense, preventing fraudulent usage, and optimizing site performance.
- Consent (Art. 6(1)(a)): For the placement of non-essential cookies, analytics, and personalized advertising where required by law.
Under the GDPR, you have the right to request access to, rectification of, or erasure of your personal data; the right to restrict or object to processing; and the right to lodge a complaint with your national Data Protection Authority (DPA).
8. California & US State Privacy Disclosures (CCPA / CPRA)
This section provides supplemental disclosures required under the California Consumer Privacy Act of 2018 as amended by the California Privacy Rights Act of 2020 (collectively, "CCPA"), as well as comprehensive privacy laws in Virginia, Colorado, Connecticut, Utah, and other US jurisdictions:
- No Sale of Personal Information: LatencyPulse does not exchange personal information or audio data for monetary consideration.
- Sharing for Cross-Context Advertising: Third-party advertising partners (such as Google AdSense) may receive identifiers or cookie data to facilitate online behavioral advertising, which may be deemed "sharing" under California law. You may exercise your right to opt out as outlined in Section 4.2.
- Non-Discrimination: We will not deny services, provide a different quality of service, or charge different prices for exercising your statutory privacy rights.
9. Children's Privacy (COPPA Compliance)
LatencyPulse is a technical utility intended for general audiences and is not directed toward or marketed to children under 13 years of age (or under 16 years of age in the European Union). We do not knowingly collect, request, or solicit personal information from children. If you believe a child has provided personal information to our site, please contact us immediately so we can take appropriate remedial action.
10. Data Security & Retention
We employ industry-standard technical safeguards, including HTTPS TLS encryption for all web transmission, to protect information against unauthorized access, alteration, disclosure, or destruction. Because audio analysis occurs in volatile RAM and is not written to permanent storage, there is no retained audio data at risk of data breach.
11. Contact Information & Policy Amendments
We reserve the right to revise or update this Privacy Policy periodically to reflect legal amendments, technological enhancements, or modifications in our operational practices. Any updates will be published on this page with an updated "Effective & Last Updated" date.
If you have any questions, comments, or legal inquiries regarding this Privacy Policy or our client-side data handling procedures, you may reach our administrative team via email at: digitalwebstudio.yu@gmail.com.