Privacy Policy
Last updated: September 2026
The short version
- You can browse the public directory without an account.
- Accounts are optional and exist for ASVAB purchases and synced study progress.
- We collect data you submit, account and purchase records, study progress, usage analytics, and operational logs.
- We do not sell personal data or run ads.
What we collect
Account and sign-in
If you request a sign-in link or buy Complete ASVAB Prep, we store your email address, a generated account identifier, verification status, paid-access status, and account timestamps. Sessions include a token, expiration time, IP address, and browser user agent. Sign-in uses emailed magic links, so we do not ask you to create a password. If checkout creates your account, a basic display name is derived from the part of your email address before the @ sign.
If you request a sign-in link or buy Complete ASVAB Prep, we store your email address, a generated account identifier, verification status, paid-access status, and account timestamps. Sessions include a token, expiration time, IP address, and browser user agent. Sign-in uses emailed magic links, so we do not ask you to create a password. If checkout creates your account, a basic display name is derived from the part of your email address before the @ sign.
Purchase records
Checkout takes place with our payment processor, which collects the payment details needed to complete the charge. It sends us the checkout email, amount, payment status, and checkout session identifier. We store the email, paid-access date, and checkout session identifier, and we send an internal sale notification. We do not receive or store your full card number or security code.
Checkout takes place with our payment processor, which collects the payment details needed to complete the charge. It sends us the checkout email, amount, payment status, and checkout session identifier. We store the email, paid-access date, and checkout session identifier, and we send an internal sale notification. We do not receive or store your full card number or security code.
ASVAB study activity
Your browser stores your last practice test result, selected target, seen question identifiers, topic-level correct and total counts, and review-card timing. For a signed-in paid account, subject practice progress is also copied to the site database so it can be used on another device.
Your browser stores your last practice test result, selected target, seen question identifiers, topic-level correct and total counts, and review-card timing. For a signed-in paid account, subject practice progress is also copied to the site database so it can be used on another device.
Contact form
Your name, email address, and message, exactly as you type them. We use them to read your message and to reply. They are delivered to us as an email and a notification. They are not stored in the site database.
Your name, email address, and message, exactly as you type them. We use them to read your message and to reply. They are delivered to us as an email and a notification. They are not stored in the site database.
Specialty requests
When a search finds nothing, you can ask us to add that code. We store the search text, branch filter, request time, and whether the request has been handled. The IP address used for rate limiting is kept in memory and is not stored with the request.
When a search finds nothing, you can ask us to add that code. We store the search text, branch filter, request time, and whether the request has been handled. The IP address used for rate limiting is kept in memory and is not stored with the request.
Analytics and operations
We collect basic usage analytics and operational logs, which may include page views, your IP address, browser and device information, approximate region, requested URLs, timestamps, and interaction events. Some events include search terms or summary ASVAB activity such as subject, topic, difficulty, correct-or-incorrect result, session score, or estimated AFQT. We use this information for security, rate limiting, debugging, and understanding site usage. Analytics runs through a first-party path on mos.directory. Outgoing requests from this site use only the site origin, https://mos.directory/, as their referrer, so a referrer never includes the page path.
We collect basic usage analytics and operational logs, which may include page views, your IP address, browser and device information, approximate region, requested URLs, timestamps, and interaction events. Some events include search terms or summary ASVAB activity such as subject, topic, difficulty, correct-or-incorrect result, session score, or estimated AFQT. We use this information for security, rate limiting, debugging, and understanding site usage. Analytics runs through a first-party path on mos.directory. Outgoing requests from this site use only the site origin, https://mos.directory/, as their referrer, so a referrer never includes the page path.
DD Form 214 reference pages
On the DD Form 214 pages, analytics is limited to one pageview per page load that records only the general section you visited, such as the decoder, the review checklist, the records guide, or the SPD, RE, or authority browse sections. The exact SPD code, RE entry, or authority citation you open, the form values you decode, review marks, filter text, and print actions never reach analytics, and session replay is switched off. It stays off when you navigate elsewhere without reloading. A fresh page load outside the DD Form 214 section can enable replay again. When a DD Form 214 page is remembered as the entry point or referrer of a later event, it is reduced to the same general section before collection. Opening an exact public reference is your choice: its public path and any fragment appear in your address bar and browser history. Only the destination path is sent in HTTP requests and may appear in logs. The network service in front of this site also runs a separate web analytics product, and keeping that product off every DD Form 214 route is a required release step for these pages. This policy does not claim that exclusion is already in effect.
On the DD Form 214 pages, analytics is limited to one pageview per page load that records only the general section you visited, such as the decoder, the review checklist, the records guide, or the SPD, RE, or authority browse sections. The exact SPD code, RE entry, or authority citation you open, the form values you decode, review marks, filter text, and print actions never reach analytics, and session replay is switched off. It stays off when you navigate elsewhere without reloading. A fresh page load outside the DD Form 214 section can enable replay again. When a DD Form 214 page is remembered as the entry point or referrer of a later event, it is reduced to the same general section before collection. Opening an exact public reference is your choice: its public path and any fragment appear in your address bar and browser history. Only the destination path is sent in HTTP requests and may appear in logs. The network service in front of this site also runs a separate web analytics product, and keeping that product off every DD Form 214 route is a required release step for these pages. This policy does not claim that exclusion is already in effect.
What we do not collect
- No account passwords. Sign-in uses emailed magic links.
- No full payment card number or card security code.
- No service records, DoD ID numbers, or Social Security numbers. The specialty data on this site is public reference material about job codes, not information about you.
- No DD Form 214 worksheet or review activity in analytics. Entered form values, decoded results, the exact references you open, filter text, checked review items, and print actions are excluded from our analytics.
- No precise location. Our analytics and network services may infer a country or region from your IP address.
- No advertising profile, and no personal data sold or rented.
Cookies and local storage
Sign-in cookie
Signed-in accounts use a required first-party session cookie. It lets the server recognize your session and is sent with requests to mos.directory.
Signed-in accounts use a required first-party session cookie. It lets the server recognize your session and is sent with requests to mos.directory.
Analytics cookie
Analytics uses a first-party cookie with a random browser identifier so repeat visits can be counted together.
Analytics uses a first-party cookie with a random browser identifier so repeat visits can be counted together.
Study progress
Practice test results and practice progress are saved in your browser's local storage. Paid accounts also copy subject progress to the server after completed activity. First-party cookies remember your study target and a summary of your recent practice state so these pages can show them immediately.
Practice test results and practice progress are saved in your browser's local storage. Paid accounts also copy subject progress to the server after completed activity. First-party cookies remember your study target and a summary of your recent practice state so these pages can show them immediately.
Theme preference
Your light or dark mode choice is saved in your browser's local storage and stays on your device.
Your light or dark mode choice is saved in your browser's local storage and stays on your device.
Network cookies
The network service in front of this site may set cookies to distinguish real traffic from automated attacks.
The network service in front of this site may set cookies to distinguish real traffic from automated attacks.
We set no advertising cookies and no cross-site tracking cookies.
Changes to this policy
If this policy changes, the date at the top of the page changes with it. Material changes will be described here rather than made quietly.
Questions
Ask us through the contact page. See also the terms of use.