ELA · LEGAL & PRIVACY

Data Processing Agreement

Pre-launch information. ELA is a product brand being prepared for launch. Company registration and certain operational details are pending. This page describes the intended approach and must be updated if actual practices differ. Do not submit CVs, sensitive personal information, or confidential material through this marketing website.

Important

This page is an outline only and is not a signed DPA. A complete agreement must identify the parties, processing details, security measures, subprocessors, transfer mechanisms and applicable legal requirements. Obtain legal review before using it with customers.

1. Parties and roles

Parties must be identified in the customer-specific agreement before processing begins. ELA’s operating legal entity is not yet registered, so this public page does not identify a contracting processor and is not an agreement between parties. The customer’s documented instructions and actual service determine the processing roles.

2. Processing details

Subject matter: recruitment and applicant-tracking services. Duration: the subscription term and any agreed deletion period. Data subjects may include candidates, customer personnel and business contacts. Data types may include contact details, CVs, work history, qualifications, communications, application records and user account data.

3. Processor obligations

The final DPA should cover documented instructions, confidentiality, appropriate technical and organisational security measures, assistance with data-subject requests, breach notification, audits, deletion or return of data, and restrictions on subprocessors and international transfers.

4. Subprocessors and transfers

Insert the actual hosting, email, messaging, monitoring, support and backup providers, relevant locations, transfer safeguards and notification process. Do not publish a generic list unless it matches the production environment.

5. Security schedule

Attach verified controls covering access management, encryption, backups, logging, vulnerability management, incident response, business continuity and personnel access. Do not claim controls that have not been implemented and tested.

6. Execution

This outline is not an offer or binding agreement. A customer-ready DPA must be separately approved, versioned and executed by the parties.