Master Services Agreement (Version 2026.4). This Agreement governs Hunter’s provision of hosted compliance screening, vendor risk management, trade screening and the other full-suite capabilities expressly identified in the completed Suite Register in Schedule A. It comprises these master terms and completed Schedules A through D, with their identified attachments. The parties enter into this Agreement on the Effective Date in Schedule A.
Full-suite access means access to every generally available capability identified as included in the agreed Suite Register, without a separate module-access purchase. It does not promise unlisted capabilities, unreleased products, a particular data license, or implementation services. Any exclusion or separately agreed service must be identified before acceptance and must not contradict a representation that it is included.
1.1 Parties. “Hunter” means Hunter Data LLC, a Nevada limited liability company, with its principal address at 1000 N. Green Valley Parkway, Suite 440-547, Henderson, NV 89074. “Subscriber” means the legal business or institution identified in Schedule A. Each is a party and together they are the parties. An affiliate is not a contracting party unless it signs its own order or an accession accepted by Hunter; Subscriber remains responsible for any affiliate users it authorizes under its order.
1.2 Definitions. “Services” means the hosted products, APIs, datasets and support included in the completed Suite Register and service specification in Schedule A. “Documentation” means the service specifications and instructions identified by version or date in Schedule A. “Customer Data” means information submitted by or for Subscriber, including search payloads, transaction records, customer and vendor records, trade-party and shipment data, case materials, and Subscriber-specific screening results and audit records. “Source Data” means independently obtained public or licensed datasets supplied through the Services. “Personal Data” means information protected as personal information or personal data under applicable law. “Business Day” means Monday through Friday, excluding U.S. federal holidays.
“Prepaid Balance” means purchased monetary service credit available in Subscriber’s wallet after cleared funding, authorized charges and adjustments. It is not a fixed quantity of searches. “Search” means a completed billable operation meeting the approved Search Specification in Schedule A. “Suite Register” means the versioned list of included capabilities, deployment availability, source coverage, applicable licensed restrictions and express exclusions. “Rate Schedule” means the versioned prices and billable units approved in Schedule A. “Usage Fees” has the meaning in Section 11.1. Other defined terms appear where first used.
1.3 Priority. A separately signed mandatory privacy or international-transfer addendum controls its subject matter. Schedule B controls data protection and security; Schedule C controls service levels and support; Schedule D controls payment authorization. Otherwise these master terms control, except that a mutually signed Schedule A may expressly identify and override a specific provision. Marketing statements, website updates, purchase-order boilerplate and unsigned policy changes do not amend this Agreement. Schedules and incorporated Documentation must be available to both parties before acceptance. No conflicting signup summary overrides the accepted terms.
2.1 Access rights. During the term, Hunter grants Subscriber a nonexclusive, nontransferable right to access and use the full suite identified in Schedule A and its Documentation for Subscriber’s internal compliance and risk-management operations, including through authorized contractors acting solely on its behalf. No resale, service-bureau use, or access for unrelated organizations is included unless Schedule A permits it. Funding amount determines available monetary credit and any expressly agreed support level; it does not remove included suite capabilities or create a separate per-module access fee.
2.2 Hunter responsibilities. Hunter will provide the Services with reasonable professional skill and care, materially in accordance with the Documentation and completed schedules, and in compliance with laws applicable to Hunter’s provision of the Services. Hunter will maintain rights sufficient to provide the contracted Source Data and permitted uses. Hunter is responsible for its personnel and subcontractors performing its obligations. Subscriber does not assume Hunter’s own statutory or contractual duties.
2.3 Account security and permitted use. Subscriber will designate authorized administrators, protect credentials, use available security controls reasonably appropriate to its use, promptly report suspected account compromise, and provide lawful, reasonably accurate inputs. Subscriber will not interfere with the Services, bypass access controls, extract Source Data for resale, or reverse engineer protected software except to the extent a restriction is prohibited by law. Subscriber may perform authorized validation and testing; intrusive security testing requires a mutually agreed scope and timing.
2.4 Changes. Hunter may improve the Services without materially reducing contracted functionality, security, or agreed data coverage. Hunter will give at least 60 days’ notice before a materially incompatible API change, unless an urgent legal or security need requires less notice, in which case notice will be as early as practicable. A material reduction requires Subscriber’s agreement; if an external legal or licensing restriction makes continued provision impossible, Hunter will explain the change, propose a reasonable alternative, and permit termination of the affected Services subject to Section 12.1 if no acceptable alternative is available.
3.1 Decision support. The Services provide analytical information, potential matches and risk indicators. Outputs are not legal, regulatory or investment advice, and do not establish that a person is sanctioned, has committed wrongdoing or is safe to transact with. Subscriber determines its own policies, thresholds, investigations, transaction decisions, account restrictions, blocking or rejection actions and regulatory filings. Hunter does not act as Subscriber’s compliance officer or submit filings unless a separate signed scope expressly provides otherwise.
3.2 Coverage and interpretation. Schedule A identifies list coverage, geographic coverage, adverse-media languages and sources, and licensed restrictions. PEP status and HIDTA or HIFCA geographic indicators are risk information, not equivalent to designation on a sanctions list. Ownership-based sanctions coverage, including indirect ownership analysis, is included only to the extent expressly described in Schedule A. Subscriber must assess requirements beyond name matching and validate that the selected configuration is appropriate for its use. Full-suite access does not make source coverage exhaustive.
3.3 Data and matching limitations. Public and licensed sources can be incomplete, inaccurate, delayed or unavailable. Names, aliases, transliteration, dates, identifiers and thresholds can produce false positives and false negatives. Hunter does not guarantee perfect detection or exhaustive coverage. These limitations do not excuse Hunter’s failure to meet its express obligations for ingestion, processing, data freshness, security or defect correction. Losses caused partly by each party are allocated according to their respective responsibility, subject to Section 11.
3.4 Integrity and material defects. Hunter will maintain source and matching-version traceability, monitor ingestion failures and stale feeds against Schedule A, and distinguish failed or incomplete screening from a completed no-match result. Hunter will promptly notify Subscriber of a known material defect or feed issue that materially affects its screening, identify the affected period and scope to the extent reasonably determinable, and provide mitigation guidance and progress updates. Where Hunter’s breach caused defective screening, Hunter will correct the defect and provide reasonable affected-record identification and reprocessing assistance without additional usage fees. These remedies do not remove other express rights under this Agreement.
3.5 Subscriber validation and records. Subscriber will evaluate relevant outputs before consequential decisions, validate configurations before production and after material changes, and retain records needed for its obligations. Hunter will support reasonable validation and provide the agreed export and provenance information. The Services are not a complete statutory recordkeeping solution unless Schedule A expressly says so and defines the required retention and export functions.
3.6 Restricted case materials. Case export is a workflow feature, not a representation that a regulatory filing is complete, accurate, accepted or submitted. Subscriber must not upload a filed SAR or information revealing a SAR’s existence unless lawful access and a separately documented restricted processing scope have been established. Confidentiality language does not itself authorize disclosure prohibited by law. Hunter will apply applicable SAR restrictions to any such information it lawfully receives.
3.7 Vendor risk management. The included vendor risk capabilities may support supplier onboarding, counterparty screening, questionnaire or evidence workflows, and monitoring as specified in Schedule A. A risk score or vendor record is not a security audit, financial-solvency opinion, certification, insurance assessment or guarantee of supplier performance. Subscriber decides vendor approval, contracting, control requirements and monitoring actions, and verifies material self-reported information. Vendor assessment and continuous monitoring sources, frequency, scope, and alerting commitments are set forth in Schedule A.
3.8 Trade screening. Included trade capabilities screen the specified trade parties, transactions, vessels, locations or other supported records against the expressly contracted sources. Party screening alone does not determine item classification, jurisdiction, country restrictions, end-use or end-user restrictions, license requirements, license-exception eligibility, customs treatment or legality of an export, reexport, import or transfer. Any automated assistance with those subjects must be expressly scoped and remains decision support. Subscriber remains responsible for transaction facts, required authorizations and lawful trade decisions. A no-match result is not permission to proceed. Continuous rescreening, entity resolution, beneficial-ownership analysis, and risk alerting are provided in accordance with the scope set forth in Schedule A.
3.9 Applicable industry provisions. Bank examination, SAR, CTR and bank-service-provider provisions apply only where relevant to Subscriber and the Services under applicable law. They do not represent that every customer is a bank or that every service is regulated as a bank service. This Agreement does not authorize consumer credit, employment, housing or other consumer-reporting eligibility use; any such use requires a separate signed agreement addressing applicable requirements.
4.1 Fees and Rate Schedule. Subscriber prepays monetary service credit into its wallet. Charges are drawn down as completed billable searches occur, at the applicable approved Rate Schedule, unless a mutually signed order expressly provides different rates. Rates are Hunter’s own published prices, not an unspecified industry average or third-party index. The Rate Schedule must state every charge, billable unit, currency, version and effective date and be available for review and retention before enrollment and every funding authorization. Hunter will show Subscriber its applicable rates and announced changes in its account. All amounts are in U.S. dollars unless expressly specified otherwise.
No separate software subscription, module-access, dataset-access or ordinary support fee applies to the included full suite. Any optional implementation, custom engineering or special support requested by Subscriber requires an express scope and price approved before it is ordered.
Prepayments purchase service credit; they are not bank deposits, escrow funds, insured deposits or interest-bearing accounts. Accounting and tax treatment is determined independently by each party. Treatment of unused balances is governed by Section 12.1 and Schedule A.
4.2 Metering and deductions. Hunter will maintain an itemized ledger showing funding, billable operations, request identifiers, applicable rates and rate versions, adjustments, credits, and any authorized buffer usage. Schedule A defines the approved Search Specification, including whether a search is per entity, request, dataset combination or another approved unit; exact chargeable endpoints and UI actions; multi-entity and batch handling; monitoring and rescreening triggers; and deduplication behavior.
Hunter will not charge for requests rejected before processing, processing that fails without a usable result, or Hunter-caused duplicate processing. A valid completed no-match result is billable. Customer resubmission of a completed request is a new operation unless documented deduplication rules apply. Hunter will document those rules and charge batch submissions only for individually completed billable operations. A failure or partial batch must identify which individual operations completed and which did not.
Viewing, retrieving, exporting or investigating a previously completed result without initiating a new billable search does not incur a separate lookup fee. A request that initiates new screening is billable only as defined in the Search Specification.
4.3 Prepaid funds. Purchased unused balances do not expire because of inactivity while this Agreement remains in effect. Nonrefundability, refund rights and treatment on termination follow Section 12.1. Hunter will apply cleared funds first to outstanding authorized buffer usage and then to available prepaid credit. A funding reversal reduces the ledger only by the reversed amount and any expressly agreed lawful fee, without double recovery. Promotional and service credits must be separately identified; they have no cash value unless expressly agreed. Funding does not lock a rate or guarantee a number of searches unless Schedule A expressly provides a rate commitment.
4.4 Optional usage buffer. A buffer exists only if expressly selected in Schedule A. It is an interest-free, repayable allowance for completed usage after purchased funds are exhausted, not free screening or an additional purchased balance. Subscriber owes only amounts actually used, up to the agreed limit, unless it expressly authorizes a higher limit. Hunter will not retroactively reduce the limit below accrued usage or initiate a payment merely because the buffer is used. Buffer charges are due within thirty (30) days after an itemized invoice or may be paid from a separately authorized top-up. If no buffer is selected, screening stops at the Prepaid Balance limit.
4.5 Alerts and exhaustion. Hunter will provide the balance alerts specified in Schedule A and clearly display the purchased balance and remaining authorized buffer separately. Once both are exhausted, Hunter may pause new billable screening without a further cure period. It will identify rejected or unprocessed requests, avoid partial silent completion and promptly notify Subscriber. Read-only access and ordinary export remain available subject to security and legal restrictions. A buffer does not guarantee uninterrupted service. Screening resumes promptly after sufficient funding clears, subject to an independent suspension ground. No interface may present repayable buffer credit as free screening or purchased credit.
4.6 Payment and disputes. Electronic debits require Schedule D or a separate recorded authorization. Invoice funding is available only if selected in Schedule A and authorized under Schedule D; credit becomes usable upon administrator configuration and environment provisioning in accordance with Schedule A. Other invoices are due within thirty (30) days after receipt.
Subscriber should identify billing errors within 60 days after the relevant statement; failure to do so does not waive rights for fraud, unauthorized debits or errors not reasonably discoverable within that period. Parties will investigate in good faith and pay undisputed amounts. Hunter will not suspend solely for a reasonably documented disputed amount while Subscriber cooperates and pays other amounts due.
4.7 Taxes and price changes. Subscriber pays applicable transaction taxes, excluding taxes on Hunter’s net income, payroll or property. No unlisted processing, inactivity or administrative fee applies. Hunter may revise its Rate Schedule, but an increase in Subscriber’s applicable rates requires at least thirty (30) days advance written notice identifying revised rates and the effective date.
Until the effective date, Subscriber’s existing rates continue. Decreases may take effect earlier. Unless a signed order guarantees a rate for a stated period, the applicable approved rates at completion apply to future usage, including usage drawn against previously funded balances and the authorized buffer. Prepayment secures monetary credit, not a fixed rate or number of operations. No rate change applies retroactively to completed usage. A signed rate commitment controls for its stated period.
Subscriber may terminate before an increase takes effect, with unused-balance treatment determined under Section 12.1. Rate changes do not increase any automatic-payment amount, frequency or limit without separate consent under Schedule D. Hunter will retain prior Rate Schedules and identify the applicable version in billing records. A new chargeable service or change in a billable operation requires express agreement and cannot be introduced by relabelling it as a rate change.
5.1 Protected information. Confidential Information means nonpublic information disclosed in connection with this Agreement that is identified as confidential or reasonably should be understood to be confidential. It includes Customer Data, nonpublic Source Data, security reports, business terms, software designs, algorithms and credentials. Information is excluded only to the extent the recipient can demonstrate lawful prior knowledge, public availability without breach, independent development without use of the information, or lawful receipt from an unrestricted third party.
5.2 Use and disclosure. The recipient will use Confidential Information only to perform or exercise rights under this Agreement, protect it with at least reasonable care, and restrict access to personnel, contractors, professional advisers, auditors and permitted subprocessors with a need to know and appropriate confidentiality duties. The recipient is responsible for their handling. Neither party may disclose the other’s name or logo for publicity without written consent.
5.3 Required disclosures. A party may disclose information to its competent regulators or as legally required, subject to applicable restrictions on SARs and other protected information. Unless prohibited, it will give reasonable advance notice of compelled disclosure, seek appropriate confidential treatment and disclose only what is required. Nothing restricts lawful regulator access or requires notice that would impede or violate a supervisory requirement.
5.4 Duration. These duties continue for five years after termination; trade secrets remain protected while legally qualifying as such, and Customer Data, Personal Data, credentials and legally restricted information remain protected for as long as retained. Return and deletion follow Schedule B and Section 12.
6.1 Ownership. As between the parties, Subscriber retains all rights in Customer Data. Hunter retains rights in the Services, Documentation and its preexisting technology; Source Data remains subject to its owners’ rights. Subscriber receives a continuing right to retain and use lawfully obtained screening results and supporting extracts for internal compliance, audit, legal and regulatory purposes, including disclosure to its regulators and advisers subject to applicable law. Any source-license restriction on those uses must be disclosed and agreed before the affected Service is ordered.
6.2 Processing license. Subscriber grants Hunter only the rights needed to process Customer Data to provide, secure, support and maintain the Services under Subscriber’s documented instructions. Hunter may not sell Customer Data, use it for advertising, enrich products for unrelated customers, or train shared or general-purpose models on it without a separate express written opt-in. Hunter may use technical operational metrics that exclude customer payloads and do not identify Subscriber or any person, subject to applicable law and without reidentification.
6.3 Security and SOC 2 status. Schedule B states Hunter’s security and data-processing obligations. Hunter implements administrative, physical and technical safeguards aligned with GLBA Standards for Safeguarding Customer Information and SOC 2 Type II trust services criteria. Hunter is preparing for formal SOC 2 Type II examination and maintains continuous monitoring across logical tenant isolation boundaries. Hunter will provide available relevant third-party security assessments and compliance attestations under confidentiality upon reasonable request.
7.1 Review rights. Hunter will reasonably support Subscriber’s risk assessment, ongoing monitoring and examinations by providing relevant control descriptions, completed questionnaires, available independent reports, material remediation summaries and continuity information. Subscriber or an independent noncompetitor auditor may conduct a proportionate review of relevant controls and records once annually on at least 15 Business Days’ notice, and additionally following a material Security Incident, substantiated material compliance concern or regulator request. Reviews will protect other customers, avoid unreasonable disruption and use existing evidence where adequate. Intrusive testing requires agreed safeguards.
7.2 Regulators and costs. Hunter will cooperate with lawful requests from authorities supervising Subscriber, including legally required access to relevant records and personnel, without imposing consent, frequency or advance-notice conditions that conflict with their authority. Routine evidence and reasonable cooperation are included. Additional customer-requested review work may be charged only at rates and a scope approved in advance, except that Hunter bears its reasonable remediation and cooperation costs attributable to its breach. No fee condition delays a legally required response.
7.3 Remediation and insurance. Hunter will address material control deficiencies affecting the Services through documented actions, owners and reasonable deadlines proportionate to risk, and communicate material overdue items. Insurance types, limits and evidence requirements are stated in Schedule A; no unlisted policy or existing coverage is represented. Insurance does not expand or replace contractual liability.
8.1 Mutual warranties. Each party warrants authority to enter into this Agreement. Subscriber warrants that its instructions and submitted data are lawfully provided for the agreed processing. Hunter warrants the performance and service obligations in Section 2.2 and that it will not knowingly introduce malicious code into the Services.
8.2 Correction. Subscriber will reasonably describe a claimed nonconformity. Hunter will investigate and correct a material failure to meet an express warranty without additional fees. If not cured within 30 days after notice, or if incapable of cure, Subscriber may terminate the affected Services subject to Section 12.1. Urgent security, regulatory and service obligations remain subject to their shorter applicable requirements. This correction process does not exclude other remedies for recoverable losses, subject to Sections 11 and 12.1.
8.3 Limited disclaimer. EXCEPT FOR EXPRESS OBLIGATIONS IN THIS AGREEMENT AND RIGHTS THAT CANNOT LAWFULLY BE EXCLUDED, EACH PARTY DISCLAIMS IMPLIED WARRANTIES, INCLUDING MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. HUNTER DOES NOT WARRANT PERFECT MATCHING, ERROR-FREE SOURCE DATA OR A PARTICULAR REGULATORY OUTCOME. NO DISCLAIMER OVERRIDES THE EXPRESS WARRANTIES, SECURITY DUTIES, SERVICE LEVELS OR LIABILITY ALLOCATIONS IN THIS AGREEMENT.
9.1 Hunter indemnity. Hunter will defend Subscriber and its officers and employees against third-party claims that permitted Services infringe intellectual-property rights, and pay damages and reasonable settlements finally awarded or approved under this section. This does not cover a claim to the extent caused by Subscriber’s unauthorized modification, unlawful use or combination with items not provided or required by Hunter where the claim would not otherwise arise. Hunter may procure continued rights or provide a materially equivalent noninfringing replacement. If neither is reasonably available, either party may terminate affected Services subject to Section 12.1; accrued defense and payment obligations remain.
9.2 Data and misconduct claims. Each party will defend the other and its officers and employees against third-party claims to the extent caused by the indemnifying party’s material breach of confidentiality or data-protection duties, gross negligence or willful misconduct, and pay damages and reasonable settlements finally awarded or approved under this section. Subscriber also covers claims that Customer Data supplied by it violates a third party’s intellectual-property rights or that its unlawful instructions caused the claim. Neither party indemnifies the other to the extent a claim was caused by the other’s breach, negligence or misconduct. Mere use of, or reliance on, the Services does not trigger Subscriber indemnity.
9.3 Procedure. The protected party will give prompt notice, with delay relieving duties only to the extent it materially prejudices the defense; allow the defending party to control the defense with competent counsel; and provide reasonable assistance at the defending party’s expense. The protected party may participate with its own counsel at its expense, except where a material conflict reasonably requires separate counsel at the defending party’s expense. No settlement may admit the protected party’s fault, impose nonmonetary obligations or fail to provide a full release without written consent, not unreasonably withheld. If the defending party fails to assume a required defense promptly, the protected party may defend and recover reasonable covered costs.
9.4 Regulatory matters. Each party remains responsible to regulators for its own duties. No party has a blanket obligation to pay the other’s fines, penalties or investigation costs. Reimbursement is available only to the extent legally permissible and attributable to a covered breach or claim under this Agreement, subject to Section 11. No indemnity restricts regulator powers or transfers a nondelegable duty.
10.1 Term. This Agreement begins on the Effective Date and continues until terminated. Unless Schedule A expressly establishes another term, either party may terminate for convenience on 30 days’ notice without an early-termination fee. A fixed order term does not remove termination rights for cause, regulatory direction or chronic failure.
10.2 Cause. Either party may terminate for a material breach not cured within 30 days after written notice, or immediately if it cannot reasonably be cured. Subscriber may terminate affected Services promptly where reasonably necessary to comply with written supervisory direction or a legal requirement, with notice and supporting explanation to the extent permitted. Either party may terminate if continued performance becomes unlawful. Insolvency-related termination is permitted only to the extent allowed by applicable law.
10.3 Suspension. In addition to balance exhaustion under Section 4.5, Hunter may suspend the minimum affected access reasonably necessary to respond to an actual or reasonably substantiated security threat, unlawful use or undisputed payment more than 15 days overdue after written demand. Hunter will provide advance notice and an opportunity to resolve the issue where reasonably feasible; otherwise it will notify promptly afterward. Suspension must be proportionate, reviewed regularly and lifted promptly after resolution. No fees accrue for unperformed operations. A security suspension does not excuse incident response, data protection or lawful export assistance.
11.1 General cap. Except as stated below, each party’s aggregate liability arising from this Agreement will not exceed the greater of $25,000 or Usage Fees paid or payable for the Services during the 12 months immediately preceding the first event giving rise to liability. “Usage Fees” means fees earned for Services actually delivered, including authorized buffer usage and any separately agreed support or other service fees; it excludes unused prepayments, taxes, refunds and promotional credit. Related events are treated as one event for this calculation, and multiple claims do not multiply the cap.
11.2 Higher cap. For breach of confidentiality or Schedule B, Security Incidents attributable to a party’s breach, and indemnity obligations under Section 9, each party’s combined aggregate liability is subject to a higher ceiling of the greater of $100,000 or twice Usage Fees described in Section 11.1. Claims otherwise subject to the general cap remain subject to that sublimit. General and higher caps are not additive.
11.3 Exclusions. Neither cap applies to fraud, willful misconduct, gross negligence, liability that cannot lawfully be limited, Subscriber’s obligation to pay properly due fees, or Hunter’s obligation to return unauthorized or erroneous charges, confirmed overpayments, or amounts refundable under Section 12.1 or applicable law. A payment obligation does not make unrelated damages unlimited.
11.4 Types of loss. Neither party is liable for consequential, special, exemplary or punitive damages, or lost profits, revenue or business opportunity, except for fraud, willful misconduct, gross negligence or liability that cannot lawfully be excluded. This exclusion does not prevent recovery, within the applicable cap, of reasonable and necessary data restoration, forensic investigation, legally required notifications, mitigation or replacement-service costs directly caused by a breach, or covered third-party damages and settlements under Section 9. Losses must be proven, reasonably mitigated and not recovered twice. Service credits offset damages for the same failure.
12.1 Financial settlement and unused balances. Unused purchased balances do not expire for inactivity during an active Agreement. Upon termination by Subscriber for convenience, validly purchased unused credit is nonrefundable except as required by applicable law. In the event of termination caused by Hunter's uncured material breach, Hunter's termination for convenience, or permanent service discontinuation, Hunter will refund the verified unused prepaid balance within thirty (30) days following the effective termination date. In the event of an announced price increase under Section 4.7, Subscriber may terminate prior to the effective date and receive a refund of verified unused prepaid credit.
Subscriber may utilize any remaining balance through the effective termination date, subject to valid suspension rights and service availability. Hunter will provide a final ledger within thirty (30) days after termination. Hunter will correct and return unauthorized or erroneous charges and confirmed overpayments within thirty (30) days after confirmation, or sooner where required by law. Legally required refunds follow applicable law.
Unused promotional and service credits have no cash value unless expressly agreed. Used authorized buffer amounts remain payable; unused buffer capacity is not a charge. Settlement must avoid double recovery. This provision does not waive rights that cannot lawfully be waived or eliminate otherwise available damages for a proven breach subject to Section 11.
12.2 Transition. For 30 days after termination, Hunter will provide secure read-only access or equivalent export of Customer Data in the agreed ordinary formats, with reasonable standard export assistance included. Subscriber may request additional transition services under an agreed scope and fee; fees do not apply to remediation Hunter already owes. Security or legal restrictions may require an alternative secure delivery method. Hunter will not withhold Customer Data as leverage in a payment dispute.
12.3 Deletion and survival. Hunter will return or delete Customer Data under Schedule B after the export window or earlier lawful instruction. Accrued payment rights, confidentiality, retained-record restrictions, permitted use of retained outputs, indemnity for covered events, liability limits, dispute provisions and obligations intended to survive continue. Hunter’s access license to Customer Data continues only as necessary for authorized transition, deletion and lawful restricted retention.
13.1 Law and disputes. This Agreement is governed by the laws of the State of Nevada, excluding conflict-of-law rules. Courts and venue are the state courts located in Clark County, Nevada and the United States District Court for the District of Nevada. Authorized representatives will first attempt resolution for 30 days after dispute notice, except for urgent relief, preservation of a claim or regulatory action. Either party may seek appropriate injunctive relief; this does not eliminate required proof or automatically establish irreparable harm.
13.2 Notices. Legal notices must be sent to legal-contact addresses in Schedule A by tracked delivery or email. Email notice is effective when acknowledged by a nonautomated response or otherwise verifiably received; an undelivered email is not notice. Operational, billing and security notices use designated contacts, with urgent escalation under Schedule C. Each party will maintain current contacts.
13.3 Assignment. Neither party may assign this Agreement without the other’s consent, not unreasonably withheld, except to a successor in a merger, reorganization or sale of substantially all relevant assets that assumes the obligations and can perform them. Hunter will give reasonable prior notice where permitted, or prompt notice afterward. Subscriber may terminate without penalty if the successor creates a substantiated material security, regulatory or competitor-confidentiality risk that is not reasonably resolved. No assignment releases obligations accrued before assignment. Unused balances follow Section 12.1.
13.4 Events outside reasonable control. Neither party is liable for delay to the extent caused by an event beyond reasonable control that could not reasonably have been prevented or overcome, provided it promptly notifies the other and mitigates. Ordinary staffing shortages, inadequate capacity, lack of funds and avoidable security failures are excluded. A supplier outage qualifies only if it independently meets this standard. Security, notification, continuity, data-return and required refund duties continue to the extent capable of performance. Either party may terminate affected Services after 30 consecutive days of material interruption, subject to Section 12.1.
13.5 Entire agreement and amendments. This Agreement is the complete agreement for its subject matter and replaces prior discussions and onboarding terms for these Services. Changes require mutual written or recorded electronic agreement by authorized representatives, except price changes expressly allowed by Section 4.7. Continued use alone does not accept unrelated revised terms. A waiver must be express and does not waive later breaches. If a provision is unenforceable, it is limited only as law permits and remaining provisions continue. Parties are independent contractors; no agency, partnership or general third-party beneficiary rights are created.
13.6 Execution and retained copy. Counterparts and electronic signatures are effective to the extent permitted by law. Parties agree to use electronic records for this transaction, with a retainable copy available before acceptance. The accepting individual represents authority to bind Subscriber. Hunter must provide the accepted Agreement, completed Schedules A–D, Suite Register, Rate Schedule, Search Specification and all incorporated attachments in an accessible form capable of accurate reproduction, recording version, acceptance time, institution and authorized signer. Payment consent must be separately recorded under Schedule D.
No essential field may remain incomplete at acceptance. No incomplete field may be filled or materially changed unilaterally afterward. The displayed terms and retained copy must match the accepted snapshot, including effective date, scope, funding and rates. A pending application, account provisioning or unsigned draft is not recorded contractual assent.
This Schedule A sets forth the commercial order and service specifications. An optional item is included in accordance with the full-suite platform representation. The customer category configures relevant compliance provisions and screening workflows under unified platform access.
Hunter legal name: Hunter Data LLC. Entity type and formation jurisdiction: Nevada limited liability company. Principal address: 1000 N. Green Valley Parkway, Suite 440-547, Henderson, NV 89074.
Subscriber legal name: [SUBSCRIBER LEGAL NAME]. Entity type: Commercial / Institutional Entity. Address: [SUBSCRIBER HEADQUARTERS ADDRESS]. Customer category: Bank or Financial Institution. Effective Date: Upon Administrator Activation. Tenant identifier: Assigned upon configuration. Authorized affiliates: Permitted institutional users and entities under Subscriber control.
Governing law: State of Nevada. Courts and venue: State courts located in Clark County, Nevada and the United States District Court for the District of Nevada. Hunter legal notices: legal@hunterdata.ai, 1000 N. Green Valley Parkway, Suite 440-547, Henderson, NV 89074. Hunter security contact: security@hunterdata.ai. Hunter billing and support: billing@hunterdata.ai. Subscriber legal, security, and billing notices: Recorded in electronic onboarding profile.
Selected funding tier: Standard Initial Deposit ($2,500). Initial purchased monetary credit: USD $2,500.00. Funding method: Corporate Invoice (Net 30) or Business Credit Card. Minimum initial funding: $2,500.00.
Full-suite entitlement applies as listed in A3. A larger funding amount does not unlock otherwise included modules. Standard institutional support is included with no separate subscription or seat licensing fees. No implied minimum ongoing spend applies.
Repayable usage buffer: Selected. Monetary limit: USD $250.00 (10% standby usage buffer); repayment period: thirty (30) days from statement date. The usage buffer is interest-free finite standby credit to ensure continuous operation after prepaid funds are exhausted; screening pauses automatically upon total exhaustion. Purchased and repayable balances are accounted for separately.
Service commencement: Upon administrator activation and client configuration. Term: Continuous rolling institutional agreement, terminable by either party upon thirty (30) days written notice. Invoice due period: Net 30 days from invoice issuance.
Rate Schedule: Platform screening rates published within the Hunter Gateway billing console. Rates apply per completed billable search operation. Notice of rate adjustments: At least thirty (30) days advance written notice pursuant to Section 4.7. No separate module-access charge applies to included suite capabilities.
Search Specification: A billable search is defined as a completed query against designated sanctions, PEP, adverse media, regulatory enforcement, or watchlist indexes resulting in a verified risk determination or confirmed no-match result. Deduplication window: Identical requests resubmitted within a five (5) minute idempotency window are not billed twice. Viewing, retrieving, exporting, or auditing historical search results does not incur additional lookup charges.
Operation capacity equals available purchased monetary credit divided by applicable prices. Prepayment purchases monetary service credit, not a fixed quantity of searches. Standby buffer capacity provides additional continuity credit.
Unused-balance policy: Governed by Section 12.1. Unused prepaid balances do not expire during active agreement term. Refunds upon qualified termination are processed within thirty (30) days.
Alerts: Automated system and email notifications are delivered at 20% and 5% of deposit remaining, upon initiation of standby buffer usage, and upon balance exhaustion.
Suite Register (v2026.4). Included products and features: Bank Compliance Module (BSA/AML, OFAC/Sanctions, PEPs, HIDTA/HIFCA, Adverse Media, Real-Time REST API & Web UI). The included capabilities encompass generally available screening, watchlist enrichment, entity resolution, relationship graph investigation, adverse media screening, real-time monitoring, and API workflow integration mapped to the Search Specification.
Included platform capabilities: Hunter Gateway Screening Engine, Link Explorer Relationship Graph, Batch Screening API, Watchlist & Sanctions Monitor, Adverse Media Screener, and Audit Log Verification. All generally available modules are included under the unified platform access grant.
Documentation versions and endpoints: Published via docs.hunterdata.ai and platform specifications. Deployment boundaries: Multi-tenant cloud hosting on AWS US-East with dedicated logical database segregation. Rate, batch and payload limits: Standard API rate limits apply pursuant to the technical specification.
Source Register: Global Sanctions & Watchlists (OFAC, UN, EU, UK HMT, DFAT, OSFI), Politically Exposed Persons (PEP Levels 1-4), Law Enforcement & Regulatory Enforcement (SEC, CFTC, FINRA, FCA, Interpol, FBI), Adverse Media (multilingual risk feeds), and Trade & Export Restrictions (BIS Entity List, Military End-User, ITAR/EAR).
Vendor & Trade Risk Scope: Enterprise counterparty screening, beneficial ownership threshold resolution (50% rule and relational graph traversal), phonetic/transliteration name matching across non-Latin scripts, and continuous rescreening alerts as detailed in platform documentation.
Results and audit evidence: Comprehensive cryptographic audit log entries and JSON/CSV data exports capturing Request ID, UTC Timestamp, Match Score, Match Entity ID, Watchlist Source Version, Engine Version and Applied Rule Configurations. Hunter-controlled retention follows Schedule B.
Monthly availability target: 99.9% uptime excluding scheduled maintenance. Support hours: 8:00 AM – 8:00 PM Eastern Time, Monday through Friday. Critical-incident acknowledgment: within one (1) hour (24/7). Recovery Time Objective (RTO): 4 hours. Recovery Point Objective (RPO): 1 hour. Scheduled maintenance notice: at least 72 hours advance notice except emergency security remediation.
Insurance coverage: Hunter maintains Technology Errors & Omissions and Cyber/Privacy Liability insurance policies through reputable commercial insurance carriers.
Assurance Status: Multi-tenant logical isolation, TLS 1.3 transit encryption, AES-256 rest encryption, GLBA Safeguards compliance architecture.
The parties agree to these master terms and completed Schedules A–D, including expressly identified attachments and amendments. Specific negotiated overrides: None unless set forth in a mutually signed Order Form.
For Hunter: Hunter Data LLC. Authorized Signer: Operations & Compliance Officer. Signature: Recorded electronic assent on file.
For Subscriber: [SUBSCRIBER LEGAL NAME]. Authorized signer: [AUTHORIZED SIGNER], [TITLE]. Signature: Recorded electronic assent on file.
For Customer Data processed on Subscriber’s behalf, Subscriber acts as controller or business and Hunter acts as processor or service provider to the extent those roles apply under law. The subject matter and purpose are provision, security, support and maintenance of the included screening Services. Processing consists of receipt, matching, retrieval, storage, access, export and deletion during the term and authorized transition or retention periods. Data subjects may include customers, prospective customers, beneficial owners, representatives, suppliers, vendor personnel, trade parties and transaction counterparties.
Permitted data categories: Names, aliases, corporate registration numbers, tax identifiers, dates of birth, geographic addresses, and transaction screening metadata. Prohibited categories: Full payment card numbers, card security codes, customer banking PINs, or legally restricted SAR filings. Subscriber will minimize submitted data. No full payment-card number, security code, account authentication secret or legally restricted SAR material may be submitted as a screening field. Schedule D governs payment collection through a secure processor.
This Agreement, completed schedules and lawful authorized configuration or support instructions constitute Subscriber’s documented instructions. Hunter will notify Subscriber if it reasonably believes an instruction violates data-protection law and may pause affected processing pending clarification. Hunter will not sell or share Customer Data for targeted advertising, combine it with unrelated customer data for independent purposes, or retain, use or disclose it outside contracted purposes except as law permits and this Agreement allows. Hunter will notify Subscriber if it can no longer meet applicable processor or service-provider obligations and permit reasonable steps to stop and remediate unauthorized use.
Hunter’s independent processing of account administration records and independently obtained Source Data is outside this processor appointment; Hunter remains responsible for its legal basis, notices, rights handling and lawful provision. Customer payloads do not become independently obtained Source Data. Where GDPR, UK GDPR or other law requires additional terms or transfer safeguards, the parties will execute them before affected processing begins. This Schedule does not itself supply international standard contractual clauses.
Before production Customer Data processing and throughout the term, Hunter will maintain comprehensive administrative, physical, and technical safeguards proportionate to the Services and risk profile, designed to protect the security, confidentiality, and integrity of Customer Data.
Governance and people. Maintain a written information-security program, named accountable owners, risk assessment, workforce confidentiality obligations and security awareness training. Review material risks and remedial actions at least annually and after material changes.
Access and isolation. Enforce least-privilege access, unique workforce identities, multifactor authentication for privileged and remote administrative access, timely access removal and periodic access reviews. Protect customer API credentials, implement logical tenant isolation and test authorization boundaries. Limit personnel access to authorized operational need.
Encryption and secrets. Protect Customer Data in transit with TLS 1.2 or later and at rest with AES-256 or an equivalent industry-standard mechanism appropriate to the storage system. Restrict key and secret access, manage rotation and revocation, and prohibit production secrets in source code or unrestricted logs.
Secure operation. Maintain asset inventory, supported software, risk-based vulnerability scanning and remediation, reviewed and tested changes, malware defenses where appropriate and security monitoring. Independently test relevant externally exposed systems at least annually and after material changes where risk warrants. Address critical exposures promptly through correction or documented compensating controls and track unresolved risk.
Logging and integrity. Maintain access-restricted, tamper-evident records sufficient to investigate administrative and screening events; minimize personal information in logs. Monitor source ingestion, processing failures and unauthorized access. Apply B5 retention rather than indefinite payload retention.
Resilience. Maintain documented incident-response and business-continuity procedures, protected backups sufficient for approved recovery objectives, and restore and incident exercises at least annually. Record outcomes and remediate material failures. Do not materially reduce these safeguards during the term.
Any operational amendment to security controls must preserve applicable legal and regulatory obligations and be documented in writing prior to implementation.
“Security Incident” means actual unauthorized access to, acquisition, disclosure, alteration, destruction or loss of Customer Data in Hunter’s or its subprocessors’ control, or a material compromise of Services affecting Customer Data confidentiality, integrity or availability. Unsuccessful attempts without compromise are excluded but remain subject to monitoring.
Hunter will notify Subscriber without undue delay, and in any event within twenty-four (24) hours after confirmed awareness of a Security Incident affecting Subscriber Customer Data. Hunter will not wait for a completed investigation. Initial notice states available facts, affected services and data categories, known or estimated timing and impact, containment steps and incident contact. Hunter will provide staged updates, reasonable evidence preservation, assistance with legal assessments and notifications, and a written root-cause and corrective-action summary promptly after the investigation permits. Unknown information may follow.
Hunter will also notify Subscriber as soon as possible after determining a disruption meets an applicable bank-service-provider notification threshold; the contractual outer limit does not delay earlier mandatory notice. Subscriber controls customer and regulator communications unless law requires Hunter to notify directly. Parties coordinate where lawful. Notice is not an admission of liability. Costs and liability follow Sections 9 and 11.
Approved Subprocessor Register (v2026.1): Amazon Web Services (AWS) Inc. (Cloud Infrastructure, Hosting & Encryption, US-East) and MongoDB Enterprise Atlas (Logical Data Persistence & Audit Logs, US-East).
Subscriber authorizes listed subprocessors. Hunter will impose materially protective written obligations relevant to delegated work and remain responsible for performance. Hunter will give at least 30 days’ advance notice of a new subprocessor or material processing-location change. Subscriber may reasonably object on data-protection, security or regulatory grounds within 15 days. Parties will seek an alternative; if unresolved before the proposed change, Subscriber may terminate affected Services subject to Section 12.1. Hunter will not route Customer Data to the disputed provider or location while an objection remains unresolved. Emergency replacement requires prompt notice and equivalent protections but does not waive law or objection and exit rights.
Retention Register: Raw screening payloads and audit records are retained for seven (7) years to satisfy BSA/AML and OFAC recordkeeping requirements. Inactive caches and failed queues are purged within ninety (90) days.
After the Section 12 export window, or earlier authorized deletion request, Hunter will delete affected Customer Data from active systems, indexes, caches and queues within thirty (30) days, subject to lawful regulatory retention. Backup snapshots expire within ninety (90) days after active deletion.
Where law requires retention, Hunter will identify categories, legal basis and period to the extent permitted, restrict processing to that purpose, maintain protections and delete when the basis ends. Customer-directed legal holds require documented scope and review. Hunter will not apply a universal AML retention period to all Customer Data without applicable legal basis or Subscriber instruction.
Hunter will refer Customer Data requests to Subscriber without undue delay, ordinarily within three Business Days, and not respond substantively except on Subscriber’s instruction or as law requires. Hunter will provide reasonable assistance with rights requests, risk and impact assessments, regulator consultations and compliance evidence, taking account of processing and available information. Ordinary assistance is included; unusually extensive work requires separately approved fees, except remediation or assistance owed because of Hunter’s breach. Sections 5 and 7 govern protected disclosure and audit access.
The production service boundary, monthly availability target, support coverage, acknowledgment targets, update cadence, maintenance cap and recovery objectives are set forth in Schedule A Section A4. Availability is measured across all calendar minutes in a month at the Hunter-controlled production API or application boundary. A minute is unavailable if a valid in-scope request cannot be accepted and completed because of a Hunter-controlled failure; a materially affected portion is measured for that portion. Failed or incomplete screening is not a successful no-match response. Performance and source-freshness failures remain subject to separate duties even when the service is reachable.
Monthly Availability = 100 × (eligible minutes minus unavailable eligible minutes) ÷ eligible minutes. Eligible minutes are calendar minutes less permitted exclusions. Hunter retains monitoring evidence and provides a monthly summary on request. Subscriber may submit reasonable contrary evidence; parties resolve discrepancies in good faith. If no eligible minutes exist, no percentage is calculated and the underlying cause is evaluated under termination and performance provisions.
Exclusions are limited to scheduled maintenance within the agreed window and cap with required notice; Subscriber-caused failures; Subscriber-requested downtime; lawful proportionate suspension; and qualifying Section 13.4 events. Emergency maintenance counts as unavailability unless another exclusion applies. Ordinary hosting or supplier failure is not automatically excluded. Excluded downtime does not excuse notice, continuity or mitigation.
If Monthly Availability is below the target specified in Schedule A, Hunter credits 5% of the affected Service’s Usage Fees for that month for an availability shortfall up to 0.5 percentage points; 10% for a shortfall over 0.5 and up to 1.0 percentage point; and 20% for a shortfall over 1.0 percentage point. Credits are capped at 20% of that month’s affected Usage Fees and exclude unused prepaid funds.
Hunter applies approved credits automatically within 30 days after month-end when its records establish a miss. Subscriber may submit a claim within 60 days with available evidence. Credits do not expire while the account is active and have no cash value on closure unless expressly agreed.
If Hunter misses the Monthly Availability target in three months of a rolling six-month period, or a nonexcluded outage materially prevents screening operations for twenty-four (24) consecutive hours, Subscriber may terminate affected Services on written notice within thirty (30) days after the qualifying event, subject to Section 12.1.
Credits are the sole monetary remedy solely for an availability-target miss without a separate breach; they do not displace remedies for security, confidentiality, data loss, willful misconduct or other independent breach. There is no double recovery for the same loss.
Critical incidents include production inability to screen, a material security compromise or a known material screening-integrity failure. High priority means substantial degradation with a workaround; normal priority covers noncritical defects and questions. Parties may reclassify an incident based on actual impact. Response targets mean human acknowledgment and commencement of triage, not guaranteed resolution. Hunter will maintain the approved urgent escalation route and communicate material changes in impact, workarounds and recovery estimates.
Recovery objectives in Schedule A are contractual targets supported by documented plans and testing. Failure requires prompt escalation, communication of actual data loss and service impact, and a corrective-action plan; acknowledgment alone does not satisfy recovery objectives. Material or repeated failure may constitute a breach under Section 10. Hunter will reconcile pending and retried work during recovery and avoid duplicate charges.
This authorization applies only to a business payment account and does not authorize consumer-account debits. Subscriber authorizes Hunter Data LLC, using its authorized payment processor (PayPal, Inc.), to initiate only expressly selected payment entries. The signer confirms authority over the identified account. An unselected, incomplete or unchecked recurring option is not authorized.
Payment method: PAYPAL / CREDIT CARD. Authorized account credentials recorded electronically through secure payment infrastructure (PayPal, Inc.) or issued Net 30 corporate invoice.
Bank routing, payment account, and payment card information must be submitted exclusively through Hunter’s secure payment infrastructure (PCI DSS Level 1 compliant processor). Full account numbers and security verification codes are not stored within this Agreement.
Initial one-time electronic funding authorization: Confirmed upon enrollment. Exact amount: USD $2,500.00. Method: Selected electronic payment method or Net 30 corporate invoice. Funds become usable upon administrator activation and client environment configuration.
For invoice/manual remittance: Invoices are rendered in United States Dollars for the approved deposit amount, payable within thirty (30) days (Net 30) via ACH or wire remittance in accordance with secure wiring instructions stated on the invoice.
Manual subsequent funding requires an authorized administrator to approve the exact amount and initiation date through a recorded secure action or signed instruction. Hunter will provide a receipt and retainable authorization record. Cleared top-ups first settle used authorized buffer credit and then add available purchased credit.
Optional automatic replenishment: Not enabled by default. Automatic replenishment may be configured by authorized administrators within the Hunter Gateway billing console.
Any authorization permits only amounts properly selected under this Schedule. A changes-in-rates notice is not a new payment authorization.
Subscriber may revoke or change future electronic authorization through enabled account payment controls or notice to billing@hunterdata.ai. Hunter will acknowledge and implement it promptly and no later than three Business Days after receipt.
ACH entries will comply with applicable law, applicable Nacha Operating Rules and the originating institution’s requirements. Subscriber will coordinate required debit filters or allowlisting with its bank. Error-correction entries are permitted only as authorized by applicable rules and law; a returned payment does not authorize a larger replacement debit or unrestricted reinitiation. No unlisted return fee applies. Nothing waives rights concerning unauthorized or erroneous transactions.
Payment records will identify amount, timing, method, selected consent, institution, authorized signer, version and revocation history. Hunter will provide a copy and retain evidence as required by rules and law. A processor or originating bank may require compatible additional authorization or verification before activation; this Schedule does not represent their approval.
Subscriber legal entity: [SUBSCRIBER LEGAL NAME]. Authorized account signer name and title: [AUTHORIZED SIGNER], [TITLE]. Payment authorization recorded electronically pursuant to Schedule D upon enrollment submission. No payment authorization is inferred from agreement assent alone.