Security
At a glance
- Anonymity is the main safeguard: the platform does not know anyone's name.
- Block an unwanted contact with one button — permanently, across all opportunities.
- Send complaints by email with your own screenshots: we do not read conversations.
- Account deletion is immediate, with no archive kept.
1Anonymity — your main protection
Accounts are created with an invite, a nickname and a password; the platform does not know or store your name. Candidates and companies see each other only by ID until they choose to introduce themselves. A company sees a candidate's card only with their consent and only in the form they approved.
Your avatar and its approved versions, the cards you approve, the results of your White Mirror sessions, your recovery email address and your messages with companies are stored encrypted, with a key kept outside the database and its backups. The team has no tool for reading conversations between candidates and companies.
What is not encrypted: the text of your conversations with White Mirror, and the avatar suggestions the background draws from them with the words they are based on. They are stored in the clear so that a conversation can go on from another device and its result can be shown after the session; the team can open them to keep the service working and to investigate a technical problem. They are erased together with the account.
You are responsible for any information about yourself that you share with the other person in a conversation. Take your time before sharing your name, phone number or address, until you trust them.
2Blocking a contact
The “Block contact” button is available to both parties in every conversation. After a block, the company will no longer see this candidate for any opportunity, and the candidate will no longer receive requests from this company. Messages can no longer be sent; the conversation stays with you, marked as blocked, and you can delete it if you wish.
You do not need to give a reason. We only see how many times an account has been blocked — without the conversation content.
3How to submit a complaint
If the other person's behaviour threatens your safety or anyone else's — email compliance@candiddate.eu from your personal email address. The other person's ID appears at the top of the conversation and can be copied with a click.
- the ID of the account you are reporting;
- what happened, with dates;
- screenshots of the conversation — take them yourself, as we cannot see the conversation;
- how to contact you.
We do not share the information in your email with the other party.
4How we handle complaints
We treat a complaint as a report of a threat to public safety. We do not mediate, investigate disputes between users or make decisions on them.
We assess whether people are at risk. We may suspend or close an account for the reasons listed in the Terms — a threat to people's safety, a credible report, use of the service against the Terms or the law — and we tell its owner the reason unless the law forbids it. If there are signs of a breach of the law, we pass the information to the relevant authorities. We handle companies' reports about candidates in the same way.
If you simply dislike talking to someone — block the contact: it is faster and more reliable.
5Account deletion
You can delete your account at any time using the “Delete account” button in the menu. Your account is erased immediately: your avatar, interviews, messages and recovery data. No archive is kept, and recovery is not possible. Your conversation partners keep the conversation with an “Account deleted” label; deleted conversations can be removed individually or all at once.
What happens to purchased credits is set out in the Terms (section 6 for candidates) and the Business Terms (section 7).
6Where code and data are stored
Source code is in a private GitHub repository. Servers and the database are hosted on DigitalOcean in Frankfurt (fra1, EU); backups are on DigitalOcean Spaces in the same region. Only the team has access to the servers. Upon a lawful request from a competent authority, we provide code, documentation and data to the extent required by law.
7How code is protected and reviewed
Encryption
AES-256-GCM with a key stored separately from the database and its backups, for: the avatar and its approved versions, approved cards, session results, recovery email addresses, messages between candidates and companies, and the context given to the models. Conversations with White Mirror and the suggestions drawn from them are not encrypted (section 1).
Passwords
Passwords and security question answers are stored only as salted scrypt hashes. Login attempts are rate-limited.
Transfer
HTTPS only with HSTS, secure cookies, a strict Content Security Policy (CSP) and page embedding blocked.
Checks
Automated tests and static checks run before every release; database changes are tested on a copy first, and a backup is made before applying them.
Team actions
Admin actions on accounts are logged: who did what and when.
Status
Closed beta. An independent security audit has not yet been conducted.
Terms · Privacy · Principles · AI and the AI Act · Sign in