Documentation
On this page
Everything you make in LoadOut is a record in a database on your device. The records are small, plain, and related in the way a reloader thinks: components go into a recipe, a recipe and a firearm make a profile, a profile makes a solution, and a solution goes to the range and to your wrist.
Two kinds of data
| Kind | Examples | Who writes it | Where it goes |
|---|---|---|---|
| Reference catalogs | Cartridges, powders, bullets, primers, brass, firearms, scopes, reticles, targets, equipment | Ships in the app; updates in place without a store release | Never in your export or your cloud copy; it is the same for everyone |
| Your data | Recipes, firearms, batches, brass lots, profiles, sessions, notes, and your own catalog entries | You | The JSON export, the encrypted cloud copy, and nowhere else |
A catalog row and a record of yours never blur: when you type a component the catalog does not have, LoadOut saves it as your own entry, listed under Settings › My Entries, and a later catalog update never overwrites it.
Your records
| Record | What it holds | Relates to |
|---|---|---|
| Recipe | Cartridge, powder and charge, bullet, primer, brass, overall length as COAL or CBTO, seating and case-prep measurements, date established, notes, custom fields, a photo | The batches loaded from it; the profiles built on it; the equipment used to make it |
| Firearm | Name, make and model or a custom build's components, action, chambering, barrel length and twist, scope height, optic and reticle, round count, barrel-life target, a photo | Its barrels; the profiles and sessions that use it; a catalog firearm it was picked from |
| Batch | A loading run: the recipe, the count loaded, the process checklist with each step ticked, rounds fired, and notes | Its recipe; the inventory it drew from |
| Brass lot | Headstamp, cartridge, count, firings, anneal history, trim and neck measurements, prep flags | The batches loaded on it |
| Component inventory | On-hand counts of powder, primers, bullets, brass, and factory ammunition, with a lot number, reorder threshold, and an adjustment log | Its adjustment entries, each with a reason and a date |
| Equipment | Presses, dies, scales, and tools, picked from the catalog or typed | The recipes they were used on |
| Ballistic profile | A firearm and a load bound together with the muzzle velocity, coefficient and drag model, zero, sight height, twist, and any truing | Its firearm and recipe; the target cards, sessions, and watch documents solved from it |
| Atmosphere preset | A saved set of conditions, with the coordinates it was captured at if you pulled weather | Any solve you apply it to |
| Target card | A string of targets: distance, name, plan mode, per-target wind, mover, and spoken callout | Its profile; the watch it is sent to |
| Range Day session | Load, firearm, target, distance, conditions and coordinates, every shot impact and shot event, the timer starts, and the notes | Its profile and firearm; its group analyses |
| Group analysis | A photographed target's impacts with the measured spread, mean radius, CEP, and point of impact | The session it came from |
| Load development session | The method, the ladder, every shot with its velocity and group, per-charge summaries, and pressure-sign flags | Its recipe and firearm; the recipe a charge was adopted into |
| Match log | A match with its discipline, stages, per-stage scores and strings, match settings, and stage plans | The profile a stage plan was solved from |
| Note | Folders, notes built from text, checklist, table, reference and divider blocks, tags, and links to other records | Any record a note references |
| Custom field and layout | Your extra fields per record type, their values, and your saved form layouts | The records they extend |
| Preferences you author | Mover presets, your own Siri words, favourites, shooter capability | The screens that read them |
The Sample flag
The Sample rifle, recipe, profile, and target card carry a flag that draws the Sample badge and keeps them out of the free-tier count. Saving an edit through the relevant form clears the flag: the record becomes yours, badge gone. The Sample profile's solution is never stored; it is computed live from the sample's inputs and the disclosed standard atmosphere, so nothing about it is ever presented as a fact about your rifle.
Identifiers
Records are numbered per device; the numbers are not global and carry no meaning beyond linking records together. Cloud Sync matches records across your devices by identity, not by number, and resolves a record edited in two places by the latest write. Crash reports may carry these numbers; they never carry a record's contents.
Deletion and Recently Deleted
What the export contains
The JSON export writes every record type above, parents before children, in one file. It leaves out the reference catalogs, records waiting in Recently Deleted, the on-device search index, and photos. Cloud Backup and Cloud Sync carry the same set, encrypted, plus the deletions that let devices converge.
Where it is stored
On iPhone, iPad, and Android the database sits inside the app's own storage and is excluded from the platform's own cloud backup on purpose, because that backup is not encrypted with your passphrase; on the Mac it sits inside the app's own storage too, but the Mac app carries no such exclusion, so a Time Machine backup includes it. In the web app the database lives in the browser's storage for that computer. Reference catalogs are files that ship with the app and update in place. Nothing about your records is ever written to a LoadOut server.