Privacy Policy

Scope and Purpose of This Policy

This Privacy Policy applies to KeyPulse Studio version 1.4.0. It explains how the extension processes physical keyboard activity, updates its on-page visual interfaces, calculates live session metrics, stores limited local preferences, operates its Keyboard Arcade features, and uses the browser permissions required for those functions.

KeyPulse Studio is designed as a physical keyboard visualizer and lightweight keyboard interaction workspace. It includes a Compact Mode for minimal on-page feedback and a larger Studio Mode with a full keyboard layout, animation controls, live statistics, and three built-in Arcade challenges.

The extension is not designed as a keylogger, text recorder, productivity surveillance tool, behavioral advertising service, cloud account product, or remote analytics platform. Its primary purpose is to provide immediate visual and interactive feedback from current keyboard activity inside the browser.

This policy does not govern the privacy practices of the user's browser, operating system, extension marketplace, websites visited by the user, or other applications and extensions installed on the device.

How KeyPulse Studio Operates

KeyPulse Studio uses browser content scripts on ordinary HTTP and HTTPS webpages so that its visual interface can appear directly over the page the user is viewing. The extension can show a small Compact HUD or an expanded Studio interface without requiring the user to open a separate web application.

The extension's toolbar action and built-in controls are used to show, hide, collapse, expand, or switch the visualizer between Compact and Studio modes. The current interface state is rendered locally inside the browser.

Studio Mode combines a visual representation of the physical keyboard with live session metrics, animation controls, and access to Keyboard Arcade. Compact Mode presents a smaller visual layer intended to stay visible while the user continues browsing, presenting, recording, or demonstrating shortcuts.

The extension does not require a developer-operated account, login system, cloud database, or remote API to decide which key should be highlighted or which visual effect should be displayed.

Physical Keyboard Event Processing

KeyPulse Studio listens for supported browser keyboard events, including keydown and keyup activity, on webpages where its content script is allowed to run. The extension primarily uses browser-provided physical-key information such as KeyboardEvent.code so the on-screen keyboard can represent the physical key position being pressed.

This physical-key approach allows KeyPulse Studio to visualize individual keys, held modifiers, and simultaneous key combinations without depending solely on the final text character produced by a keyboard layout or input method.

The extension processes keyboard activity as it occurs in order to update visual key states, the last-physical-key indicator, temporary counters, and interactive Arcade logic. It does not create a persistent chronological transcript of every key the user presses.

KeyPulse Studio does not intentionally preserve complete typed sentences, messages, search queries, document content, form submissions, or other text as a replayable history. Current keyboard events are used for immediate extension behavior rather than for building a stored text log.

Input Methods, Composition, and International Keyboards

Some keyboard layouts and input methods, including IME-based composition and language-specific typing tools, can cause browser keyboard events to behave differently from simple Latin-key input. KeyPulse Studio includes handling intended to keep physical-key visualization stable during composition-related input and to reduce duplicate or misleading visual responses.

The extension's purpose in handling composition-related events is to identify physical-key activity for visualization. It is not designed to reconstruct or store the composed text produced by an IME, Vietnamese input method, or other language-input system.

Because browser, operating-system, keyboard-layout, and third-party input-method behavior can differ, the exact event sequence may vary by environment. Regardless of those differences, KeyPulse Studio does not intentionally transmit composed text or maintain a persistent record of composition output.

Password Fields and Sensitive Input

KeyPulse Studio includes a safeguard for standard HTML password fields. When supported keyboard activity originates from an input element recognized by the browser as type="password", the extension excludes that input from the normal visualization and counting path.

This means ordinary browser-recognized password fields are not intended to update the visible key indicator, increase normal session press counts, or become part of a stored key history.

Some websites may implement custom sensitive-input controls that are not technically standard password inputs. The internal structure of those controls is determined by the website and may not be detectable in the same way as a native password field.

Live Session Metrics

Studio Mode can display live activity information such as current keys per second (KPS), peak KPS, total recognized presses during the active session, and the most recent supported physical key.

These values are calculated from current keyboard activity so the extension can provide immediate visual feedback about the rhythm and intensity of the session. They are not intended to create a long-term productivity record or behavioral profile.

Current KPS, peak KPS, total press counts, and the last-physical-key value are treated as active-session information. They are not used to build a remote account history and are not uploaded to a developer-controlled analytics service.

Temporary metrics may reset when the relevant extension session, page context, or visualizer session is recreated.

Visual Effects and Animation Preferences

KeyPulse Studio includes selectable keypress effects such as Logo Orbit, Aurora Bloom, Shockwave, Ember Trail, Prism Shift, Signal Glitch, and Clean Press. These effects change how current physical-key activity is presented visually.

Selecting an effect does not require keyboard activity to be sent to a server. The animation is produced locally by the installed extension using the current visualizer state.

The extension may store the user's selected visual preference locally so that the chosen effect can be restored in a later browser session. This stored preference identifies an interface choice; it is not a stored history of the keys that produced the visual effect.

Arcade Games and Local Best Scores

KeyPulse Studio includes three keyboard-based Arcade challenges: Target Hunt, Key Sprint, and Sequence Relay. These games reuse the same physical-key event system to provide reaction, speed, and memory interactions inside the extension.

During active gameplay, current key events may be evaluated to determine whether the requested target was pressed, how many recognized presses occurred during a timed sprint, or whether a displayed sequence was reproduced correctly.

The extension may store Arcade best scores locally in browser extension storage so that a user can see their previous best result when returning to the game. Best-score storage is limited to game result values and is not intended to preserve the sequence of keys typed during normal browsing.

Arcade activity is not transmitted to a developer-operated leaderboard, remote profile, advertising service, or analytics backend in the reviewed version.

Locally Stored Preferences and Settings

The extension uses browser extension storage to preserve limited settings that help restore the user's preferred KeyPulse Studio experience between sessions.

Depending on the feature state in version 1.4.0, locally stored values may include:

• whether the KeyPulse interface is shown or hidden;
• whether Compact Mode or Studio Mode is selected;
• the saved position used to restore the floating interface;
• the selected animation or visual-effect preference;
• locally retained best scores for supported Keyboard Arcade games.

These preferences remain within the browser's extension storage environment unless they are changed or cleared by the user or removed when the extension is uninstalled.

Website and Content-Script Access

KeyPulse Studio declares access that allows its content script to run on ordinary HTTP and HTTPS webpages. This access is necessary because the extension's visualizer is intended to appear directly on webpages and respond to supported keyboard events while the user interacts with those pages.

This access allows the extension to insert the Compact or Studio interface, attach keyboard-event listeners, update visual states, and respond to extension controls. It does not mean that KeyPulse Studio operates a developer-maintained browsing-history service.

The reviewed implementation is not designed to capture screenshots, upload webpage text, collect form submissions, inspect private messages for analytics, or send webpage content to a developer-controlled server.

Browser-controlled pages and other restricted environments may block content scripts. On those pages, the extension may be unable to display or control its interface because the browser does not allow the required script to run.

Extension Permissions

KeyPulse Studio uses browser permissions that support its visible functionality. These permissions may include storage access for local preferences and host or content-script access needed to place the visualizer on supported webpages.

Permissions are used to support extension features such as showing the visualizer, switching views, restoring interface preferences, and running the on-page keyboard interaction system. They are not intended to provide unrelated access for advertising, profiling, or remote data harvesting.

If future versions add materially different permissions, the privacy policy should be updated to explain why those permissions are required and whether they introduce any new data flow.

Network Requests and Remote Code

The reviewed version of KeyPulse Studio does not require a developer-operated backend to visualize keyboard activity, calculate live session metrics, apply keypress effects, or operate its built-in Arcade challenges.

The executable code required for those extension features is included with the installed extension package rather than being downloaded as remote executable code at runtime.

The reviewed implementation does not include a developer-configured endpoint used to upload physical key events, typed text, live KPS values, total press counts, Arcade input sequences, or local interface preferences.

The browser and extension marketplace may independently perform network operations for installation, updates, security scanning, account services, or other platform functions. Those operations are controlled by the relevant platform and are outside the extension's own data practices.

Information KeyPulse Studio Does Not Intentionally Collect

KeyPulse Studio is not designed as a personal-data collection service. The reviewed implementation does not intentionally maintain the following categories for the developer:

• names, email addresses, telephone numbers, postal addresses, or user account profiles;
• passwords, authentication credentials, payment details, or financial information;
• a persistent transcript or chronological history of the user's key presses;
• complete typed messages, documents, search terms, or form submissions;
• a developer-maintained database of visited URLs or browsing history;
• IP-address profiles, precise location histories, advertising identifiers, or demographic profiles;
• behavioral analytics, session replay, advertising-conversion data, or commercial user profiling;
• remote long-term productivity records based on KPS, press counts, or Arcade activity.

Because the extension does not operate a developer-managed keyboard-activity backend for these categories, the developer does not maintain a cloud archive of users' typed content or physical keypress histories.

Advertising, Analytics, Tracking, and Data Sharing

KeyPulse Studio does not display advertising and is not designed to include advertising SDKs, tracking pixels, browser-fingerprinting systems, session-replay tools, or behavioral analytics used for commercial profiling.

Keyboard activity used by the visualizer is not intended to infer purchasing intent, health characteristics, employment performance, financial status, political beliefs, or other unrelated personal traits.

The extension does not sell or rent physical keyboard activity, typed content, local preferences, live metrics, or Arcade best scores to advertisers, data brokers, or analytics providers.

Because the reviewed version does not maintain a developer-operated remote store of keyboard activity, there is ordinarily no remote keypress dataset available for commercial sharing or disclosure.

Data Retention and Removal

Individual physical keyboard events are processed as they occur and are not retained by KeyPulse Studio as a persistent chronological history.

Live session values such as current KPS, peak KPS, total presses, and last physical key are associated with the active visualizer session and are not intended to become a permanent remote record.

Limited interface preferences, selected visual settings, and supported Arcade best scores may remain in local browser extension storage so they can be restored later.

Users can remove locally stored extension data by clearing the extension's stored data through browser controls or by uninstalling KeyPulse Studio, subject to the browser's own storage and deletion behavior.

Security and Privacy-Oriented Design

KeyPulse Studio limits privacy risk by processing its primary keyboard visualization locally and by avoiding a developer-operated remote data pipeline for ordinary keyboard activity.

The extension excludes standard password fields from the normal visualization path and uses current keyboard activity for immediate interface behavior rather than for building a persistent key history.

The extension may also clear or reset active visual key states when focus or page visibility changes, helping prevent stale on-screen key states from remaining after the user's browsing context changes.

No software can eliminate every possible privacy or security risk, particularly when its declared function requires access to keyboard events on supported webpages. KeyPulse Studio therefore follows a purpose-limited model: process what is needed for current visual or game behavior, avoid storing typed content as history, avoid transmitting normal keyboard activity to a developer backend, and retain only limited local state needed for usability.

Changes to This Privacy Policy

This Privacy Policy may be revised when KeyPulse Studio's implementation or data practices change. Examples that may require a meaningful policy update include adding new permissions, introducing a backend service, transmitting new categories of information, changing how keyboard events are retained, adding analytics, expanding website access, or storing additional long-term data.

Future versions should be reviewed against the actual extension implementation rather than assuming that behavior described for version 1.4.0 remains unchanged indefinitely.

When material changes occur, the policy should be updated with a revised effective date and an explanation that accurately reflects the new data flow or feature behavior.

Contact

Questions about this Privacy Policy or the privacy behavior of KeyPulse Studio may be sent to thanhthuc284917@gmail.com.

When contacting support about privacy or extension behavior, users do not need to provide passwords, private text, complete browsing histories, or other sensitive content. A description of the issue and the relevant extension version is generally sufficient.