AvalaAvala
නීතිමය තොරතුරු

Data Processing Addendum

අවසන් යාවත්කාලීනය: 2026 ඉල් 6අනුවාදය: 2026-11-06

This Data Processing Addendum ("DPA") is between Avala AI, Inc. ("Avala") and the customer that incorporates it ("Customer"). "Customer Data" has the meaning given in the Master Services Agreement. "Data Protection Laws" means the privacy and data-protection laws that apply to the Customer Data Avala processes under the Agreement, including the GDPR, the UK GDPR, the Swiss Federal Act on Data Protection, and the California Consumer Privacy Act as amended. "Security Incident" has the meaning in Section 6. "Subprocessor" means a third party Avala engages to process Customer Data, other than Avala's own personnel and affiliated operating entities. "Agreement" means the Master Services Agreement and each statement of work ("SoW") that references this DPA.

Opening this page does not by itself create a contract. The standard text is published here so a customer can read it before signing.

1. Scope and roles

1.1 Scope

This DPA applies to Avala's processing of Customer Data under the Agreement. It does not apply to Capture Data that Avala licenses to a customer under the Dataset License. Avala is an independent controller of Capture Data it collects. For a licensed copy, the Dataset License controls.

1.2 Processor role

For Customer Data, Avala is the processor, and Customer is the controller. Where the California Consumer Privacy Act applies, Avala is a service provider.

1.3 Instructions

Avala processes Customer Data only on Customer's documented instructions, which are the Agreement, this DPA, and the settings Customer uses in Mission Control, unless the law requires otherwise. If Avala believes an instruction violates Data Protection Laws, Avala will tell Customer.

1.4 Customer responsibilities

Customer is responsible for the lawfulness of the Customer Data it provides, for the notices it gives to data subjects, and for the instructions it gives Avala.

1.5 Acceptance

This DPA applies to every Master Services Agreement and SoW that references it, or on countersignature. A signed negotiated DPA prevails over this page for that customer. Visiting this page does not form a contract. The Master Services Agreement still says the parties will execute a data processing addendum at Customer's reasonable request if required by applicable law.

2. Nature of the processing

The roles in this Section 2 are a contractual allocation, not a determination of status under any Data Protection Law.

Avala processes Customer Data to provide the Services: ingest, storage, visualization, annotation, quality review, and delivery of Deliverables. The duration is the term of the Agreement, plus the deletion period in Section 10. The categories of data and data subjects are in Exhibit A.

Avala's own personnel and affiliated operating entities are not Subprocessors. A third party that processes Customer Data for Avala is a Subprocessor and is listed under Section 7.

3. Customer instructions and service-provider limits

3.1 Documented instructions

Avala will not process Customer Data except as Section 1.3 allows.

3.2 Confidentiality of personnel

Avala will ensure that persons authorized to process Customer Data are bound by a duty of confidentiality.

3.3 No sale

Avala will not sell or share Customer Data and will not combine it with personal information received from another customer, except as Data Protection Laws permit for a service provider.

3.4 Service-provider restrictions

Avala will not retain, use, or disclose Customer Data for any purpose other than the Services, and will not retain, use, or disclose it outside the direct business relationship with Customer, except as Data Protection Laws permit.

3.5 CCPA certification

Avala certifies that it understands the restrictions in Section 3.4 and will comply with them. Avala will notify Customer within 5 business days if Avala determines that it can no longer meet its obligations under the California Consumer Privacy Act. Customer may take reasonable and appropriate steps to stop and remediate unauthorized use of Customer Data. These terms are the service-provider terms in Cal. Code Regs. tit. 11, section 7051(a).

4. Use of Customer Data

4.1 Purpose limit

Avala uses Customer Data to provide the Services and as the Agreement otherwise permits.

4.2 No secondary use

Avala will not use Customer Data to market to data subjects in that data, and will not disclose it to a third party for that third party's own purposes.

4.3 Model training

Avala may train, fine-tune, and improve auto-labeling and related models using Customer Data solely (a) to provide the Services to Customer and (b) to develop and improve Avala Technology in ways that do not embody, identify, or expose Customer Data, Deliverables, or Customer's confidential information. Avala will not provide Customer-specific fine-tuned model weights or Customer-derived training data to any third party, and will not use Customer Data to train models that are sold or licensed to any direct competitor of Customer (e.g., other developers or operators of comparable autonomous systems, vehicles, or robots, or a specific list of competitors provided by Customer in writing from time to time).

4.4 Identification

Avala will not use Customer Data to identify a person. Annotation of objects, lanes, and similar labels that the customer requested is allowed, including where a person appears in the scene. That annotation is not identification of the person. Avala will not extract a face, hand, gait, or voice template from Customer Data for identification.

4.5 No combination for identification

Avala will not combine Customer Data with other datasets for the purpose of identifying a person in it.

5. Security

5.1 Program

Avala will maintain the administrative, technical, and physical safeguards in Exhibit B, and a written security program consistent with SOC 2 controls for a service provider in Avala's industry.

5.2 No material reduction

Avala will not materially reduce the safeguards in Exhibit B during the term. A change that keeps the same or a better level of protection is not a material reduction.

5.3 Changes

Avala may update the safeguards as its platform changes, subject to Section 5.2. Customer does not have a veto over those changes.

5.4 Personnel and access

Avala limits access to Customer Data to personnel and Subprocessors who need it to provide the Services, and only for that purpose.

6. Security Incidents

6.1 Notice

Avala will notify Customer in writing without undue delay and within 72 hours after Avala becomes aware of a Security Incident. "Security Incident" means an unauthorized access to, or acquisition of, Customer Data in Avala's possession or control.

6.2 Contents

The notice will describe, to the extent known, the nature of the Security Incident, the categories of Customer Data affected, the measures Avala has taken, and a contact for further information. Avala may give that information in stages as it learns more.

6.3 Cooperation

Avala will reasonably cooperate with Customer to investigate and mitigate the Security Incident.

6.4 No admission

A notice under this Section 6 is not an admission of fault.

7. Subprocessors

7.1 General authorization

Customer gives Avala general authorization to engage Subprocessors. The current list is the Subprocessors page, which is incorporated by reference.

7.2 Flow-down

Avala will bind each Subprocessor to written terms that require protection of Customer Data consistent with this DPA. Avala remains responsible for a Subprocessor's processing of Customer Data to the same extent Avala would be if it did the processing itself.

7.3 Changes

Avala will give at least 30 days' notice of a new Subprocessor that processes Customer Data, through the subscription mechanism on the Subprocessors page. Customer may object in writing within 15 days on reasonable data-protection grounds. If the objection is not resolved within 30 days, Customer may terminate the affected SoW without penalty. Silence is not an objection, and silence is not a rejection.

7.4 Emergency replacement

Avala may replace a Subprocessor immediately where necessary to address a security or continuity risk, and will give notice as soon as practicable. Section 5.2 still applies.

7.5 List accuracy

Avala will keep the Subprocessors page aligned with the vendors named in Section 4 of the Privacy Policy.

8. Data subject requests

8.1 Notice to Customer

Avala will notify Customer of a data subject request that Avala receives and that relates to Customer Data, within 5 business days, unless the law prohibits the notice.

8.2 Assistance

Avala will assist Customer, taking into account the nature of the processing, with reasonable technical and organizational measures so Customer can respond to the request.

8.3 No independent response

Avala will not respond to the request itself except to tell the person to contact Customer, or where the law requires Avala to respond.

8.4 Cost

Assistance that goes beyond what the Services already provide is at Customer's reasonable cost, unless the request arose from Avala's breach of this DPA.

9. Location of processing

9.1 Approved locations

The default approved locations are the places where Avala actually processes Customer Data. Those places are the locations on the Subprocessors page and Avala's workforce locations. They include, at a minimum, the United States and Kenya. They also include India, Ireland, the United Kingdom, and Cloudflare's edge network, to the extent a listed Subprocessor processes Customer Data there.

9.2 Customer restriction

A customer may restrict locations in a SoW. Avala will process that customer's Customer Data only in the locations the SoW allows.

9.3 Additions

A new location follows the notice route in Section 7.3. Avala does not add a location for Customer Data by sole discretion, and Customer has no unilateral right to revoke an approved location on 30 days' notice outside Section 7.3.

9.4 Workforce

Avala's personnel may access Customer Data from an approved location to provide the Services, under Section 5.4.

9.5 No extra copies

Avala will not move Customer Data to a location that is not approved under this Section 9 in order to avoid a restriction in a SoW.

10. Deletion and return

10.1 Timing

Avala will delete or return Customer Data within 30 days of Customer's written request or of termination or expiration of the Agreement. Encrypted backups are purged on the normal cycle and within 90 days. Avala may keep trained model weights and anonymized metrics developed in compliance with Sections 5.4 and 5.5 of the Master Services Agreement. A SoW may set a shorter raw-data retention.

10.2 Return format

If Customer asks for return, Avala will return Customer Data in a reasonable format the Services already support, and then delete it under Section 10.1.

10.3 Certification

Within 10 days after Avala completes the deletion, an officer of Avala will sign a written certification that the deletion is complete, subject to the backups and retained weights and metrics in Section 10.1.

11. Aggregated metrics

11.1 Ownership and use

Avala may collect and generate anonymized, aggregated operational metrics derived from the Services (e.g., throughput, accuracy distributions, system telemetry). As between the Parties, Avala solely and exclusively owns all right, title, and interest in and to such anonymized metrics, and Customer hereby assigns to Avala any rights it may have therein. To the extent any such rights are not assignable, Customer grants Avala a perpetual, irrevocable, worldwide, royalty-free, fully paid-up, sublicensable license to use and exploit those rights. Avala will not publicly disclose Customer's identity, Customer Data, or Customer-specific Deliverables without Customer's prior written consent, except as expressly permitted in Section 5.8 (Customer Identification) of the Master Services Agreement.

Avala may use those metrics to operate and improve the Services. Avala will not re-identify them. Nothing in the metrics identifies Customer.

11.2 No product restriction beyond Section 11.1

Section 11.1 is the whole of Avala's right to use aggregated metrics. It does not ban Avala from using those metrics to develop the Services.

12. Audits

12.1 Reports and questionnaires

Avala's current SOC 2 report, as offered to customers at trust.avala.ai as of November 6, 2026, plus written answers to a reasonable security questionnaire, satisfy the audit right. This page does not restate an audit period or a report type that is not printed on those materials.

12.2 Scope

An audit covers Avala's compliance with this DPA for that customer's Customer Data. It does not include another customer's data, and it does not include access to source code except as needed to resolve the documented concern.

12.3 Confidentiality

Audit findings are Customer's confidential information, and Avala's security details disclosed in the audit are Avala's confidential information.

12.4 On-site or remote audit

An on-site or remote audit is available once per 12 months, on 30 days' notice, at Customer's cost. It is available only for a specific documented concern that the report in Section 12.1 does not resolve, or after a Security Incident. Remediation of a failure the audit confirms is at Avala's cost.

13. Liability and term

13.1 Liability and indemnity

Liability under this DPA is liability under the Master Services Agreement, including the super-cap in Section 9.3 of that agreement for indemnities. Each party will indemnify the other for its own breach of this DPA or of Data Protection Laws, subject to the limits in the Agreement. A breach of this DPA is not, by itself, deemed a breach of the privacy, data security, confidentiality, and data-use obligations of the Agreement.

13.2 Conflict

If this DPA conflicts with the Master Services Agreement on a subject this DPA covers, this DPA controls for that subject. A signed negotiated DPA controls over this page, as Section 1.5 says.

13.3 Term

This DPA lasts for as long as Avala processes Customer Data under the Agreement.

13.4 Survival

Sections 10, 11, 12, and 13 survive for as long as their subject matter requires.

13.5 Order of precedence with a SoW

A SoW may restrict locations or shorten retention, as Sections 9.2 and 10.1 allow. It does not reduce Exhibit B.

13.6 Notices

Notices under this DPA follow the notice clause of the Master Services Agreement. Notices to Avala may be sent to legal@avala.ai.

13.7 Governing law

This DPA is governed by the law and venue in Section 11.2 of the Master Services Agreement.

Exhibit A. Processing details

The SoW supplies the specifics of a customer's engagement. In general, Customer Data includes sensor recordings and related files the customer uploads, annotations and labels, account identifiers of the customer's users, and support correspondence about that data.

Data subjects include the customer's personnel who use Mission Control, and individuals who incidentally appear in sensor data the customer uploads. The parties do not intend Avala to extract, derive, or annotate gait, biometric identifiers, or behavioral characteristics from Customer Data.

Processing is the Services described in Section 2, for the term described there.

Exhibit B. Security measures

ControlMeasure
Encryption in transitCustomer Data is encrypted in transit using industry-standard transport encryption.
Encryption at restCustomer Data stored by Avala is encrypted at rest.
Access controlAccess is limited to personnel and Subprocessors who need it, and is revoked when that need ends.
PersonnelPersons who can access Customer Data are bound by confidentiality.
Browser platformCustomer Data is accessed through the browser platform. Annotators do not download Customer Data to a personal device. Browser-platform access inside the secured environment is the access this row allows, and it is not a download.
LoggingAvala logs administrative access to production systems that store Customer Data.
BackupsEncrypted backups follow Section 10.1.
Incident responseAvala maintains a process for investigating and notifying a Security Incident under Section 6.
SubprocessorsSubprocessors are bound under Section 7 and listed on the Subprocessors page.
Third-party attestationAs of November 6, 2026, Avala offers customers the SOC 2 report published at trust.avala.ai. That report, together with written answers to a reasonable security questionnaire, is the attestation this row refers to. This page does not state an audit period or a report type that is not printed on that report.

Exhibit C. Subprocessors and affiliated operating entities

The Subprocessors are the vendors on the Subprocessors page. That page is incorporated by reference. Changes follow Section 7.3.

Avala has no affiliated operating entities that process Customer Data. If that changes, the change follows Section 7.3.

Exhibit D. International transfer terms

Where Customer Data is transferred from the European Economic Area, the United Kingdom, or Switzerland to a country that has not been found to provide adequate protection, the transfer uses:

  • The European Commission's Standard Contractual Clauses, Module 2 (controller to processor) and Module 3 (processor to processor), incorporated by reference. The annexes are Exhibit A (description of the transfer), Exhibit B (technical and organizational measures), and Exhibit C (Subprocessors). Avala completes those annexes with the details on this page. A separate annex file is provided with an executed copy when the customer asks for one.
  • The UK International Data Transfer Addendum, with the tables completed by the same exhibits.
  • The Swiss adjustments required so the clauses apply to transfers from Switzerland, including the competent authority being the Swiss Federal Data Protection and Information Commissioner.
  • Where the EU-U.S. Data Privacy Framework, the UK Extension, or the Swiss-U.S. Data Privacy Framework covers the transfer of non-HR personal data, Avala may rely on that participation, as the Privacy Policy describes. Where it does not cover a transfer, the clauses above are the transfer basis.
  • Supplementary measures as the parties reasonably agree when a transfer impact assessment shows they are needed.

Customer does not have a unilateral right to suspend transfers. A dispute about a transfer follows the Agreement.

If these transfer terms conflict with the Standard Contractual Clauses, the clauses control for that transfer. Otherwise this DPA controls.

Contact

Email: legal@avala.ai

Address: Avala AI, Inc., 403 Broderick Street, Unit 3, San Francisco, CA 94117