Which simulators are supported?
Generic CSV is the safest path today. Several simulator-specific exports are in beta, and compatibility is expanding as real files are validated.
FAQ
DivotData is focused on the core loop: upload a simulator session, get one card, practice the block, and retest.
Generic CSV is the safest path today. Several simulator-specific exports are in beta, and compatibility is expanding as real files are validated.
Uploads currently save to a signed-in notebook. Facility guest-card workflows are planned so guests can receive a no-login card and claim it later.
Yes. A shot-level CSV, TSV, XLSX file, JSON file, or pasted table can work if it includes clear headers and measured shot rows.
No. DivotData is designed to make between-lesson practice clearer. Coaches can review, edit, approve, and assign cards.
Not by itself. It can detect ball-flight and delivery patterns, but exact mechanics need coach review, strike data, or other context.
Single-player sessions usually work. Facility or group sessions may need manual assignment before reliable guest cards can be generated.
The planned workflow lets staff create a bay session, upload once, generate guest cards, and let golfers claim cards later.
Each Divot Card includes a matched retest protocol, such as 20 stock shots to the same target, plus pass/fail criteria.
During beta, DivotData stores account data, uploaded simulator files or backups, parsed shot summaries, notes, and generated practice insights.
Yes. You can remove uploaded files and simulator history in the app. For account-level deletion requests, contact support@getdivotdata.com.
Try a smaller or cleaner shot-level export, confirm the file type, or contact support with the simulator source and upload issue.
The current beta starts with a free first Divot Card. Founder and pilot pricing may be offered while the parser, card quality, and retest loop are being validated.
A Divot Card is one focused practice assignment from a simulator session. It states what changed, why it matters, what to practice, and how to retest it.
Confidence describes how strongly the available data supports the pattern and likely focus. Ball-flight confidence can be high while exact mechanical-cause confidence stays low.
Data quality scores the usefulness of the upload: club labels, carry or total distance, offline data, launch, spin, delivery metrics, shot order, sample size, and baseline/retest match quality.
Yes. Send the source, file type, and a sample export through contact/support. Real files are how compatibility moves from planned to beta to live.
Still stuck?