Security
Two people can ever see a recording. Nobody else.
The candidate who took it, and the enterprise that posted the role, that’s the whole list. Here’s exactly how it’s stored and when it’s gone for good. (Looking for the fairness story? That’s on Trust.)
In one sentence
A requested Skill Dril’s two 5-second identity clips always upload into a private storage bucket. A Job Dril you invited or personally invited uploads its full recording there too. A self-serve Job Dril’s stays on the candidate’s own device. Nothing passes through or sits on our own servers.
Our own infrastructure, operated directly.
The application and database run on infrastructure aidril operates directly, not handed off to a third-party platform’s shared tenancy. Interview videos and identity clips live in a private storage bucket, regardless of where the rest of the stack runs.
Two people can ever open a recording.
The candidate who took the Dril, and the enterprise that posted the role it was taken for. Every playback link is re-checked against that rule every time it’s requested.
The candidate
Their own session, always.
The hiring enterprise
Invited drils.
Nothing sits around by default.
An automatic job checks every day.
The Dril happens
Two 5-second identity clips upload straight to the private bucket, with the candidate's consent. For a Job Dril you invited or personally invited, the full recording uploads there too. A self-serve Job Dril's full recording stays on the candidate's own device, never uploaded. Transcript and scores land in the database either way.
Clips, transcript, scores, and any uploaded recording are purged
Unless you saved that Dril Card first, which exempts it.
If a candidate deletes their own account
Every session of theirs goes with it, instantly, including a Job Dril's video, transcript, and scores. Saving that Dril Card doesn't protect it from this one, only from the day-90 purge above.
In transit, and said plainly.
Every connection to aidril runs over HTTPS. A transcript sent to our AI providers travels over their own encrypted APIs, the same way it always would.
This page tells you plainly, and exactly, where things stand today.