Privacy
Privacy
This page describes how HeadPeek processes account data, uploaded resumes, job descriptions, and screening outputs. It is written in plain language so users can understand the product's data flow without reading legal boilerplate.
Effective May 2026
This page was updated to reflect the current product architecture: tier-based retention (90 days free / 2 years paid), paid-tier AI providers with no-training terms, and a complete subprocessor list. It will be reviewed with legal counsel before production launch.
HeadPeek helps teams upload resumes, compare them against a job description, and review ranked screening outputs. This page describes what data HeadPeek processes, who processes it, how long it stays, and how to request deletion. It is written in plain language so users understand the data flow without reading legal boilerplate.
Account data: your name, email address, and a hashed password. Workspace content: resumes you upload (PDF, DOCX, or TXT files), job descriptions you provide, and the screening results HeadPeek generates — candidate names, professional titles, years of experience, skills, scores, verdicts, reasons to interview, concerns, and interview questions. Payment metadata: Razorpay order and payment IDs, purchase history, and wallet balance. HeadPeek never sees or stores your credit card number, CVV, or card expiry — payments are handled entirely inside Razorpay's hosted checkout. Operational data: request logs with user and batch identifiers, error traces (with resume text redacted before logging), and security events.
When you upload a resume, HeadPeek extracts the text in memory and sends it to an AI provider for structured parsing. The AI returns a structured profile (name, skills, work history, etc.), which is stored. The raw extracted text is then discarded — it is never written to the database. The structured profile is passed through additional AI evaluation steps to produce scores, verdicts, and recommendations. Job descriptions follow a similar path: they are sent to the AI provider for analysis, and the resulting context is stored for reuse across the batch.
HeadPeek uses Anthropic (Claude) as the primary AI provider and Google (Gemini) as a fallback. Both operate under paid-tier API terms that prohibit the use of customer data for model training. No resume, job description, or screening output is used to train or improve AI models.
Anthropic and Google (Gemini) process resume and job description text for AI inference. Razorpay processes payment transactions. Fly.io hosts the application and database in the United States (Chicago region). Upstash provides Redis for task queuing and rate limiting. Vercel serves the frontend. Sentry receives error traces (with resume text redacted). BetterStack or Axiom receive structured application logs. Cloudflare R2 or Backblaze B2 store encrypted database backups. Each subprocessor only receives the data it needs to perform its function.
HeadPeek uses only essential cookies to operate the service: a session cookie (httponly, same-site strict) to keep you logged in, and a CSRF token cookie to protect against cross-site request forgery. No tracking, analytics, or advertising cookies are used.
HeadPeek shares data with subprocessors only to the extent needed to operate the product. Data may also be disclosed when required by law, to respond to a security incident, to prevent fraud, or in connection with a business transfer. HeadPeek does not sell user data.
Free accounts (starter credits only): batch data, uploaded resumes, and screening results are retained for 90 days, then automatically deleted. Paid accounts (any credit pack purchased): data is retained for 2 years. Billing records are retained indefinitely for financial audit purposes and contain only pseudonymous identifiers (order and payment IDs). Application logs auto-expire within 30 days. Error traces auto-expire within 90 days.
You can delete your account at any time from the Account page. This immediately removes your account data, wallets, batches, screening results, and all associated database records. Uploaded resume files and debug artifacts are cleaned up within 24 hours by a scheduled retention job. Billing records are retained for financial compliance and contain only pseudonymous identifiers. To request deletion without logging in, use the Contact page. Deletion requests without an authenticated account require identity verification.
HeadPeek encrypts data in transit (TLS) and at rest. Access to production systems is restricted. Resume text is redacted from all application logs and error traces before they leave the application. No system can be guaranteed perfectly secure — avoid uploading information you are not comfortable handling electronically.
HeadPeek provides AI-assisted screening output to support your review, not to make hiring decisions on your behalf. You remain responsible for interpreting results and making employment decisions.
Application data is processed and stored in the United States (Fly.io, Chicago region). Payment processing occurs in India (Razorpay, per RBI data localization requirements) and involves only payment metadata — no resume or candidate data reaches Razorpay. AI inference may be processed in data centers operated by Anthropic or Google depending on the active provider.
This page is updated as product behavior, providers, or compliance requirements change. The current version was last updated May 2026.
Contact
Use the Contact page to request deletion, ask about retention, or raise product privacy concerns. If a dedicated privacy support channel is added later, this page should be updated to point to it directly.