Version 1.0 · Effective October 14, 2026 · Permanent link to this version: /dpa/v1

SETTLE DATA, INC. - DATA PROCESSING ADDENDUM

Version: 1.0

Effective Date: October 14, 2026

This Data Processing Addendum (“DPA”) forms part of the Terms of Use between Settle Data, Inc. (“Company”) and Customer, together with accepted purchases and any separately executed agreement that expressly incorporates this DPA (collectively, the “Agreement”). It takes effect when Customer accepts the Agreement incorporating it, without requiring a separate signature to this standard DPA. Capitalized terms not defined here have the meanings given in the Agreement. This DPA applies to Company’s processing of Customer Personal Data in both free and paid Services, including where Customer processes information for its own clients.

The security, retention, and deletion commitments in this DPA’s Security Schedule and Retention Schedule also apply contractually to all Customer Data, whether or not it is personal data, as provided in Section 7 of the Terms. Their placement in this DPA does not narrow that application. Provisions specific to personal data and particular data-protection laws apply according to their stated scope.

This DPA governs its stated processing subject matter, subject to the Agreement’s order of precedence and Section I.3 below. It does not change purchased functionality, prices, the Restricted Data rules, or the Agreement’s financial remedies.

A separately executed replacement data processing agreement controls only to the extent expressly provided in that agreement. Updates to this DPA and its schedules are governed by Section K.3; publication alone does not amend an existing signed agreement.

A. Definitions

A.1. "Applicable Data Protection Laws" means privacy, data-protection, and data-security laws and binding regulations applicable to the relevant party’s processing under the Agreement, including, to the extent applicable, the GDPR, UK GDPR and Data Protection Act 2018, the Swiss Federal Act on Data Protection, applicable U.S. federal and state privacy laws including the CCPA, and applicable Canadian federal or provincial privacy laws. References include applicable amendments and successor provisions. Naming a law does not make it applicable to processing outside its scope.

A.2. "Customer Personal Data" means personal data in Customer Data that Company or a Subprocessor processes on Customer’s behalf in connection with the Services, including personal data in source records, normalized or derived copies, customer-specific mappings and results, AI Input or AI Output, and associated records processed on Customer’s behalf. Protection under this DPA is not lost merely because data is generated, inferred, labeled metadata, or submitted contrary to a use restriction.

A.3. Reserved.

A.4. “Customer Data” has the meaning given in the Agreement.

A.5. “Data Subject Request” means a request from a data subject to exercise their personal data-related rights under Applicable Data Protection Laws, such as rights to access, correct, or delete their personal data.

A.6. "GDPR" means Regulation (EU) 2016/679.

A.7. "Security Breach" means a breach of security leading to accidental or unlawful destruction, loss, alteration, unauthorized disclosure of, or access to Customer Personal Data processed by Company or a Subprocessor in connection with the Services. An unsuccessful attempt that does not compromise the confidentiality, integrity, or availability of Customer Personal Data is not itself a Security Breach.

A.8. "Standard Contractual Clauses" or “SCCs” means Module Two (controller to processor) or Module Three (processor to processor) of the Standard Contractual Clauses for the transfer of personal data to third countries pursuant to Regulation (EU) 2016/679 of the European Parliament and the Council approved by European Commission Implementing Decision (EU) 2021/914 of 4 June 2021, available at https://eur-lex.europa.eu/eli/dec_impl/2021/914/oj.

A.9. "Subprocessor" means a third party engaged by Company to process Customer Personal Data on Customer’s behalf in connection with the Services.

A.10. “UK Addendum” means the International Data Transfer Addendum to the EU Commission SCCs, version B.1.0, as revised under its mandatory change mechanism, available at https://ico.org.uk/media2/migrated/4019539/international-data-transfer-addendum.pdf.

A.11. The terms “personal data”, “data subject”, “processing”, “controller”, and “processor” as used in this DPA have the meanings given by Applicable Data Protection Laws or, absent any such meaning or law, by GDPR.

A.12. References to “controller” and “processor” include the corresponding roles of business and service provider or contractor where applicable under U.S. Privacy Laws; the parties’ actual roles depend on the relevant processing and law.

A.13. “UK GDPR” means Regulation (EU) 2016/679 as it forms part of the law of England and Wales, Scotland and Northern Ireland by virtue of Section 3 of the European Union (Withdrawal) Act 2018, as amended.

A.14. “CCPA” means the California Consumer Privacy Act of 2018, as amended by the California Privacy Rights Act, and its binding regulations.

A.15. “U.S. Privacy Laws” means U.S. federal and state privacy laws applicable to the relevant processing.

A.16. “Security Schedule” means Schedule 2, “Subprocessor List” means Schedule 4, and “Retention Schedule” means Schedule 5.

B. Processing of Customer Data

B.1. For Customer Personal Data, Company acts as Customer’s processor. Where Customer acts as a processor for another controller, Company acts as its subprocessor. Customer is responsible for having authority from the relevant controller for the instructions and appointment. Each party will comply with the obligations applicable to its actual role. The processing details are in Schedule 1. This DPA does not itself establish joint controllership. Customer’s representations and warranties in the paragraph headed “Customer Data authority” in Section 6 of the Terms apply to Customer Personal Data processed under this DPA and do not reduce Company’s obligations under this DPA.

B.2. Company will process Customer Personal Data only to provide, secure, support, and maintain the contracted Services and implement Customer’s documented lawful instructions, including the Agreement, this DPA, accepted Project configurations and approvals, Customer’s organization/project AI settings, and authorized written requests. These instructions include the transfers described in this DPA. Company will inform Customer of a legal requirement to process outside those instructions before doing so unless prohibited by law, and will comply with Section I and applicable transfer clauses. A third-party demand does not by itself enlarge permitted processing.

B.3. Without limiting the foregoing, Company will not:

B.3.a. “sell” or “share” Customer Personal Data, as defined by Applicable Data Protection Laws;

B.3.b. retain, use, or disclose Customer Personal Data (i) outside the direct business relationship between Company and Customer, or (ii) for any purpose other than the specified business purposes in Part B of Schedule 1, except to the extent permitted by Applicable Data Protection Laws and this DPA; and

B.3.c. except as otherwise permitted by Applicable Data Protection Laws, combine Customer Personal Data with personal data that Company receives from or on behalf of another person or persons, or collects from its own interaction with the data subject.

An exception permitted by law does not grant a contractual data-use right broader than the Agreement. Neither this DPA nor a schedule authorizes model training, cross-context behavioral advertising, or use of Customer’s identifiable content for another customer.

B.4. As required under Applicable Data Protection Laws, Company will promptly inform Customer if it makes a determination that it can no longer comply with its processing obligations under this DPA, in which case Customer may take reasonable and appropriate steps in accordance with the Agreement to stop or remediate any unauthorized processing of Customer Personal Data.

B.5. Company will promptly inform Customer if, in its opinion, an instruction from Customer relating to the processing of Customer Personal Data violates Applicable Data Protection Laws.

Company may pause the affected processing while the parties resolve that instruction, but this does not suspend unrelated protective duties or override mandatory return/deletion or transfer requirements. Service suspension and termination otherwise remain governed by the Agreement.

B.6. Taking into account the nature of processing and information available to it, Company will provide reasonable and timely assistance with Customer’s applicable obligations concerning security, breach notification, data protection and transfer impact assessments, required U.S. privacy risk assessments, and prior consultation or inquiries from competent authorities. Assistance includes available information necessary for those purposes. Any permitted charge is subject to Section K.2 and does not condition performance of a mandatory obligation on a new agreement or payment.

B.7. Company will ensure that each person it authorizes to process Customer Personal Data is subject to an appropriate duty of confidentiality and may access Customer Personal Data only on a need-to-know basis to perform an authorized function.

B.8. Company will honor the AI data access controls and no-training commitments in Section 5 of the Terms. Those controls are documented instructions, not permission to process Restricted Data. The applicable table-field protections, schema-only processing, assistant messages, and context-document channels have the same scope as in the Terms. This DPA does not promise a complete no-data mode, customer-supplied model key, or automatic filtering across message and document channels.

B.9. This DPA does not authorize any Restricted Data prohibited by Section 4 of the Terms or replace its category-specific signed-addendum requirement. Describing a data category in Schedule 1 is not permission to submit it. If Company nevertheless receives prohibited data, its applicable security, confidentiality, incident-response, and lawful deletion obligations continue; receipt does not become authorized merely because this DPA protects the data.

B.10. Personal information Company independently collects to administer its own account, billing, sales, and business relationships is addressed in the Privacy Policy to the extent Company actually processes that information for its own lawful purposes. Treatment of support, analytics, security, and fraud-prevention information depends on the specific information and processing purpose, not on its label. This does not remove imported contact records, Customer’s client records, Project records, or personal data processed on Customer’s behalf from this DPA merely because similar fields appear in Company’s own business records or are included in a support ticket or log. It grants no new own-purpose processing right. Treatment of any narrowly retained legal-claims record is subject to Section H.4.

B.11. Company may use operational metrics only to the extent already permitted by Section 6 of the Terms: for service maintenance and improvement, excluding customer content and with deidentification where legally required. Company will not attempt reidentification. This provision does not authorize Company to extract or repurpose Project content, messages, context documents, or customer-specific results for its own analytics or to train or fine-tune models. Any processing of Customer Personal Data to produce metrics must itself comply with Customer’s documented instructions and this DPA. Metrics that remain personal data remain subject to Applicable Data Protection Laws and, where processed on Customer’s behalf, this DPA; pseudonymization or an analytics label does not remove those protections.

C. Subprocessors

C.1. Customer grants Company general authorization to engage the Subprocessors listed in Schedule 4, and any additional Subprocessors in accordance with Section C.3. below.

C.2. Before permitting a Subprocessor to process Customer Personal Data, Company will enter into a written agreement imposing the applicable data-protection obligations required by this DPA and Applicable Data Protection Laws, including sufficient security, confidentiality, assistance, breach-notification, onward-processing, transfer, and deletion obligations. Company remains responsible to Customer for the Subprocessor’s performance of those obligations. The Agreement’s liability provisions apply to the extent permitted by applicable law and the mandatory transfer clauses; they do not eliminate that responsibility.

C.3. Company will give Customer at least thirty (30) calendar days’ advance written notice before an additional or replacement Subprocessor first processes Customer Personal Data on Customer’s behalf. The notice will identify the provider, activities, data categories, and processing countries and will be sent to Customer’s designated privacy contact or, absent one, its account notice email. Company may send the notice through an automated email-notification process; it need not be individually composed or sent to every Authorized User. Updating a website without that notice is not sufficient, and Customer is not required to subscribe separately to receive it.

Notwithstanding the foregoing, where an additional or replacement Subprocessor is required on shorter notice to address an urgent security, legal, regulatory, or service-continuity need, or results from a change initiated by an existing Subprocessor or its upstream providers on less than thirty (30) calendar days’ notice to Company, Company may provide shorter notice to Customer. In that circumstance, Company will provide notice as soon as reasonably practicable and will otherwise comply with the objection and protection requirements of this Section C.3.

Customer may object within fifteen (15) calendar days after notice on reasonable grounds concerning protection of Customer Personal Data, identifying those grounds in writing to privacy@settledata.com. The parties will work in good faith to resolve a timely objection. If Customer does not object within that period, the notified appointment is authorized after the applicable notice period under this Section C.3 has expired, but Customer’s silence does not waive Company’s continuing data-protection duties. A timely unresolved objection does not authorize Company to send that Customer’s data to the disputed Subprocessor.

If the parties cannot reasonably resolve a timely objection, either may terminate only the affected Services by written notice before the disputed processing begins. For that termination, the financial treatment in Section 15.3 of the Terms applies to the affected Services, without duplicate recovery. This does not make termination the exclusive remedy for an independent breach or override mandatory rights. Company need not build a custom replacement service or agree to an unreasonable technical alternative, and may not unilaterally impose new charges to resolve the objection.

C.4. The prior-notice, objection, authorization, and affected-service termination procedures in Section C.3 also apply contractually before an additional or replacement provider engaged by Company to process Customer Data on Customer’s behalf first processes that Customer’s nonpersonal Customer Data. For that limited application, references in Section C.3 to a “Subprocessor” and “Customer Personal Data” mean the relevant provider and nonpersonal Customer Data, respectively, and reasonable grounds for objection may concern the confidentiality or security of that data. Such providers must be identified in Schedule 4. This paragraph does not extend personal-data-specific statutory or SCC obligations to nonpersonal information.

D. Data Subject Requests

D.1. Company will forward to Customer promptly any Data Subject Request received by Company relating to the Customer Personal Data and may advise the Data Subject to submit their request directly to Customer.

D.2. Company will, taking into account the nature of the processing, provide Customer with reasonable and timely assistance as necessary for Customer to fulfill its obligation under Applicable Data Protection Laws to respond to Data Subject Requests.

D.3. Company will not independently resolve a Data Subject Request concerning Customer Personal Data except on Customer’s instructions or where law requires; it may acknowledge receipt and direct the requester to Customer. Available self-service tools may be used, but their absence does not eliminate Company’s required assistance. Company will cooperate sufficiently promptly to allow Customer to meet applicable deadlines. Deletion will be completed without undue delay in accordance with Schedule 5 and Section H, and that standard is not permission to miss a shorter mandatory deadline.

E. Security

E.1. Company will comply with the data security obligations of Applicable Data Protection Laws, and will implement and maintain reasonable and appropriate technical and organizational data protection and security measures designed to ensure a level of security for all Customer Data (including Customer Personal Data) appropriate to the risk of the relevant processing, as summarized in the Security Schedule. Company may update these measures from time to time only in accordance with Section K.3 and Terms Section 17.2, and may not use an implementation update to reduce an express security commitment.

E.2. Customer remains responsible for determining whether its authorized use and configuration meet its obligations, without reducing Company’s duties under this DPA. Customer’s acceptance is not a waiver of those duties or a representation that any particular measure is legally sufficient. Company’s security obligations are not displaced by the availability of a cloud provider’s controls or certifications.

F. Compliance and Audits

F.1. Company will make available information reasonably necessary to demonstrate compliance with this DPA, including its then-current independent reports, certifications, or assessment materials applicable to the Services, if any, subject to appropriate confidentiality restrictions. Available materials may satisfy a request to the extent they adequately address it; they are not the exclusive response where further information or an audit is required.

F.2. Company will initially provide available documents, reports, and remote review that reasonably address Customer’s compliance request. Before requesting an on-site inspection or other customer-specific audit, Customer will identify in reasonable detail the compliance question not adequately addressed by the information, reports, certifications, assessment materials, or remote review already provided by Company. Those materials and methods do not eliminate Customer’s audit or inspection rights under this Section where further examination is necessary to verify compliance or required by Applicable Data Protection Laws or the applicable transfer clauses. Company will permit Customer, or a competent independent auditor bound by confidentiality, to audit or inspect Company’s applicable controls and compliance with this DPA, normally no more than once in any twelve (12) month period, within a reasonable scope and during ordinary business hours, with reasonable advance notice and measures protecting other customers’ data. Routine audits will ordinarily be subject to at least ten (10) business days’ advance notice and agreed reasonable administrative details, except in response to a Security Breach, reasonable indications of material noncompliance, a request by a competent regulator, or where a shorter period is required by law. Company will cooperate in arranging legally required audits, and disagreement over administrative details will not prevent an audit required by applicable law. Company need not provide access to other customers’ data, facilities it does not control, privileged material, passwords, or security-sensitive source code merely because an ordinary audit is requested; Company will provide proportionate alternative evidence, subject to law and regulators’ authority.

F.3. Customer will bear its own auditor and professional-adviser costs and Company’s reasonable, documented incremental costs of supporting a customer-specific audit, inspection, or other bespoke compliance review, except to the extent such costs result from material noncompliance by Company or a Subprocessor with this DPA or such charges are prohibited by Applicable Data Protection Laws. Company may require reasonable arrangements concerning such costs before undertaking non-mandatory bespoke assistance. Company will not charge for correcting Company or Subprocessor noncompliance or for Company’s own mandatory incident response, and no audit or assistance payment is a prerequisite to a statutory right.

F.4. Customer may use audit results and materials only to meet its regulatory audit requirements or assess compliance with this DPA, including by disclosing them to professional advisers bound to confidentiality for those purposes. Customer will keep those results and materials confidential, except for such adviser disclosures, disclosures required by a competent authority, and other disclosures required by applicable law.

G. Security Breaches

G.1. Company will notify Customer in writing without undue delay after becoming aware of a Security Breach and, in any event, within seventy-two (72) hours after that awareness. For this Section, Company is aware when it has a reasonable degree of certainty that a security incident has occurred resulting in compromise of Customer Personal Data. Company’s awareness includes receipt of a Subprocessor notice containing sufficient information to satisfy that standard. Company will not delay its initial notice pending completion of an independent investigation or receipt of complete particulars. Company will promptly investigate credible indications of a possible Security Breach to determine whether that threshold has been met. The threshold does not require completion of a forensic investigation, a finding of fault, identification of every affected record, or a finding of likely harm to individuals. Initial notice may be supplemented in phases without undue further delay. The outside limit is not permission to wait where earlier notice is required. Company will reasonably cooperate with Customer’s investigation and notification obligations. Notification or assistance does not itself constitute an admission of fault or liability. Company’s notice obligations are subject to any applicable law or binding governmental or judicial order that prohibits or requires delay of notice, in which case Company will provide notice as soon as legally permitted.

G.2. Upon becoming aware of a Security Breach, Company will (a) investigate the Security Breach, (b) promptly take reasonable steps to contain and mitigate its effects, and (c) provide timely information relating to the nature of the Security Breach, such as, where reasonably possible, a contact point, the categories and approximate number of data subjects concerned, the categories and approximate number of Customer Personal Data records concerned, the likely consequences of the Security Breach, and the measures taken or proposed to be taken by Company to address the Security Breach, including measures to mitigate its possible adverse effects. Company will provide updates as additional information becomes available.

G.3. Notices under this Section will be sent to Customer’s designated security contact or, if none is designated, its account notice email. Company will not wait for Customer to provide a special subscribed-contact list before notifying Customer.

G.4. Customer decides its own required notices. Company will not notify individuals or regulators on Customer’s behalf without Customer’s instructions unless law requires. No Company approval right may prevent or delay Customer’s lawful notices, and no customer-fault exclusion removes Company’s notice and information duties for a breach in the covered processing.

G.5. Nonpersonal Customer Data. Company will notify Customer in writing without undue delay after becoming aware of a breach of security leading to accidental or unlawful destruction, loss, alteration, unauthorized disclosure of, or access to nonpersonal Customer Data processed by Company or its service providers on Company’s behalf in connection with the Services. Company will investigate the incident, promptly take reasonable steps to contain and mitigate its effects, and coordinate with the relevant service providers concerning their response.

Company will provide reasonably available information concerning the nature of the incident, the affected nonpersonal Customer Data, its likely consequences, and measures taken or proposed to address it, with updates as additional information becomes available. Notices under this Section G.5 will use the contact route in Section G.3. Notification or assistance does not itself constitute an admission of fault or liability.

This Section G.5 applies while Company or its service providers retain the covered nonpersonal Customer Data in connection with the Services. Where an incident also involves Customer Personal Data, Sections G.1–G.4 continue to apply to that Customer Personal Data without limitation by this Section G.5.

H. Deletion and Return

H.1. During the Services, Customer may request a copy of Customer Personal Data or request its deletion in accordance with Section H.2 and the Retention Schedule. A request for a copy during the Services does not, by itself, instruct Company to delete the data or terminate the affected Services. At the end of the relevant processing, Company will, at Customer’s choice, return or delete the Customer Personal Data and delete remaining copies, subject to Sections H.3–H.4 and the Retention Schedule. Company will provide a reasonable secure means of returning the requested Customer Personal Data in a commonly used machine-readable form. Return does not require handing over Company’s underlying software, third-party trade secrets, or other customers’ data.

H.2. Requests will follow Terms Section 10’s request route, authority and scope verification, file-versus-derived-record distinction, and organizational-account closure instruction. Company may use manual procedures where necessary. Nonrenewal or individual-user deletion alone does not delete organizational Projects. Customer may instruct return before deletion, and Company must coordinate a timely return election with deletion rather than erase the data first. A request submitted after data has already been lawfully deleted does not require reconstruction. The return and deletion procedures in this Section do not extend or reinstate hosted access after the applicable entitlement ends.

H.3. Company will use the Retention Schedule’s active-system deletion obligations and bounded recovery and backup cycles. Backups pending expiry will be protected and unavailable for ordinary processing; restored backups are subject to reapplication of completed deletion requests. Company will cause its applicable Subprocessors to perform corresponding return and deletion duties. Company will provide written confirmation or certification of completed deletion upon Customer’s request and, without requiring a request, where required by applicable Standard Contractual Clauses or Applicable Data Protection Laws. Any confirmation or certification must accurately identify its scope, pending recovery-copy or backup expiry, and any limited lawful retention; Company will not certify complete eradication while covered copies remain.

H.4. Retention of Customer Personal Data in Company’s processor capacity after the relevant Services end is permitted only to the extent recognized by Applicable Data Protection Laws and the applicable transfer clauses; Article 28 return/deletion duties are not displaced by a general business interest in retention. In particular, where the GDPR or UK GDPR requires return/deletion unless law requires storage, that requirement controls. The limited legal-claims provision in Section 10 of the Terms is not a blanket exception to these duties. Any processing of narrowly identified records for Company’s own legal claims must have a separately established lawful basis and comply with applicable purpose, transparency, retention, and transfer requirements. Describing Company as an independent controller does not itself authorize that processing. Retained records remain protected, restricted to the lawful retention purpose, periodically reviewed, and deleted when that basis ends. No complete migration dataset may be retained merely because of possible future disputes.

H.5. This DPA and the applicable protective, assistance, audit, and transfer obligations survive while Company or an applicable Subprocessor retains Customer Personal Data, including recovery and backup copies.

I. Standard Contractual Clauses

I.1. The parties agree that, to the extent required by Applicable Data Protection Laws and legally available for the relevant restricted transfer, Module Two (controller to processor) applies where Customer is controller and Company is processor, and Module Three (processor to processor) applies where Customer is processor and Company is subprocessor. The applicable SCCs, completed annex information, and elections described in Schedule 3 are incorporated by reference and will be deemed to have been executed by the parties. Residence of a data subject alone is not the trigger.

I.2. To the extent required by Applicable Data Protection Laws and legally available for the relevant restricted transfer, the jurisdiction-specific addenda to the SCCs set out in Schedule 3, together with their completed appendix information and mandatory clauses, are incorporated herein by reference and will be deemed to have been executed by the parties.

I.3. Mandatory data-transfer clauses prevail over any conflicting term of this DPA or the Agreement, including liability limitations, audit restrictions, dispute provisions, and return/deletion exceptions. Subject to that rule and the Agreement’s express treatment of a separately executed replacement DPA, this DPA controls its stated personal-data processing subject matter. Nothing in the Agreement or this DPA modifies the mandatory text of applicable SCCs or the UK Addendum beyond permitted elections, completion of annex information, and authorized adaptations.

I.4. Company will provide Customer reasonable support to enable Customer’s compliance with the requirements imposed on international transfers of Customer Personal Data. Company will, upon Customer’s request, provide information to Customer which is reasonably necessary for Customer to complete a transfer impact assessment to the extent required under Applicable Data Protection Laws.

I.5. Company will maintain lawful onward-transfer arrangements for Customer Personal Data, provide reasonable assistance with applicable transfer-risk assessments and supplementary measures, and promptly notify Customer if Company cannot comply with the applicable transfer mechanism. Execution of SCCs alone does not complete a transfer assessment. If a lawful mechanism cannot be maintained, Company will stop the affected transfer and use the applicable SCC suspension or termination process without eliminating existing financial remedies.

J. Jurisdiction-Specific Provisions

J.1. U.S. Privacy Laws.

J.1.a. Where applicable, Company acts as a service provider, contractor, or processor for the specified processing, including downstream processing where Customer itself acts for a business or controller.

J.1.b. Customer discloses Customer Personal Data only for the limited, specified purposes in Schedule 1.B.

J.1.c. Company will not sell or share Customer Personal Data, use it outside the direct business relationship or specified purposes, or combine it with personal information from other sources except as permitted by law and subject to stricter contractual limits.

J.1.d. Company will comply with its applicable legal obligations and provide the level of privacy protection required by applicable law, including the CCPA’s required level of protection. Company certifies that it understands and will comply with the applicable contractual restrictions.

J.1.e. Customer may take reasonable and appropriate steps to verify that processing is consistent with its obligations and, on notice, stop or remediate unauthorized use. The assistance and audit procedures in this DPA implement, and do not eliminate, those rights.

J.1.f. Company will promptly notify Customer if it determines that it cannot meet its obligations and will provide reasonable cooperation with rights requests, required risk assessments and cybersecurity audits, and applicable automated-decisionmaking compliance assistance.

J.1.g. Confidentiality, security, return and deletion, information access, reasonable assessments, and written downstream obligations apply as addressed in Sections B through H. Any exception permitted under U.S. Privacy Laws remains subject to the purpose and use limits in Section B and the Agreement.

J.2. Canada. Where Canadian federal or provincial privacy law applies, including PIPEDA or British Columbia PIPA to the extent applicable to the relevant processing, the same instruction, confidentiality, security, assistance, subprocessor, and retention commitments in this DPA apply. Company-managed Project storage and AI processing locations are identified in Schedule 1 and are not represented as Canadian-resident. Customer remains responsible for required cross-border notices and authority matters, and Company remains responsible for its contractual safeguards and cooperation. SCC execution alone does not establish compliance with Canadian law, and applicability depends on the actual processing and law.

K. General Provisions

K.1. Liability. Liability arising from this DPA is part of, not additional to, liability under the Agreement and is subject to Section 14 of the Terms, including its exclusions, applicable shared aggregate cap, and exceptions, only to the extent permitted by applicable law and mandatory transfer clauses. This DPA does not create a separate cap, additional indemnity, or additional third-party commercial claim. Nothing limits mandatory data-subject rights, supervisory powers, or liability under applicable transfer clauses where such limitation is prohibited, including applicable interparty SCC liability. The monetary limitations of liability do not excuse either party from performing non-monetary obligations that Applicable Data Protection Laws or mandatory data-transfer clauses require that party to perform.

K.2. Costs and notices. Routine DPA and deletion contacts are privacy@settledata.com; incoming security reports use security@settledata.com. Customer notices go to its designated contact or account notice email. Additional bespoke assistance outside ordinary contracted performance may be charged only if separately agreed in advance and lawful. No new fee applies simply because deletion is performed manually. Company may not condition mandatory incident notice, legally required assistance, or correction of Company or Subprocessor noncompliance on a paid order.

K.3. Changes. Changes to this DPA and its schedules follow Terms Section 17.2. Material changes will be notified at least thirty (30) days in advance and will require affirmative acceptance where required. No change may retroactively expand use or reduce committed protection. Nonreducing implementation details may be updated consistently with those commitments. Without limiting the foregoing, Company may modify or replace particular technologies, vendors, technical controls, implementation methods, or other operational details identified in the schedules without amending this DPA, provided that the change does not materially decrease the overall level of protection for Customer Data or conflict with an express commitment concerning permitted data use, processing location, retention, deletion, or Customer’s applicable AI settings. Subprocessor notice is governed by Section C.3; a material amendment of deletion or security commitments is not merely a vendor-list update. Approved SCC and UK mandatory update mechanisms remain controlling. The DPA will retain a version, date, and change record.

Before implementing a change to an AI model, endpoint, optional feature, or processing configuration within an existing provider that materially affects Customer Data retention, permitted use, processing locations, or safeguards, Company will assess its consistency with the Agreement and update the applicable processing information. Where the change would amend a contractual commitment, Company will follow the applicable advance-notice and acceptance requirements before implementing it for Customer. Such a change does not escape those requirements merely because the provider’s identity is unchanged. This paragraph does not authorize a reduction in committed protection, an expanded data-use right, or processing inconsistent with Customer’s applicable AI settings.

K.4. Disputes and term. The Agreement’s governing law and dispute procedures apply to ordinary DPA disputes, subject to mandatory transfer law, forum, and data-subject rights. This DPA remains operative through completed lawful return and deletion and does not automatically cease on subscription nonrenewal.

Schedule 1 - Details of Processing and Transfers

A. List of Parties

A.1. Data Exporter: The data exporter is the Customer, with its legal organization name, address, and authorized privacy or contact details recorded in the accepted Agreement or account information. Customer’s role is controller or processor according to the actual processing. Relevant representative and controller particulars will be included where required. Any affiliate exporting Customer Personal Data will be identified as a separate relevant party through verified Agreement records; unidentified group companies are not deemed SCC signatories.

A.2. Data Importer: Settle Data, Inc., 1111B S Governors Ave, #87244, Dover, Delaware 19904, United States. Contact: privacy@settledata.com. Role: processor or subprocessor, according to the actual processing. Any data protection officer, representative, or additional contact particulars required for a particular transfer will be recorded in the applicable Agreement, account, or transfer records or otherwise provided to Customer as required.

A.3. The parties’ legally effective acceptance incorporates the selected clauses and their completed appendix information. The acceptance date is the date recorded in the accepted Agreement or account records. Required party and contact information must be recorded before the parties rely on the applicable transfer clauses.

B. Description of Processing

B.1. Subject matter and purpose: Hosted ERP, CRM, and HCM migration assessment, profiling, mapping/configuration, transformation, validation, Project storage, approved export, and related support and security. Fixed Project instructions and permissions govern.

B.2. Nature: Receipt or upload, storage, organization and normalization, analysis, mapping and transformation, generation of Project-specific results, validation, controlled transmission to listed providers, export or return, and deletion.

B.3. Categories of data subjects: Customer’s customers, vendors, business contacts and employees, plus corresponding people in its authorized clients’ records; relevant Authorized Users and dependent or benefits-related persons only to the extent their information is permitted under Terms Section 4. This description is not an exception to the children’s-data restriction.

B.4. Categories of personal data: Names, business contact details, addresses, account and transaction history; employee IDs, compensation, tax and government IDs including SSNs, and payroll banking details; benefits-enrollment and dependent fields only to the extent permitted by Section 4 of the Terms. Personal information in schema names, messages, context documents, mappings, and results is included where applicable; schema information is not presumed anonymous.

B.5. Sensitive information: Customer Personal Data may include government identifiers, payroll financial information, compensation information, benefits-enrollment information, dependent information, and other workforce information reasonably necessary for an authorized ERP, CRM, or HCM migration. This description does not authorize Restricted Data prohibited by Section 4 of the Terms. Any Restricted Data remains prohibited unless expressly authorized under the signed addendum process specified in the Terms.

Permission to process information within Company’s hosted Services does not itself authorize transmission of that information to an AI model provider. The permitted AI Input is separately limited by Section 5 of the Terms and the applicable provider entry in Schedule 4. Any additional permission for HCM or dependent information remains subject to the specific category, purpose, environment, and safeguards authorized under the Agreement. This Schedule does not lift a Restricted Data prohibition.

B.6. The AI-data-access provisions in Section 5 of the version of the Terms contractually applicable to Customer—including organization/project settings, the table-field protections, schema-only processing, and the scope of assistant messages and designated context documents—are incorporated into this processing description as Customer’s documented instructions, subject to this DPA’s mandatory-law and transfer protections. The applicable settings determine which inputs may be transmitted to an AI provider; the provider does not receive all hosted Project records merely because it supplies an AI feature. A later Terms version affects those instructions only when it becomes effective for Customer under the agreed amendment process. This reference does not turn an output disclaimer into a processing permission.

B.7. Frequency and duration: Customer-directed uploads and runs and associated ongoing storage and security during the relevant Project or Services, followed by the bounded deletion and retention periods in Schedule 5.

B.8. Geography: Company-managed Project storage, database, and services are in Google Cloud us-east1, United States. Active AI calls to Anthropic are in the United States. Model processing is not represented as occurring inside Company’s Google Cloud region.

B.9. Subprocessors: Company may use the providers listed in Schedule 4 for the purpose-specific data and duration stated there, subject to Section C and the applicable transfer safeguards.

C. Competent Supervisory Authority

C.1. For each transfer relying on the SCCs, the competent supervisory authority is determined under Clause 13 using the relevant Agreement, account, and transfer information as follows:

C.1.a. Where the exporter is established in an EU Member State, the competent authority is the supervisory authority responsible for ensuring that exporter’s GDPR compliance for the transfer.

C.1.b. Where the exporter is not established in an EU Member State but is subject to Article 3(2) of the GDPR and has appointed an Article 27(1) representative, the competent authority is the authority of the Member State in which that representative is established.

C.1.c. Where the exporter is not established in an EU Member State, is subject to Article 3(2) of the GDPR, and is exempt from appointing a representative under Article 27(2), the competent authority is the authority of a Member State in which affected data subjects are located, selected consistently with Clause 13 and identified in the relevant customer and transfer records.

C.2. Where the applicable rule and records do not identify the competent authority, the parties must obtain and record the missing selection or details before relying on the SCCs for that transfer. The UK and Swiss provisions in Schedule 3 apply within their respective scopes.

Schedule 2 - Security Measures

This Security Schedule applies to all Customer Data.

1. Infrastructure and encryption. Company-managed Project infrastructure is in Google Cloud us-east1. Stored data is encrypted at rest and communications are encrypted in transit. Database backups are encrypted and retained for seven days.

2. Access and confidentiality. Company personnel access Company-managed production systems processing Customer Data only while located in the United States. Within the Services, editors and admins approve tables and download results; only admins start exports; and runs record the initiator. These controls preserve the Terms’ approved-configuration mechanics.

3. Segregation, minimization, and AI controls. Product analytics are configured not to capture Customer Data displayed on screen. Company’s stored Stripe records are limited to customer and subscription IDs, event IDs and types, invoice amounts, and subscription status, rather than full event payloads. Company applies the AI-data-access settings and field protections in Section 5 of the Terms and uses the AI provider identified in Schedule 4. Sensitive fields are designated through the customer controls described in the Terms; this statement does not represent that the Services automatically detect every sensitive field.

4. Logging and monitoring. The log and recovery categories and periods are addressed in Schedule 5. The in-app activity log is distinct from Google Cloud admin and data-access logs.

5. Backup, recovery, and deletion. Database backups are encrypted and retained for seven days. The applicable retention periods, protected-backup treatment, deletion reapplication after restoration, and written confirmation requirements are in Schedule 5 and Section H.

6. Infrastructure, access, and confidentiality. Company will designate responsibility for security of systems processing Customer Data, maintain documented access controls and confidentiality commitments, use named privileged accounts and multi-factor authentication where appropriate, revoke access when no longer authorized, and periodically review privileged access.

7. Segregation and minimization. Company will maintain reasonable tenant separation and data-minimization processes appropriate to the Services, including controls for Customer Data in development, testing, support, and analytics contexts.

8. Logging and monitoring. Company will maintain documented logging and monitoring appropriate to detect and investigate suspicious activity affecting systems that process Customer Data, with access to logs restricted and retention aligned to Schedule 5.

9. Backup and recovery. Company will maintain a documented backup-restoration process and test restoration sufficiently to support the applicable deletion, recovery, and continuity obligations without extending retention beyond Schedule 5.

10. Development and vulnerability management. Company will use protected development and deployment practices and risk-based vulnerability identification and remediation appropriate to systems processing Customer Data.

11. Incident response. Company will maintain documented incident-response procedures addressing investigation, containment, mitigation, notification, and cooperation under Section G, and will preserve evidence needed to provide phased updates.

12. Supplier oversight and compliance evidence. Company will maintain a proportionate process to assess relevant supplier security, confidentiality, transfer, deletion, and use-policy commitments and will provide available supplier evidence under Sections C, F, and I. Supplier certifications will not be represented as Company certifications.

Schedule 3 - International Data Transfers

A. EU SCCs

A.1. Elections for the purposes of Module Two and Module Three of the Standard Contractual Clauses. Module Two applies to controller-to-processor transfers and Module Three applies to processor-to-subprocessor transfers. No default Module One or Module Four applies.

A.1.a. Clause 7 (Docking clause) – does not apply.

A.1.b. Clause 11 (Redress) – optional wording does not apply.

A.1.c. Clause 17 (Governing Law) – Option 1 will apply and the governing law will be the law of the Republic of Ireland.

A.1.d. Clause 18 (Choice of forum and jurisdiction) – the applicable choice of forum and jurisdiction will be the courts of the Republic of Ireland, preserving the SCCs’ mandatory data-subject forum rights.

A.1.e. For the purpose of Annex I of the Standard Contractual Clauses, Annex I.A maps to Part A of Schedule 1, Annex I.B maps to Part B of Schedule 1 with Schedule 5 for retention, and Annex I.C maps to Part C of Schedule 1.

A.1.f. For the purpose of Annex II of the Standard Contractual Clauses, Schedule 2 contains the Security Measures. Subprocessor particulars and Annex III information, where relevant, are provided in Schedule 4; the contractual information is provided regardless of whether Annex III is mandatory for Option 2.

A.2. Additional elections for the purposes of Module Two and Module Three of the Standard Contractual Clauses:

A.2.a. Clause 9 (Use of subprocessors) – Option 2 (General written authorization) will apply, with notice as provided under Section C.3 of this DPA and a fifteen (15) calendar day objection period.

A.2.b. For the purpose of the applicable SCC appendix information, the Subprocessor List and purpose-specific provider particulars are set out in Schedule 4 or as otherwise determined by Section C.3 of this DPA. The Subprocessor’s contact person, position, and contact details will be provided by Company upon request where available.

B. UK Addendum

This UK Addendum will apply to any processing of Customer Personal Data that is subject to the UK GDPR or both the UK GDPR and the GDPR. For the purposes of this UK Addendum:

“Approved Addendum” means the International Data Transfer Addendum to the EU Commission SCCs, version B.1.0, issued by the UK Information Commissioner under S119A(1) of the Data Protection Act 2018 and laid before the UK Parliament on 2 February 2022, as revised according to its mandatory change mechanism, available at https://ico.org.uk/media2/migrated/4019539/international-data-transfer-addendum.pdf.

“UK GDPR” means Regulation (EU) 2016/679 of the European Parliament and of the Council of 27 April 2016 as it forms part of the law of England and Wales, Scotland and Northern Ireland by virtue of Section 3 of the European Union (Withdrawal) Act 2018 and as amended by the Data Protection, Privacy and Electronic Communications (Amendments etc.) (EU Exit) Regulations 2019.

B.1. With respect to any transfers of Customer Personal Data falling within the scope of the UK GDPR from Customer (as data exporter) to Company (as data importer), the Approved Addendum applies to the extent required by Applicable Data Protection Laws and as completed by the Part 1 table information in Sections B.1.b–B.1.d of this Part B.

B.1.a. The Approved Addendum, including its Part 2 Mandatory Clauses and mandatory update mechanism, is incorporated into and forms part of this DPA to the extent necessary for the relevant transfer.

B.1.b. For Table 1 of Part 1 of the Approved Addendum, the exporter is the Customer identified in Part A of Schedule 1 and the importer is Company, Settle Data, Inc., at the address and contact shown in Part A of Schedule 1. Any representative, DPO, or contact particulars are included only where required and verified in the accepted Agreement or account records.

B.1.c. For Table 2 of Part 1 of the Approved Addendum, the selected SCCs are Module Two where Customer is controller and Company is processor, and Module Three where Customer is processor and Company is subprocessor, with the EU elections and appendix information in Part A of this Schedule 3.

B.1.d. For Table 3 of Part 1 of the Approved Addendum, the appendix information maps to Schedule 1 for processing and transfers, Schedule 2 for security measures, Schedule 4 for subprocessors, and Schedule 5 for retention and deletion. For Table 4 of Part 1, Company (as data importer) may end the Approved Addendum only on the grounds specified in its mandatory Section 19; this is not an unrestricted ordinary termination right.

B.2. Part 2: Mandatory Clauses.

Mandatory Clauses

Part 2: Mandatory Clauses of the Approved Addendum, being the template Addendum B.1.0 issued by the ICO and laid before Parliament in accordance with s119A of the Data Protection Act 2018 on 2 February 2022, as it is revised under Section 18 of those Mandatory Clauses.

C. Swiss Addendum

This Swiss Addendum will apply to any processing of Customer Personal Data that is subject to Swiss Data Protection Laws (as defined below) or to both Swiss Data Protection Laws and the GDPR.

C.1. Interpretation of this Addendum

C.1.a. Where this Addendum uses terms that are defined in the Standard Contractual Clauses, those terms will have the same meaning as in the Standard Contractual Clauses. In addition, the following terms have the following meanings:

C.1.a.i. This “Addendum” means this Addendum to the Clauses.

C.1.a.ii. “Clauses” means the Standard Contractual Clauses as further specified in this Schedule.

C.1.a.iii. “Swiss Data Protection Laws” means the Swiss Federal Act on Data Protection of 25 September 2020 and applicable implementing ordinance, as amended.

C.1.b. This Addendum will be read and interpreted in the light of the provisions of Swiss Data Protection Laws, and so that it fulfills the intention for it to provide the appropriate safeguards as required by Article 46 GDPR and/or applicable Swiss transfer law, as the case may be.

C.1.c. This Addendum will not be interpreted in a way that conflicts with rights and obligations provided for in Swiss Data Protection Laws.

C.1.d. Any references to legislation (or specific provisions of legislation) means that legislation (or specific provision) as it may change over time. This includes where that legislation (or specific provision) has been consolidated, re-enacted and/or replaced after this Addendum has been entered into.

C.2. Hierarchy. In the event of a conflict or inconsistency between this Addendum and the provisions of the Clauses or other related agreements between the parties, existing at the time this Addendum is agreed or entered into thereafter, the provisions which provide the most protection to data subjects will prevail.

C.3. Incorporation of the Clauses

C.3.a. In relation to any processing of personal data subject to Swiss Data Protection Laws or to both Swiss Data Protection Laws and the GDPR, this Addendum amends the DPA and the Standard Contractual Clauses to the extent necessary so they operate:

C.3.a.i. for transfers made by the data exporter to the data importer, to the extent that Swiss Data Protection Laws or Swiss Data Protection Laws and the GDPR apply to the data exporter’s processing when making that transfer; and

C.3.a.ii. to provide appropriate safeguards for the transfers in accordance with Article 46 of the GDPR and applicable Swiss transfer law, as the case may be.

C.3.b. To the extent that any processing of personal data is exclusively subject to Swiss Data Protection Laws, the amendments to the DPA including the SCCs, as further specified in this Schedule and as required by Section C.3.a of this Swiss Addendum, include (without limitation):

C.3.b.i. References to the "Clauses" or the "SCCs" mean this Swiss Addendum as it amends the SCCs.

C.3.b.ii. Clause 6 Description of the transfer(s) is replaced with: "The details of the transfer(s), and in particular the categories of personal data that are transferred and the purpose(s) for which they are transferred, are those specified in Schedule 1 of this DPA where Swiss Data Protection Laws apply to the data exporter’s processing when making that transfer."

C.3.b.iii. References to "Regulation (EU) 2016/679" or "that Regulation" or “GDPR" are replaced by "Swiss Data Protection Laws" and references to specific Article(s) of "Regulation (EU) 2016/679" or "GDPR" are replaced with the equivalent Article or Section of Swiss Data Protection Laws to the extent applicable.

C.3.b.iv. References to Regulation (EU) 2018/1725 are removed.

C.3.b.v. References to the "European Union", "Union", "EU" and "EU Member State" are all replaced with "Switzerland".

C.3.b.vi. Clause 13(a) and Part C of Annex I are not used; the "competent supervisory authority" is the Federal Data Protection and Information Commissioner (the "FDPIC") insofar as the transfers are governed by Swiss Data Protection Laws;

C.3.b.vii. Clause 17 is replaced to state: "These Clauses are governed by the laws of Switzerland insofar as the transfers are governed by Swiss Data Protection Laws".

C.3.b.viii. Clause 18 is replaced to state: "Any dispute arising from these Clauses relating to Swiss Data Protection Laws will be resolved by the courts of Switzerland. A data subject may also bring legal proceedings against the data exporter and/or data importer before the courts of Switzerland in which he/she has his/her habitual residence. The parties agree to submit themselves to the jurisdiction of such courts."

C.3.c. Where a transfer is subject to both the GDPR and Swiss Data Protection Laws, the SCCs apply under both regimes. For GDPR-governed processing, the competent EU supervisory authority is determined under Clause 13 and Schedule 1.C. The FDPIC is additionally competent for the processing governed by Swiss Data Protection Laws. References to the GDPR are also read as references to Swiss Data Protection Laws to the extent necessary for that Swiss-governed processing, without displacing the GDPR protections.

For such transfers, the Irish law and court elections in Sections A.1.c and A.1.d of this Schedule remain applicable under Clauses 17 and 18. The Swiss-only substitutions in Sections C.3.b.vi–C.3.b.viii do not replace those elections or the competent EU supervisory authority. Data subjects habitually resident in Switzerland may also bring proceedings in the courts of Switzerland under Clause 18(c); all other mandatory data-subject forum rights remain unaffected. The Swiss-only treatment in Section C.3.b continues to apply to transfers governed exclusively by Swiss Data Protection Laws.

Schedule 4 - Subprocessors

The providers below process Customer Data for the specified functions, subject to Section C. Provider Use Policy references have only the limited effect stated in Section 4 of the Terms. References to other supplier documents identify the applicable supplier arrangements; they do not incorporate an entire supplier commercial agreement into the Agreement or override Company’s obligations under this DPA.

PROVIDER / CONTRACTING ENTITY

FUNCTION

CUSTOMER DATA INVOLVED

PROCESSING LOCATION

RETENTION / DELETION

DATA-PROTECTION / PROVIDER USE POLICY REFERENCES

Google Cloud – Google LLC

Hosting, compute, storage, database, and infrastructure logging for the platform.

Customer Data hosted in the Services and associated service records.

Company-managed Project infrastructure: Google Cloud us-east1, United States. Supplier-controlled support and other processing are subject to the locations permitted under the applicable Google Cloud Data Processing Addendum and its transfer requirements, and to Sections C, I, and K of this DPA. The selected Project hosting region is not a representation that every supplier support or other processing activity occurs in that region.

Company-controlled active deletion and configured recovery copies follow Schedule 5. Separately, under Google Cloud DPA Section 6.1, once Company’s deletion is unrecoverable by Company, Google must carry out its corresponding deletion instruction as soon as reasonably practicable and within a maximum of 180 days, subject to the provision’s legally required storage exception. This supplier-controlled deletion period does not extend Company’s active-system deletion obligations or permit ordinary use of deleted Customer Data.

Google Cloud Data Processing Addendum, including its security, subprocessor, and transfer provisions: https://cloud.google.com/terms/data-processing-addendum

Google contracting-entity information: https://cloud.google.com/terms/google-entity

Anthropic – Anthropic, PBC

AI inference for mapping, assistant, and context functions enabled in the Services.

Only AI Input permitted under Section 5 of the Terms, including permitted sample values, assistant messages, and Customer-designated context, subject to Customer’s applicable settings and the field protections. Permission for hosted HCM or dependent data does not itself permit transmission of that information to Anthropic.

United States for the model calls described by Company.

Zero-data-retention treatment is configured for eligible Claude API traffic under Company’s Anthropic API organization, subject to the retention terms applicable to the specific model, endpoint, and feature used and to any retention by Anthropic that is required by law or permitted under its applicable terms. Anthropic does not use Customer Content submitted through the Services to train its models. Company will not enable a materially different retention treatment for Customer Personal Data without complying with Section K.3. Company-held AI Input and AI Output remain subject to Schedule 5.

Commercial Terms: https://www.anthropic.com/legal/commercial-terms

Data Processing Addendum: https://www.anthropic.com/legal/data-processing-addendum

Usage Policy: https://www.anthropic.com/legal/aup

Supported Countries and Regions: https://www.anthropic.com/supported-countries

Service Specific Terms: https://www.anthropic.com/legal/service-specific-terms

Schedule 5 – Retention and Deletion

This Retention Schedule applies to Customer Data in the Services, subject to Section H and Applicable Data Protection Laws.

RECORD / PROCESS

RETENTION OR DELETION RULE

Project source files, normalized or derived copies, profiles, mappings, sign-offs, run history, and results

Customer Data associated with a Project is retained for the life of the Project unless Customer instructs scoped deletion or the relevant processing ends under Section H. Closure or termination of Customer’s organizational account constitutes an instruction to delete its Project Customer Data, subject to any expressly agreed wind-down and Section H. Company will complete deletion from its active systems without undue delay and, in any event, within ten (10) business days after receiving an authorized deletion instruction containing sufficient information to identify Customer and the data to be deleted. Company will promptly request any information reasonably necessary to verify authority or scope. Deletion includes corresponding normalized and derived copies, profiles, Customer-specific mappings and configurations, sign-offs, run history, Project results, and associated assistant messages and context documents. Company may use manual procedures where automated deletion is unavailable. The separate log, recovery-copy, supplier-residual, and limited-retention provisions below remain subject to Section H and any shorter period required by Applicable Data Protection Laws.

Deleting a source upload alone

Deleting an uploaded source file removes that uploaded file from active use. The file remains recoverable through the configured file-recovery function for seven days after file deletion. Deleting that uploaded file alone does not delete its normalized or derived copies, profiles, mappings, or Project results and is not complete Project erasure. Customer may request deletion of those associated materials under the Project deletion rule above. Supplier-controlled residual copies are addressed separately below and in Schedule 4.

AI assistant messages, designated context, and Customer Personal Data in Project outputs

Associated assistant messages, Customer-designated context documents, and Customer Personal Data in Project outputs are included in an authorized scoped Project deletion. Deleting an individual Authorized User’s account does not itself instruct deletion of Customer’s organizational Projects.

In-app activity log

The in-app activity log is retained for the life of Customer’s organizational account and is distinct from Google Cloud admin audit logs and data-access logs. Organizational-account closure is subject to the applicable deletion obligations in Section H, except for specific records lawfully retained under Section H and the limited-record provisions below.

Google Cloud admin audit logs

Google Cloud admin audit logs are retained for 400 days for applicable security and administration purposes. This period does not authorize retaining raw Project content under an audit-log label or displace a shorter mandatory deletion, response, or assistance obligation. These logs are distinct from the in-app activity log and Google Cloud data-access logs.

Google Cloud data-access logs

Google Cloud data-access logs are retained for 30 days for applicable security purposes. This period does not authorize retaining raw Project content under a data-access-log label or displace a shorter mandatory deletion, response, or assistance obligation. These logs are distinct from the in-app activity log and Google Cloud admin audit logs.

Database backups and Company-configured recovery tools

Database backups are retained for seven days. Deleted uploaded files are separately recoverable for seven days as stated above. Recovery copies pending expiry remain protected and unavailable for ordinary service processing. If a backup is restored, Company will reapply previously completed deletion requests before using the restored data for ordinary service processing. These recovery periods do not establish or extend the separate supplier-controlled residual deletion periods identified below and in Schedule 4.

Supplier-controlled residual copies

Residual copies of Customer Data maintained within a provider’s internal systems, but no longer accessible through Company’s active systems or configured backup, soft-deletion, point-in-time-recovery, or other recovery tools, are subject to the provider-specific deletion periods and triggers stated in Schedule 4. Those periods are distinct from, and do not extend, Company’s active-system deletion obligations or the periods applicable to Company’s configured recovery tools under this Schedule. Such residual copies must remain protected and unavailable for ordinary service processing pending deletion. Company will require the relevant provider to delete those copies in accordance with Section C and the applicable Schedule 4 entry. This residual-copy treatment remains subject to Sections C, H, I, and K. No provider policy or supplier deletion period authorizes retention or use inconsistent with Applicable Data Protection Laws or applicable mandatory data-transfer clauses, or overrides an earlier return or deletion obligation imposed by those requirements. Any confirmation or certification of deletion must accurately distinguish completed active-system deletion, expired Company-configured recovery copies, and any remaining supplier-controlled residual copies.

Free Plan

Customer Data associated with a Free Plan Project is retained and deleted under the general Project retention, return, and deletion rules in this Schedule and Section H. Free Plan status does not itself cause automatic deletion of Project Customer Data. Cancellation or nonrenewal alone does not instruct Company to delete a Project or close Customer’s organizational account.

Limited retained records

Limited retention does not apply to complete Project datasets. The separately identified security-log categories follow their stated periods. Specific records required by a binding preservation obligation may be retained only for that obligation. Records necessary for actual or reasonably anticipated legal claims may be retained only as permitted by Section H.4, limited to the identified claim and required records, with periodic review and deletion when the lawful basis ends. Company will document the record category, purpose and legal basis, and maximum period or objective end criterion before relying on such additional retention. A billing, support, audit, or compliance label does not itself establish a retention basis. Copies of Project content in support or other systems remain subject to applicable scoped deletion. Company’s independent corporate billing and marketing records are governed by the Privacy Policy to the extent actually processed independently; that classification does not authorize retaining Customer’s migration dataset.

Deletion and return procedures

An authorized representative of Customer may submit a deletion or return request to privacy@settledata.com, identifying Customer’s organization, the relevant Project, and the requested scope. Company may reasonably verify the requester’s authority and the requested scope and will promptly request only information reasonably necessary for that verification. Customer may elect return before deletion under Section H, and Company will coordinate a timely return election with deletion rather than erase the requested data first. Manual processing does not create an additional charge. Company will provide confirmation or certification as required by Section H.3 and will identify any pending recovery-copy expiry or limited lawful retention accurately. Retained Customer Data remains protected under the Agreement and this DPA for as long as it is held. The active-system deletion obligation stated above does not override a shorter mandatory response, assistance, return, or deletion obligation. This procedure does not promise instant in-product Project deletion or an activity-log export, extend hosted access after its entitlement ends, or require reconstruction of data already lawfully deleted.

Change Record

Version | Effective Date | Summary

1.0 | October 14, 2026 | Initial publication.