Who sees what
Understand the scope before sharing
Sharing a result does not open your account
Practice results are not public. Each sharing path opens a specific scope. Our team and service providers process information under the Privacy notice.
- Your result
- When available and retained
- Shared summary
- Summary only
- Detailed evidence
- Permission and consent
Who can read what, and under which conditions
| Viewer | Information | Condition |
|---|---|---|
| You | Own result and evidence | Available, retained, and permitted; hidden checks stay private |
| Summary-link holder | Mission, verdict and piece levels | You created a link for an eligible published public-mission result; the link remains valid |
| Company public-link recipient | Summary, with separately chosen contact sharing | Your deliberate share to an eligible company |
| Application recipient | Selected application information and results | Submitted application and the company’s authority |
| Company round or class | Disclosed result sections | Active consent, role, purpose and result-specific grants |
| Our team and providers | Relevant information for their function | Privacy notice and applicable authority |
A summary link excludes the working record
A bearer link works until expiry or revocation
For eligible public-mission results, you can create a summary link valid for 30 days unless revoked sooner. Anyone with the link can view the summary while it's active. It excludes BUILD, files, timeline, Defense, and hidden-check counts—share it only with people you intend.
Summary-link scopeDiagram - Mission and verdict
- Included
- Piece levels
- Included
- Files, timeline, Defense
- Excluded
Opening a company link and sharing are separate steps
-
A visit does not share a result
On the company public-mission path, a visit does not send the company your result. Sharing requires a deliberate choice.
-
Contact sharing has its own choice
In this sharing flow, name and verified email are included only with the separate contact choice.
-
Private missions stay outside public sharing
A private company mission cannot become public through the public-result-link writer.
An application sends a selected snapshot
| Item | Scope | What it does not mean |
|---|---|---|
| Application information | Chosen profile details and CV | The company can browse the whole account |
| Selected results | Selected results and their grants | All practice history becomes visible |
| Recipient copies | Copies already received | Withdrawing erases every copy |
Detailed evidence needs result-specific access
-
Organisation and role
Current membership and role must allow the read. Owning a customer organisation does not make someone OperatorRank staff.
-
Consent and purpose
A round or class discloses its consent scope. Defense needs its own permitted section rather than arriving with every result.
-
The record must still exist
Only available, retained sections can be read. A grant cannot recreate missing files or conversations.
Example: when more than one grant exists
Example scenario: someone shares a summary link and also submits a job application.
| Action | That grant | Still separate |
|---|---|---|
| Revoke summary link | That link stops working | Application access is separate |
| Withdraw company share | That share’s grant ends | Other valid grants do not all end |
| Recipient already kept a copy | Withdrawal cannot retrieve the copy | Your original follows its own retention policy |
Withdrawing, leaving a group and deleting an account are different actions. Read each action’s consequence.
Practice, learning and hiring have separate purposes
Keep practice private
Having a practice result does not automatically make it available to recruiters. Sharing and applications have their own grants.
Read the class disclosure
Check which sections teachers can read for issued class work. Learning consent is not automatically hiring access.
Inspect your groups
The groups view lists what you agreed a company or school could see. Read it before leaving or withdrawing a grant.
Know what is processed and by whom
Work records and security data
We process AI prompts and replies, files, commands, timestamps, grading, and Defense (when enabled) to run missions and troubleshoot issues. Account and security data include IP, browser, device details, and a device ID. Core servers are in Lille, France, with some providers processing elsewhere. AI context goes to AI providers under the disclosed terms, so keep unnecessary secrets out of it.
Read the notice by data typeDiagram - Work and results
- Run and evaluate missions
- Account and security
- Account access and abuse controls
- Providers
- Roles and countries in the notice
Different records have different retention periods
| Data | Disclosed period | Important context |
|---|---|---|
| Operational logs | 90 days | A retention schedule, not proof of every cleanup run |
| Security signals | 12 calendar months | Separate from session lifetime |
| Submissions for re-checks | 365 days from submission | Subject to the notice’s exceptions and holds |
Section 5 of the Privacy notice covers the full schedule, conversations, backups and exceptions. Recipient copies have their own boundaries.
Use the sign-in method your account actually has
-
Google
Use the Google method linked to your account, without creating another password for that method.
-
Email and password
Email signup verifies the mailbox. Passwords require at least 15 characters and reject obvious weak choices.
-
Recover the matching credential
Password reset changes an OperatorRank password, not a Google password. Repeated wrong guesses temporarily pause password sign-in.
Inspect and end other signed-in sessions
-
Inspect signed-in browsers
Use the security page to identify a browser session you no longer need.
-
End one or all other sessions
The other-sessions action keeps your current session. Check the resulting state.
-
Know the lifetime
Sessions expire after 30 idle days and at most 90 days overall, unless revoked earlier. A new sign-in request does not establish lost work.
Important account changes need fresh proof
| Change | Proof | Before confirming |
|---|---|---|
| Password-account email | Both old and new mailboxes | Check the intended new address |
| Link Google | Signed-in account and fresh required proof | Matching email alone does not merge accounts |
| Request deletion | Email code and the displayed typed phrase | Keep confirmation codes private |
Data-copy and deletion requests have receipts
A received request is separate from completed processing.
-
Request from your account
Follow the copy or deletion flow. If you cannot sign in, the notice also provides an email rights-request path.
-
Keep the ID and follow status
A request ID confirms we received it—not instant deletion. Account deletion requires the export step first.
-
Read the remaining scope
Some records may remain with identity fields removed. Holds and external copies follow the notice’s limits.
Staff access has permissions and records too
-
Check the permission
Supported staff operations check current permission for the operation and target; customer membership alone is insufficient.
-
Important changes have approval rules
Operations on the approval path record proposal, reason, approval and outcome. The required approvers depend on policy and owner exceptions.
-
Question a result
Report from the result page before its deadline. See How we measure for review rules and correction history.
A few more questions
Does no camera mean no data collection?
No. The workspace denies camera, microphone and screen capture, while work, account and security records remain as disclosed.
Do credits buy access to everything?
No. Credits or a plan name do not replace result-specific consent, role, purpose, permitted sections and retained evidence.
Does reporting a result issue correct my account too?
They are separate requests. Use the affected result for an assessment issue and account controls or the Privacy notice’s channel for personal-data rights.
Share with a clear scope
Read the scope of the sharing path before confirming. The Privacy notice and support channel cover further questions.