Privacy policy

This policy is in two parts, because two quite different things are going on.

• Part A covers this website — the pages you are reading, the waitlist, the contact and design-partner forms, and analytics. It applies to you right now.
• Part B covers the Recio interview platform — what happens when an employer uses Recio to interview candidates. It applies if you have been invited to a Recio interview, or if your company is running interviews with us.

It does not cover other websites we link to, or an employer’s own privacy notice, which is the notice that governs their hiring process as a whole.

We do not ask you to create an account, and we do not build a profile of you. Everything below is either something you typed into a form or something a server records in the ordinary course of serving a page.

Waitlist form

Your name, your email address, and your company if you give one. We store it with a waitlist position and email a copy to our shared founders inbox. Submitting the same address again returns your original position rather than creating a second record.

Contact form

Your name, email address, message, and your company if you give one.

Design-partner application

Your name, email address, company, the roles you are hiring for, and an optional message.

Bot protection

Our forms can run a Cloudflare Turnstile check to confirm a submission comes from a person. When it runs, your IP address is shared with Cloudflare for that check. Turnstile sets no tracking cookies, so it keeps working even if you decline analytics.

Analytics

If — and only if — you accept analytics, Google Analytics 4 records which pages you visit, roughly where you are (derived from your IP address), and what device and browser you use. See section 5.

Server logs

Our hosting provider records requests to the site, including IP address, user agent, and the page requested. We use these for security and reliability, not to identify you.

We do not buy personal data, we do not sell it, and we do not use it for advertising or send it to advertising networks.

This site is not aimed at children, and we do not knowingly collect personal data from anyone under 18 through it. If you believe a child has sent us something, tell us and we will delete it.

We use what you send us to reply to you, to assess whether the design-partner programme is a fit, to let you know when Recio is available, and to keep a record of the conversation. We use logs and analytics to keep the site working and to understand which pages are useful.

Replying to you

You asked us to. Under the DPDP Act this is the consent you gave by submitting the form; under the GDPR it is your consent, or our legitimate interest in responding to a business enquiry.

Analytics

Your consent, given through the banner. Nothing is measured before you choose, and you can change your mind at any time.

Security, logs, and bot protection

Our legitimate interest in keeping the site available and free of abuse.

We do not make automated decisions about you on this website.

Analytics is switched off until you accept it. When you first arrive you will see a small banner with two buttons, and nothing is measured until you press one of them. If you decline, no analytics cookies are ever set. This is the only posture consistent with a product that says it is not a surveillance product.

How we remember your choice

Your answer is stored in your browser under a key called recio_consent. It is stored in local storage rather than in a cookie, so it never travels with your requests to us — we cannot see it from the server, and it is not used to identify you.

What analytics we use

Google Analytics 4, configured with Google Consent Mode. Advertising signals are permanently denied; only analytics storage can ever be granted, and only by you. We use it to see which pages are read, not to follow individuals around the internet.

Changing your mind

Clearing your site data in your browser removes the stored choice, and the banner will appear again on your next visit so you can choose differently. You can also block analytics in your browser, and we will not work around it.

Our fonts are self-hosted: they are built into the site rather than fetched at page load, so opening a page here does not make a request to Google Fonts.

We run a small site and we buy the infrastructure under it. These are the providers involved, and what each one sees. We do not share your data with anyone else, and none of these providers is permitted to use it for their own purposes.

Vercel

Hosts and serves the site. Sees requests to it, including IP addresses.

Neon

The Postgres database that stores waitlist, contact, and design-partner submissions.

Resend

Delivers the notification email when you submit a form, so we see the enquiry. The email includes what you submitted.

Cloudflare

Runs the Turnstile bot check on our forms, when it is enabled.

Google

Google Analytics 4 — only after you accept analytics, never before.

Sanity

Stores our blog posts. Blog images are served from Sanity’s CDN, so opening a blog post makes a request to them from your browser. The rest of the site does not.

We may also share information where the law requires it, or to establish or defend a legal claim. If Recio is ever acquired or reorganised, data may transfer as part of that, and this policy — or one at least as protective — will continue to apply.

We keep waitlist entries and enquiries for as long as we are realistically still going to act on them: while we are in touch with you, while you are on the waitlist for a product that has not launched, and for a reasonable period afterwards so we have a record of the conversation. We review these records periodically and remove what we no longer need.

Analytics data is retained by Google under the retention setting on our property. Server logs are kept for a short period by our hosting provider for security and debugging.

You do not have to wait for any of that. Ask us to delete your record and we will, as described in section 9.

Data is encrypted in transit and at rest by the providers above. Access to the database and the shared inbox is limited to the two founders. Credentials are kept out of the codebase and out of anything served to your browser.

The providers we use operate globally, so your data may be stored or processed outside the country you are in — including in the United States and the European Union. Where the law requires a transfer safeguard, we rely on the provider’s standard contractual clauses and equivalent terms.

No system is perfectly secure. If a breach ever affects your personal data, we will tell you and the relevant authority as the law requires, and we will tell you what actually happened rather than the smallest thing we can defend.

Wherever you are, you can ask us for a copy of what we hold about you, ask us to correct it, or ask us to delete it. We will not charge you and we will not make it difficult.

In India

Under the Digital Personal Data Protection Act, 2023 you have the right to access a summary of your personal data and how it is processed, to have it corrected, completed, updated, or erased, to nominate someone to exercise your rights, and to have a grievance addressed.

In the EEA or UK

Under the GDPR and UK GDPR you have the rights of access, rectification, erasure, restriction, portability, and objection, and you may withdraw consent at any time. You may also complain to your local supervisory authority.

Elsewhere

We apply the same practice everywhere: ask, and we will show you what we have or delete it.

To exercise any of these, write to contact@therecio.com from the address you gave us, or tell us which address to look up. We aim to answer within 30 days. If you are unhappy with how we handled it, say so in the same thread — a grievance goes to the founders, because there is currently nobody else for it to go to.

If you are a candidate asking about an interview rather than about this website, section 14 explains how that works.

A Recio interview is a video interview with hands-on labs, and it is recorded. You are told this before it starts. What gets captured:

Video and audio

The recording of your interview. It is kept as the evidence of record for integrity and for any dispute about the result. It is not what the scoring reads.

Transcript

A timestamped, written record of what was said in each stage. This is what the scoring actually reads.

Lab work

What you built in the labs, plus a log of the steps you took to build it.

Evidence items

Each score is linked to the exact moment that justifies it — a span of the transcript, an action in a lab, or a point in the video. This is what makes a report reviewable line by line instead of a number you have to trust.

Application details

Your résumé and the details you submitted when you applied, along with the result of the screening step.

Session and integrity signals

Pre-flight checks on your camera, microphone, and network, plus in-session signals used for integrity. These are flags and counts about the session, not a record of anything outside it.

Video and audio are treated as sensitive personal data: encrypted in transit and at rest, access-controlled per employer, and never mixed between employers.

Before an interview begins we capture your identity and your consent — to the interview being recorded, and to any check that will run during it. The version of the notice you were shown and the time you consented are recorded, so it is always clear what you agreed to.

Where a document-and-selfie verification check also runs, it is carried out by a specialist vendor, and it is a check we can switch off for a particular country or at a particular employer’s request. Whether it ran is recorded on the report rather than assumed, so nobody has to guess.

Recio does not store a face template. Not for the identity check, and not for anything else. What is kept is the result — pass, fail, declined, or not applicable — with a timestamp and a reference to the vendor that ran the check.

That is a deliberate design decision, not an accident of implementation. Biometric law in several jurisdictions attaches obligations to holding a biometric identifier; we hold none to attach them to. It does not remove our responsibility — presence checks during a session do process biometric information in the moment, which is why your consent is taken up front — but it does mean there is no face database at Recio to leak, subpoena, or misuse.

Presence checks during the session produce flags and sampled counts. They are computed inside the interview session and are not retained as an image record.

Recio uses AI to conduct the interview, to adapt the questions to your answers and your level, and to score your work against a rubric fixed for the role and level. Every candidate at a given role and level is measured against the same competencies, the same difficulty, and the same rubric — only the surface questions differ.

What it does not do

• It does not reject you. Recio produces a recommendation with evidence; the employer sets the bar and a person makes the decision.
• It does not infer emotion, mood, personality, or affect from your face or your voice. There is no such signal anywhere in the system, by design.
• It does not act on an integrity flag by itself. A flag sends a session for human review — never an automatic fail — because wrongly doubting an honest candidate is the worse error.

Where the law gives you a right to an explanation of automated processing in hiring, the evidence trail is that explanation: every score points at the moment behind it, and the transcript and rubric are available for review.

Employers are told what to disclose to candidates, and where a jurisdiction requires notice, consent, or a bias audit before an AI interview may run, that requirement is part of the employer’s agreement with us.

Interview records stay in active storage for one year. After that, the video and audio move to cheap cold archive while the transcript and evidence remain searchable, so a hiring decision stays reviewable long after the interview.

Records are keyed to you as a candidate, not just to a single session. If you interview again — for another role at the same employer, or later — your history can be carried across rather than starting from nothing.

If you ask to be erased

On request we anonymise your record rather than deleting it outright. The identifying parts go — the video, your name, your contact details. What remains is a nameless outcome record, so the employer keeps a defensible account of how a hiring decision was made without keeping you personally in it.

We would rather say this plainly than bury it: erasure here means the identifying data is destroyed and an anonymous record of the outcome survives. That is a trade-off between your privacy and an employer’s legal need to show how it hired. If it matters to you, ask us before you interview, not after.

To make a request, contact the employer who invited you, or write to us at contact@therecio.com and we will route it. Because the employer instructs us, we will normally act on their confirmation — we will not quietly delete a hiring record from under them, and we will not sit on a request either.

Interview data runs on cloud infrastructure we operate, with media and transcripts stored in the region agreed for that engagement. Some processing may run in a different region where a service we depend on is not offered locally; where that applies, it is set out in the employer’s agreement rather than left vague.

The platform depends on external providers for specific jobs — cloud hosting and storage, speech transcription, AI model inference, identity verification, and email delivery. We name each of them, and what they see, in the agreement with the employer.

Our standard for any provider that touches interview content is that it must not train its models on it, must cap how long it retains it, and must delete it on request. A provider that cannot commit to that does not get the data.

The list of providers changes as the platform is built. Rather than publish a list here that goes stale, we keep the current one in the agreement, where it is contractually binding and where you can be told when it changes.

Recio is being built, and this policy will change as it is. Part B in particular will get more specific as capability moves from designed to live — we describe what the platform does, and we do not claim a control is in place before it is.

The “last updated” date at the top of this page always reflects the current version. If a change materially affects how we handle your data, we will make that clear rather than editing the page quietly.