Data processing agreement
Last updated: 21 November 2026
This Data Processing Agreement ("DPA") forms part of the Terms of Service (the "Agreement") between Proppel Inc. ("Processor", "we") and the customer named in the Agreement ("Customer", "Controller"). It applies whenever we process Customer Personal Data while providing Proppel ATS (the "Service").
1. Definitions
- Data Protection Laws: all laws that apply to the processing, including the EU GDPR, the UK GDPR and Data Protection Act 2018, the Swiss FADP, US state privacy laws (including the California Consumer Privacy Act as amended by the CPRA), Brazil's LGPD, and other laws in Latin America that apply.
- Customer Personal Data: personal data in Customer Data that we process on the Customer's behalf.
- Subprocessor: a third party we engage to process Customer Personal Data.
- Security Incident: a breach of security leading to the accidental or unlawful destruction, loss, alteration, or unauthorised disclosure of or access to Customer Personal Data.
- "Controller", "processor", "data subject", "personal data", "processing" and "supervisory authority" have the meanings given in the GDPR. "Business", "service provider" and "sell" or "share" have the meanings given in the CCPA.
2. Roles
The Customer is the controller (or, under the CCPA, the business) and we're the processor (or service provider). Details of the processing are in Annex 1.
3. Customer's responsibilities
The Customer:
- has a lawful basis for the processing and gives data subjects the notices the law requires, including on its application forms and before recording calls
- gives lawful instructions only
- is responsible for the accuracy of the data and for the criteria and decisions it makes using the Service, including meeting laws on automated tools in hiring (such as NYC Local Law 144 and the EU AI Act) that apply to it as an employer
- doesn't put special category data (such as health, ethnicity, religion or criminal records) in the Service unless it has a lawful basis and it's necessary
4. Our obligations
We will:
- process Customer Personal Data only on the Customer's documented instructions. The Agreement, this DPA and the Customer's use of the Service's settings are those instructions. If we think an instruction breaks Data Protection Laws, we'll say so.
- make sure everyone authorised to process the data is bound by confidentiality
- put in place the security measures in Annex 2
- use Subprocessors only as section 6 allows
- help the Customer, taking into account the nature of the processing, to answer data subject requests (section 7), and with security, breach notification, data protection impact assessments and consultations with supervisory authorities
- delete or return Customer Personal Data at the end of the Service (section 9)
- make available the information needed to show we comply with this DPA, and allow audits (section 10)
US state law commitments. We won't sell or share Customer Personal Data, keep, use or disclose it outside our direct business relationship with the Customer or for any purpose other than providing the Service, or combine it with personal data we get from other sources, except as the CCPA allows a service provider to do. We'll tell the Customer if we can no longer meet the CCPA.
AI features. When the Customer uses AI features, we send the relevant data to our AI Subprocessor only to produce the requested output. Neither we nor that Subprocessor use Customer Personal Data to train AI models.
5. Security incidents
We'll notify the Customer without undue delay after becoming aware of a Security Incident affecting Customer Personal Data. We'll give the information we have (what happened, the data and people affected, likely consequences, and what we're doing about it), update it as we learn more, and take reasonable steps to contain it. Notifying the Customer isn't an admission of fault.
6. Subprocessors
- The Customer gives general authorisation for us to use Subprocessors. The current list is in Annex 3 and at proppelats.com/subprocessors.
- We'll post any new or replacement Subprocessor on proppelats.com/subprocessors at least 10 days before it starts processing Customer Personal Data. The Customer is responsible for checking that page.
- The Customer can object on reasonable data protection grounds within that period. We'll then work in good faith to find a solution. If we can't, the Customer's only remedy is to end the Agreement before the new Subprocessor starts, without a refund of fees already paid.
- We'll put contracts in place with each Subprocessor that give at least the same protection as this DPA, and we stay responsible for their performance.
7. Data subject requests
If we receive a request from a data subject about Customer Personal Data, we'll pass it to the Customer and won't answer it ourselves unless the Customer tells us to. The Service lets the Customer find, export, correct and delete candidate data, including merging duplicates and deleting calls with their transcripts. Where the Customer can't do something itself, we'll help.
8. International transfers
- Customer Personal Data is stored in the United States (Annex 3).
- For transfers from the EEA, the Standard Contractual Clauses adopted by the European Commission in Decision 2021/914 ("SCCs") apply and are incorporated by reference: Module 2 (controller to processor) and, where the Customer is itself a processor, Module 3. In those SCCs: clause 7 (docking) applies; clause 9 option 2 (general authorisation, with the notice period in section 6); the optional wording in clause 11 doesn't apply; clauses 17 and 18 are governed by the law and courts of Ireland; Annexes I to III are completed by Annexes 1 to 3 of this DPA.
- For transfers from the UK, the UK International Data Transfer Addendum to the SCCs applies, with Table 1 to 3 completed from this DPA, and either party may end it as allowed in Table 4.
- For transfers from Switzerland, the SCCs apply with references to the GDPR read as references to the FADP, and the supervisory authority is the FDPIC.
- Where a Subprocessor is certified under the EU-US Data Privacy Framework (and its UK and Swiss extensions), we may rely on that instead.
- For transfers from Brazil, we'll use the standard contractual clauses issued by the ANPD where the LGPD requires them.
9. Return and deletion
During the Service, the Customer can export its data at any time. When the Service ends, the Customer has 14 days to export. We then delete Customer Personal Data within 90 days, and from backups as they roll over, unless the law requires us to keep it. We'll confirm deletion in writing on request.
10. Audits
We'll answer the Customer's reasonable security questionnaires, no more than once a year. If that isn't enough to show compliance, or a supervisory authority requires it, the Customer may audit us (or use an independent auditor bound by confidentiality) on at least 30 days' notice, during business hours, at its own cost (including our reasonable time), no more than once a year, and in a way that doesn't put other customers' data at risk.
11. Liability and order of precedence
Each party's liability under this DPA is subject to the limits in the Agreement. There's no separate or higher cap for data protection. If this DPA and the Agreement conflict on data protection, this DPA wins. If the SCCs conflict with this DPA, the SCCs win.
12. Term
This DPA lasts as long as we process Customer Personal Data for the Customer.
Annex 1: Details of the processing
| Controller | The Customer, as identified in the Agreement. Contact: the account owner. |
| Processor | Proppel Inc., 1111B S Governors Ave, STE 37957, Dover, DE 19904, United States. Contact: hello@proppelats.com |
| Subject matter | Providing an applicant tracking system for the Customer's own hiring |
| Duration | The term of the Agreement, plus the deletion period in section 9 |
| Nature and purpose | Hosting, storing, organising, displaying, searching, sending emails about, and analysing data (including with AI) so the Customer can plan roles, receive applications, run interview processes and make hiring decisions |
| Data subjects | Candidates and applicants; the Customer's Users (employees, contractors, interviewers); referees and other people named in candidate records; people who take part in recorded or transcribed calls |
| Categories of data | Identity and contact details (name, email, phone, country, LinkedIn); CVs and their content (work history, education, skills, and anything else the candidate includes); answers to application and knockout questions (such as location, English level, salary expectations, work authorisation); notes, scorecards and stage history; call notes, recaps and transcripts; emails sent and received through the Service; AI fit reviews and their history; consent records; technical data (IP address, browser, log data; for spam protection, only a hash of the applicant's IP address is kept) |
| Special category data | Not intended. Candidates may include it in a CV or the Customer may record it. Protected by the measures in Annex 2. |
| Frequency | Continuous |
| Retention | Set by the Customer. By default, candidates are deleted or anonymised after 12 months unless they agree to stay on file. |
Annex 2: Security measures
- Encryption: TLS for all data in transit; AES-256 at rest for the database and file storage (provided by our hosting Subprocessors).
- Customer separation: every business table carries a workspace identifier and is protected by row level security in the database, so access is enforced in the database itself, not only in the app. Automated security tests check these rules.
- Access control: role based access in the Service (admin, hiring manager and others). Our staff access production data only when needed to support the Customer or keep the Service running, with access limited to named people and multi-factor authentication on admin accounts.
- Authentication: passwords stored hashed by our authentication provider; sign-in with Google available; two-factor login available to every User.
- Logging: an append only history log records stage moves, notes, changes and settings switches in each workspace. Server and access logs are kept for 90 days.
- Backups: daily backups of the production database, kept for up to 30 days.
- Environments: separate production and test databases. Real customer data isn't used in testing.
- Application form protection: spam and abuse controls, including rate limits per connection.
- AI controls: account wide and per role switches for fit reviews; every fit review kept with the criteria, CV and model it used; no automatic rejection.
- Vulnerability management: dependencies kept up to date; regular reviews of the code and the database security rules.
- Incident response: a documented plan for finding, containing and notifying about Security Incidents.
- Staff: confidentiality obligations for everyone with access, and training on data protection.
Annex 3: Subprocessors
The current list of Subprocessors, with what each one does and where it processes data, is published at proppelats.com/subprocessors and forms this Annex 3.