Sub-processors

The companies that process personal data to run Elsin, and what each one handles.

Last updated
  • 5 companies process personal data for Elsin. Supabase, Vercel and Resend are always used; Stripe and Microsoft only when a feature needs them.
  • The Elsin database and files are stored in the United States, on AWS in N. Virginia.
  • We tell customers at least 30 days before a new sub-processor starts handling personal data, and they can object.

1. What this list is

A sub-processor is a company we engage that processes personal data on our behalf.

When Elsin processes candidate data for an employer, we are that employer's processor, and the companies below are our sub-processors. They process personal data only to provide their service to us, under written terms that protect it at least as well as our data processing addendum. The same companies process the data we control ourselves, as described in the privacy policy.

2. Sub-processors

Supabase stores the data, Vercel runs the app and this website, Resend sends email, Stripe takes payments and Microsoft writes AI summaries on request.

Supabase, Inc.

DetailSupabase, Inc.
ServiceDatabase, sign-in, file storage and secrets
PurposeHosts the Elsin database, sign-in accounts, résumés, uploaded documents and encrypted integration keys.
Personal dataAll Elsin data, including candidate records, verification results, ID images sent for review and demo requests.
LocationUnited States (AWS us-east-1, N. Virginia)
UsedAlways

Vercel Inc.

DetailVercel Inc.
ServiceHosting, Web Analytics and Speed Insights
PurposeRuns the Elsin app and this website and delivers their pages. Tells Elsin the approximate location of a request (country, region, city and time zone, worked out from the IP address), which Elsin uses to check location consistency. Measures visits and page speed on this website, without cookies.
Personal dataRequest details, including IP addresses, for every request; for website analytics, the page, referrer, approximate location, browser, operating system and device type.
LocationUnited States (app functions in iad1, Washington, D.C.), with a global edge network
UsedAlways

Resend

DetailResend
ServiceEmail delivery
PurposeSends every email Elsin sends: sign-up confirmations, sign-in links, password resets and team invitations, application updates, employer messages, interview invitations, referee, work-history and equipment requests, and email copies of team notifications.
Personal dataRecipient address, subject, body and any calendar attachment. Open and click tracking are not turned on.
LocationUnited States
UsedAlways

Stripe, Inc.

DetailStripe, Inc.
ServicePayments
PurposeTakes payment for paid plans, monthly or annually, and runs checkout and the billing portal. Elsin keeps only the Stripe customer and subscription identifiers, the plan and the identifiers of billing events.
Personal dataThe customer's organisation name, the buyer's email, billing name and address, tax number and payment card. No candidate data.
LocationUnited States
UsedWhen a customer subscribes to a paid plan

Microsoft Corporation

DetailMicrosoft Corporation
ServiceAzure AI Foundry
PurposeWrites a résumé summary of a candidate when a manager at the employer asks for one. An employer can switch summaries off.
Personal dataThe candidate's name, headline, location, the employer's tags, the jobs applied for, application answers and résumé text.
LocationUnited States (Azure East US 2)
UsedOnly when a manager asks for a summary

3. File delivery networks

Two public networks deliver the files the on-device check needs. They see only the device downloading them.

The identity check runs in the candidate's browser. Its open-source model files are downloaded from public content delivery networks. They receive no candidate data, only what any download reveals.

NetworkWhat it sees
jsDelivr: Delivers open-source model and text-recognition files to the candidate's browser.The device's IP address and browser details, as with any download. Location: Global.
Google Cloud Storage: Delivers face and head-pose model files to the candidate's browser.The device's IP address and browser details, as with any download. Location: Global.

4. Public lookups

To check a profile, Elsin's servers look up public records. These sources receive only the handle or domain being looked up.

Some fraud signals come from public records. Elsin's servers ask the sources below for them and keep the answer with the candidate's record, and a copy of the public response until it expires. The source receives the handle or domain being looked up, never a candidate's name, email address or application.

SourceWhat Elsin looks up
GitHubThe public profile of a GitHub account a candidate links: its age and public statistics.
Domain registries (RDAP)The registration date of a domain, such as the one in an email address or a candidate's website.

5. Services an employer connects

These are the employer's own providers. Data goes to them only when the employer connects them.

An employer can connect its own accounts with the services below. When it does, Elsin exchanges data with them on the employer's instructions, under the employer's own agreement with each provider. They are not our sub-processors.

ServiceWhat Elsin sends or receives
Greenhouse, Ashby, Lever, WorkableApplicant tracking: candidates, jobs and applications are imported; a verification tag and note are written back.
CheckrBackground checks: name, email, phone and work location are sent; status comes back.
BambooHRHR system: a new hire's name, personal email, mobile phone and start date.
Google Calendar and Meet, Microsoft Outlook and Teams, ZoomFree and busy times are read; interview meetings are created with the candidate's name in the title.
SlackHiring events with the candidate's name and job, and interview reminders.
Calendly, Cal.comBooking links pre-filled with the candidate's name and email.
The employer's own webhook addressesEvents the employer subscribes to.

Job boards receive job listings only, never candidate data.

6. Changes and objections

We update this page at least 30 days before a new sub-processor starts. Customers can ask to be emailed, and can object.

We update this page, and its date, at least 30 days before a new sub-processor starts processing personal data, except in an emergency needed to keep the service running, when we update it as soon as we can. To be emailed about changes, write to contact@surfplatforms.com from your work address.

A customer may object to a new sub-processor on reasonable data protection grounds within those 30 days. We will then work with the customer in good faith on an alternative; if there is none, the customer may end the affected part of the service and receive a refund of fees prepaid for it, as the data processing addendum sets out.

7. Contact

Questions about this list go to the address below.

See also Data processing addendum. How Elsin processes candidate data as an employer's processor. Part of the terms of service.