RunHarvester Terms of Service

These Terms of Service (the "Terms") govern access to and use of RunHarvester. RunHarvester is a business-oriented web-data operations service operated by Isentró Kft. These Terms form a legally binding agreement between Isentró Kft. and the Customer.

Please read these Terms carefully. By creating an account, accepting an Order, clicking to accept these Terms, starting a trial, purchasing or receiving credits, accessing an API, or otherwise using the Service, the Customer agrees to the Agreement. A person accepting on behalf of an organization represents that the person has authority to bind that organization.

Important notice

• The Service is intended for business, professional, institutional, and organizational use, not personal or household consumer use.
• The Customer decides which Targets, data, credentials, routing parameters, extraction rules, workflows, and recipients it uses. The Customer is responsible for the legality of those choices and for its later use of results.
• A technical ability to access a page, use a browser, route through a proxy, submit credentials, or interact with a challenge does not establish legal permission to do so.
• Publicly accessible data is not automatically free of privacy, intellectual-property, database-right, contractual, confidentiality, or other restrictions.
• RunHarvester does not guarantee that any Target will be accessible, that any request will succeed, or that any output will be complete, accurate, current, unique, lawful for the Customer's purpose, or suitable for a particular decision.
• Data API result content is ordinarily available for seven days after completion. The Service is not an archival or backup service unless a separate written agreement expressly says otherwise.
• The Acceptable Use requirements in Section 10 are material conditions of the Agreement.

1. Provider

The Service is provided by:

Isentró Kft.
Hungarian company registration number: 01-09-444499
Hungarian tax number: 32822933-1-42
Registered office: 1082 Budapest, Corvin sétány 6, 8th floor, unit 4, Hungary
Website: https://runharvester.com
Documentation: https://docs.runharvester.com
Legal and support contact: [email protected]

In these Terms, "RunHarvester", "we", "us", and "our" refer to Isentró Kft.

2. Contract structure and acceptance

2.1 The Agreement

The "Agreement" consists of, as applicable:

1. an Order Form, statement of work, enterprise agreement, or other document signed by both parties (an "Order");
2. these Terms;
3. the RunHarvester Data Processing Addendum (the "DPA") where RunHarvester processes Customer Personal Data as a processor or sub-processor;
4. the Privacy Policy and Cookie Policy for processing where RunHarvester acts as a controller;
5. any service-level agreement, security schedule, or product-specific terms expressly incorporated into an Order; and
6. the Documentation and policies expressly incorporated by reference.

Marketing pages, demonstrations, sales discussions, proposals not signed by both parties, roadmaps, forecasts, feature previews, and general statements about future functionality do not create contractual commitments.

2.2 Electronic acceptance

The Customer agrees that electronic acceptance, account registration, an API request made with a Customer credential, continued use after an effective update, or another legally recognized electronic act may bind the Customer to the Agreement. The Customer should retain a copy of the version accepted.

2.3 Business-use representation

The Customer represents that it enters into the Agreement primarily for purposes relating to its trade, business, craft, profession, public function, or organizational activity, and not as a consumer acting for personal or household purposes. If mandatory consumer law nevertheless applies, nothing in the Agreement excludes a right that cannot lawfully be excluded.

2.4 Order of precedence

If documents conflict, the following order applies, but only for the subject matter of the conflict:

1. the EU Standard Contractual Clauses and the mandatory clauses of the UK Addendum;
2. a signed Order that expressly identifies the provision it overrides;
3. the DPA for the processing of Customer Personal Data;
4. a signed service-level or security schedule;
5. these Terms;
6. the Privacy Policy and Cookie Policy; and
7. the Documentation.

A purchase order or vendor portal term issued by the Customer is for administrative convenience only and does not modify the Agreement unless RunHarvester expressly agrees in a document signed by an authorized representative.

3. Definitions

In the Agreement:

• Account means a RunHarvester account, organization, workspace, project, environment, or similar access arrangement.
• Affiliate means an entity that directly or indirectly controls, is controlled by, or is under common control with a party.
• Applicable Law means any law, regulation, binding court order, sanction, regulatory requirement, or legally enforceable rule applicable to a party, the Service, a Target, Customer Content, or the Customer's use.
• Authorized User means a person whom the Customer permits to access or use the Service through the Customer's Account.
• Customer means the person or entity entering into the Agreement, including an organization on whose behalf an Account is created or an Order is accepted.
• Customer Content means data, instructions, configurations, files, credentials, secrets, headers, cookies, selectors, schemas, recipes, workflows, requests, pages, evidence, outputs, results, and other material submitted to, transmitted through, generated for, or retrieved through the Service on the Customer's behalf.
• Customer Personal Data has the meaning given in the DPA.
• Documentation means the then-current technical documentation, API specifications, product notices, and operational instructions published by RunHarvester for the Service.
• Fees means amounts payable for the Service, including recurring, prepaid, usage-based, overage, support, professional-service, tax, and other agreed charges.
• Output means a response, result, event, dataset, screenshot, evidence item, extraction, generated recipe, classification, or other material returned or made available to the Customer through the Service.
• Personal Data means information relating to an identified or identifiable individual and equivalent terms under Applicable Law.
• Restricted Data means data identified as restricted in Section 10.7 or the DPA, including certain Sensitive Data, regulated data, credentials, and private communications.
• Sensitive Data means special-category, sensitive, or highly regulated Personal Data, including health, biometric, genetic, sexual-life, political, religious, precise-location, government-identifier, financial-account, authentication, private-communication, children's, and criminal-offence data, as applicable.
• Service means RunHarvester websites, dashboard, APIs, proxy routing, web retrieval, browser workflows, extraction, AI-assisted features, evidence, result delivery, support, billing, and related functionality made available by RunHarvester.
• Target means a third-party website, page, API, server, endpoint, account, network resource, or other destination selected or reached by a Customer request.
• Third-Party Service means a product, website, network, proxy, identity provider, payment service, AI provider, integration, webhook destination, or other service not controlled by RunHarvester.

4. Eligibility, authority, and Authorized Users

4.1 Minimum age

A natural person must be at least 18 years old and legally capable of entering into a contract to create an Account or accept the Agreement. The Customer must not permit a person under 18 to administer an Account. Use by a minor as an Authorized User requires a separately approved organizational arrangement, all legally required authorization, and appropriate supervision.

4.2 Authority

A person using a business email address, creating an organization, accepting an Order, or using the Service for an employer, client, public body, or other entity represents that the person:

• has authority to act for that entity;
• has authority to bind it to the Agreement;
• is permitted to submit the relevant Targets, credentials, instructions, and Customer Content; and
• will not exceed the authority granted by that entity or by an upstream controller.

If the person lacks authority, the person may be individually responsible to the extent permitted by law.

4.3 Authorized Users

The Customer controls and is responsible for its Authorized Users. The Customer must:

• authorize only users with a legitimate business need;
• assign least-privilege roles and API scopes;
• keep Account and organization information accurate;
• promptly remove or restrict users whose authorization ends;
• ensure each user complies with the Agreement; and
• remain responsible for actions performed through its Account, except to the extent caused by RunHarvester's breach of the Agreement.

4.4 Managed organizations

An organization owner or administrator may control user access, Customer Content, billing, keys, logs, export, deletion, and other Account settings. An Authorized User using an organization-managed email or workspace understands that the organization may administer that access and related data.

5. Accounts, credentials, and access security

5.1 Registration information

The Customer must provide accurate, current, and complete registration, billing, tax, use-case, and verification information. RunHarvester may reject, suspend, or close an Account if information is materially inaccurate, incomplete, misleading, unverifiable, or associated with abuse.

5.2 Credential protection

The Customer must protect passwords, multi-factor authentication methods, recovery codes, API keys, proxy credentials, target credentials, webhook secrets, tokens, and connected services. The Customer must not:

• disclose a full secret in a public repository, URL, client-side application, analytics event, support message, or log;
• share a personal credential between users;
• permit unauthorized third-party access;
• reuse a compromised secret; or
• attempt to recover or derive another Customer's credential.

The full value of an API key may be shown only once. RunHarvester may retain a non-reversible verification value, prefix, scope, status, and audit metadata.

5.3 Security notification

The Customer must notify RunHarvester promptly at [email protected] if it suspects unauthorized access, credential exposure, account takeover, an incorrect webhook destination, or other security issue. The Customer must rotate affected credentials and take reasonable containment steps without waiting for RunHarvester.

5.4 Account activity

RunHarvester may treat activity authenticated through the Customer's credentials as authorized by the Customer until RunHarvester has a reasonable opportunity to act on a valid compromise notice. RunHarvester is not responsible for unauthorized activity caused by the Customer's failure to secure or revoke its credentials, except to the extent caused by RunHarvester's breach.

6. Access to the Service

6.1 Limited right to use

Subject to the Agreement and payment of applicable Fees, RunHarvester grants the Customer a limited, non-exclusive, non-transferable, non-sublicensable, revocable right during the applicable term to access and use the Service for the Customer's internal business purposes and permitted services for its own clients.

This right does not transfer ownership of the Service, software, infrastructure, proxy inventory, Documentation, or RunHarvester technology.

6.2 Client and agency use

A Customer may use the Service to perform lawful work for a client only if the Customer:

• has authority from the client;
• remains responsible for the client's instructions and use case;
• has an appropriate contract and, where applicable, data-processing terms with the client;
• does not disclose RunHarvester credentials to the client unless expressly permitted; and
• ensures that the client receives no broader rights than the Customer has under the Agreement.

The Customer may not operate a white-label proxy or scraping resale service, pool Accounts, broker credentials, or resell raw Service capacity without RunHarvester's prior written approval.

6.3 Documentation and API changes

The Customer must use supported interfaces and follow the Documentation. RunHarvester may introduce, change, deprecate, or remove endpoints, schemas, fields, limits, authentication methods, providers, or workflows. Where reasonably practicable, RunHarvester will give advance notice of a material breaking change to a generally available paid API, unless an urgent security, legal, provider, or stability issue requires faster action.

6.4 No implied exclusivity

The Agreement is non-exclusive. RunHarvester may provide similar services to others and may independently develop products, methods, or know-how, provided it does not use the Customer's Confidential Information in breach of Section 21.

7. Service functionality and operational characteristics

7.1 General description

The Service may provide web requests, asynchronous jobs, proxy routing, browser execution, structured extraction, recipes, evidence, events, result delivery, APIs, Account administration, and related operational tools. The precise functionality available to a Customer depends on the Account, Order, configuration, jurisdiction, use-case approval, provider availability, and current Documentation.

7.2 Asynchronous operation

Requests may be queued, retried, rerouted, delayed, cancelled, recovered, or failed. Status and event information reflects the Service's current record and may be updated as processing continues. A request accepted by an API is not a promise that it will complete successfully.

7.3 Request modes and routing

The Service may use direct HTTP, browser execution, datacenter routing, residential routing, or combinations of these methods. RunHarvester may select or change an underlying endpoint, provider, route, browser implementation, retry strategy, or operational method where consistent with the Customer's documented parameters and maximum-cost settings.

7.4 No fallback contrary to configured restrictions

Where the Service offers a setting intended to prevent a particular fallback, region, proxy class, or maximum usage amount, RunHarvester will apply the setting according to the Documentation. The Customer remains responsible for testing the configuration and must not assume that an undocumented setting has a particular effect.

7.5 Results and temporary artifacts

Data API result content is ordinarily available for seven days after completion, unless the product, an Order, legal hold, abuse investigation, or shorter Customer-controlled setting specifies otherwise. Screenshots, evidence, traces, caches, and temporary artifacts may have a different and often shorter lifetime. Browser one-run session state is intended to exist only for the relevant run and to be deleted when the run reaches a terminal status.

The Customer must retrieve and securely store required Output before it expires. RunHarvester is not a system of record, records-management service, or backup provider unless an Order expressly says so.

7.6 Service boundaries

The Service does not include legal clearance, permission from a Target, verification of the Customer's lawful basis, intellectual-property licensing, accuracy verification, data-subject notice delivery, records-management compliance, or human review of Output unless expressly included in an Order.

8. Customer responsibilities

The Customer is responsible for its use of the Service, including for:

• selecting lawful and proportionate Targets, methods, routes, fields, selectors, schemas, and recipients;
• determining and documenting the legal basis for processing Personal Data;
• giving required privacy notices, including notices for indirectly collected data;
• respecting valid objections, opt-outs, deletions, suppression requests, access restrictions, and contractual duties;
• conducting a legitimate-interests assessment, data-protection impact assessment, transfer assessment, AI impact assessment, or other review where required;
• obtaining required permission to use accounts, credentials, copyrighted material, databases, and protected services;
• configuring reasonable rates, concurrency, retries, and schedules;
• validating Output before use;
• maintaining an independent backup where needed;
• securing downstream systems, webhooks, exports, and Authorized User access;
• complying with laws applicable to marketing, profiling, surveillance, employment, credit, housing, insurance, health, education, migration, policing, and other regulated uses; and
• responding to claims and requests arising from the Customer's collection or later use of data.

RunHarvester's review, automated guard, successful request, support response, or failure to block an activity does not constitute legal approval and does not transfer these responsibilities to RunHarvester.

9. Customer Content, instructions, and Output

9.1 Customer rights and limited license

As between the parties, the Customer retains its rights in Customer Content. The Customer grants RunHarvester and its authorized sub-processors a worldwide, non-exclusive, limited right to host, receive, access, reproduce, transmit, route, transform, execute, display, cache, secure, troubleshoot, and delete Customer Content only as reasonably necessary to:

• provide the Service and comply with the Customer's documented instructions;
• maintain security, reliability, billing integrity, and abuse prevention;
• provide support requested by the Customer;
• comply with Applicable Law; and
• enforce the Agreement.

This license ends when no longer needed for those purposes, subject to applicable retention, backup, legal-hold, and dispute requirements.

9.2 Customer warranties

The Customer represents and warrants that:

• it has all rights, authority, permissions, and lawful bases necessary for Customer Content and the instructed processing;
• Customer Content and instructions do not infringe or misappropriate rights or violate Applicable Law;
• credentials, cookies, accounts, and sessions submitted to the Service are lawfully controlled or authorized;
• any instruction from an upstream controller permits the appointment of RunHarvester and relevant sub-processors; and
• the Customer will not instruct RunHarvester to make an unlawful transfer or perform unlawful processing.

9.3 No ownership of third-party material

RunHarvester does not grant the Customer ownership of content obtained from a Target. Copyright, database rights, privacy rights, personality rights, trade secrets, contractual restrictions, and other third-party rights remain with their holders. The Customer must determine what it may collect, retain, reproduce, transform, combine, publish, sell, train on, or otherwise use.

9.4 Output license from RunHarvester

To the extent RunHarvester owns a transferable right in Customer-specific Output generated solely for the Customer, and subject to payment of applicable Fees, RunHarvester grants the Customer a perpetual, worldwide, non-exclusive right to use that RunHarvester-owned portion for the Customer's lawful business purposes. This does not include:

• third-party content or data;
• RunHarvester software, platform components, general extraction engines, libraries, models, templates, proxy inventory, or Documentation;
• open-source components governed by separate licenses;
• confidential provider technology; or
• any right that RunHarvester does not own or cannot transfer.

9.5 Aggregated and de-identified information

RunHarvester may create and use statistics that are aggregated or effectively de-identified so that they do not identify the Customer, an Authorized User, a Data Subject, or Customer Confidential Information. RunHarvester may use those statistics to operate, secure, measure, plan, and improve the Service. RunHarvester will not attempt to re-identify effectively de-identified Customer Personal Data except to test whether de-identification is effective where permitted by law.

9.6 Feedback

If the Customer voluntarily provides ideas, suggestions, or feedback, the Customer grants RunHarvester a perpetual, irrevocable, worldwide, royalty-free right to use and incorporate that feedback without restriction or attribution. This does not permit disclosure of Customer Confidential Information.

10. Acceptable Use Policy

This Section 10 is the RunHarvester Acceptable Use Policy. The Customer must ensure that its Authorized Users, clients, agents, applications, and downstream users comply with it.

10.1 Lawful and authorized use only

The Customer must use the Service only for lawful purposes and only where it has the rights, permissions, contracts, authority, and other legal basis required for the requested access and processing.

The Customer must not use the Service to:

• violate Applicable Law, a binding order, sanctions, or another person's rights;
• access non-public data, an account, a private API, or a restricted system without authorization;
• obtain or use data through fraud, misrepresentation, theft, coercion, or a compromised credential;
• induce RunHarvester or a provider to violate law or contract; or
• conceal an unlawful purpose behind an apparently legitimate Target or request.

10.2 Access controls, authentication, and challenges

The Customer must not use the Service to bypass, defeat, or evade authentication, paywalls, rate controls, CAPTCHAs, bot-management systems, technical protection measures, access restrictions, or security controls without authorization from the relevant rights holder or another lawful basis that permits the specific conduct.

A browser, challenge-handling, retry, proxy, header, cookie, or session feature is a technical tool and is not permission to circumvent a control. RunHarvester may refuse, block, or require proof of authorization for any Target or method.

The Customer must not:

• perform credential stuffing, password spraying, brute-force access, account takeover, session hijacking, or recovery-code attacks;
• test a Target for vulnerabilities without explicit authorization;
• use stolen, purchased, leaked, or deceptively obtained credentials;
• impersonate a person or entity for fraud or unauthorized access; or
• manipulate headers, fingerprints, identity attributes, or session state to commit fraud or evade a lawful restriction.

10.3 Security abuse and harmful activity

The Customer must not use the Service for:

• malware, ransomware, spyware, botnets, cryptojacking, malicious code delivery, or command-and-control activity;
• phishing, pharming, credential theft, malicious redirects, or deceptive login collection;
• denial-of-service, distributed denial-of-service, destructive traffic, resource exhaustion, or deliberate service disruption;
• scanning, exploitation, intrusion, exfiltration, or persistence without authorization;
• spam, unlawful bulk messaging, list washing, email harvesting for unlawful marketing, or evasion of anti-spam controls;
• fraudulent clicks, fake engagement, ad fraud, affiliate fraud, survey fraud, review manipulation, or search-ranking manipulation;
• ticket-buying, reservation, inventory-hoarding, or purchase automation that violates law, contractual limits, or fair-access rules;
• creation or operation of deceptive accounts, coordinated inauthentic behavior, or platform abuse; or
• conduct reasonably likely to damage RunHarvester, a provider, a Target, an endpoint owner, a user, or the public.

10.4 Excessive load and network integrity

The Customer must use reasonable rates, concurrency, retry, payload, timeout, and scheduling settings. The Customer must not intentionally overload a Target, ignore repeated overload signals, create disproportionate traffic, or continue a pattern that materially disrupts a third-party service.

RunHarvester may enforce quotas, delays, blocks, route restrictions, rate limits, concurrency limits, target restrictions, and emergency controls. Provider or endpoint restrictions may be stricter than the Customer's general Account limits.

10.5 Privacy, surveillance, and profiling

The Customer must not use the Service to:

• unlawfully track, monitor, identify, locate, profile, or surveil a person;
• stalk, harass, intimidate, dox, threaten, discriminate against, or facilitate harm to a person;
• create an unlawful marketing, political, credit, employment, insurance, housing, health, education, migration, policing, or investigative profile;
• infer Sensitive Data without a valid legal basis and appropriate safeguards;
• combine datasets in a manner that creates an unjustified or undisclosed privacy risk;
• defeat a legally effective opt-out, suppression request, access restriction, or anti-tracking choice; or
• use collected data for a materially incompatible purpose without a lawful basis and required notice.

The Customer may not use Output as the sole basis for a decision producing legal or similarly significant effects on an individual. Any permitted high-impact use requires independent validation, meaningful human review, documented legal compliance, anti-discrimination controls, and any assessment or notice required by law.

10.6 AI-related prohibited and high-risk uses

The Customer must not use the Service, Customer Content, Output, or an AI-assisted feature for an AI practice prohibited by Applicable Law. Without limiting that rule, prohibited uses include unlawful:

• harmful manipulation or deception designed to materially distort a person's behavior;
• exploitation of age, disability, social, or economic vulnerability in a way likely to cause significant harm;
• social scoring that leads to unjustified or disproportionate treatment;
• prediction of an individual's criminal-offence risk based solely on profiling or personality traits;
• untargeted collection of facial images from the internet or CCTV to create or expand a facial-recognition database;
• emotion recognition in a workplace or education setting where prohibited;
• biometric categorization intended to infer protected or highly sensitive characteristics;
• real-time remote biometric identification in publicly accessible spaces where prohibited;
• creation or facilitation of non-consensual intimate imagery or child sexual abuse material; or
• deployment of a high-risk AI workflow without the governance, data quality, documentation, transparency, logging, human oversight, accuracy, robustness, and security required by law.

The Customer is responsible for determining whether its workflow is an AI system, a high-risk AI system, or another regulated system, and whether it acts as provider, deployer, importer, distributor, or another regulated operator.

10.7 Restricted Data

Unless RunHarvester expressly approves the use in a written enterprise agreement and the parties implement appropriate safeguards, the Customer must not submit, retrieve, store, or process through the Service:

• full payment-card data, card verification codes, private cryptographic keys, or online-banking credentials;
• protected health information subject to HIPAA or equivalent health-secrecy regimes;
• data subject to CJIS, classified-information rules, export-controlled technical-data restrictions, or equivalent government-security regimes;
• educational records subject to FERPA or equivalent restrictions;
• passwords, authentication secrets, recovery codes, or private communications belonging to an unauthorized person;
• large-scale biometric templates, facial-recognition databases, genetic data, or precise movement histories;
• children's data for profiling, advertising, surveillance, or another high-risk purpose;
• data obtained in breach of professional secrecy, legal privilege, confidentiality, or a statutory access restriction; or
• any data category that the Documentation or a compliance notice designates as unsupported.

Submitting a header, cookie, session token, or target credential needed to access an authorized Customer account is permitted only for that authorized purpose and subject to the security requirements of the Agreement.

10.8 Intellectual property, databases, and confidential information

The Customer must not use the Service to infringe copyright, database rights, trademark rights, trade-secret rights, contractual access restrictions, or other proprietary rights. The Customer must not collect or disclose confidential or non-public information without authorization.

The Customer is responsible for evaluating whether an exception, license, statutory right, consent, or other legal basis permits its intended copying, extraction, storage, transformation, publication, model training, or commercial reuse.

10.9 Children and vulnerable people

The Customer must not knowingly use the Service to collect, profile, target, or make decisions about children or vulnerable people in violation of law. Any permitted processing involving children requires age-appropriate transparency, required parental or institutional authorization, strict minimization, heightened security, and documented safeguards.

10.10 Government, law-enforcement, intelligence, and military use

The Customer must not use the Service for law-enforcement, intelligence, immigration enforcement, military targeting, public-space surveillance, or coercive governmental decision-making without RunHarvester's prior written approval and a documented legal and human-rights compliance review. RunHarvester may refuse such use in its discretion where permitted by law.

10.11 Regulated markets and fraud

The Customer must not use the Service for market manipulation, insider trading, deceptive financial promotion, unlawful gambling, sanctions evasion, fraud, money laundering, or circumvention of regulated-platform controls. Legitimate market research, price monitoring, and public-data analysis remain subject to all other terms.

10.12 Proxy and Account resale

The Customer must not sell, lease, sublicense, disclose, pool, broker, or make available Account access, API keys, proxy credentials, endpoint lists, route capacity, or raw Service access unless an Order expressly permits it. The Customer must not use the Service to build a directly substitutable proxy or scraping infrastructure service using RunHarvester's non-public systems, inventory, or confidential information.

10.13 Restricted Targets and use cases

RunHarvester may maintain undisclosed or disclosed restrictions on Targets, sectors, countries, ports, protocols, content classes, account-management activity, or use cases. RunHarvester may require enhanced verification, proof of authorization, a legal memorandum, target allowlisting, rate controls, or a separate agreement before enabling access.

A restriction may arise from law, provider requirements, endpoint-owner rights, security risk, abuse patterns, or reputational risk. RunHarvester is not required to disclose a security-sensitive blocklist or the precise detection method.

10.14 Investigations and remedies

RunHarvester may investigate suspected violations using proportionate Account, usage, routing, request, billing, and security information. RunHarvester may request information, restrict a Target or feature, reduce limits, hold a job, require remediation, suspend access, preserve evidence, notify an affected provider or authority where legally appropriate, or terminate the Agreement.

The Customer must cooperate reasonably and must not obstruct, mislead, or retaliate against a complainant. RunHarvester's investigation does not make it responsible for the Customer's conduct and does not create a duty to monitor all use.

11. Targets, proxy routes, browser sessions, and webhooks

11.1 Customer-selected Targets

The Customer instructs the Service which Target to contact. The Customer acknowledges that a Target may receive or infer:

• the source or proxy IP address and approximate location;
• request time, path, method, headers, cookies, user agent, locale, language, and browser characteristics;
• credentials or session state intentionally submitted by the Customer;
• network, TLS, and device-like signals associated with the request; and
• the fact and pattern of automated access.

RunHarvester does not control a Target's logs, terms, security practices, privacy notice, response, blocking decision, or later use of data.

11.2 Proxy routes

Proxy availability, reputation, endpoint location, protocol, latency, anonymity, and success can change. Geographic and network attributes are estimates and are not guaranteed. A route may traverse jurisdictions or providers other than the apparent endpoint location.

The Customer must not use a proxy route as a guarantee of anonymity, non-attribution, legal compliance, or data residency. RunHarvester may validate, rotate, replace, quarantine, or remove endpoints and may disclose limited traffic metadata to a provider as needed to operate or investigate abuse.

11.3 Customer-provided proxies

If the Customer supplies a proxy or proxy credential, the Customer represents that it is authorized to use it and to route the relevant data through it. The Customer is responsible for the proxy operator's terms, security, logging, transfer mechanism, and endpoint permissions.

11.4 Browser state and credentials

Browser workflows may process cookies, local storage, session storage, page state, headers, tokens, and credentials. The Customer should use least-privilege service accounts and must not submit a personal or broadly privileged account where a restricted account is sufficient.

One-run browser session state is intended to be encrypted where supported, isolated to the relevant run, and removed after terminal status. The Customer must not rely on the Service to preserve a login or browser profile unless a specific persistent-session feature and retention term are expressly provided.

11.5 Webhooks and integrations

A Customer-selected webhook, integration, storage service, AI model, or other recipient is the Customer's destination and may be an independent controller or the Customer's own processor. The Customer is responsible for:

• selecting and authorizing the recipient;
• establishing any required data-processing and international-transfer terms;
• using TLS and verifying certificates;
• validating webhook signatures and replay protections;
• applying least-privilege credentials;
• ensuring destination availability and security; and
• deleting or correcting data at the destination.

Delivery by RunHarvester completes when the Service transmits the payload according to the configured interface. RunHarvester does not control copies retained by the recipient.

11.6 Evidence and assisted troubleshooting

Screenshots, page evidence, traces, videos, browser views, and support artifacts may capture Personal Data, confidential information, or credentials visible on a page. The Customer must minimize and mask evidence where possible and must not request assisted access to Restricted Data without a written agreement and safeguards.

Authorized RunHarvester personnel may temporarily access relevant evidence or a controlled session when the Customer requests support or where necessary for security and abuse response. Such access is subject to role restrictions and confidentiality obligations.

12. Data protection

12.1 Privacy documents

The Privacy Policy explains RunHarvester's controller-side processing. The Cookie Policy explains browser storage and access technologies. The DPA governs Customer Personal Data that RunHarvester processes as a processor or sub-processor.

12.2 Customer as controller or processor

The Customer determines the purposes of its collection and later use of Output. The Customer is normally the controller of Customer Personal Data, or a processor acting for an upstream controller. RunHarvester normally acts as the Customer's processor or sub-processor for that data.

The Customer must not submit Customer Personal Data until it has ensured that an appropriate DPA and any required upstream authorization are in place.

12.3 Independent controller activities

RunHarvester separately acts as a controller for Account administration, billing, security, abuse prevention, legal compliance, support, and other purposes described in the Privacy Policy. Target operators, Customer-selected recipients, identity providers, and payment providers may be independent controllers for their own activities.

12.4 International transfers

The Customer is responsible for identifying and lawfully authorizing a restricted transfer caused by its selection of a Target, proxy region, webhook, integration, storage location, AI provider, or Authorized User location. RunHarvester's DPA addresses transfers made by RunHarvester to its sub-processors. No data-residency commitment applies unless expressly stated in an Order.

13. AI-assisted features

13.1 Optional processing

An AI-assisted feature may generate or repair extraction recipes, selectors, schemas, transformations, classifications, or other Output. When the Customer enables or invokes such a feature, the Customer instructs RunHarvester to transmit the data reasonably needed for that feature to the applicable AI gateway or model provider, subject to the DPA.

A non-AI HTTP, browser, proxy, or extraction request is not sent to an AI provider merely because AI functionality exists elsewhere in the Service.

13.2 Data minimization

The Customer must not include credentials, authorization headers, cookies, private keys, Sensitive Data, confidential information, or unnecessary Personal Data in an AI prompt or source sample. RunHarvester may apply redaction or provider restrictions but does not guarantee that all sensitive content can be detected automatically.

13.3 Provider practices

RunHarvester may use OpenRouter and authorized downstream model providers. Providers can differ in location, logging, retention, and human-review practices. Where an AI input contains Customer Personal Data processed under the DPA, the applicable provider must be disclosed through the Subprocessor Register and is subject to the DPA's restrictions, including the prohibition on using that data for the provider's independent model-training purpose unless the Customer has separately and expressly authorized a different documented arrangement.

A zero-data-retention commitment applies only where the relevant route, Account control, Subprocessor Register, or Order expressly provides it. Limited provider retention for delivery, security, abuse prevention, or legal compliance may therefore occur even where independent model training is prohibited. The Customer must review the disclosed route and minimize AI inputs accordingly.

13.4 Output limitations

AI-generated Output is probabilistic and may be inaccurate, incomplete, unstable, biased, insecure, or unsuitable. The Customer must test generated logic and validate Output before production use. The Customer must maintain meaningful human review for legal, financial, medical, employment, housing, education, insurance, migration, public-benefit, or similarly significant decisions.

13.5 AI compliance

The Customer is responsible for complying with laws governing AI systems, training data, transparency, copyright, prohibited practices, high-risk systems, deployer obligations, and automated decisions. RunHarvester is not the provider or deployer of the Customer's downstream AI system merely because the Customer uses RunHarvester to collect or structure data.

14. Intellectual property and reserved rights

14.1 RunHarvester property

RunHarvester and its licensors own all rights in the Service and related technology, including software, source and object code, APIs, architecture, algorithms, proxy-management methods, validation systems, workflow engines, extraction engines, user interfaces, designs, trademarks, trade names, Documentation, templates, and improvements, excluding Customer Content and third-party material.

No right is granted except the limited right expressly stated in the Agreement.

14.2 Restrictions

Except to the extent mandatory law expressly permits and cannot be waived, the Customer must not:

• copy, modify, translate, adapt, reverse engineer, decompile, disassemble, or attempt to discover source code or non-public algorithms;
• bypass license, authentication, quota, billing, rate, security, or access controls;
• scrape, harvest, or systematically extract non-public information from RunHarvester itself;
• remove proprietary notices;
• use the Service to develop a competing product through unauthorized access to confidential or non-public elements;
• frame, mirror, or redistribute the Service;
• use RunHarvester trademarks without permission;
• access another Customer's data or tenant; or
• conduct intrusive security testing without prior written authorization.

This Section does not prevent lawful interoperability, security research expressly permitted by mandatory law, or use of documented APIs in accordance with the Agreement.

14.3 Open-source and third-party components

Some components may be governed by open-source or third-party license terms. Those terms apply to the relevant component and prevail only where they expressly require it.

15. Third-Party Services and content

15.1 Independent services

The Service may interoperate with Targets, proxy providers, payment processors, identity providers, AI providers, CAPTCHA services, monitoring providers, email services, storage services, and Customer-selected integrations. RunHarvester does not control and is not responsible for a Third-Party Service's terms, acts, omissions, security, availability, legality, data, or changes.

15.2 Third-party terms

The Customer must comply with third-party terms applicable to its own use. RunHarvester may enforce a provider restriction or suspend a feature where necessary to preserve access to an underlying service, even if the restriction is not separately listed in these Terms.

15.3 No endorsement or affiliation

A reference to, compatibility with, or ability to access a Target or Third-Party Service does not imply endorsement, partnership, agency, or authorization by that third party.

15.4 Changes and discontinuation

A Third-Party Service may change or end functionality without notice. RunHarvester may replace or discontinue an integration, model, route, payment method, or provider. If a material paid feature is permanently discontinued during a fixed prepaid Order and no reasonably comparable alternative is provided, the Customer's exclusive remedy is to terminate the affected portion and receive a pro-rata refund of unused prepaid Fees for that portion, unless the discontinuation results from the Customer's breach or a legal prohibition.

16. Fees, invoicing, and payment

16.1 Fees

The Customer must pay the Fees shown at checkout, in the billing area, in an Order, or in another applicable commercial document. Unless stated otherwise, Fees are quoted without taxes and are payable in the displayed currency.

16.2 Recurring charges

If the Customer selects a recurring Service, it authorizes RunHarvester and its payment provider to charge the payment method at the beginning of each billing period until cancellation takes effect. The billing period and renewal conditions are shown before purchase or in the Order.

16.3 Usage measurement

RunHarvester may measure requests, credits, bandwidth, provider costs, features, results, concurrency, or other usage units according to the Documentation and Account records. RunHarvester's records control absent a demonstrable material error. The Customer must raise a billing discrepancy within 30 days after the relevant invoice or Account statement, unless mandatory law requires longer.

16.4 Payment authorization

The Customer authorizes RunHarvester and its payment providers to process charges, refunds, payment status, fraud checks, and authentication information. The Customer must keep payment and billing information current.

16.5 Failed payment and collection

If payment fails or is overdue, RunHarvester may retry the payment method, restrict paid functionality, suspend the Account, offset available balances where lawful, or terminate the affected Service. The Customer is responsible for reasonable collection costs and statutory late interest to the extent permitted by law.

16.6 Disputes and chargebacks

The Customer should contact RunHarvester before initiating a chargeback. A fraudulent, abusive, or unjustified chargeback may result in suspension and recovery of provider, administrative, and collection costs. Exercising a good-faith legal right to dispute a charge is not itself a violation.

16.7 No set-off

The Customer may not withhold, deduct, or set off Fees except where mandatory law permits or RunHarvester agrees in writing.

17. Taxes

17.1 Customer responsibility

Fees exclude VAT, sales tax, use tax, withholding tax, duties, and similar governmental charges unless expressly stated. The Customer must pay applicable taxes associated with the purchase, excluding taxes based on RunHarvester's net income.

17.2 Tax information

The Customer must provide a valid legal name, address, country, tax number, VAT number, exemption certificate, and other information reasonably required to determine tax treatment. RunHarvester may correct tax treatment or invoice additional tax where required by law.

17.3 Withholding

If the Customer is legally required to withhold tax, it must provide valid evidence and, unless prohibited by law or expressly agreed otherwise, increase the payment so that RunHarvester receives the amount it would have received without the withholding.

18. Credits, prepaid balances, and promotions

18.1 Nature of credits

Credits, usage units, grants, coupons, and promotional balances are contractual rights to eligible Service capacity, not money, deposits, securities, virtual currency, stored value, or property. They have no cash value, do not earn interest, and cannot be redeemed for cash.

18.2 Restrictions

Credits are non-transferable and non-refundable except where mandatory law or an Order expressly provides otherwise. They may be limited by Account, feature, use case, geography, validity period, or promotion terms.

18.3 Expiration and adjustment

A credit or promotional balance may expire where disclosed when issued or shown in the Account. RunHarvester may correct a technical or billing error, reverse a duplicate grant, or remove a balance obtained through fraud, abuse, chargeback, or ineligibility. RunHarvester will not remove valid purchased credits arbitrarily.

18.4 No guarantee of result

Consumption or reservation of a credit does not guarantee that a Target request will succeed. Charging, settlement, retries, refunds, cache treatment, and failure treatment follow the applicable product rules and Account records.

19. Trials, previews, beta features, and free access

RunHarvester may offer trials, previews, beta features, experimental functionality, free allowances, or early access. Unless an Order says otherwise, such functionality:

• may be changed, limited, or withdrawn at any time;
• may have lower limits and different retention;
• is provided for evaluation and testing;
• may contain defects or produce data loss;
• has no service-level commitment;
• may not be used for production, high-risk, regulated, or irreversible decisions; and
• may be subject to additional terms.

RunHarvester may end free or trial access and delete associated Customer Content after the stated trial or a reasonable closure period, subject to the DPA and Applicable Law.

20. Availability, maintenance, and support

20.1 As-available service

Unless a signed service-level agreement applies, the Service is provided on an as available basis. RunHarvester does not guarantee uptime, capacity, route availability, response time, completion time, geographic coverage, proxy availability, Target access, browser compatibility, challenge resolution, or uninterrupted operation.

20.2 Maintenance and emergency changes

RunHarvester may perform scheduled or emergency maintenance, deploy security fixes, change infrastructure, or temporarily restrict functionality. Where practicable, material planned maintenance will be communicated through the Service, status page, or Account contact.

20.3 Support

Support scope, channels, and response targets depend on the applicable Order or Service. A response target is not a resolution guarantee. The Customer must provide non-sensitive diagnostic information and must not send passwords, full API keys, private keys, card data, or unnecessary Restricted Data.

20.4 Customer dependencies

RunHarvester is not responsible for failures caused by the Customer's systems, code, network, credentials, webhook, configuration, unsupported use, or failure to follow Documentation.

21. Confidentiality

21.1 Confidential Information

"Confidential Information" means non-public information disclosed by one party (the "Discloser") to the other (the "Recipient") that is marked confidential or reasonably should be understood as confidential, including Customer Content, credentials, security information, non-public product information, pricing in a negotiated Order, business plans, and technical information.

21.2 Obligations

The Recipient must:

• use Confidential Information only to perform or receive the Agreement;
• protect it using at least reasonable care and no less care than it uses for its own similar information;
• disclose it only to personnel, Affiliates, professional advisers, and contractors who need it and are bound by confidentiality obligations; and
• notify the Discloser of an unauthorized disclosure where required by law or the DPA.

21.3 Exclusions

Confidential Information does not include information that the Recipient can demonstrate:

• is or becomes public without breach;
• was lawfully known without confidentiality duty;
• is received lawfully from a third party without confidentiality duty;
• is independently developed without use of the Discloser's Confidential Information; or
• is approved for release in writing.

Public Target content is not Customer Confidential Information merely because the Customer retrieved it, but the Customer's non-public selection, compilation, credentials, schema, workflow, and business context may be confidential.

21.4 Compelled disclosure

The Recipient may disclose Confidential Information when legally required, provided it gives prior notice where lawful, discloses only what is required, and reasonably assists the Discloser in seeking protection at the Discloser's expense.

21.5 Equitable relief

Unauthorized use or disclosure may cause irreparable harm. A party may seek appropriate injunctive or equitable relief in addition to other remedies, without waiving jurisdictional objections or mandatory requirements.

22. Security and shared responsibility

22.1 RunHarvester measures

RunHarvester maintains technical and organizational measures described in the DPA and Privacy Policy. Those measures are designed to protect the Service and relevant Personal Data but do not guarantee absolute security.

22.2 Customer measures

The Customer must implement security appropriate to its use, including:

• least-privilege users, API scopes, and service accounts;
• multi-factor authentication where available;
• secret storage and rotation;
• TLS and certificate validation;
• webhook signature and replay validation;
• environment separation;
• access logging and prompt revocation;
• masking and minimization of evidence;
• secure storage and deletion of Output; and
• incident response and business continuity for its downstream systems.

22.3 Security testing

The Customer must not conduct penetration testing, load testing, vulnerability scanning, or security research against RunHarvester without prior written authorization. Good-faith vulnerability reports should be sent to [email protected] with minimal proof and no unnecessary access to Customer data.

23. Compliance review, verification, and monitoring

23.1 Verification

RunHarvester may require business verification, identity verification, beneficial-owner information, payment verification, use-case details, Target lists, rate estimates, authorization evidence, data samples, a privacy assessment, or other information reasonably needed to manage legal, provider, fraud, and abuse risk.

23.2 Ongoing review

RunHarvester may review Account usage, traffic metadata, error patterns, target categories, provider reports, payment risk, and complaints. RunHarvester is not obligated to inspect the content of every request and does not assume responsibility for approved or undetected use.

23.3 Customer cooperation

The Customer must provide accurate information and reasonable cooperation. RunHarvester may restrict or refuse a use case if information is insufficient, inconsistent, or creates unacceptable risk.

23.4 Provider requirements

A proxy, hosting, payment, AI, or other provider may impose verification or use restrictions. RunHarvester may share the minimum information required to complete a legitimate review, subject to the Privacy Policy and DPA.

24. Suspension and emergency action

24.1 Grounds

RunHarvester may immediately restrict, suspend, quarantine, or disable an Account, credential, Target, route, integration, job, Output, or feature where RunHarvester reasonably believes that:

• the Customer breached the Agreement;
• activity is unlawful, abusive, fraudulent, unauthorized, or harmful;
• payment is overdue or disputed through an abusive chargeback;
• a credential or Account is compromised;
• a Target, provider, endpoint owner, authority, or rights holder raises a credible complaint;
• continued operation creates a security, privacy, legal, sanctions, or provider risk;
• the activity threatens the Service, another customer, or a third party;
• suspension is required by law or a binding order; or
• immediate action is needed to prevent material harm.

24.2 Scope and notice

RunHarvester will seek to limit suspension to the affected use where reasonably practicable. RunHarvester may provide notice and an opportunity to remedy unless notice would increase risk, violate law, compromise an investigation, or be impracticable in an emergency.

24.3 No liability for justified suspension

To the extent permitted by law, RunHarvester is not liable for a good-faith suspension under this Section. The Customer remains responsible for Fees incurred before suspension and for non-cancellable provider costs attributable to its use.

24.4 Reinstatement

Reinstatement may require remediation, verification, payment, credential rotation, target restriction, reduced limits, a new Order, or other safeguards. RunHarvester is not required to reinstate an Account terminated for serious or repeated abuse.

25. Term, cancellation, and termination

25.1 Term

The Agreement begins when the Customer first accepts it or uses the Service and continues until all Accounts and Orders have ended.

25.2 Order term and renewal

An Order applies for the term stated in it or shown at checkout. If automatic renewal is selected, the Order renews for the stated renewal period unless cancelled through the available controls or by valid notice before the applicable deadline.

25.3 Customer cancellation

The Customer may cancel a self-service recurring Service through the Account or another stated method. Cancellation generally takes effect at the end of the current paid period unless the interface or Order says otherwise. Cancellation does not entitle the Customer to a refund of already paid Fees except where mandatory law or the Agreement expressly provides it.

25.4 Termination for cause

Either party may terminate an affected Order or the Agreement by written notice if the other party materially breaches and fails to cure within 15 days after notice, unless the breach cannot be cured or a different cure period is required by law. RunHarvester may terminate immediately for serious Acceptable Use violations, fraud, sanctions risk, unlawful activity, security threats, repeated breach, or non-payment after applicable notice.

25.5 Insolvency

To the extent permitted by law, either party may terminate if the other enters liquidation, ceases business, becomes insolvent, or is subject to an analogous proceeding not dismissed within a reasonable period.

25.6 Effect of termination

On termination or expiration:

• the Customer's right to use the affected Service ends;
• all accrued Fees become due;
• the Customer must stop using and delete RunHarvester credentials and non-public materials;
• RunHarvester may revoke keys and access;
• Customer Content is handled under Section 26 and the DPA; and
• provisions that by their nature should survive remain effective, including payment, confidentiality, intellectual property, disclaimers, indemnity, liability, dispute, and data-protection provisions.

26. Data export, deletion, and switching

26.1 Customer export responsibility

The Customer must export required Output before result expiration, cancellation, or termination. Ordinary result availability is seven days after completion and may be shorter for temporary artifacts. Termination does not extend an already applicable retention period.

26.2 Account deletion

RunHarvester will delete or de-identify Customer Content according to the DPA, Account-deletion process, retention schedule, and Applicable Law. Limited billing, tax, security, suppression, legal-hold, dispute, and audit records may be retained. Deleted data may remain temporarily in protected backups until overwritten under the ordinary rotation.

26.3 External copies

RunHarvester cannot delete copies already exported, downloaded, transmitted to a Customer-selected recipient, stored in a Customer system, logged by a Target, or retained by an independent third party.

26.4 EU Data Act switching

To the extent Chapter VI of Regulation (EU) 2023/2854 applies to an affected Service, the parties will comply with its mandatory switching, export, continuity, transparency, contractual, and deletion requirements. The Customer may initiate an applicable switching process through the Account or by contacting support and identifying the affected Service, destination, requested export, preferred switching date, and authorized contact.

Unless a shorter period is agreed or Applicable Law requires otherwise:

• any contractual notice period for initiating an applicable switching process will not exceed two months;
• after that notice period, RunHarvester will support completion of the switching process within a transition period of 30 calendar days;
• where the 30-day transition period is technically unfeasible, RunHarvester will notify the Customer within 14 working days after the switching request, explain the technical reason, and identify an alternative transition period that will not exceed seven months;
• after the transition period, the Customer will have a retrieval period of at least 30 calendar days for exportable data within the scope required by Applicable Law; and
• RunHarvester will erase exportable data and digital assets within the applicable statutory scope after successful switching or after the agreed retrieval period, subject to legal retention, security, backup rotation, and material that Applicable Law permits RunHarvester to retain.

RunHarvester will make exportable Customer input and output data, including relevant metadata generated by the Customer's use, available in a supported, commonly used, machine-readable format to the extent required by law and technically available. RunHarvester is not required to disclose its trade secrets, proprietary software, internal security data, data of another customer, third-party material it is not entitled to disclose, or material otherwise excluded by Applicable Law. RunHarvester will not use those exclusions to frustrate a lawful switch.

The Customer must cooperate in good faith, maintain an authorized and secure destination, provide necessary access and technical information, preserve its own backups, and complete Customer-controlled actions within the applicable transition and retrieval periods. RunHarvester is not responsible for delays caused by the Customer, the destination provider, a Customer-selected third party, an incompatible destination, or circumstances outside RunHarvester's reasonable control, except to the extent Applicable Law provides otherwise.

From 12 January 2027, RunHarvester will not impose switching charges where Regulation (EU) 2023/2854 prohibits them. Before that date, any applicable switching or data-egress charges will not exceed the reduced charges permitted by Applicable Law and will be limited to directly attributable switching costs where required. Ordinary Service Fees accrued before completion of the switch remain payable.

Mandatory statutory rights prevail over inconsistent ordinary cancellation, retention, export, or deletion terms. Nothing in this Section requires RunHarvester to provide professional migration engineering, rewrite Customer applications, guarantee functional equivalence with another provider, or disclose protected intellectual property beyond what Applicable Law requires.

26.5 No migration guarantee

Except where mandatory law or an Order requires otherwise, RunHarvester does not guarantee functional equivalence with another provider, transform data for a proprietary destination, rewrite the Customer's application, or provide professional migration services without separate agreement.

27. Customer warranties

The Customer warrants throughout the Agreement that:

• it has validly entered into the Agreement;
• it and its Authorized Users will comply with the Agreement and Applicable Law;
• its Customer Content, instructions, Targets, credentials, routes, and recipients are authorized;
• it will not rely on the Service as legal advice or as proof that collection is lawful;
• it will validate Output and maintain suitable human review;
• it will not make a false claim about RunHarvester's affiliation, certification, approval, or capabilities; and
• information provided for billing, tax, compliance, and verification is accurate.

28. Disclaimers

28.1 As-is and as-available

To the maximum extent permitted by law, the Service, Output, Documentation, proxy inventory, routes, AI features, beta features, and support are provided as is and as available.

RunHarvester disclaims all express, implied, statutory, and other warranties, including warranties of merchantability, satisfactory quality, fitness for a particular purpose, title, non-infringement, accuracy, completeness, availability, quiet enjoyment, and compatibility.

28.2 No collection or legal guarantee

RunHarvester does not warrant that:

• a request, browser workflow, extraction, challenge interaction, proxy route, or webhook will succeed;
• a Target will permit or continue to permit access;
• a proxy will be anonymous, exclusive, accurate in location, uncompromised, or accepted by a Target;
• Output will be accurate, current, complete, unique, unbiased, free of third-party rights, or lawful for the Customer's purpose;
• retries will produce a result;
• errors will be corrected;
• data will never be lost; or
• the Service satisfies a specific regulatory regime not expressly stated in an Order.

28.3 No professional advice

The Service, Documentation, support, policies, examples, and Output do not constitute legal, compliance, financial, tax, medical, cybersecurity, or other professional advice. The Customer must obtain independent advice appropriate to its use case.

28.4 Mandatory warranties

Nothing in the Agreement excludes a warranty or remedy that cannot lawfully be excluded. Any mandatory warranty is limited to the minimum scope and duration required by law.

29. Customer indemnity

29.1 Covered claims

To the extent permitted by law, the Customer will defend, indemnify, and hold harmless RunHarvester, its Affiliates, and their directors, officers, employees, and contractors from third-party claims, proceedings, damages, fines, penalties, settlements, and reasonable legal costs arising from or relating to:

• Customer Content, instructions, Targets, credentials, routes, recipients, or downstream use of Output;
• the Customer's or an Authorized User's violation of the Agreement or Applicable Law;
• unauthorized access, scraping, circumvention, surveillance, profiling, marketing, or data use;
• infringement or misappropriation of privacy, data-protection, copyright, database, trademark, confidentiality, contract, or other rights;
• a Customer-selected webhook, integration, proxy, model, storage provider, or other recipient;
• Restricted Data submitted without required approval;
• a claim by an upstream controller, client, Data Subject, Target, endpoint owner, provider, or authority caused by the Customer's acts or omissions; or
• fraud, willful misconduct, or security compromise attributable to the Customer.

29.2 Procedure

RunHarvester will provide reasonably prompt notice of a covered claim, subject to no loss of rights except to the extent delay materially prejudices the defense. The Customer may control the defense with counsel reasonably acceptable to RunHarvester, but may not settle a claim that admits fault by RunHarvester, imposes non-monetary obligations on RunHarvester, or fails to release RunHarvester without RunHarvester's written consent.

RunHarvester may participate with its own counsel at its own cost, or at the Customer's cost where a conflict of interest reasonably requires separate counsel.

29.3 Exclusion

The Customer has no indemnity obligation to the extent a final judgment determines that the claim was caused by RunHarvester's gross negligence, willful misconduct, or material breach of the Agreement.

30. Limitation of liability

30.1 Excluded losses

To the maximum extent permitted by law, neither RunHarvester nor its Affiliates, suppliers, or licensors is liable for any indirect, incidental, special, exemplary, punitive, or consequential loss, or for loss of profits, revenue, savings, business, opportunity, goodwill, reputation, anticipated benefit, use, or data, even if advised that the loss was possible.

RunHarvester is not liable for the cost of a replacement data source, alternative proxy network, downstream remediation, or a decision made from Output, except to the extent a signed Order expressly provides otherwise.

30.2 Aggregate cap

To the maximum extent permitted by law, the total aggregate liability of RunHarvester and its Affiliates arising out of or relating to the Agreement, the Service, or the DPA will not exceed the greater of:

1. the Fees paid or payable by the Customer to RunHarvester for the affected Service during the 12 months immediately preceding the first event giving rise to liability; or
2. EUR 100 where the Customer used only a free Service or paid no Fees during that period.

Multiple claims, events, Accounts, legal theories, or affected persons do not increase the cap.

30.3 Allocation of risk

The exclusions and cap apply to contract, tort, negligence, strict liability, misrepresentation, restitution, statutory duty, indemnity, and any other legal theory. The parties agree that Fees reflect this allocation of risk and that the limitations are an essential basis of the Agreement.

30.4 Non-excludable liability

Nothing excludes or limits liability to the extent it cannot lawfully be excluded or limited, including liability for:

• death or personal injury caused by negligence where non-excludable;
• fraud or fraudulent misrepresentation;
• intentional misconduct or gross negligence where limitation is prohibited;
• payment obligations properly due from the Customer;
• infringement caused by a party's unauthorized use of the other party's intellectual property; or
• rights of Data Subjects or supervisory authorities under the EU SCCs or other mandatory data-protection law.

30.5 DPA and SCC claims

Inter-party liability under the DPA is subject to this Section to the extent permitted by Applicable Law. This does not restrict a Data Subject's third-party rights under the EU SCCs or UK Addendum and does not prevent a regulator from exercising statutory powers.

31. Intellectual-property and abuse complaints

31.1 Reporting

A rights holder or affected person may report alleged infringement, unauthorized access, harmful traffic, privacy misuse, or proxy endpoint abuse to [email protected].

A report should include, as applicable:

• the reporter's identity and authority;
• the affected work, data, endpoint, system, or right;
• the relevant URL, timestamp, request indicator, or other location information;
• a clear explanation of the alleged violation;
• supporting evidence;
• a good-faith statement that the report is accurate; and
• safe contact details.

Do not send passwords, full API keys, private keys, unnecessary identity documents, or unrelated Sensitive Data.

31.2 Action

RunHarvester may request additional information, preserve relevant records, restrict a Target or endpoint, notify the Customer, seek a response, remove or suppress access, or take another proportionate action. RunHarvester may reject incomplete, fraudulent, abusive, or unsupported notices.

31.3 Repeat violations

RunHarvester may terminate Accounts associated with repeated or serious infringement or abuse.

32. Legal requests and government access

RunHarvester may preserve or disclose information where required by Applicable Law, a binding legal request, or a valid court or regulatory order. RunHarvester may also disclose limited information where reasonably necessary to protect rights, investigate fraud or abuse, respond to an emergency involving risk of serious harm, or establish or defend legal claims.

Where legally permitted and appropriate, RunHarvester will:

• verify the request's apparent authority and scope;
• seek clarification or narrowing of overbroad demands;
• disclose only information reasonably required;
• notify the Customer before disclosure; and
• preserve confidentiality and security.

RunHarvester is not required to challenge a lawful request at its own expense. The Customer is responsible for responding to requests directed to it as controller.

33. Sanctions, export controls, and anti-corruption

The Customer represents that neither it nor, to its knowledge, its controlling persons or intended users are prohibited from receiving the Service under applicable sanctions or export-control law. The Customer must not use the Service:

• for a sanctioned person, entity, territory, or prohibited end use;
• to evade sanctions, export controls, customs rules, or trade restrictions;
• to develop or support prohibited weapons, military targeting, or unlawful surveillance;
• to export controlled technical data unlawfully; or
• in connection with bribery, corruption, or unlawful payments.

RunHarvester may screen relevant Account and payment information and may suspend or terminate access where required or reasonably necessary to manage sanctions risk.

34. Changes to the Service, policies, and Terms

34.1 Service changes

RunHarvester may improve, modify, replace, limit, or discontinue Service components. Changes may be required by security, law, providers, target behavior, infrastructure, or product development.

34.2 Terms updates

RunHarvester may update these Terms. The updated version will state its effective date. For a material change that adversely affects an existing Customer, RunHarvester will provide reasonable advance notice through email, the Account, or the website, unless immediate effect is required for law, security, fraud prevention, provider compliance, or to prevent material harm.

34.3 Existing fixed Orders

A material commercial change will ordinarily apply to a fixed paid Order at renewal, unless the Order permits an earlier change or the change is required by law, tax, security, or an external provider. Other changes apply on the stated effective date.

34.4 Rejection of changes

If the Customer does not agree to an update, it must stop using the affected Service and cancel before the update takes effect. Continued use after the effective date constitutes acceptance where permitted by law.

35. Governing law and disputes

35.1 Governing law

The Agreement and any non-contractual obligation arising from it are governed by the laws of Hungary, without regard to conflict-of-law rules. The United Nations Convention on Contracts for the International Sale of Goods does not apply.

The EU SCCs, UK Addendum, and mandatory local data-protection rules remain governed as stated in those instruments.

35.2 Good-faith escalation

Before filing a court claim, a party should send a written dispute notice describing the issue and requested remedy. Authorized representatives will attempt in good faith to resolve the dispute for at least 30 days, unless urgent injunctive relief, a limitation period, a security incident, non-payment, or mandatory law requires earlier action.

35.3 Jurisdiction

To the extent permitted by law, the courts competent for Budapest, Hungary have exclusive jurisdiction over disputes arising from or relating to the Agreement. A party may seek interim or protective relief in another competent court where necessary to protect Confidential Information, intellectual property, security, or evidence.

If mandatory law gives a consumer, Data Subject, or public authority a different forum, that mandatory forum is unaffected.

36. General provisions

36.1 Independent contractors

The parties are independent contractors. The Agreement does not create a partnership, joint venture, fiduciary relationship, employment relationship, franchise, agency, or authority to bind the other party.

36.2 Assignment

The Customer may not assign, transfer, or delegate the Agreement without RunHarvester's prior written consent, except to a successor in a merger or sale of substantially all relevant assets that is not a direct competitor and agrees in writing to assume the Agreement. RunHarvester may assign the Agreement to an Affiliate or in connection with a merger, reorganization, financing, or sale of business or assets, subject to the DPA and Applicable Law.

An attempted assignment contrary to this Section is void to the extent permitted by law.

36.3 Subcontracting

RunHarvester may use Affiliates and subcontractors to provide the Service. Processing of Customer Personal Data is subject to the DPA's sub-processor terms.

36.4 Force majeure

Neither party is liable for delay or failure caused by events beyond its reasonable control, including internet or telecommunications failure, cloud or provider outage, Target blocking or change, endpoint unavailability, denial-of-service attack, natural disaster, epidemic, war, terrorism, civil unrest, labor dispute, governmental action, sanctions, power failure, or failure of a critical third party, provided the affected party uses reasonable efforts to mitigate. This Section does not excuse payment obligations already due.

36.5 Notices

RunHarvester may give operational and contractual notice by email to the Account contact, through the Account, or by posting a prominent notice on the Service. Legal notices to RunHarvester must be sent to [email protected] with the subject "Legal Notice" and, where formal service is required by law, to the registered office.

The Customer must keep its contact information current. Notice is effective when delivered, posted in the Account, or, for email, when sent without a delivery failure, subject to mandatory law.

36.6 Entire agreement

The Agreement is the complete agreement regarding its subject matter and supersedes prior or contemporaneous proposals, statements, discussions, and agreements on that subject. Each party acknowledges that it does not rely on a statement not expressly included in the Agreement, without excluding liability for fraud.

36.7 No waiver

Failure or delay to enforce a provision is not a waiver. A waiver must be in writing and applies only to the stated instance.

36.8 Severability

If a provision is held invalid or unenforceable, it will be limited or replaced to the minimum extent needed to make it enforceable while preserving its purpose. The remaining provisions continue in effect.

36.9 No third-party beneficiaries

Except for rights expressly granted under the DPA, EU SCCs, UK Addendum, or Applicable Law, the Agreement creates no third-party beneficiary rights.

36.10 Interpretation

Headings are for convenience. "Including" means "including without limitation." A singular term includes the plural where appropriate. A reference to a law includes amendments and replacements. An obligation not to do something includes not permitting or assisting it.

36.11 Counterparts and electronic signatures

An Order or DPA may be signed in counterparts and electronically. Electronic signatures and accepted online terms have the same effect as originals to the extent permitted by law.

36.12 Language

The controlling language of the Agreement is English. A translation is for convenience unless a signed Order expressly states otherwise. Where mandatory law requires a local-language version, that version controls only to the required extent.

37. Contact

Questions about the Agreement, billing, Account access, compliance review, abuse, security, or legal notices may be sent to:

Isentró Kft. / RunHarvester
1082 Budapest, Corvin sétány 6, 8th floor, unit 4, Hungary
[email protected]

Use the subject line Terms Question, Legal Notice, Security Report, or Abuse Report, as appropriate. Do not include passwords, full API keys, authorization headers, private keys, card data, or unnecessary Sensitive Data in the initial message.

Schedule 1 - Conditional Consumer Information and Withdrawal Form

1. When this Schedule applies

RunHarvester is designed and offered primarily for business, professional, institutional, and organizational use. This Schedule applies only where:

1. mandatory law treats the Customer as a consumer despite the business-use representation in Section 2.3; or
2. RunHarvester expressly permits a Customer to purchase the Service for purposes outside the Customer's trade, business, craft, or profession.

Nothing in this Schedule converts a business Customer into a consumer or grants a business Customer rights that mandatory law reserves for consumers. Where this Schedule conflicts with a mandatory consumer right, the mandatory right prevails. Otherwise, the remainder of the Agreement continues to apply.

2. Pre-contract information

Before a consumer places an order, the checkout, Order, pricing interface, or other durable information made available by RunHarvester will identify, as applicable:

• the main characteristics of the selected Service;
• the identity and contact details of Isentró Kft.;
• the total price, applicable taxes, billing interval, usage basis, and any additional charge that can reasonably be calculated in advance;
• the method of payment and performance;
• the contract duration, renewal mechanics, and termination conditions;
• the minimum duration of the consumer's obligations, if any;
• the functionality, compatibility, and interoperability of digital content or a digital service to the extent reasonably known and material;
• the availability of statutory conformity remedies;
• the existence, conditions, time limit, and method of exercising a right of withdrawal, or the circumstances in which that right does not apply or may be lost; and
• any other information required by mandatory consumer law.

The commercial information displayed at the final ordering step forms part of the Agreement for that transaction. The consumer should retain the order confirmation and the version of the Agreement accepted.

3. Right of withdrawal

3.1 Fourteen-day period

Unless a statutory exception applies, an eligible consumer may withdraw from a distance contract within 14 days after the contract is concluded, without giving a reason.

To meet the deadline, it is sufficient for the consumer to communicate the decision to withdraw before the 14-day period expires. The consumer may:

• send an unequivocal withdrawal statement to [email protected] with the subject Consumer Withdrawal;
• send the statement by post to Isentró Kft. at the registered office stated in Section 1 of the Terms;
• use the model form in Section 8 of this Schedule; or
• use an online withdrawal function made available by RunHarvester where mandatory law requires such a function.

Use of the model form is optional. RunHarvester may request information reasonably necessary to identify the Account and relevant transaction, but the withdrawal is not invalid merely because the consumer did not use a specific form.

3.2 Confirmation

Where the consumer uses an online withdrawal function provided by RunHarvester, RunHarvester will provide an acknowledgment of receipt on a durable medium without undue delay where required by law.

4. Performance during the withdrawal period

4.1 Express request for early performance

Where the Service can begin before the 14-day withdrawal period expires, RunHarvester may ask the consumer to make an express request for performance to begin immediately. Merely accepting the Terms is not, by itself, treated as the required express request where Applicable Law requires a separate action.

4.2 Proportionate payment

If the consumer validly withdraws after expressly requesting that a service begin during the withdrawal period, the consumer may be required to pay an amount proportionate to the Service supplied before RunHarvester received the withdrawal notice, compared with the full contractual coverage, where mandatory law permits such a charge.

The calculation may take into account consumed credits, completed requests, usage, elapsed subscription access, third-party charges irreversibly incurred for the consumer's request, or another reasonable measure stated at checkout, but will not exceed what mandatory law allows.

4.3 Loss of the right for a fully performed service

For a service contract, the right of withdrawal may be lost only after the service has been fully performed and only where the consumer gave any express prior request and acknowledgment required by Applicable Law.

4.4 Digital content not supplied on a tangible medium

To the extent a transaction is legally classified as a contract for digital content not supplied on a tangible medium, the right of withdrawal may be lost after supply begins only where all conditions required by Applicable Law are satisfied, including the consumer's prior express consent, acknowledgment that the right will be lost, and receipt of the required confirmation on a durable medium.

RunHarvester will not rely on a purported loss of the withdrawal right where the legally required consent, acknowledgment, or confirmation was not obtained.

5. Effects of withdrawal

Subject to lawful deductions described in Section 4, RunHarvester will reimburse payments required to be reimbursed following a valid withdrawal without undue delay and no later than 14 days after being informed of the consumer's decision, unless a different mandatory rule applies.

Reimbursement will ordinarily use the same payment method used for the original transaction unless the consumer expressly agrees otherwise and incurs no fee as a result. Processing time after RunHarvester initiates a refund may depend on the payment provider.

Withdrawal does not require RunHarvester to reimburse:

• a proportionate amount lawfully payable for performance requested during the withdrawal period;
• usage or third-party cost that mandatory law permits RunHarvester to charge;
• an amount attributable to a separate transaction not covered by the withdrawal; or
• a payment for which the statutory withdrawal right was validly excluded or lost.

On withdrawal or termination, the consumer must stop using the affected paid entitlement. RunHarvester may deactivate associated access, credits, keys, jobs, and integrations, subject to statutory data-access and deletion obligations.

6. Statutory conformity rights

Where mandatory consumer law governing digital content or digital services applies, RunHarvester remains responsible for the statutory conformity obligations that cannot be excluded. Depending on the circumstances and Applicable Law, the consumer may be entitled to:

1. have the digital service brought into conformity within a reasonable time, free of charge, and without significant inconvenience;
2. receive a proportionate reduction in price; or
3. terminate the affected contract and receive the reimbursement required by law.

A remedy may depend on the nature and materiality of the lack of conformity, whether conformity is impossible or disproportionate, whether RunHarvester failed to remedy it, and other statutory conditions. These rights are separate from voluntary service credits, support commitments, or contractual warranties.

The consumer must cooperate reasonably in determining whether the issue results from the consumer's digital environment where mandatory law permits such cooperation, provided RunHarvester supplies clear and proportionate technical instructions and uses the least intrusive means reasonably available.

7. Complaints and dispute resolution

A consumer may first contact [email protected] with the subject Consumer Complaint. RunHarvester will handle the complaint in accordance with mandatory law and will provide information about any competent alternative dispute-resolution or conciliation body where legally required.

A consumer may also contact the competent Hungarian regional conciliation board or another competent consumer-protection authority. Any mandatory right to bring proceedings in the courts of the consumer's residence or another mandatory forum is unaffected by Section 35 of the Terms.

The former European Union Online Dispute Resolution platform has been discontinued. RunHarvester therefore does not direct consumers to that former platform.

8. Model withdrawal form

Complete and return this form only if you wish to withdraw from an eligible consumer contract. An unequivocal statement containing the same information is sufficient.

To: Isentró Kft., 1082 Budapest, Corvin sétány 6, 8th floor, unit 4, Hungary; [email protected]

I/We hereby give notice that I/We withdraw from my/our contract for the following service:

Service or order: ______________________________________________

Order or contract date: ________________________________________

Account email or customer identifier: ___________________________

Name of consumer(s): ___________________________________________

Address of consumer(s): ________________________________________

Signature of consumer(s), only if submitted on paper: ___________

Date: ___________________________________________________________