Effective date: not set. This schedule has effect only when its completion conditions are satisfied for a specific Restricted Transfer.

Legal Data Hunter International Data Transfer Completion Schedule

Effective date: This Schedule applies automatically when the DPA is incorporated into a Paid Agreement and the relevant Processing is a Restricted Transfer requiring the mechanism described here.

This Schedule forms part of the Legal Data Hunter, Inc. Data Processing Addendum, the DPA. It completes factual elections for the EU Standard Contractual Clauses adopted by Commission Implementing Decision (EU) 2021/914, the SCCs, and the ICO International Data Transfer Addendum, Version B1.0, the UK Addendum. It does not modify their mandatory text. Capitalized terms not defined here have the meanings in the DPA.

1. Automatic incorporation and scope

The same paid online clickwrap, Order Form, or other valid acceptance that incorporates the DPA also incorporates this Schedule and any mechanism that applies under it. No separate signature, transfer questionnaire, role selector, privacy-contact field, authority checkbox, or additional checkout assent is required.

The DPA, SCCs, and UK Addendum apply only to the Processing and Restricted Transfers within their legal scope, and are unnecessary when an applicable adequacy decision or another lawful transfer mechanism applies. EEA processing locations and restricted non-EEA access are supplementary safeguards and do not, by themselves, determine whether a Restricted Transfer occurs.

LDH records internal execution evidence from information already held, including the paid acceptance timestamp, account identity, Order Form facts, Stripe customer identifier or billing information where available, and the exact incorporated document versions and SHA-256 hashes. Missing customer-specific business details do not block ordinary self-serve checkout and are not fabricated. If an enterprise customer requires negotiated or customer-specific completion information, the parties will record it in the Order Form or enterprise contracting process.

2. Parties and role routing

The Exporter is the Customer identified in the Agreement, online Order Form, paid account record, and available billing records. The Exporter's primary account-administrator email is its contact unless another contact is already recorded in the Agreement, Order Form, account, or billing records.

The Importer is:

Legal Data Hunter, Inc., 2810 N Church St STE 89040, Wilmington, DE 19802, United States. Contact: zach@legaldatahunter.com.

The modules route automatically according to the parties' actual roles for the relevant Processing:

Module 2 applies when Customer is a Controller and LDH is a Processor.
Module 3 applies when Customer is a Processor and LDH is a Subprocessor.
If Customer acts in both roles for different Processing, each module applies to the Processing governed by that role.

The role rules in DPA Sections 2.1 and 2.2 and the actual Processing control. No checkout classification changes those roles.

3. EU SCC elections and Appendix Information

For an EU GDPR Restricted Transfer requiring the SCCs:

Clause 7, the docking clause, applies.
Under Clause 9, Option 2, general written authorization applies with the 30-day notice period in DPA Section 7.
The optional language in Clause 11 does not apply.
Under Clause 17, Option 1 applies and the SCCs are governed by the law of France.
Under Clause 18, disputes are resolved by the competent courts of France.
Annex I.A uses the parties and contacts identified under Section 2 and existing Agreement, account, Order Form, and billing records.
Annex I.B uses DPA Annex 1 and any customer-specific Order Form terms.
Annex I.C selects the competent Supervisory Authority under SCC Clause 13 from the Exporter's establishment and GDPR territorial circumstances shown by existing records. LDH keeps that routing logic and any resolved authority in internal evidence.
Annex II is the exact LDH-TOMS version and SHA-256 recorded in the acceptance evidence.
Annex III is the dated Subprocessor List version and SHA-256 recorded in the acceptance evidence.

The SCCs control to the extent of conflict.

4. UK Addendum Part 1 Tables

For a UK Restricted Transfer relying on the EU SCCs, the UK Addendum is incorporated automatically with these Part 1 completions:

Table 1: Parties

Start date: the paid DPA acceptance timestamp recorded in LDH's acceptance evidence.
Exporter: the Customer identified under Section 2, using existing Agreement, account, Order Form, and billing details.
Importer: Legal Data Hunter, Inc., at the address and contact in Section 2.
Signature: the existing paid clickwrap or Order Form acceptance evidence, to the extent a signature is required under UK Addendum Section 2.

Table 2: Selected SCCs, modules, and clauses

The Approved EU SCCs identified in Section 3 apply. Module 2 and Module 3 route by the actual roles stated in Section 2. Clause 7 applies; Clause 11 does not; Clause 9 uses general written authorization and the 30-day notice period in DPA Section 7. No combining election is made except as the actual Processing described in DPA Annex 1 requires.

For the UK Addendum itself, the governing law and courts are those of England and Wales. This UK-specific election does not change the governing-law or forum terms for ordinary disputes under the main commercial Agreement.

Table 3: Appendix Information

Annex 1A is completed by Sections 2 and 3 and existing Customer records.
Annex 1B is DPA Annex 1 and any applicable Order Form detail.
Annex II is the incorporated LDH-TOMS version and SHA-256.
Annex III is the incorporated dated Subprocessor List version and SHA-256.

Table 4: Ending the Addendum when the Approved Addendum changes

Importer and Exporter may end the UK Addendum as set out in Section 19 of the UK Addendum.

The UK Addendum's mandatory clauses apply without modification and control to the extent of conflict.

5. Internal evidence

The backend stores one content-addressed transfer evidence object inside the existing immutable paid legal-acceptance record. It uses the same acceptance timestamp, user/account identity, Stripe customer identifier where available, Order Form artifact, authority-to-bind representation in the paid clickwrap, transfer routing rules, and exact document hashes. It does not create a separate customer signature or contracting workflow.

Information not held for an ordinary self-serve account remains identified as unavailable rather than inferred. Customer-specific legal name, registered address, company number, a different privacy contact, or a negotiated transfer assessment may be supplied later through an Order Form or enterprise contract where genuinely required.

6. Transfer assessment and certification status

The parties will reasonably cooperate on a transfer assessment where required. LDH will provide information reasonably available concerning processing locations, onward transfers, contractual safeguards, and supplementary measures.

The SCCs and UK Addendum are fallback mechanisms. LDH does not rely on or represent participation in the EU-U.S. Data Privacy Framework, UK Extension, or Swiss-U.S. Data Privacy Framework unless the applicable certification has separately been completed and verified.