Integrity and privacy
Hiring assessments are integrity-aware. This page states what is bound to your ticket, what is recorded during a session, and what is never collected.
Why we record a session
TaoScope needs a fair comparison across candidates for the same role. The extension therefore checks that the ticket is yours, that it is used from one machine, and that the session followed the rules shown before you began. Recorded events are used only for hiring review of that application.
This sits alongside the website Privacy Policy. If the two conflict on a point of collection, the Privacy Policy governs website data; this page describes the VS Code extension.
This computer and your ticket
When the extension starts, it registers a hostname and a machine identifier with TaoScope so the editor can be recognised as a candidate client — not an external script calling the same APIs. While the extension is open it also maintains a presence connection so we can tell that the session is live in VS Code.
Verifying a ticket binds that ticket to this computer:
- One host per ticket — the same ticket cannot be started on a second machine.
- A host may only bind a limited number of tickets, which blocks sharing a computer across many applications.
- Presence must be on for ticket-bound API calls from the extension.
Use the machine you will finish on
Technical Assessment
During a Technical Assessment session the extension records answers, timing, and focus-away events. Leaving the assessment view — another tab, the terminal, another application, or an AI assistant panel — is timestamped. Repeated leaves reduce the score by 3 points each, up to 15 points. Details are on the Technical Assessment page.
Editor lockdown (closing unrelated tabs and panels) applies to this assessment only, and is on by default.
Coding Assessment
You must accept a privacy notice before the timer starts. After that, the extension records coding activity inside the assessment workspace:
| Included | Excluded |
|---|---|
| Source files you create or edit | .env, .env.local, and similar environment files |
| Edit and paste metadata in those files | Private key material (.pem, .key, certificates) |
| Test and build command results | node_modules, .git, build output, coverage, and .assessment internals |
| Focus lost / regained timestamps | Screen capture (disabled unless you later opt in to an explicit setting) |
The submission package is written under .assessment/submission in the workspace and includes a report, a git diff when Git is available, and usually a zip. Reviewers use that package together with the remote branch when a push succeeds.
What we do not collect
- Your VS Code settings, other extensions, or files outside the assessment workspace.
- Passwords, seed phrases, or wallet keys. Never paste those into an assessment.
- Browsing history on other sites.
- A video of your screen, by default.
- A second attempt on a ticket that already has a recorded result.
Troubleshooting
Assessment already started or completed
Each candidate may take an assessment only once. If you stop mid-way or finish, re-entering the same ticket shows your recorded result instead of starting over.
This computer cannot use this ticket
The ticket is already bound to another host, or this host has reached its ticket limit. Continue on the original machine, or contact support@taoscope.com if the original computer is unavailable.
The assessment says it was already completed
That ticket has a stored result. The extension shows it rather than opening a new paper. That is the intended behaviour.
Coding Assessment will not start
Open a trusted folder, accept the privacy notice, and confirm Git is installed if the task clones a repository. The extension cannot start in an untrusted workspace.
Still stuck?
Last updated August 19, 2026