Transparency Report

This report covers demands and reports received by {{LEGAL_ENTITY}} in respect of the Cadets service. It counts requests for user data made by government bodies and law enforcement, formal preservation demands, safeguarding concerns reported to us through our own channels, and accounts removed from the platform.

It does not cover ordinary support correspondence, routine requests from schools acting as the controller of their own education records, or the data rights requests described on our Data Rights & Removal page — those are counted separately and are not compelled disclosures. Requests we are legally prohibited from disclosing are excluded from the counts and, where the law allows us to say so, that exclusion is noted.

We publish semi-annually. Reporting periods run 1 January to 30 June and 1 July to 31 December, and each report is published within 60 days of the period closing. Figures are reported for the period in which the request was received, not the period in which it was resolved; requests still open at the period end are counted as received and marked as pending in the outcome columns.

Once published, historical periods are not silently revised. If a figure turns out to be wrong we correct it and add a dated correction note beneath the affected table.

Our standard is straightforward: we do not disclose user information to government or law enforcement unless we are legally required to, and we make them do the work of requiring it properly.

We require valid legal process

Informal requests, verbal requests, and requests unaccompanied by valid legal process are declined. We require a subpoena, court order, search warrant, or other lawful process appropriate to the category of data sought, issued by a body with jurisdiction over us. Where the applicable standard for the data sought is a warrant, a subpoena will not do.

We notify affected schools and users

Where a request concerns a Cadet or instructor, we notify the school and, where appropriate, the affected individual, before disclosing — and with enough time for them to seek to challenge the request. We withhold notice only where a court order, statute, or a specific and credible risk of harm to a child prohibits or counsels against it, and where notice is delayed rather than prohibited outright, we give it as soon as the restriction lifts.

We narrow overbroad requests

Requests that sweep in more than they need — a whole unit’s records when one Cadet is at issue, or an open-ended date range — are pushed back on. We ask the requesting body to narrow the scope, and if it will not, we consider objecting or moving to quash. We produce the minimum set of records responsive to a properly scoped request, and we do not volunteer adjacent information because it happened to be in the same query.

Emergency requests

We will disclose information without legal process where we believe in good faith that there is an emergency involving a risk of death or serious physical injury to a person, and that disclosure without delay is necessary to prevent it. Given our user base, that usually means a threat to a student. Emergency disclosures are reviewed after the fact and counted in this report.

What we cannot produce

We do not hold payment card numbers — Stripe does — and requests for card data are redirected to Stripe. Requests for a school’s education records are redirected to the school, which controls them; we notify the school when such a request reaches us.

Requests for user data received from courts, law-enforcement agencies, and other government bodies during the reporting period.

Notice given

A preservation request asks us to retain a copy of specified records pending legal process. Preservation is not disclosure: we set the records aside and nothing is handed over unless valid process follows. Preservations lapse if no process arrives within the statutory window and are not renewed automatically.

Concerns reported to safeguarding@allcadets.com or through in-product reporting. These figures cover reports made to Cadets; they are not a measure of incidents occurring within JROTC and ROTC programs generally, most of which are reported to and handled by schools directly and never reach us.

A single report may appear in more than one outcome column — referring a concern to the school and suspending an account are not alternatives. Reports are counted once in the “received” column regardless of how many outcomes follow.

Accounts removed from the platform, by reason. Removals at the request of a Cadet, parent, or school are ordinary lifecycle events and are reported here for completeness rather than as enforcement.

• Counts are of discrete requests or reports, not of individual records produced. One subpoena naming four Cadets is one request affecting four users.
• Duplicate requests for the same records from the same body are counted once.
• “Complied in part” means we produced some responsive records and withheld others, whether on scope, privilege, or because the records were the school’s to release.
• Requests directed to our service providers rather than to us — for example, a demand served on Stripe for payment data — are outside our visibility and are not counted here.
• Requests we are legally barred from acknowledging are excluded, and their exclusion is not itself disclosed where doing so would breach the same prohibition.

Questions about this report may be sent to privacy@allcadets.com. Legal process should be directed to {{LEGAL_ENTITY}} at {{POSTAL_ADDRESS}}; service by email to that address is not accepted as valid service. Vulnerability reports belong at security@allcadets.com, and general enquiries at support@allcadets.com. This report is prepared under the law of United States.

Cadets is an independent product and is not affiliated with, endorsed by, or sponsored by the U.S. Department of Defense or any branch of the U.S. Armed Forces.