Candidate data is a responsibility, not a feature.
Recruiting Buddy handles resumes, phone numbers, call recordings, and screening results for your candidates. Here is how that data is protected — in plain language.
Your data stays in the customer workflow. Candidate data supports customer-directed recruiting plus the operation, security, and support needed to provide the service.
Isolation by default. The customer-data model scopes records to an organization and backs application checks with database controls.
Consent is a shared launch gate. Technical opt-out and calling-window controls support the customer’s documented consent and disclosure obligations; they do not replace them.
The controls behind the platform.
Organization-level isolation
Customer-data tables use database-enforced row-level security and application authorization. Managed launch review includes synthetic cross-organization checks before activation.
Database RLS · organization-scoped application accessTransport and storage controls
Platform data uses encrypted transport and managed storage encryption. Data location, subprocessors, retention, and cross-border requirements are confirmed in the customer security review rather than assumed from this page.
Encrypted transport · managed storage controlsAuthenticated access paths
Sign-in uses managed authentication with email/password plus optional Google and Microsoft sign-in, and secure HttpOnly session cookies. Service routes and inbound webhooks use endpoint-specific, fail-closed authentication; replay protection is applied where implemented for that protocol.
Managed sign-in · authenticated service routes · signed webhooksConsent-first candidate outreach
Customers must document the consent source before live messaging. Ordinary sends fail closed when opt-out state cannot be verified, STOP and HELP responses remain available, and outbound calls respect configured campaign windows.
Customer consent record · STOP/HELP controls · calling windowsRole-based team access
Workspaces separate account managers from recruiters, and team membership is controlled by invite. Admin actions — like renaming your AI agent or changing company info — are restricted to admins.
Roles · invite-only membership · admin controlsDocumentation on request
Managed evaluations can include technical control documentation and a security-questionnaire review. Legal conclusions, certifications, SLA terms, and customer-specific requirements are confirmed separately.
Security review available during evaluationBring your security team to the demo.
We’ll walk through data flows, retention, and controls with the people who need to sign off.