Skip to content
The PolyTrack

Contact The PolyTrack

Use contact@thepolytrack.com for website problems, inaccurate instructions or a community-track credit that needs correction. A useful PolyTrack report identifies the page and the action that failed. You do not need to write a long message; a few specific details make it much easier to understand the issue.

contact@thepolytrack.com

For loading or import problems

Say which device and browser you used, then describe the last screen that worked. Did the player stay on its loading screen, reject an import code or open a track that does not respond to the keyboard? Those are different problems. Include whether you used 0.6.3 or 0.5.0 rather than assuming the version matches another website.

For a course-specific issue, send the track name and the source link from its card. If you used a different revision, include that original link too. Avoid pasting a shortened fragment of a code as evidence; the source file is usually easier to compare.

  • Page URL and track name, if relevant.
  • Device, browser and visible game version.
  • The steps you took and the exact error text.
  • Whether the same code works in another version or source.

For authors and content corrections

If a PolyTrack track attribution is wrong, point us to the original creator credit or source. If an instruction is inaccurate, identify the sentence and the menu or behavior that contradicts it. Screenshots can help, but crop out unrelated personal information.

The website is independent of Kodub. We can review our pages and source references; we cannot promise to restore cleared browser saves, change external leaderboard records or act as another service’s account support.

Keep the message focused

Do not include passwords, payment details or private account credentials. We do not offer a live support queue or promise a fixed reply time. If you need immediate help getting a PolyTrack code into the game, the import guide covers the common text and version checks before you send a report.

Check the import troubleshooting steps