Skip to content

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.

Access has separate scopesDiagram
Your result
When available and retained
Shared summary
Summary only
Detailed evidence
Permission and consent

Who can read what, and under which conditions

ViewerInformationCondition
YouOwn result and evidenceAvailable, retained, and permitted; hidden checks stay private
Summary-link holderMission, verdict and piece levelsYou created a link for an eligible published public-mission result; the link remains valid
Company public-link recipientSummary, with separately chosen contact sharingYour deliberate share to an eligible company
Application recipientSelected application information and resultsSubmitted application and the company’s authority
Company round or classDisclosed result sectionsActive consent, role, purpose and result-specific grants
Our team and providersRelevant information for their functionPrivacy notice and applicable authority

A summary link excludes the working record

  1. 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

An application sends a selected snapshot

ItemScopeWhat it does not mean
Application informationChosen profile details and CVThe company can browse the whole account
Selected resultsSelected results and their grantsAll practice history becomes visible
Recipient copiesCopies already receivedWithdrawing erases every copy

Detailed evidence needs result-specific access

  1. Organisation and role

    Current membership and role must allow the read. Owning a customer organisation does not make someone OperatorRank staff.

  2. Consent and purpose

    A round or class discloses its consent scope. Defense needs its own permitted section rather than arriving with every result.

  3. The record must still exist

    Only available, retained sections can be read. A grant cannot recreate missing files or conversations.

For organisations

Example: when more than one grant exists

Example scenario: someone shares a summary link and also submits a job application.

ActionThat grantStill separate
Revoke summary linkThat link stops workingApplication access is separate
Withdraw company shareThat share’s grant endsOther valid grants do not all end
Recipient already kept a copyWithdrawal cannot retrieve the copyYour 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

  1. 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

Read the Privacy notice

Different records have different retention periods

DataDisclosed periodImportant context
Operational logs90 daysA retention schedule, not proof of every cleanup run
Security signals12 calendar monthsSeparate from session lifetime
Submissions for re-checks365 days from submissionSubject 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.

Read the full retention table

Use the sign-in method your account actually has

  1. Google

    Use the Google method linked to your account, without creating another password for that method.

  2. Email and password

    Email signup verifies the mailbox. Passwords require at least 15 characters and reject obvious weak choices.

  3. 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

  1. Inspect signed-in browsers

    Use the security page to identify a browser session you no longer need.

  2. End one or all other sessions

    The other-sessions action keeps your current session. Check the resulting state.

  3. 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

ChangeProofBefore confirming
Password-account emailBoth old and new mailboxesCheck the intended new address
Link GoogleSigned-in account and fresh required proofMatching email alone does not merge accounts
Request deletionEmail code and the displayed typed phraseKeep confirmation codes private

Data-copy and deletion requests have receipts

A received request is separate from completed processing.

  1. Request from your account

    Follow the copy or deletion flow. If you cannot sign in, the notice also provides an email rights-request path.

  2. Keep the ID and follow status

    A request ID confirms we received it—not instant deletion. Account deletion requires the export step first.

  3. 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

  1. Check the permission

    Supported staff operations check current permission for the operation and target; customer membership alone is insufficient.

  2. 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.

  3. Question a result

    Report from the result page before its deadline. See How we measure for review rules and correction history.

How we measure

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.