Security & trust

Recruiting data is relationship data. Treat it that way.

Recruiter.ink is designed around secure cloud infrastructure, workspace isolation, controlled sharing, privileged MFA, private candidate content, and operational visibility. We describe the controls and infrastructure assurance behind the platform without claiming certifications we have not earned.

Enterprise-grade foundations for sensitive recruiting data.

Recruiter.ink is built on cloud infrastructure maintained by service providers that have achieved industry-recognized security standards, including SOC 2 Type II and ISO/IEC 27001. These controls support the security, availability, and confidentiality of the infrastructure used to operate our platform.

SOC 2

Type II infrastructure

Recruiter.ink is hosted on cloud infrastructure operated by service providers whose applicable environments have completed SOC 2 Type II examinations.

ISO

27001 infrastructure

Applicable infrastructure providers maintain ISO/IEC 27001 information-security certifications and related security management controls.

TLS

Encrypted in transit

Application traffic is protected using modern encrypted transport, helping protect data as it moves between users and the platform.

ACCESS

Layered access controls

Authentication, tenant boundaries, row-level controls, and privileged access requirements are used to reduce unnecessary access to recruiting data.

Infrastructure certifications apply to applicable third-party service providers and do not constitute an independent SOC 2 or ISO/IEC 27001 certification of Recruiter.ink.

Privacy and access are built into the workflow, not bolted on afterward.

The controls below reflect the way Recruiter.ink is currently designed. Security posture evolves with the product, and enterprise requirements should be reviewed directly with your team before purchase.

01

Tenant isolation

Organization-scoped access controls and Postgres row-level security are used to separate workspace data across tenants.

02

Privileged MFA

Owners, tenant administrators, and platform administrators are required to use multi-factor authentication before privileged workspace access.

03

Private candidate sharing

Candidate review links can hide identity and contact details until the appropriate recruiter-controlled reveal step.

04

Protected candidate media

Candidate profile media is kept private and delivered through short-lived signed access rather than public asset URLs.

05

Explicit representation authorization

Candidate authorization to be represented is recorded separately from general profile content, with event history available for auditing.

06

Voluntary self-identification separation

Sensitive voluntary self-identification data is separated from the hiring-manager presentation experience.

07

Operational health

Platform administrators can monitor workflow failures, stuck matching, integration warnings, service configuration, AI activity, and tenant warning signals.

08

Human decision control

AI can organize evidence, recommend, draft, and accelerate workflow, while candidate and hiring decisions remain with the people responsible for them.

A few principles guide the platform.

  • Least exposureDo not expose candidate identity, contact information, private media, or privileged platform detail when the workflow does not require it.
  • Tenant boundaries firstAccess is scoped to the active workspace and enforced in the data layer rather than relying only on application navigation.
  • Separate sensitive categoriesInformation such as voluntary self-identification should not be mixed into ordinary hiring-manager review content.
  • Observe the systemFailures, stuck workflows, integration errors, and configuration gaps should be visible to platform operators before they become user surprises.
  • Be precise about AIAI-generated conclusions should be grounded in supplied job and candidate evidence, with missing evidence distinguished from contradiction.

Bring your security questions.

If your organization has specific identity, retention, access, integration, or procurement requirements, we can review them as part of the product conversation.