AITeaching privacy policy

Who uses AITeaching

Only our own staff and invited testers who have accepted the AITeaching recording agreement. A person accepts it by downloading and installing the desktop app: the app shows no agreement window and asks nothing when it starts. A new version of the agreement is accepted the same way, by installing the version of the app that carries it. Nothing is recorded on a computer where AITeaching is not installed.

Once installed, AITeaching records around the clock: it starts by itself every time the person signs in and keeps running in the background until it is paused, quit or removed. The extension is listed privately (Unlisted on the Chrome Web Store) and does nothing without the desktop app.

What the browser extension records

On the web pages a person works in, the extension notes:

• the full address of each page, including everything after the "?";
• the page title;
• the fields, buttons and labels on the page, which one the person used, and the value typed into an ordinary field;
• how the page changed while the person worked;
• which browser tab and window was in use.

It never reads the value of a password field, a card number, a card security code, a one-time code, or a hidden or file field: those are masked before any value is read. It does not filter out personal websites. The extension sends nothing over the internet and saves nothing itself: it hands what it notes to the AITeaching desktop app on the same computer.

What the desktop app records

The desktop app records what the recording agreement lists:

• screenshots of the display that holds the window in use, taken when something happens (switching app or window, a click, scrolling stops, typing pauses) and about every 5 seconds otherwise. We can instead set a computer to take them at a steady rate of up to 5 per second; we set that rate remotely, without asking again, and never above 5 per second. Identical pictures are skipped;
• the position and size of the window in front, so a screenshot can be cropped to it;
• every keystroke, with the modifier keys held and the resulting text. A key typed into a password field is masked on the computer before it is saved: only the fact that a key was pressed is kept;
• mouse clicks (position and button) and scrolling;
• the names of the apps used and the titles of their windows;
• the structure and visible text of the focused window (its buttons, fields, menus and labels), leaving out password fields;
• what the browser extension hands it;
• the computer's time zone, each time recording starts;
• the person's name, if one was typed in an earlier Setup of the computer. The team can change it;
• a label with the lesson's name, when Teach is started for the person in Sam, our portal. The computer shows a notice when this happens. Teach only adds a label: AITeaching records all the time either way.

The agreement also covers two things that switch on only when a version of the app that records them is installed: continuous screen video, saved in half-hour files, and the buttons, boxes and menu items used in desktop programs outside the browser, with the values typed into them (never the value of a password box).

No audio is recorded. Personal apps and websites are not filtered out: everything on the recorded display is captured. The recording agreement is the full and binding list.

Each computer also sends us a regular status report so the team can see that it is working: for example, whether AITeaching is paused, the person's name if one was typed, and the name, size and fingerprint of any file it could not upload.

Live watching

The recording agreement also lets the team watch a computer's screen live while AITeaching runs, in our team-only viewer. Watching saves nothing beyond the normal recording, and the AITeaching icon shows when someone is watching. The live picture travels encrypted, either straight to the viewer or through relay servers of Amazon Web Services.

Where the recording goes

1. On the computer. Recordings are first saved in a local folder on the recorded computer.
2. To our cloud storage. As each file is finished, the desktop app uploads it to a storage bucket we control in Amazon Web Services (AWS), in the United States. It travels encrypted and is stored encrypted. The local copy is removed only after the upload is confirmed. Status reports go to the same place. A daily backup copy is kept in a separate, encrypted backup store in the same AWS account.
3. Processing. A processing service that we run in our own AWS account copies the recordings to its own disk and turns them into step-by-step drafts and playbooks.
4. AI. For recordings made under version 0.5 of the recording agreement or later, the recordings, screenshots and page contents included, are read by an AI model, Claude Sonnet, made by Anthropic, through Amazon Bedrock under our own AWS account, processed in AWS data centres in the United States, to find and describe the steps of each task. What it writes follows the same rules as everything else we keep.
5. Our viewer. The team looks at recordings, and at each computer's status and name, in a web viewer that we run in our own AWS account and that only our team can open.
6. Drafts and playbooks. The resulting drafts and playbooks are stored in our company account on Box, together with a small file for each computer that holds its ID and the person's name, if one was typed.

We do not sell recordings or anything made from them, and we do not share them with anyone outside our company except the service providers named above (AWS, including Amazon Bedrock, and Box), which hold or process them for us. Recordings are used only to build and review work playbooks.

How long it is kept

• On the computer: until the file is uploaded and the upload is confirmed. Anything not yet uploaded when AITeaching is removed stays on the computer until someone deletes it.
• Working copies on the processing service: deleted automatically, within about a week.
• Screen video in cloud storage: deleted 180 days after upload.
• Other recording files and status reports in cloud storage: until deleted. Today no automatic deletion is set for them. The recording agreement also allows us to keep recordings older than about 30 days in a separate, encrypted archive instead, until we delete them or the engagement ends.
• Backup copies: each daily backup is kept 35 days, so a deleted file can remain in a backup for up to 35 days.
• Drafts, playbooks and the per-computer files in Box: until deleted. Nothing deletes them automatically, and the team deletes them when they are no longer needed.

Who can see it

Only the internal team at Fidorn, Inc. that builds and reviews playbooks, and the systems described above.

How to stop

• For a while, on Windows: right-click the AITeaching icon near the clock. "Pause" stops recording until you choose "Resume", or for 60 minutes. "Quit AITeaching" stops recording at once, until the next time you sign in.
• For good: remove AITeaching. Recording stops and AITeaching no longer starts when you sign in.
  • Windows: Settings, Apps, AITeaching, Uninstall.
  • Mac: in Terminal, run the removal line from the AITeaching Mac install guide, bash ~/Downloads/install-aiteaching.sh --uninstall.
  Remove the extension in the browser as well (Chrome: chrome://extensions; Edge: edge://extensions).
• Removing AITeaching does not delete what was already recorded, whether it was uploaded or is still waiting on the computer. To ask for your recordings to be deleted, or for any question about this policy, contact bao@fidorn.com.

Changes to this policy

If we change what is recorded or where it goes, we update this page and the recording agreement. The new terms apply once you install the version of the desktop app that carries them: installing it accepts them.