Privacy at Scoreboad.

How Scoreboad handles the information used to run the hiring platform — what enters the system, what the software does with it, and what it does not do yet.

Last updated: Unfinished: EFFECTIVE DATE — COMPLETE BEFORE PRODUCTION

On this page

This document describes how the software works today. It has not been reviewed by a lawyer, and the sections marked in capitals are unfinished. It is published so the behaviour is inspectable — not as a legal agreement.

Overview

Scoreboad is recruitment software. Organisations use it to post jobs, receive applications, screen candidates, run interviews and record hiring decisions. Most of the personal information in the system is about candidates, and it is put there by the organisation hiring them or submitted by the candidate through an application link.

Scoreboad's legal relationship to that information — who is the controller and who is the processor — is not settled, and this document does not assert it. Unfinished: DATA PROTECTION ROLES — CONFIRM WITH COUNSEL

Information in the platform

Every category below corresponds to a specific place in the system. This is the complete inventory, not a summary of it.

CategoryWhat it is
Account informationThe name, email and organisation of the people who sign in.
Candidate identityA candidate's name, email and phone number.
CV filesUploaded resumes, held in private storage.
Parsed CV contentThe structured fields a model extracted from a resume.
Application answersResponses to the questions on a job's application form.
Salary and notice periodWhere a candidate supplied them or a screening call captured them.
Voice recordingsAudio of an automated screening call, where consent was given and the organisation permits recording.
Call transcriptsThe text of a screening call.
EvaluationsMatch scores, screening reports and interview feedback.
Identity documentsFiles a new hire uploads during onboarding, in private storage.
Message contentThe body of messages sent to a candidate.
Code submissionsAnswers to a coding exercise, where one was used.
Activity logA record of who changed what, and when.

Raw IP addresses are deliberately not stored. Where an address is needed to rate-limit a public form, only a keyed hash of it is kept, which cannot be read back into the original address.

How AI is used

AI features read information already in the system and return a structured result. Each one is a named function with a defined input and a validated output — there is no open-ended assistant, the model holds no database connection and no tools, and it cannot look anything up on its own.

  • Resume text is parsed into structured fields, proposed for a person to confirm rather than written straight onto the record.
  • A resume is scored against a role's requirements, with the reasoning shown beside the score.
  • A screening call is summarised into a report, with fields the model was unsure about flagged for checking first.
  • Messages, briefs and summaries are drafted for a person to edit before anything is sent.

Where a person corrects an AI-produced field, the original value and the correction are both kept, so what the model said remains visible afterwards.

Scoreboad does not claim that its AI is unbiased, objective or accurate. No model here has been audited for bias, and no part of the product treats a model's output as a finding.

Automated processing and human review

Scoreboad is built so that a person makes every consequential hiring decision. Stage moves, offers and rejections are all actions taken by a named user and recorded against them.

There is one place where processing happens without a person in the loop, and it is disclosed here rather than left to be discovered: an organisation can enable a rule that screens a resume against a passing mark automatically. Its effect is a reversible flag on the application. It does not move the application to another stage and it never rejects anyone; a recruiter sees the flag and decides.

There is currently no notice to the candidate that this automatic screening ran, and no published route for a candidate to ask for it to be reviewed by a person. Unfinished: AUTOMATED DECISION-MAKING NOTICE AND REVIEW ROUTE — REQUIRED BEFORE PRODUCTION

Screening calls, recording and consent

An automated screening call states at the start that it is automated and may be recorded. That disclosure cannot be reordered or switched off by an organisation — it is a constraint in the software rather than a setting.

  • Audio is captured only where the outcome of that disclosure was affirmative.
  • The system detects a refusal in the conversation and acts on it.
  • Where the organisation's settings do not permit a recording, the database refuses to store one.
  • An organisation chooses what survives a refusal — metadata only, the transcript, or everything — and the choice is stated in plain words in the product.

One known limitation: the disclosure is spoken by the voice agent, so if a call drops partway through it the system cannot distinguish “disclosed and accepted” from “never disclosed”.

Who else processes this information

Information is shared only with the services needed to run the features an organisation has connected. The product lists the ones actually connected, by category, inside the workspace.

ServiceWhat it handles
Hosting and databaseStorage of the records above, authentication, and uploaded files.
Application hostingServing the application and its server logs.
AI model providerThe text sent for parsing, scoring, summarising and drafting.
Telephony and speechPlacing screening calls and producing their audio and transcript.
Email providerDelivering messages to candidates, where connected.
Messaging providerDelivering reminders by message, where connected.
Calendar providerCreating interview invitations, where connected.

The named companies behind these roles, the contracts governing them and the formal sub-processor list are not published here. Unfinished: SUB-PROCESSOR LIST AND DATA PROCESSING TERMS — COMPLETE BEFORE PRODUCTION

Storage, location and transfers

Records are held in a database with row-level policies that scope every row to the organisation that owns it. Uploaded files are in private storage and are read through short-lived signed links after the requester's organisation has been checked.

The regions the data is stored and processed in are not recorded in this project, and no transfer mechanism is documented. Voice data in particular reaches the telephony and model providers wherever they operate. Unfinished: DATA RESIDENCY AND INTERNATIONAL TRANSFER MECHANISM — COMPLETE BEFORE PRODUCTION

How long information is kept

An organisation can configure a retention period and choose what should happen when it expires. The default is manual review rather than automatic deletion, because an automatic delete can destroy records an organisation is required to keep.

Stated plainly because the opposite would be a promise the software does not keep: those settings are recorded but are NOT yet acted on automatically. Nothing is deleted on a schedule today. Deletion happens when somebody performs it. Unfinished: AUTOMATED RETENTION ENFORCEMENT — NOT IMPLEMENTED

The activity log is designed to outlive the records it describes: an entry saying who deleted something has to survive the deletion, or the log cannot do its job.

Security

Access is controlled by four roles enforced in the interface, the API and the database; a record belonging to another organisation returns not found rather than forbidden. Message recipients are masked in logs, integration credentials are encrypted, and candidate-facing links are signatures that store no secret.

The full description of these controls, including what is not in place: Read the Scoreboad security page

No security certification is held and none is claimed. There has been no third-party audit or penetration test.

Choices and requests

What the software supports today, stated as it stands:

RequestWhat exists
Stop receiving messagesEvery outbound message carries an unsubscribe link that works without an account, and the sending pipeline checks the preference before each send.
CorrectionAn organisation's recruiters can correct a candidate record. There is no direct channel for a candidate to request a correction.
DeletionAn Owner or Admin can delete a candidate's data from the workspace. Whether every related file is removed alongside the record is not fully verified.
A copy of the informationNot available. There is no candidate-facing export.

Requests are made to the organisation that holds the record. Unfinished: PRIVACY REQUEST CONTACT AND RESPONSE PROCESS — COMPLETE BEFORE PRODUCTION

Cookies

The public website sets no cookies at all. Signing in sets two, both strictly necessary. There is no analytics, advertising or tracking technology anywhere in the product.

The detail, including each cookie's purpose: Read the Scoreboad cookie information

Children

Scoreboad is workplace software sold to organisations for hiring. It is not directed at children and has no feature intended for them.

Unfinished: MINIMUM AGE AND JURISDICTION-SPECIFIC WORDING — CONFIRM WITH COUNSEL

Changes and contact

When this document changes, the date at the top changes with it. There is no mailing list for notices.

There is no privacy inbox yet. The contact page explains what does exist: See how to contact Scoreboad

Unfinished: LEGAL ENTITY NAME AND REGISTERED ADDRESS — COMPLETE BEFORE PRODUCTION