> ## Documentation Index
> Fetch the complete documentation index at: https://help.touchstones.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# What is recorded

> What is recorded when you take an assessment, who can read it, and how to ask for your data.

This is what is recorded when you take an assessment.

* Your submitted work, and when you started and submitted.
* Your conversation with the AI assistant, when it is on for your assessment.
* Activity on the assessment page, with times:
  * leaving or returning to the tab or window
  * the size of anything you paste (not what you pasted)
  * counts of typing and edits
* A record of your device and network (browser type, language, time zone and network address), used to flag when two candidates share a device or network.

The page records this activity from the moment you open the start page.
That is before you press **Start assessment**.
The start page has a notice titled "Before you start: what’s recorded".
That notice shows the same list.

When you create an account, your email address, and your first name if you gave one, are added to Touchstones' contact list.

## Who can read it

* The hiring account that owns the assessment, and its active teammates, can read your submission and the score.
* Among hiring accounts, only the account that owns the assessment can read your full AI conversation and the record of your device and network.
* Its active teammates can see the first 140 characters of each question you asked the AI assistant.
* Under the product's database rules, a hiring account that is not the owner or one of its active teammates cannot read your work.
* Other candidates cannot read your work.

The list above covers accounts in the product.
It does not describe access by Touchstones staff who operate the service.

Other parties process your data too.

* The Touchstones server reads all of it.
* The AI provider receives your messages to the AI assistant, and with each message the code or text of your answer.
* An AI reviewer that uses the AI provider's models also scores your submission.
* A code sandbox service runs your code.
* If the hiring team issues a credential for your result, that credential has a public verification page.
* If the hiring team invites an outside reviewer, that person gets a link with your score and details of how it was scored, such as the points and reasoning for each criterion, the time you submitted, and any comments the hiring team shares there.
  The link shows your name if your account has one.
  The link does not show your submitted work.

## Your data

You can ask for a copy of your data, or for it to be deleted, by writing to [help@touchstones.ai](mailto:help@touchstones.ai).
Scores may be kept in anonymous form.

## The AI models and the code sandbox

The AI assistant and the scoring use OpenAI's models.
Your code runs in a sandbox.
Other pages of this guide call that sandbox the code runner.
The AI provider is set on the server, and that setting can change.

## What the product does not do

* It has no facial recognition.
* It does not try to read emotions.
* It does not use your face or an identity document to check who you are.

## Analytics

The candidate pages do not load Google Analytics or other third-party trackers.
Product analytics is separate.

The site can send product analytics to the analytics service Amplitude.
This happens only if you accepted analytics cookies and the site is set up to use that service.
In that case, the site sends an event at some steps, for example when it loads, when you press **Start assessment**, when you decline and when you submit.
With each event it also sends the page where analytics first started in your browser, any campaign tags in that page's web address, and the other website that linked to that page, if your browser reported it.
If you are signed in, it also sends your account id, and your email address once per sign-in, token refresh or page load, not with each event.

## The details

### Activity on the assessment page

Your browser reports these events, each with a time.

* You left the assessment tab, or returned to it.
* The browser window lost focus, or got focus back.
* You pasted something.
  The length of the paste is recorded, not the text.

When you submit, the page also sends a summary.

* An estimate of the number of characters you typed, the number of characters you pasted, the final length of your answer, and the time you spent.
* In a code assessment, also:
  * the number of key presses, but not which keys
  * the size and time of each paste, and the number of pastes over 120 characters
  * the number of edits for each file name, the number of switches between files, and your active and idle time

The server keeps counts of edits, not a history of your edits.
The results of **Run** are not stored.

### Your work

When you submit, the server stores these things.

* Your final answer, and a hash of it.
* The times when you started and submitted.
* Whether the submission was late, and by how many seconds.
* Which checklist items you ticked.
* Later, on an assessment with test cases: the results of the hidden tests, if they ran on your submitted code.
* Later: the score, if one is stored.

If you decline an assessment and give a reason, the reason is stored.

### The AI conversation

If AI is allowed for your assessment, these things are recorded.

* Each message you send to the AI assistant and each reply, with its time.
* For each suggested edit you review, whether you accepted or rejected it (best effort).

Each message also sends your answer to the AI provider: the code in your editor, or the text of a written answer.
At most 8,000 characters of it are sent.
That copy of your answer is not saved in the conversation.

### Camera and microphone

These events are recorded only if your assessment uses your camera and microphone.
The start page shows a notice about your camera and microphone if your assessment uses them.

* You turned the camera off or back on.
* You muted or unmuted the microphone.
* Access to the camera or microphone was lost.
* One event: "Camera and mic enabled with consent".

The product's code does not send or store video or audio.

### Server logs

The server's request log records the IP address and the headers of each request, including the browser identifier string (user agent).
Only secret headers are removed.

## Questions

Questions or a problem?
Write to [help@touchstones.ai](mailto:help@touchstones.ai).
We answer within one working day.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.