Skip to content
Ratify

Security and privacy

Immigration records are some of the most sensitive data an HR team holds. Here is how Ratify protects them.

Your data

  • Data is encrypted in transit (TLS 1.2 or newer) and at rest, in the database and in file storage.
  • Each company's data is kept apart in the application and in the database (row-level security), and automated cross-tenant tests run on every change before it ships.
  • We don't collect government ID numbers, such as Social Security, passport, or A-numbers.
  • No advertising or third-party analytics in the application.
  • Optional tracking-only mode: use the product without storing any documents.

Documents

  • Documents are kept in private storage. Download links expire within a minute, and every download is recorded in your audit log.
  • Uploaded files are limited to PDFs and images, and checked for active content before anyone can open them.
  • Employees upload through expiring, revocable links plus a one-time code sent to their email.

Access

  • Multi-factor authentication is required for every user.
  • Role-based access decides who can see, change, and download what, and a full audit log is available to your Owners, Admins, and HR managers.
  • Our staff can view customer data in the application only through audited, time-limited, read-only support sessions, visible in your audit log.
  • Direct access to our infrastructure is limited to the founder, requires multi-factor authentication, and follows a documented break-glass procedure, with every use logged and reviewed.

AI connectors

  • AI connectors for Claude and ChatGPT stay off until an Owner or Admin turns them on for your organization.
  • AI connectors are read-only and return only what the connecting person can already see in the app. They never return documents, download links, or notes.
  • Every lookup through an AI connector is recorded in your audit log.
  • Connecting Claude or ChatGPT goes through the same sign-in as the app, with multi-factor authentication.

How we build and run it

  • Every change passes automated tests, including the security tests, and needs the founder's approval before it merges. Only our CI pipeline deploys to production, and only the founder can start it.
  • Credentials are kept in a dedicated secrets manager, never in code. Staging and production are separate environments with separate credentials and no shared data.
  • The infrastructure providers that process your data are listed on our subprocessors page.

SOC 2

We are building to SOC 2 controls and will complete an audit as customer needs require. Ask us for our current status.

Request our security packet

Doing a security review? Tell us where to send it, and we'll email you a filled-in security questionnaire and our policies.