Contact & feedback

1. Feedback channel and response expectations

The Give feedback button opens the website’s text feedback form. No account or email address is required. The current form accepts a message of up to 5,000 characters and does not offer file attachments, a public comment thread or an account-based support inbox.

A success message indicates that the request was accepted. It does not guarantee a personal reply, a response time or implementation of a suggestion. Anonymous messages without a reply route cannot be assumed to receive individual follow-up. This form is not an emergency service.

2. Reporting a conversion discrepancy

Describe the expected result, the displayed result and how the physical distance was measured. Include enough conditions to reproduce the calculation. A mismatch alone does not establish an incorrect coefficient: percentage units, target DPI, rounding and a modified game scale can explain a difference.

• Source and target game profiles, including the selected trainer scale or known game version.
• Source sensitivity or turn distance, input unit, source DPI and target DPI.
• Rotation or monitor-distance matching, both FOV values and the match percentage when relevant.
• Any yaw override, custom multiplier, retained in-game value and measured cm/360.
• A reproducible sequence or reference link; remove unrelated personal information before submitting.

3. Reporting a button, display or download problem

Identify the page and control, the steps immediately before the failure, the expected behavior and any visible error text. Browser name/version, device category, viewport size and whether the problem repeats after a refresh can help describe the conditions.

For an export, specify TXT, CSV or JSON and distinguish a failed request from a file saved in an unexpected download location. For an import, specify whether the file selector or pasted-text route was used. Do not submit an entire private backup when a small description of the error is sufficient.

If a screenshot would help, describe the relevant part in text; the current form has no attachment upload. Do not paste unrelated browser history, account pages or private conversations.

4. Reporting a practice-range problem

Include the scenario, trial multiplier, FOV, raw-input choice and whether fullscreen was active. Describe whether the issue occurred before mouse capture, during a round, after pausing or in the completed report. Browser focus and mouse-capture permissions can affect startup.

For a scoring concern, distinguish shots, hits, tracking time and self-reported turn observations. Report the visible values and the action that produced them. Session reports clear on reload, so note the relevant details before leaving the page. Avoid treating a small sample as a reliable comparison of sensitivity settings.

5. Suggestions and new game references

Explain the task a proposed feature would solve, the current obstacle and the expected behavior. For a game-profile suggestion, include a reliable coefficient source or repeatable measurements, the exact input mode and any multiplier assumptions.

A shared engine, a popular game name or a sensitivity value copied from another tool is not enough to establish a supported scale. New references need a clear scope. Suggestions are considered without a guarantee of a release date or implementation.

6. Privacy and record-related enquiries

Begin the message with “Privacy enquiry” and identify the relevant data category. An approximate submission date and a short non-sensitive excerpt can help locate feedback. State whether the request concerns access, correction, deletion or an explanation of processing.

Local settings can be removed directly through the website’s clear-data control and the browser’s site-data settings. A server-side enquiry is separate: clearing a browser does not erase feedback already submitted. Anonymous records may be difficult to associate with a requester, and the form provides no private status thread.

Do not send identity documents, passwords or access tokens to prove a request. The privacy policy explains the available route and its limitations. A submission is not confirmation that a record has been found or removed.

7. Security and content concerns

For a suspected security issue, describe the affected feature and a minimal, non-destructive reproduction. Do not access another visitor’s information, submit live secrets, perform disruptive testing or publish an exploit through the feedback form.

For a content or rights concern, identify the specific page or passage, the material concerned and the reason for the report. Include an appropriate reference when available. Do not imply ownership of material that cannot lawfully be represented. The form does not provide a public takedown tracker or guarantee a particular outcome.

8. Information attached to a submission

The feedback service receives the entered text together with the website domain and page origin/path. Query strings and fragments are removed from the automatically attached address. A full link pasted into the message remains part of the text, so inspect it before sending.

Opening the form does not submit a message. Sending is optional. Submissions are stored for review through the feedback service described in the privacy policy; feedback is not published as a visitor comment. Avoid sensitive personal information and use only the details needed to explain the issue.

9. When a message does not send

Check that the message is not empty and stays within the displayed length limit. Network restrictions, content blockers, timeouts or service limits can prevent delivery. Keep a private copy of the message if it matters before refreshing or closing the form.

A timeout does not always prove that a server received nothing. Avoid repeated rapid retries; a duplicate message may be stored if a prior request completed without its confirmation reaching the browser. Follow any rate-limit notice and try again later. The current service can limit a network to 10 messages per hour.

The converter can still be used when optional feedback is unavailable. No public email address or alternative ticket system is published by this page.