Anuva uses the third parties below to provide the service under the Data Processing Agreement. CV files stay in our own storage, so no third-party storage provider receives them.
We email workspace admins in advance before adding or replacing a sub-processor and update this page. Customers can object within the notice period by writing to hello@anuva.io. Processing locations are available on request.
In use today
These providers are active for every workspace.
| Sub-processor | Purpose | Personal data |
|---|---|---|
| Anuva's own servers | Run the application and databases, and store CV files in our own S3-compatible storage. Each workspace has its own database. | All Customer data |
| Cloudflare | DNS, TLS and the network tunnel in front of the service; Turnstile bot checks on public forms. | Traffic in transit, IP address, browser signals |
| Resend | Sending email to candidates and workspace users. | Name, email address, email content |
| OpenRouter | AI features on Anuva's key: drafting job descriptions and scoring templates, and CV screening when a workspace turns it on. Requests are only routed to model providers that keep no copy of the data and do not train on it. | Role briefs and job text. For screening, CV text of candidates who agreed to AI screening, with email addresses, phone numbers and street addresses removed. CV files are never sent. |
| Sign in with Google. | Name, email address | |
| Sign in with LinkedIn, and filling an application from a LinkedIn profile when a candidate chooses to. | Name, email address, profile details the person shares | |
| GitHub | Sign in with GitHub. | Name, email address |
| Slack | Internal alert to the Anuva team when a new workspace signs up. | Workspace name, admin name and email address |
| Netlify | Hosting this website, anuva.io, and receiving demo requests. Holds no workspace data. | Details entered in the demo form |
Only when turned on
Not in use today. Each one receives data only after we configure it for the service or a workspace turns it on, and we email workspace admins before that happens.
| Sub-processor | Purpose | Personal data |
|---|---|---|
| Your own AI provider | AI screening on the workspace's own API key, for example OpenAI, Anthropic or Microsoft Azure OpenAI. The provider is then the Customer's sub-processor, under the Customer's own terms with it. | Same as OpenRouter above |
| Microsoft | Sign in with Microsoft. | Name, email address |
| Single sign-on (SAML) for Enterprise workspaces. | Name, email address, sign-in records | |
| Stripe | Card payments for paid plans. | Billing contact, company details, payment data (held by Stripe) |
| Slack | Hiring notifications to the Customer's own Slack workspace, when a workspace connects it. | Candidate name, role, stage and decision summary |
| Zoho Sign | Electronic signature of offer letters. | Candidate name, email address, offer document |
| Sentry | Error monitoring. Reports exclude request bodies and personal data by default. | Technical error details, which may include identifiers |