What we send, what we keep.

Course Inventory Triage, Asset Sync Checker, Course Inspector, SCORM Flight Recorder, Session Timer, Group Maker, QR Activity Launcher do all of their work in your browser tab. Files you drop in are read with the browser's own file APIs; the parsing, diffing, scoring, zip reading and QR drawing all happen on your machine. No request is made to our server with that content, so we never see it and nothing is stored on our side.

Some of these tools remember your working state in your browser's localStorage (for example a timer agenda, a group roster or a QR set) so it is still there when you come back. That data stays in your browser and is cleared when you clear your site data.

When you press the run button on an AI tool, the text you pasted plus the options you picked are sent to our server at /api/ai. Our server adds the tool's instructions and forwards the whole thing to Anthropic's Claude API, which returns the structured result you see on screen. That round trip is the only place your content leaves your browser, and it only happens when you press the button.

We do not write your input or the model's output to our database as part of a run. Anthropic processes the request under their API terms; we do not use your content for training and we do not share it with anyone else.

Every AI run writes one usage row so the free limits can be enforced. That row holds the tool's name, the current month, a timestamp, and the number of input and output tokens the request used. It does not contain your quiz, your script or any other content.

The row is attached to your account id if you are signed in, and to an anonymous visitor id if you are not. Signed-in usage is counted per month (40 runs on a free account); anonymous usage is counted for the lifetime of the cookie (3 runs). Your account page shows the same numbers back to you.

A result is only stored when you press Save on it, and only if you are signed in. Saving keeps a title, the input you ran and the output you got, under your account, so you can reopen it from the Saved menu on the tool or from your account page.

You can delete any saved result from either of those lists and it is removed from the database immediately. There is no self-serve button to delete an entire account and everything attached to it yet: email us at hello@ldtoolkit.com and we will do it by hand.

An anonymous id. The first time you run an AI tool without signing in, we set a cookie holding a random id. It exists to count your free runs, lasts a year, and is not readable by scripts on the page.

A session cookie. When you sign in, we set a signed session cookie that says which account you are. It lasts 90 days, is not readable by scripts, and is deleted when you sign out.

That is the whole list. There are no advertising or tracking cookies.

Signing in works by email: you type your address, we create a one-time token that expires after an hour, and we email you a link. Only a hash of that token is stored, so the link in your inbox is the only copy. The email itself is delivered by Resend, which handles the sending on our behalf.

An account stores your email address, your plan and when you created it. If you join the Pro waitlist we store the email you gave and which page you gave it on, and we use it only to tell you when Pro is ready.

We use Vercel Analytics to count page views so we know which tools people actually open. It does not set cookies and does not follow you across sites. There is no other analytics or session-recording script on the site.

If something here is unclear, or you want your data removed, write to hello@ldtoolkit.com. If this page ever stops matching what the code does, that is a bug and we want to hear about it.