YOUR SETTINGS STAY WITH YOU.
Privacy policy.
Effective October 10, 2026 · Applies to the Treadory website, desktop previews and Treadory — Foot Pedal Control browser extension.
Local controls. Clear choices. Treadory has no accounts, advertising, analytics or telemetry. We do not receive or sell your pedal reports, settings, browsing activity or page content.
The app processes the information needed for the features you choose on your device. Your hosting provider, browser and websites you visit may have their own data practices.
What Treadory processes
- Pedal input and device information: authorized USB device identifiers, device name, readable HID reports and learned press/release fingerprints identify physical controls. Recent history keeps up to 50 decoded presses with computer timestamps.
- Settings you provide: pedal mappings, custom text, recorded shortcut combinations, selected model and website-specific presets are stored locally. Shortcut recording is an explicit setup action; Treadory does not continuously log ordinary keystrokes.
- Website addresses: the extension reads the active tab’s URL to identify the website and choose its mapping. Saved site presets contain the website’s origin, such as https://example.org, rather than a browsing-history log. Browser permissions may also retain the sites you authorize.
- Website content and activity: when an action runs, the extension accesses the page elements, scrolling state, media state or focused plain text field needed to perform it. It does not copy a page’s text, images, audio or video to our servers. DOM actions are paused when the active element is a password field.
- Nearby mouse observations on the website: while a readable pedal is connected, the website may attach a nearby mouse-button event to a pedal-history row. This is a timing observation, not proof of which physical device sent the click. Ordinary clicks do not create pedal presses. These observations are not collected across other apps.
How this information is used
Information is used only to connect and learn supported pedal inputs, apply your mappings, display input history, diagnose compatibility and manage your configuration. The website’s separate compatible-device programming flow writes stored outputs only after you explicitly review and save them. In browser mode, the extension maps website actions without rewriting hardware output or suppressing existing operating-system clicks. The optional Windows app mode is described below.
We do not use this information for advertising, profiling, creditworthiness or lending. We do not sell it, transfer it to data brokers or use it for purposes unrelated to Treadory’s user-facing pedal-control features.
Storage and retention
The website stores configuration in your browser’s localStorage. The extension uses local extension storage, not Chrome Storage Sync. Their settings are separate. Device metadata, mappings and learned fingerprints remain until you change, reset or delete them. This browser storage is not presented as an encrypted secret vault; do not put passwords or other secrets in custom text mappings.
Recent history is held in memory and clears when the page or extension worker restarts. Raw reports are used for current decoding and learning; learned fingerprints may persist in your settings. The app does not upload a report or activity log. Optional diagnostics keep up to 50 press outcomes in memory, including timestamps, action types and failure categories. Copy diagnostics creates a report only on request; it excludes website URLs, page content, device names, custom text, selectors and shortcut keys. Reports are not uploaded automatically; sharing a copied report is your choice.
Export creates a JSON file on your device only when you request it. It may include device names, custom text and saved website origins. Review exported settings before sharing them. Any copies you export or share remain under your control.
Permissions and your choices
USB access requires authorization through the browser’s WebHID chooser. The extension asks separately for optional access to one website or all normal HTTP/HTTPS websites. Access is used to perform the actions you configure, not to continuously capture page content. Browser settings, extension stores and other protected pages are excluded.
You can pause pedal actions, disconnect the USB device, clear recent history, reset settings or remove website access from the extension. You can also revoke permissions through your browser. Clearing the website’s browser data removes its local settings; uninstalling the extension removes its local extension storage. Exported files must be deleted separately.
Optional Windows app
The Windows app runs independently of the extension and has no browser native-messaging connection, network listener or telemetry. Mappings, optional guard scope and the driver integrity hash stay in local app settings. Device identities are checked transiently and are not sent to websites. The app checks input-device inventory and the recovery chord without recording ordinary mouse or keyboard content. Stopping capture or exiting restores original pedal input. Its separately licensed driver has its own installation and removal instructions.
Optional click guards and desktop previews
Click guards are off by default. The extension processes mouse/pointer button events only in permitted frames; Windows and macOS guards process normal-session mouse button events. The extension observes ContextMenu/Shift+F10 locally to preserve keyboard menus, without canceling or storing key input. Temporary sequence state pairs canceled presses/releases for at most five seconds; no mouse-position or click history is stored or uploaded. Legitimate ordinary-mouse clicks can also be blocked. Movement and scrolling remain available. Choose All buttons or Right-click only explicitly.
The macOS preview stores local mappings and guard scope in Application Support/Treadory; permissions are managed by macOS. Linux stores local mappings under the XDG config directory, reads only the selected eligible pedal node, creates configured uinput output and queries systemd-logind for session safety. Its OS click guard is unavailable. Native identities/learning/activation do not persist. No preview installs auto-start or telemetry; remove settings and permission grants separately during uninstall.
Hosting and third-party websites
The website is hosted on Netlify. Netlify may process technical request information, such as IP addresses and request metadata, to deliver and secure the website under its privacy policy. Treadory does not add visitor analytics or tracking scripts.
Opening a manufacturer, source-code or support link makes a normal request to that third-party service. Browser stores and your browser may also process information under their own policies. These services operate independently of Treadory’s local pedal processing.
A configured button click, shortcut or inserted text can trigger the destination website’s own behavior, including submitting data to that website. Those interactions follow that website’s privacy policy. Treadory itself has no backend receiving your configurations or page content.
Chrome Web Store Limited Use
Treadory’s use of information received from Google APIs adheres to the Chrome Web Store User Data Policy, including its Limited Use requirements. Local processing is limited to the pedal-control features described here. There is no independent data collection for marketing or unrelated analysis.
Changes to this policy
This page will be updated when data practices change. The effective date above identifies the current policy. Material new handling or permissions will be disclosed before they are introduced, with consent where required.
Questions or requests
Treadory is maintained by Ronit Gandotra. Privacy questions and general support are available through GitHub issues; do not include personal information, device exports or sensitive text in a public issue.