Privacy Policy

Who Runs LOCK IN

LOCK IN is a freight-loading training simulator operated by F‑Keys Creative LLC ("F‑Keys"), a Florida limited liability company, and made available at www.trailer-load.com. This Policy explains what information the simulator and this website collect, how F‑Keys uses it, and the choices you have. It applies to the LOCK IN simulator, this website, and the instructor dashboard.

What Is Collected

Board initials · only if you sign a board

After a sealed wall or a daily wall you can sign a public board with three initials. F‑Keys keeps the initials, the mode, that wall's score, integrity, pieces and pack, and the date and exact time you signed. Nothing else is kept with them: no account, no device, no name. Pick letters that do not identify you.

Crews · only if you join one

An instructor makes a crew on the dashboard and gives out its join code. When you enter the code, the simulator first shows the crew's name and does not send anything about you. To join, you then either type a name and choose a 4-digit PIN (a "PIN crew"), or type the personal code your instructor handed you (a "manual crew", where the instructor typed your name). For a PIN crew F‑Keys keeps the name you typed and a scrambled (salted PBKDF2-SHA256) copy of the PIN, never the PIN itself. For a manual crew it keeps the name and the personal code the instructor issued. Your device receives a random token that identifies it to the crew; F‑Keys keeps only a scrambled (SHA-256) copy of it.

While a device is on a crew, the simulator sends that crew every wall you seal and every session you finish on it: the mode, score, pieces, wall time, integrity, density, safety incidents, collapses, and for a session its start and end times, length, the app version, a summary of these figures (with shelves locked, recoveries, water breaks, rotations, lifts, rejected drops, staging actions and similar counts), the incidents with the rule broken, and a timed log of your moves (up to 6,000 per session, timed to a tenth of a second). F‑Keys also records when you joined and when you last played. A device that is not on a crew sends none of this.

Instructor accounts · only if you create one

The instructor is the only account in LOCK IN. Creating one on the dashboard takes an email address and a password. The account works once the address is confirmed from an email. The LOCK IN server stores the password only as a scrambled (salted PBKDF2-SHA256) hash, and keeps when the account was made and when it last signed in. F‑Keys keeps each crew the instructor makes (its name, join code, kind, and whether it is licensed) and the names and personal codes the instructor adds.

Device & technical data

The host of the LOCK IN server and database (Cloudflare, which also provides content delivery and security), the website host (GitHub Pages), and the email service that sends instructor account emails (Resend) may process limited technical data such as IP address, browser type, approximate region, and pages requested, as an ordinary part of serving and securing the site, and may keep it in their service logs. Cloudflare also sends Network Error Logging headers, which ask your browser to report failed page loads to Cloudflare. F‑Keys adds no analytics or tracking script of its own. The only counting F‑Keys does is one visit total and a set of anonymous daily totals, both described in Cookies & Analytics.

Your Choices

• Play without a crew. Every mode is free and nothing about your play leaves your device. Your settings, personal bests and daily streak stay in your browser.
• Sign a board, or do not. Signing is a separate choice after each run and sends only the initials and that run's numbers.
• Join a crew. Only with the code an instructor gives you, and only after the simulator shows the crew's name and lists what the crew will receive. The panel is ◆ JOIN A CREW on the menu, or ADMIN > CREW when paused.
• Leave a crew. The same panel has LEAVE THE CREW ON THIS DEVICE. That device stops sending at once and forgets its token. What was already sent stays with the instructor until the instructor removes you or deletes the crew, or you ask F‑Keys to delete it (see Your Rights).

Shared computers. Crew membership belongs to the browser it was joined on. On a shared computer, choose LEAVE THE CREW ON THIS DEVICE when you finish, or the next person's walls go to your crew under your name. Anyone who knows your name and PIN can join your crew as you on another device, so keep the PIN private. Five wrong PINs lock that name for 15 minutes, and your instructor can reset it.

Students & Minors

Under 13. LOCK IN is not directed to children under 13. A child under 13 can play without a crew, which sends nothing personal; a signature on a board keeps only three letters and that run's numbers. A child under 13 should join a crew only one that a school or program set up after giving any notice and obtaining any consent the law requires (in the United States, the Children's Online Privacy Protection Act). If you believe a child under 13 joined a crew without that, contact F‑Keys and that person's crew records will be deleted.

Ages 13-17 (students). Where LOCK IN is used inside a school or CTE program, the school may act as the party that provides notice to, and obtains consent from, students and their parents or guardians under applicable law, including the Family Educational Rights and Privacy Act (FERPA) and state student-data-privacy laws. Where a school uses LOCK IN under a signed agreement with F‑Keys, that agreement can name F‑Keys a school official under FERPA, and it controls how F‑Keys handles that school's student records. F‑Keys uses student data only to run LOCK IN for that school, never for advertising, and does not sell it.

Schools and instructors: if you intend to use LOCK IN with minors, contact F‑Keys first so the appropriate data-protection terms can be put in place. A manual crew lets you choose the names (first names or pseudonyms work), so a student never types one.

How Data Is Used

• To run the simulator and show you your own numbers on your device.
• To show a crew's instructor the walls and sessions its members play, on the dashboard and, for a licensed crew, in a CSV export.
• To show the public boards.
• To understand, in aggregate, how the training is used so F‑Keys can improve it, through the anonymous daily totals described below.
• To keep the service secure and prevent abuse.

F‑Keys does not sell personal information, does not use anyone's data to target advertising, and does not use a crew's results in demonstrations.

Sharing

F‑Keys shares information only in these limited cases:

• On the public boards · if you sign a board, your three initials and that run's score, integrity and date are public. No board shows a name.
• With your crew's instructor · only the crew you joined. The instructor sees the name you joined with, when you joined and last played, and every wall and session your device sent while it was on the crew (see What Is Collected). A manual crew's instructor also sees the personal codes they issued. No instructor sees a PIN. A licensed crew's instructor can export the walls and sessions to a CSV file. An exported file leaves LOCK IN; deleting your data with F‑Keys does not delete their copy.
• With service providers who run the infrastructure: Cloudflare for the LOCK IN server and database and for content delivery and security, GitHub Pages for this website, Resend, the email service that sends instructor account emails (confirming the address, resetting the password, unlocking the account), the payment processor when a facility pays by card, and the email provider for email you send F‑Keys.
• For legal reasons · if required by law, or to protect rights, safety, or the integrity of the service.
• In a business transfer · if the Service or its operator is involved in a merger, acquisition, or asset sale, with notice to you.

Cookies & Analytics

F‑Keys does not use Google Analytics and adds no analytics, advertising or tracking script of its own. There is no advertising and no ad technology of any kind on this site. The simulator sets no cookies. The instructor dashboard sets one, and only after an instructor signs in: the sign-in itself, which the LOCK IN server reads and the page cannot. It lasts 14 days or until sign-out. It uses your browser's local storage and session storage, both on your device. Local storage keeps your settings and controls, your personal bests and daily streak, the last initials you signed with, a few flags (whether you finished the briefing, whether you have played, and whether this browser has opened LOCK IN before), and, while the device is on a crew, the crew's name and code, the name you joined with, and the device's crew token. Session storage keeps a few tab-only flags, such as your level bests for that tab and a mark that this tab was already counted.

The front page keeps one aggregate total, visits: a single integer on the LOCK IN server. Your browser adds 1 to it once per tab session. The simulator also keeps a few daily totals: how many times it was opened, how many first-time and returning visits there were, how many times each mode was started, how many walls were finished, how many daily walls were submitted, how many times the briefing was finished, how many runs were signed on a board, and how many crews were joined. Each is one number per day. Nothing about you is attached to a total: no account, device, cookie, or IP address. Whether a visit counts as new or returning is decided on your own device, which keeps a single "1" in local storage; only which total to add 1 to is sent. As with any request, the database provider's request log records it (see Device & technical data). The totals are private and are used only to see what in the simulator is working.

Data Retention

F‑Keys keeps a crew member's name, walls and sessions until the instructor removes that person or deletes the crew, until the instructor's account is deleted, or until F‑Keys deletes them on a confirmed request. Removing a person or deleting a crew deletes their walls and sessions at once. An instructor account with no sign-in for 24 months is deleted, with its crews and everything saved to them; the one exception is the instructor of a licensed crew while it is licensed. F‑Keys acts on a confirmed request to delete within 30 days. When a school's or program's agreement with F‑Keys ends, F‑Keys deletes the records it covers within 60 days, unless the agreement says otherwise. Signed initials and their numbers are kept; they show on that day's board and can show on the all-time board. Settings, personal bests, your streak and a crew token stay in your browser until you leave the crew or clear your browser.

Earlier versions. LOCK IN 3 had player accounts with usernames. When LOCK IN 4.0 shipped, F‑Keys deleted every player account from earlier versions and everything saved to them: sessions, walls, daily scores, Smalls Sort runs, follows, recovery codes, and the link between a signature and an account. Initials signed on a board stay, with no link to anyone. The first time a browser opens LOCK IN 4.0, it removes the sign-in and device details earlier versions left in its storage.

Security

No table in the LOCK IN database can be reached from a browser. Every read and write goes through the LOCK IN server, which checks who is asking: for an instructor, the signed-in account must own the crew; for a crew member, the device's token must match. Passwords and PINs are kept only as salted PBKDF2-SHA256 hashes, and sign-in, device and email-link tokens only as SHA-256 hashes. Five wrong PINs lock a name for 15 minutes; five wrong passwords lock an instructor account for 15 minutes and email an unlock link. No system is perfectly secure, but F‑Keys works to protect your information and to limit what is collected in the first place. If F‑Keys confirms that saved data was accessed without permission, it will tell each school, program and employer that has an agreement with it and whose players are affected, as soon as it confirms it and within 72 hours, and will post a notice in the simulator.

Your Rights

Depending on where you live, you may have the right to access, correct, export, or delete your personal information, to withdraw consent, and to object to certain processing. To exercise any of these, email F‑Keys (below). A crew member has no account, so include the crew's join code and the name you joined with; F‑Keys confirms the request with the crew's instructor before acting. Your instructor can also remove you from the crew, which deletes your results on it. An instructor writes from the account's email address. F‑Keys acts on a confirmed request within 30 days. You can leave a crew at any time from the crew panel, and you can delete locally stored data by clearing your browser. F‑Keys will not discriminate against you for exercising your rights.

International Users

LOCK IN is operated from the United States, and saved records are stored by Cloudflare in its eastern North America region. If you use it from outside the U.S., you understand your information may be processed in the U.S. and elsewhere in North America. Where required (for example, for users in the EU/UK), F‑Keys processes data on the lawful bases of consent and legitimate interest in providing the service.

Changes to This Policy

F‑Keys may update this Policy as the product evolves. When it makes material changes, it will update the "Last updated" date above and, where appropriate, provide notice in the simulator.

LOCK IN 4.0:

• There are no player accounts. Usernames, profiles, follows, the records boards, recovery codes and the SAVE MY STATS and sharing switches are gone, and every player account from earlier versions was deleted with everything saved to it.
• Every public board takes three initials. Nothing links a signature to anyone.
• A player's results reach a person only through a crew: joined with the instructor's code and then a name and 4-digit PIN, or a personal code the instructor issued. A device that is not on a crew sends nothing about play.
• Instructors are the only accounts, made with an email address on the dashboard and confirmed from an email. An instructor can change the password, reset a lost one by email, and unlock the account by email after five wrong passwords.
• LOCK IN runs on its own server and database, hosted by Cloudflare in its eastern North America region, in place of the earlier database provider. Passwords and PINs are kept as salted PBKDF2-SHA256 hashes. The dashboard sets one sign-in cookie. For an instructor, the time of the last sign-in is kept, and no longer the IP address and browser type of each sign-in.
• Results are no longer used in demonstrations.

October 21, 2026: the policy calls LOCK IN a simulator where it said game. Nothing about what is collected, who sees it, or how long it is kept changed.

October 20, 2026: the policy names F‑Keys Creative LLC ("F‑Keys") where it used to say "we".

October 16 and October 5, 2026: changes for LOCK IN 3 player accounts, all of which 4.0 retired. They are kept in the repository's change log.

Contact

Questions, data requests (access, export, correction, deletion), and plans to use LOCK IN with minors go to:

F‑Keys Creative LLC  ·  a Florida limited liability company
Attn: Vince Gonzalez, Operations President
Email: privacy@trailer-load.com
Web: www.trailer-load.com