Privacy Policy

This Privacy Policy describes how Kendor (“we”, “us”) collects, uses and shares personal data when you use our technical hiring platform — as a hiring team member, as a candidate taking an assessment or applying to a job, or as a visitor to our site.

Our role: controller and processor

For candidate data processed as part of an organization’s hiring (assessment submissions, activity signals, recordings, applications and reviewer notes), the hiring organization is the data controller and Kendor acts as its data processor: we process that data on the organization’s instructions. If you are a candidate and want to exercise your rights over screening data, the fastest route is the organization that invited you — we assist them with every request. For account data, self-serve candidate profiles, our website and our communications, Kendor is the controller.

Information we collect

• Account data — name, email, password (stored hashed) and language preference when you create a hiring-team or candidate account; optional candidate-profile fields you choose to add (photo, title, location, links, skills).
• Assessment data — the code and answers you submit, files in your assessment workspace, test results, scores, and timing (when you started, finished, or ran out of time).
• Assessment integrity signals — during an assessment we record editor activity such as tab switches, paste events and a typing timeline of your editor session, so reviewers can verify the work is your own. Where the hiring organization enables proctoring, screen recordings made during the assessment are stored for its reviewers. We tell you before an assessment starts what is captured.
• Job applications — the details you submit on a company’s job posting: name, email, and any optional fields the company requests (headline, location, links, resume link, cover note, answers to its questions). A hiring team can also put you forward for one of its own roles without a new form, using the details it already holds for you — the record says it was added by the team rather than submitted by you.
• Reviewer content — hiring teams write notes, comments, ratings and feedback about submissions and candidates; this is controlled by the hiring organization.
• Emails a hiring team sends you — when a company acknowledges your application, tells you it is not moving forward, makes you an offer or welcomes you aboard, it sends that email through Kendor using its own wording. We keep a record that it was sent — the type of email, its subject, the address it went to, who sent it and when — so the team can see what you were told. We do not keep a copy of the message text. If a team closes your application without writing to you, we record that decision too, marked as not sent; your data export says which it was.
• Live review sessions — when a hiring team invites you to walk through your submission, we process the invite (your email and its expiry) and any comments you write in the review thread. During a live session your display name, the file you have open and your cursor position are relayed to the other participants in real time; these presence signals are not stored. A live session can also carry an audio/video call between you and the reviewers — your microphone and camera stay off until you turn them on, the media is encrypted in transit and is not recorded or stored.
• Interviews a hiring team schedules with you — the time and length of the meeting, its type (intro, technical, team or final), who from the company is joining, and the calendar invitation we email you. A hiring team can also keep private notes on the interview — what to probe on, and their read afterwards. Those notes are about you, so they are yours to see: they are included in your data export and deleted when you erase your data. They are never shown to you inside the product and never sent to you.
• Usage and log data — basic technical logs (requests, errors, approximate region) kept for security and operations. We do not run third-party analytics or advertising trackers.

How we use information, and on what basis

• To run assessments, grade submissions and show results to the hiring team — performance of a contract, and the hiring organization’s legitimate interest in evaluating applicants.
• To capture integrity signals and (where enabled) recordings — the hiring organization’s legitimate interest in verifying assessment authenticity, with notice to you before the assessment begins.
• To operate accounts, send transactional email (invitations, password resets, notifications) and provide support — performance of a contract.
• To secure the platform, prevent abuse and debug faults — legitimate interest.

Cookies

We use only strictly necessary and functional cookies: keeping you signed in, remembering your language, and carrying an assessment invitation across pages. We set no advertising, analytics or cross-site tracking cookies, which is why you don’t see a cookie banner.

Sharing and sub-processors

We do not sell personal information. Candidate screening data is shared with the hiring organization that runs the assessment or job posting — that is the service. To operate the platform we use a small set of infrastructure providers acting on our instructions: netcup (hosting, Frankfurt), Amazon Web Services (file and recording storage, Frankfurt), Mailgun (email delivery, EU region), Cloudflare (DNS/CDN and security) and LiveKit (live audio/video for review calls — media transits their servers in real time and is not stored). Each is bound by a data-processing agreement — the full list lives at kendor.io/legal/subprocessors. For hiring organizations, our own Data Processing Agreement governs the candidate data we process on their behalf.

International transfers

Our infrastructure — application servers, database, code execution and file storage — is located in the European Union (Frankfurt, Germany). Where a provider’s corporate structure could involve access from outside the EU/EEA, we rely on the EU–US Data Privacy Framework and Standard Contractual Clauses as safeguards.

Retention

• Account and profile data — kept while your account exists; deleted when you delete your account.
• Assessment submissions and results — kept while the hiring organization’s account retains them, so hiring decisions stay auditable.
• Proctoring recordings and editor-session captures — deleted automatically 12 months after the assessment.
• Unused assessment invitations — deleted 90 days after they expire; password-reset tokens 30 days after they expire.
• Sign-in session records — kept while the session can be renewed (30 days of inactivity, refreshed each time you use the site) and deleted 7 days after they expire. Signing out ends them immediately.
• Records of emails a hiring team sent you — deleted 24 months after the email was sent.
• Interviews a hiring team scheduled with you, including the panel’s private notes about the conversation — deleted 24 months after the interview was due to take place.

Your rights

Depending on where you live (including under the GDPR), you may have the right to access, correct, export, delete or restrict the processing of your personal data, to object to processing based on legitimate interest, and to lodge a complaint with your supervisory authority. Candidates with a Kendor account can download their data and delete their account directly from account settings. For anything else, contact us at hello@kendor.io — where the hiring organization is the controller we will pass the request on and help resolve it.

Security

Passwords are stored hashed, candidate code runs in isolated sandboxes, recordings and workspace files live in private storage accessed through short-lived signed URLs, and access to candidate data is limited to the hiring organization’s authorized members.

Changes and contact

We will update this policy as the product evolves and adjust the date above. Questions or requests: email hello@kendor.io.