Support and bug reports

Mail [email protected]. A human reads it — no ticket robot, no auto-reply — so answers can take a day or two. A good report usually gets fixed embarrassingly fast.

Every report

What happened, and what you expected instead.
When it happened — date, rough time, and your timezone (our logs are timestamped; this is how we find your moment).
Your username if you have one. Never send your password — we will never ask for it.
A screenshot when the problem is visible.

The site

The page’s address (copy the URL).
Browser and device (e.g. “Chrome on a Pixel 10”).
Signed in or not, free or paid.
The steps that got you there, if you can retrace them.

Shot Timer

App version (Account → About), phone model, Android version.
Was a run going? Report after the stage — never fiddle with a phone mid-match.
Detection problems: which mode (Live or Dry), indoors or outdoors, roughly how far the phone sat from the rifle — and which rifle, if it misses one rifle but not another.
Ballistics problems: which rifle and cartridge, and what the dope readout showed versus what you expected.
If you had Diag WAV on (Account → Developer), you can attach the run’s recording. It contains the sound of your session — attach it only if you’re comfortable with that. It’s the single most useful thing for a detection bug, and it never leaves your phone unless you send it yourself.

Stage Watch

Watch model and app version, and whether a phone/account was connected or the watch ran standalone.
Ballistics problems: the “synced” date from the rifle screen, and which rifle + cartridge was picked.

Spotter

Phone model and app version, and whether you were joined to a shooter or counting standalone.
If a delivery went wrong: the match tag, the shooter’s name, and whether you counted plain or green/red per shot.

Witness

Phone model and app version, and the camera setup: built-in camera, or an RTSP camera (which one).
Local hit-caller, or connected to an account.

Bridge

Wind meter model, phone model, app version.

Stage HUD

Phone model and app version, and which camera recorded the footage.
Which run and rifle, and roughly how the sync landed (on the mark, or nudged by hand).

Crashes

Android crashes often reach us automatically through Google Play (if your phone has that reporting on). A mail with the context around the crash still helps enormously — what you did right before matters more than the crash itself.

One privacy note

Don’t send videos or photos where other people are identifiable — crop or blur, or describe instead. Everything you send stays between you and us; see Account and data for how the platform itself treats your data.