Privacy policy
Last updated .
This policy explains what information Sensitivity Converter handles, why it is used, where browser storage differs from server processing, and the choices available to visitors.
1. Scope and practical overview
This policy describes information handled through Sensitivity Converter, including the conversion tool, saved profiles, practice range, file exports, usage statistics and feedback form. It distinguishes data kept inside a browser from information transmitted when a page, script, export or feedback service is requested.
The website currently provides its tools without registration, an account password, a payment form or an advertising integration. A lack of registration does not mean that every visit is anonymous: network requests and usage statistics can contain technical identifiers. External websites reached through reference links follow separate policies.
2. Calculation inputs and local processing
Game selections, sensitivity, DPI, yaw, turn distance, FOV and matching options are used to calculate results in the browser. Typing these values does not by itself upload a saved profile or submit a feedback message. The application does not read mouse-driver settings, scan installed games or detect actual hardware DPI.
Input validation, conversion formulas, comparison values and the measured-distance helpers run locally. Usage events can separately indicate that a conversion succeeded or that validation failed; the application’s custom event fields do not include the numeric settings entered into the converter. Exporting or voluntarily including settings in feedback creates the separate transmissions described below.
3. Browser storage and device access
The website uses local storage for the current conversion setup, named profiles, favorite games and theme choice. These records help restore a visit without an account. Up to 20 profiles can be saved. Profile names are user-entered text; descriptive setup names are preferable to personal identifiers.
Local storage is associated with the website origin and browser profile. It has no application-defined expiry for saved converter data. It can remain until cleared, overwritten or removed by the browser. Private browsing, storage restrictions, extensions, low-storage cleanup and browser changes can prevent persistence or remove records. Local saving is not a backup guarantee.
Another person using the same browser profile may be able to open saved settings. Separate browser profiles and device access controls are appropriate on shared devices. Sensitivity Converter does not provide account-based access control or cloud synchronization for local profiles.
4. Usage statistics and technical identifiers
The website loads a usage-statistics script delivered through Supabase infrastructure. The current integration enables statistics automatically; there is no on-page analytics preference panel. The script first attempts to obtain a valid site configuration. If configuration is unavailable or requests are blocked, events may not be delivered.
When active, the script assigns a random visitor identifier in local storage and a session identifier in session storage. It records page-view events, normalized page paths, event times, selected control identifiers, active engagement duration and maximum scroll depth. Sessions are renewed after approximately 30 minutes of inactivity. A visitor identifier is not a name, but it can associate activity across visits in the same browser.
Feature events describe outcomes such as conversion success, validation errors, copying, sharing, profile saving or importing, and practice lifecycle actions. A completed practice event may include a hit count. Custom feature events use an allowlist and do not include profile names, search text, feedback text, complete share links, raw pointer movement or full practice reports. The reviewed script does not record typed text or create session-replay recordings.
Query strings and URL fragments are excluded from the analytics route field. The script also replaces some dynamic-looking path segments with generic labels. Requests to the script and collection services still involve network metadata. Removing identifiers from an event body does not prevent infrastructure from receiving an IP address when handling a request.
5. Cookies, storage choices and privacy signals
The converter’s own persistence uses browser storage rather than an account cookie. The reviewed analytics script also uses local and session storage, and its network requests omit browser credentials. This description is not a claim that hosting or other infrastructure can never use cookies or technical request records.
The analytics script checks the Global Privacy Control signal and suppresses analytics event collection when that signal is present. Loading the script itself can still create a network request. The website does not claim to recognize every browser privacy signal, and a Do Not Track preference should not be assumed to have the same effect.
Browser controls or content-blocking tools can restrict storage and third-party requests. Blocking analytics should not prevent local calculations. Blocking all scripts can prevent interactive conversion, saving, feedback and practice. Clearing a visitor identifier does not delete previously received events and does not prevent a new identifier from being created on a later eligible visit.
7. Reports, backups, imports and printing
Downloading a TXT report or comparison CSV sends the selected calculation inputs to the website’s export endpoint. Downloading a profile backup sends the included profile identifiers, names and settings. These requests are necessary for the current server-generated attachment workflow, even though the underlying calculations are available locally.
The export endpoint validates the submitted payload and returns an attachment. It does not write that payload to an application database, and the response instructs caches not to store it. This does not establish that all hosting logs, security systems or downloaded copies are automatically erased.
A backup selected for import is read by the browser. Pasted backup text is also parsed locally. The import operation itself does not upload the entire backup to a server. Importing can add local profiles; existing data and capacity limits affect the result. A later backup export sends the selected saved profiles as described above.
Downloaded files remain in the location chosen by the browser or device. Printing invokes the browser’s print workflow. A selected printer, PDF destination or print service may receive the printed content. Clearing website storage does not delete files, clipboard entries, printed copies or copies held by a recipient.
8. Practice range data and mouse access
The practice range uses relative mouse movement and clicks to update the scene and calculate round statistics. Mouse capture starts through a practice action and can be released through browser controls. Optional raw-input support and fullscreen behavior depend on the browser. The website does not request camera or microphone access for practice.
Round results, comparison history and optional turn-comfort observations are held in the current page session. Reloading the page clears those session reports. They are not a durable record or a cloud profile. Saving or applying a setup changes converter settings; it does not create a cloud archive of the full practice report.
Practice-related usage events are described in the statistics section. Local processing of movement and reports should not be confused with an absence of all practice-related telemetry.
9. Optional feedback messages
Submitting feedback sends the entered message, website domain and page origin/path to a feedback service using Supabase infrastructure. Query strings and fragments are removed from the automatically attached page address. If a complete link or personal information is typed into the message itself, it becomes part of the submitted content.
Opening the form does not submit a message. The form does not require an account or email address and currently accepts text rather than file attachments. A successful submission stores the message for review; it does not publish the message as a public comment.
Feedback can be used to investigate reported problems, consider corrections or suggestions, and review abuse or privacy concerns. Do not submit passwords, access tokens, payment details, identity documents, private conversations or another person’s personal information. Network metadata may be processed to deliver the request and apply abuse controls.
A success notice confirms acceptance of the request, not a promised answer, repair or review deadline. Anonymous feedback has no user-facing inbox or message-status page. Without a suitable reply route, an individual response cannot be assumed.
10. Processing purposes and service recipients
Information is used to deliver requested pages and attachments, remember selected settings, measure feature usage, understand errors, support feedback review and protect the service against abuse. The current application does not provide advertising targeting, a profile marketplace or an automated decision system determining access to employment, credit or similar opportunities.
Hosting, network and security services process requests needed to deliver the website. Supabase infrastructure supports the current statistics and feedback integrations. These services may receive technical request information as well as the particular event or message payload. Service providers apply their own infrastructure and account-level controls.
Information may also need to be preserved or disclosed in response to a valid legal obligation, a security incident or an enforceable request. This policy does not assert that every legal request requires disclosure, or that information is publicly accessible merely because it is stored by a service.
The purpose and necessity of processing depend on the activity selected. Reading this policy is not treated as blanket consent to every possible future use. Where applicable requirements call for consent or another condition, the relevant requirement still applies; this notice alone does not establish that such a condition has been satisfied.
11. Retention and limits of automatic deletion
Saved converter settings and the analytics visitor identifier can persist in browser local storage without a fixed application expiry. Session identifiers use session storage, subject to browser session restoration behavior. Practice reports are temporary page-session data. Downloads and shared copies remain under the control of the device or recipient.
The application does not currently publish a verified, fixed automatic-deletion period for server-side feedback, collected analytics, hosting logs or provider backups. A submission should not be assumed to disappear when a browser tab is closed or local storage is cleared. The absence of a published period is not a promise of indefinite retention or immediate deletion.
A retention enquiry can identify the record category and approximate submission time through the contact form. The relevant record, processing purpose, unresolved issue, abuse investigation, provider configuration, backup lifecycle and applicable preservation requirements affect whether a record can be located and removed. The website cannot delete copies independently retained by link recipients or external applications.
12. Removing local information
“Clear saved profiles & favorites” removes the corresponding converter records and restores the default example. It does not clear the theme preference, analytics identifiers, previously submitted feedback or downloaded files. The ordinary Reset button restores example inputs without deleting saved profiles.
Use the browser’s site-data controls to remove remaining local and session storage for the website. Export a backup first if saved profiles need to be kept. Browser cleanup can also remove preferences required to remember prior choices. If storage operations fail, the visible state may change for the visit without changing the stored record; the interface provides an error message when that failure is detected.
13. Privacy enquiries and applicable rights
Depending on the requirements that apply to a particular situation, rights may include requesting information about processing, access, correction, deletion, restriction, objection, portability or withdrawal of consent where processing relies on consent. These rights are subject to their actual scope, exceptions and verification requirements. Nothing in this notice removes mandatory rights or prevents raising a concern with an appropriate supervisory body.
Use Contact & feedback and identify the request as a privacy enquiry. Include the data category, approximate date and enough non-sensitive context to distinguish the relevant record. For feedback, a short excerpt may help. Do not submit an entire identity document or sensitive credentials through the general feedback form.
The website has no account that automatically links an anonymous visitor to every server record. A request may therefore require additional information or may not identify a record reliably. The form itself offers no private reply thread. A message should not be treated as proof that deletion has occurred; local records can be cleared directly using browser controls.
14. Security and responsible disclosure
The application validates supported export and import formats, limits payloads, filters custom analytics fields and removes query/fragment data from automatically attached feedback addresses. These measures reduce particular risks but do not guarantee that every device, transmission, provider or stored copy is secure.
No online service can promise absolute protection against unauthorized access, data loss or service interruption. Protect the device and browser, review shared content and use trusted software. A suspected security issue can be reported through Contact & feedback without exposing credentials, exploiting another visitor’s data or performing disruptive testing.
15. External references and younger visitors
Links to game documentation, source repositories and reference material lead to separate websites. Visiting those destinations may disclose request information to them. Their cookies, storage, account features and privacy practices are not controlled through the converter’s settings.
Sensitivity Converter is a general-purpose mouse-settings reference and has no age-verification or parental-account feature. Younger visitors should avoid submitting personal information and obtain suitable guidance before using optional feedback or sharing features. A concern about a submitted message containing a child’s information can be reported through the privacy enquiry route without adding unnecessary sensitive details.
16. Changes to this policy
The date at the top identifies the most recent revision of this page. Material changes to features, processing or service integrations should be reflected in the notice. A future feature is not described as active merely because it could be added later.
Review this policy before submitting new information if the website’s behavior has changed. Changes to a notice do not by themselves replace a consent choice, waive a mandatory right or authorize an incompatible use of previously collected information.