TypeWriter
Request Access Home Teacher Login

Test Security

Stop fighting the internet.

Two levels of lockdown on devices: locked browser, or kiosk on managed Chromebooks. Paper options as well.

A browser can deter a student from cheating and record everything that happens on its own page. It cannot lock down the device, because no web page can. Secure lockdown can happen at the device level through Chromebook kiosk settings. Of course, the strongest security option is no devices at all. TypeWriter works at all three levels, no install required.

Browser

Set per assessment, in any regular browser, with nothing for a school district to configure.

Secure mode + PIN gate

The test opens in forced fullscreen behind a PIN the teacher reads aloud. Until that PIN is entered, the questions never leave our server, so they can't be pulled from the page early.

Leave detection + lockout

Exiting fullscreen, switching tabs, or switching apps blurs the questions instantly and starts a clock the teacher sets, anywhere from 5 to 60 seconds. A student who comes back in time loses nothing. Past it, the test locks until the teacher clears it. Time away is never added up across trips, and the work is always kept.

Copy, paste & right-click blocked

Stops the two easiest shortcuts: copying the prompt out, or pasting a pre-written answer in.

Full activity log

Every test shows a timeline of what happened, when, and how long the student was away. A spotless run is clearly marked clean, so teachers can judge fairly.

Requirements:No configuration. Secure mode is a toggle on each assessment, and it runs in any current browser.

Managed Chromebook

The real lock, on the devices most schools already hand out.

TypeWriter runs as a kiosk web app, so a student can't use the device or the internet for anything else while the test is open. Nothing is installed on the device.

Requirements:One kiosk entry in the Google Admin console, on whichever org units the school picks. Done once. We walk through it on a call.

Paper

The strongest lockdown is no device.

TypeWriter generates scrambled versions of an assessment, each with its own compact answer key, plus optional bubble sheets.

Requirements:None. The teacher prints, and the exam happens away from any device.

What we never ask for

True at all three levels.

  • No roster, no accounts. Nothing gets installed, no accounts to provision, no roster to sync, no SIS integration. Students sign in with a class code their teacher makes up, so there is no name, email, or student record to hand over.
  • No access to the device. No camera, no microphone, no screen recording, no browser extension, and no agent installed. A secured test can tell that our page lost focus. It cannot tell where the student went.

Our student privacy page covers what we store and what we don't. We'll send a completed schedule of data on request.

Last updated: August 2026 · Questions?

Accessibility in kiosk mode

A Chromebook in kiosk mode ignores the accessibility settings a student normally uses. Nothing carries over, so assistive technology has to be switched on for kiosk specifically.

In the Google Admin console, under Devices › Chrome › Settings › Device Settings, an administrator turns on two settings for the org units that will run tests:

Students then use that menu to start a screen reader, magnifier, or dictation, and set those preferences again each time they open a test. Both settings apply to every kiosk app on the devices they cover, not only to TypeWriter.