Recast Recruit

Security & privacy, in plain terms

Recast Recruit reformats candidate resumes inside your browser. The resume never leaves your computer unless you deliberately press one button — and this page tells you exactly which one.

This page describes how the product is built. The legally binding text is the Privacy Policy and Terms; if anything here disagrees with them, they win.

The one-sentence version

Parsing, masking, formatting, and PDF/Word export all run as JavaScript in your browser. There is no upload endpoint for resume content, and we have no server that could store it.

What happens where

ActionRuns in your browserTouches our serversTouches a third party
Paste or drop a resume (PDF, Word, text, image)Yes — parsed locally, including OCR of scanned imagesNoNo
Choose a format, edit on the page, mask PII, anonymize to a Candidate IDYesNoNo
Export PDF or Word, batch-export a roster, build a branded cover sheetYes — the file is generated on your deviceNoNo
Roster, client presets, JD library, submission log, submission profilesYes — stored in your browser's local storage, per accountNo — never syncedNo
Sign in, plan status—Yes — your email and plan tier onlySupabase (authentication database)
Buy a plan—Purchase confirmation onlyLemon Squeezy (merchant of record; we never see card numbers)
✨ AI fix / ✨ Tailor for this JD (Studio, optional)—Yes — the text you submit passes through our proxyAnthropic's API processes that text and returns the result; we keep only a monthly usage count, not the text
🎙 Dictate in a candidate’s notes (optional)—NoYour browser’s own speech recognition: in Chrome the audio goes to Google, in Edge to Microsoft, in Safari to Apple (sometimes on the device). Only while you are dictating.

The exceptions, spelled out

Dictation. 🎙 Dictate in a candidate’s notes uses the speech recognition built into your browser. Recast sends nothing itself, but browsers transcribe speech on their maker’s servers (Google for Chrome, Microsoft for Edge, Apple for Safari unless it runs on the device). It only listens while the button says Stop dictating. Don’t use it if a candidate’s details must not leave your computer.

AI.

Studio includes an optional AI cleanup. It only runs when you click ✨ AI fix (or ✨ Tailor for this JD) on a specific resume. When you do, the raw text of that one resume is sent through our server to Anthropic's API, restructured, and returned to your browser. We do not store the resume text; we increment a per-account monthly counter so the plan cap can be enforced. If you never press that button, no resume content ever leaves your browser.

Privacy records and erasure. The lawful basis, privacy-notice dates and the erasure log are kept in your browser like everything else. The erasure log stores only a reference, the date and how many records were removed — never the person’s name or contact details. “Forget this candidate” removes them from the roster, job orders and the Submission Log entries and saved versions you tick; it cannot reach copies outside this browser (share links you already sent, files you downloaded, backup files, or a client’s own systems).

Encrypted backups and sent-CV references

Backups. A workspace backup file holds your candidates’ personal data. By default it is encrypted in your browser before it is saved: the key is derived from your passphrase with PBKDF2-SHA-256 (600,000 rounds, random salt) and the file is sealed with AES-256-GCM using the browser’s built-in Web Crypto. The passphrase is never stored or sent anywhere, so a lost passphrase cannot be recovered by us or anyone else.

Call mode. Call buttons are ordinary phone links: your phone, or the calling app on your computer, places the call. Recast does not connect, route or record calls and nothing about a call leaves your browser — only the outcome you tap is saved, with your notes.

Business cards. A photo of a card is read on your device with the same open-source text reader used for scanned resumes; the image is not uploaded or kept.

References in sent CVs. Each CV you download for a client carries a random reference (for example RR-7K3Q9P) in the file’s properties, and, only if you turn it on, printed small at the foot of each page. The reference identifies the download in your own records; it contains no personal data and nothing is sent to us. Your record of references (candidate, client, file name, time) stays in your browser and in your backups. “Forget this candidate” removes the candidate from it and keeps only the reference, client and date.

For agencies in the UK

Candidate CVs, notes, right-to-work records and placements stay in your browser on your computer, so in ordinary use no candidate data is transferred to us or to the United States. Two things can leave your computer: your account details (email and plan, held by Supabase), and, only if you use them, the AI features, which send that CV’s text to Anthropic in the United States. In UK mode the AI features are off until your agency turns them on in Region settings. Do that only once your privacy notice and records of processing cover it. Our Data Processing Agreement covers these transfers with the EU Standard Contractual Clauses and the UK International Data Transfer Addendum (with the ICO’s IDTA as a fallback). You remain the controller; the ICO (ico.org.uk) is your regulator.

What "no server" means in practice

Code we load from public CDNs

The app is a single page with its fonts and styles embedded, so the only third-party request in a normal session is the sign-in library (Supabase’s JavaScript client, loaded from the jsDelivr CDN) — it never sees your resumes. Some optional capabilities pull an open-source library from a content-delivery network the first time they are needed — the same way most web apps load their code. The CDN sees a standard request for the library file (your IP address and browser type); it never receives resume content.

Every one of those libraries runs locally once loaded. The service worker never intercepts cross-origin requests.

Roles under GDPR / UK GDPR

For candidate data you process with Recast Recruit, you or your agency are the controller. Because processing happens on your device rather than on our infrastructure, we do not receive that data in ordinary use. For your own account information (email, plan), TrueSift AI LLC is the controller. The Privacy Policy includes region-specific disclosures for the EEA/UK, United States, Canada, Japan, and Taiwan.

Sub-processors

ProviderPurposeSees resume content?
Supabase (US)Account database, authentication, the AI proxy functionOnly the text you explicitly submit to AI fix, in transit
Anthropic (US)AI processing for AI fix / TailorOnly the text you explicitly submit, not retained after the request
Vercel (US)Hosting the app pageNo
Lemon SqueezyPayments, merchant of recordNo
Netlify (US)Domain registration and DNS onlyNo
jsDelivr, cdnjsDelivery of open-source libraries on demandNo

Application security

Questions from compliance teams

Can you sign a DPA?

Yes — email support@recastrecruit.com. Because we do not process candidate data on our infrastructure in ordinary use, the DPA scope is narrow: account data, and the optional AI feature if your agency enables it.

Where is data stored?

Candidate data: on your device, in your browser's storage. Account data: Supabase, United States. See the Privacy Policy for international-transfer safeguards.

Can we disable the AI feature agency-wide?

It is off unless clicked, and it is only available on Studio. If you want it hidden for your team, email support and we will note the account.

How do we delete everything?

Roster → Clear all removes candidates; clearing the site's browser data removes every local record. To close your account and delete your account information, email support.

Do you have a security contact?

support@recastrecruit.com, subject line "Security". We read it the same business day.

Open Recast Recruit   Help center