Data processing addendum

How Elsin processes candidate data as an employer's processor. Part of the terms of service.

Last updated
  • The employer decides why and how its candidates' data is used. Elsin acts only on its instructions.
  • Elsin keeps the data confidential and secure, uses only the listed sub-processors, and tells the employer before adding one.
  • Elsin reports a personal data breach within 72 hours of becoming aware of it.
  • Elsin helps the employer answer candidates' requests, and returns and then deletes the data when the contract ends.

1. About this addendum

This addendum is part of the terms of service between Elsin and the employer, and it wins on anything about personal data.

This data processing addendum (the “DPA”) is between Surf Platforms Inc., a corporation organized under the laws of the State of Delaware with its principal place of business in San Jose, California (“Elsin”) and the customer that has agreed to Elsin's terms of service (the “Customer”). It forms part of those terms (the “Agreement”) and applies automatically from the day the Customer starts using Elsin. A countersigned copy is available on request at contact@surfplatforms.com.

If this DPA conflicts with the Agreement on the processing of personal data, this DPA wins. If it conflicts with the Standard Contractual Clauses, the Standard Contractual Clauses win.

2. Definitions

Terms such as controller, processor and personal data breach have the meaning data protection law gives them.

  • Data Protection Laws: all laws on the processing of personal data that apply to a party's processing of Customer Personal Data, including the GDPR, the UK GDPR, the California Consumer Privacy Act as amended (“CCPA”), other US state privacy laws, and biometric privacy laws such as the Illinois Biometric Information Privacy Act.
  • Customer Personal Data: personal data that Elsin processes on the Customer's behalf in providing the service, as described in Annex I.
  • Controller, processor, data subject, personal data, processing, supervisory authority: as defined in the GDPR. “Controller” includes a “business” and “processor” includes a “service provider” under the CCPA.
  • Personal Data Breach: a breach of security leading to the accidental or unlawful destruction, loss, alteration, unauthorised disclosure of, or access to, Customer Personal Data.
  • SCCs: the standard contractual clauses approved by European Commission Decision (EU) 2021/914. UK Addendum: the International Data Transfer Addendum issued by the UK Information Commissioner.
  • Sub-processor: a third party Elsin engages to process Customer Personal Data.

3. Roles and scope

The Customer is the controller and Elsin the processor, except for a few things Elsin controls itself, listed here.

For Customer Personal Data, the Customer is the controller (or a processor acting for its own controller) and Elsin is its processor (or sub-processor). Annex I sets out the subject matter, nature, purpose and duration of the processing, and the types of personal data and data subjects.

Elsin acts as an independent controller, under its privacy policy, for:

  1. candidates' own Elsin accounts, their reusable identity verification and their consent records, which the candidate controls and chooses to share with employers;
  2. keyed codes derived from Customer Personal Data and used across customers to detect identity fraud, which return only counts to any customer;
  3. Customer users' accounts, billing, security logs and support.

The Customer authorises the processing in point (b), which protects all customers from fraud, and confirms that its notices to candidates allow it.

4. Processing on instructions

Elsin uses Customer Personal Data only to provide the service, as the Customer instructs.

Elsin processes Customer Personal Data only on the Customer's documented instructions. The Agreement, this DPA, and the Customer's use and configuration of the service (including its settings, integrations, API keys and AI agents) are the Customer's complete instructions. Elsin will tell the Customer if it believes an instruction breaks Data Protection Laws, and may suspend that processing until the instruction is changed. If the law requires Elsin to process Customer Personal Data otherwise, Elsin will tell the Customer first unless the law forbids it.

The Customer is responsible for the lawfulness of its instructions, for having a lawful basis and giving the notices Data Protection Laws require, and for the accuracy of Customer Personal Data.

5. US state privacy laws

Elsin does not sell or share Customer Personal Data, and uses it only for the Customer's business purpose.

Where the CCPA or a similar US state law applies, Elsin is a service provider or processor and will not:

  • sell or share Customer Personal Data, as those terms are defined in the CCPA;
  • keep, use or disclose it for any purpose other than the business purposes in the Agreement, or outside the direct business relationship with the Customer, except as the CCPA permits, including to detect security incidents and protect against fraud;
  • combine it with personal data Elsin receives from or for others, except as the CCPA permits for those purposes.

Elsin will comply with the obligations that apply to it, give the same level of protection the law requires, and tell the Customer if it can no longer meet them. The Customer may take reasonable steps to stop and remedy unauthorised use. Elsin certifies that it understands and will comply with these restrictions.

6. Confidentiality of personnel

Everyone at Elsin who can access the data is bound to keep it confidential.

Elsin ensures that anyone it authorises to process Customer Personal Data is bound by a duty of confidentiality and accesses it only as needed to provide, secure or support the service.

7. Security

Elsin protects the data with the measures in Annex II and keeps them up to date.

Elsin implements and maintains appropriate technical and organisational measures to protect Customer Personal Data, taking into account the state of the art, the costs of implementation, and the nature, scope, context and purposes of the processing and the risks to people. The measures in place today are in Annex II. Elsin may update them, but will not materially reduce the overall protection they give.

8. Sub-processors

The Customer authorises the listed sub-processors. Elsin gives 30 days' notice of a new one, and the Customer can object.

  1. The Customer gives Elsin general authorisation to engage sub-processors. The current ones are in Annex III and on the sub-processors page.
  2. Elsin will update that page at least 30 days before a new sub-processor starts processing Customer Personal Data, and will email Customers that ask to be told.
  3. The Customer may object on reasonable data protection grounds within those 30 days. The parties will discuss it in good faith. If Elsin cannot offer a reasonable alternative, the Customer may end the affected part of the service and receive a refund of prepaid fees for it.
  4. Elsin will put in place, with each sub-processor, written terms that protect Customer Personal Data at least as well as this DPA, and remains responsible to the Customer for each sub-processor's performance.

Services the Customer connects (such as its applicant tracking system, background-check provider, HR system, calendar, video meetings or chat tool) are not Elsin's sub-processors. Elsin exchanges data with them on the Customer's instruction, under the Customer's own agreement with each.

9. International transfers

Elsin stores data in the United States. Where the law requires it, the Standard Contractual Clauses and the UK Addendum apply.

Elsin processes Customer Personal Data in the United States. Elsin is not currently offered to customers in the European Economic Area, the United Kingdom or Switzerland. Where a transfer of Customer Personal Data to Elsin is nonetheless subject to the GDPR or UK GDPR, the parties agree that:

  1. the SCCs are incorporated into this DPA: Module 2 (controller to processor) where the Customer is a controller, and Module 3 (processor to processor) where the Customer is a processor. The Customer is the data exporter and Elsin the data importer;
  2. in the SCCs, Clause 7 (docking) applies; under Clause 9(a), Option 2 (general authorisation) applies with the notice period in section 8; the optional language in Clause 11 does not apply; under Clause 13, the supervisory authority is the one that the Clause identifies for the data exporter, or the Irish Data Protection Commission where none is identified; under Clauses 17 and 18, the SCCs are governed by the law of Ireland and disputes go to the courts of Ireland;
  3. Annexes I, II and III of this DPA complete the corresponding annexes of the SCCs;
  4. for transfers subject to the UK GDPR, the UK Addendum applies, completed with the information in this DPA, and either party may end it as its Section 19 allows;
  5. for transfers subject to Swiss law, the SCCs apply with references to the GDPR read as references to the Swiss Federal Act on Data Protection, and the competent authority is the Swiss Federal Data Protection and Information Commissioner.

10. Helping with data subject requests

Elsin passes on any request it receives, gives the Customer tools to answer, and does the rest on request.

If Elsin receives a request from a data subject about Customer Personal Data, it will pass it to the Customer without undue delay and will not answer it except to say it has been passed on, unless the Customer asks it to.

Taking into account the nature of the processing, Elsin will help the Customer answer requests to access, correct, delete, restrict, port or object, through the following:

  • in the product: viewing and editing candidate records; deleting a single candidate, in the app, through the API or through the MCP server, which deletes that candidate's data in the Customer's workspace, stored files included; the per-hire data packet download; the full workspace export; the candidate's own download, consent withdrawal and account deletion; and automatic deletion of candidates whose applications have all been closed for a period the Customer sets;
  • on request, for anything the product does not do itself, or if the Customer prefers, including deleting or exporting a single candidate's data: Elsin will do it within 10 business days of the Customer's written instruction to contact@surfplatforms.com.

11. Personal data breaches

Elsin tells the Customer within 72 hours of becoming aware of a breach, and helps it respond.

Elsin will notify the Customer without undue delay, and in any case within 72 hours, after becoming aware of a Personal Data Breach. The notice will describe, as far as Elsin then knows, the nature of the breach, the categories and approximate number of people and records affected, the likely consequences, and the measures taken or proposed. Elsin will update the Customer as it learns more, take reasonable steps to contain and remedy the breach, and help the Customer meet its own duties to notify authorities and people. Notifying a breach is not an admission of fault.

12. Impact assessments and consultations

Elsin gives the Customer the information it needs for a data protection impact assessment.

Elsin will give the Customer reasonable help with data protection impact assessments and prior consultations with supervisory authorities about the service, using the information in this DPA, the privacy policy, the biometric data policy and, where needed, further information Elsin holds.

13. Return and deletion

A workspace owner can export and delete the workspace at any time. When the Agreement ends, the Customer has 30 days to ask for an export. Elsin then deletes the data within 30 days.

  1. At any time, a workspace owner can download an export of the workspace's Customer Personal Data, with its stored files, in common machine-readable formats (JSON and CSV), and can delete the workspace. Deletion takes effect after a 30-day grace period, during which any owner can cancel it; Elsin then deletes the workspace's Customer Personal Data, including stored files, from its production systems.
  2. For 30 days after the Agreement ends, the Customer may also ask Elsin at contact@surfplatforms.com for an export of Customer Personal Data in a common machine-readable format, and Elsin will provide it.
  3. Within 30 days after that period, or sooner if the Customer asks, Elsin will delete Customer Personal Data, including stored files, from its production systems. Deleted data rolls off our database backups within 7 days, inside that 30-day period, as those backups expire, and backups are never restored for use.
  4. Elsin may keep Customer Personal Data the law requires it to keep, protected under this DPA, for as long as the law requires.
  5. Data Elsin controls itself (section 3) is not part of this deletion and is handled under the privacy policy.

14. Information and audits

Elsin answers reasonable security questions and allows one audit a year on notice.

Elsin will make available the information reasonably needed to show that it meets this DPA, including written answers to reasonable security questionnaires. Elsin does not currently hold a third-party security certification or audit report.

If that information is not enough, or a supervisory authority requires it, the Customer (or an independent auditor it appoints, bound by confidentiality and not a competitor of Elsin) may audit Elsin's compliance with this DPA once a year, on at least 30 days' written notice, during business hours, in a way that does not disrupt the service or reveal other customers' data. The Customer bears its own costs. Audits under the SCCs are carried out the same way.

15. Liability and duration

The Agreement's limits of liability apply. This DPA lasts as long as Elsin processes Customer Personal Data.

Each party's liability under this DPA is subject to the limits and exclusions in the Agreement, except where Data Protection Laws or the SCCs do not allow it. This DPA lasts as long as Elsin processes Customer Personal Data, and the duties that by their nature should survive do so. It is governed by the law that governs the Agreement, except that the SCCs are governed as section 9 says. Surf Platforms Inc. may update this DPA to reflect changes in law or the service, without reducing its protection, by publishing a new version here.

16. Annex I: Details of processing

Who the data is about, what it is, why Elsin processes it, and for how long.

ItemDetails
PartiesData exporter: the Customer, as identified in its account, contact through its workspace owners. Data importer: Surf Platforms Inc., San Jose, California, United States, contact contact@surfplatforms.com. Role: processor.
Data subjectsThe Customer's job applicants and candidates, new hires, referees and other people candidates name, and the Customer's own users.
Categories of dataIdentity and contact details; résumés, application answers, work history, location and links; referees' names, email addresses and answers, and employment documents; interview schedules, notes, scorecards and messages; offer terms (including salary and equity), offer letters and electronic signatures, with IP address and browser; equipment shipping addresses; background-check status (never the report); verification outcomes and method, risk signals and review decisions; application and verification-step signals used to detect fraud (IP address and its class, approximate location derived from it, browser, operating system and device type, language, time zone, device fingerprint code, form timings and counts of pointer, key and paste events, automation indicators, keyed codes); profile facts from public records (GitHub account age and statistics, domain age) and phone country; hiring source; AI summaries the Customer asks for.
Sensitive dataThe outcome of the face comparison (no images or biometric measurements, which Elsin holds as controller under its biometric data policy); an ID photo where the candidate chooses review by a person, deleted once the Customer's reviewer decides; optional equal-opportunity survey answers, stored apart and reported only as totals with groups under five hidden. Safeguards: those in Annex II, and the restrictions on access described there.
FrequencyContinuous, for as long as the Customer uses the service.
Nature of processingCollection, storage, organisation, analysis for fraud signals, display, transmission to services the Customer connects, and deletion.
PurposeTo provide the Elsin service to the Customer: verifying applicants, detecting fraud and duplicates, and running the Customer's hiring.
Duration and retentionFor the term of the Agreement and section 13, subject to the Customer's retention settings and the retention periods in section 15 of the privacy policy.
Transfers to sub-processorsAs listed in Annex III, for the purposes stated there, for the duration above.

17. Annex II: Technical and organisational measures

The measures Elsin actually has in place today.

AreaMeasure
Access controlRow-level security on every database table limits each user to their own organisation's data and to what their role allows (viewer, interviewer, recruiter, admin, owner). Tables holding verification internals have no read access for any customer account.
Data minimisationIdentity checks run on the candidate's device. In the standard check, Elsin never receives face images, video, face templates or ID numbers; it receives a keyed code of the ID number and the outcome.
PseudonymisationIdentifiers used for cross-customer fraud checks are keyed with HMAC-SHA-256 using a secret held only by Elsin's servers. Production refuses to run without it.
StorageRésumés and ID documents are kept in private storage. Links to them are signed and expire after 30 minutes (résumés) or 2 minutes (ID documents). ID documents for review are readable only by Elsin's servers and shown to the reviewer through those links. When a record is deleted, its stored file is queued and removed.
CredentialsAPI keys are stored only as SHA-256 hashes, are limited by role and scope, and expire after 7 to 365 days (90 by default). AI agents use OAuth 2.1 with PKCE; access tokens last one hour. Keys and tokens for connected services are kept in an encrypted secrets store.
Abuse controlsRate limits on the API and on application and verification flows.
LoggingAn audit log of workspace actions and a log of every API and MCP call against the credential that made it, both kept for 2 years by default (the Customer can set 90 days to 10 years).
IntegrityReview decisions are kept as an append-only record naming the person who made them. Offer letters are stored with a SHA-256 digest of the exact text signed.
TransmissionAll connections to Elsin use HTTPS.
RetentionDaily jobs apply the Customer's retention settings for closed candidates and the logs, and the fixed periods in the privacy policy: among them, IP addresses replaced by keyed codes after 90 days, biometric data destroyed on the schedule in the biometric data policy, and unreviewed ID photos and employment documents deleted after 30 days. Each deletion of a candidate or workspace leaves a record of when, by whom and how many records, without personal data.
Human decisionThe database refuses a rejection that does not name the person who made it; no automated process rejects a candidate.

18. Annex III: Sub-processors

The sub-processors the Customer authorises, also listed on the sub-processors page.

Sub-processorPurpose and location
Supabase, Inc.: Database, sign-in, file storage and secretsHosts the Elsin database, sign-in accounts, résumés, uploaded documents and encrypted integration keys. Location: United States (AWS us-east-1, N. Virginia).
Vercel Inc.: Hosting, Web Analytics and Speed InsightsRuns 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. Location: United States (app functions in iad1, Washington, D.C.), with a global edge network.
Resend: Email deliverySends 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. Location: United States.
Stripe, Inc.: PaymentsTakes 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. Location: United States.
Microsoft Corporation: Azure AI FoundryWrites a résumé summary of a candidate when a manager at the employer asks for one. An employer can switch summaries off. Location: United States (Azure East US 2).

See also Sub-processors. The companies that process personal data to run Elsin, and what each one handles.