How web data is processed

This page summarizes how RunHarvester processes data to operate accounts, proxy inventory, collection processes, scrape jobs, APIs, exports, billing, security, analytics, and support.

It is provided for transparency and does not replace a signed data processing agreement or enterprise agreement.

RunHarvester is operated by Isentró Kft, registered at 1082 Budapest, Corvin sétány 6, 8th floor, unit 4, Hungary.

For account administration, security, billing, and direct service operations, RunHarvester generally determines the necessary processing purposes. Where a signed agreement appoints RunHarvester as a processor, covered customer data is processed according to documented instructions and applicable law.

• Receive and validate domains, URLs, queries, rules, schedules, credentials, and API requests submitted by authorized users.
• Route requests through configured infrastructure, execute collection jobs, parse responses, store results, and prepare exports or delivery events.
• Monitor proxy health, latency, status codes, job progress, failures, quotas, and security events.
• Operate authentication, permissions, billing, notifications, support, audit logging, and abuse prevention.

Customers should configure jobs to collect only data that is necessary and lawful for their purpose, and should apply appropriate retention, access, and deletion controls.

RunHarvester is not designed for collecting passwords, payment credentials, private communications, medical records, government identifiers, or similarly sensitive data without a specific authorized use case and appropriate safeguards.

RunHarvester may rely on infrastructure, storage, proxy, security, authentication, monitoring, communications, support, and payment providers. Access is limited to what is needed to perform their services.

Where required, international transfers are handled using recognized safeguards. Enterprise customers may request current processing details through support.

We use access controls, logging, encryption where appropriate, environment separation, and operational monitoring designed to protect processed data.

Retention depends on the data type, product settings, plan, security needs, legal duties, and any written agreement. Deletion requests are handled subject to backups, audit requirements, billing records, and lawful retention obligations.

• Provide lawful instructions and maintain a valid basis for collection and processing.
• Manage user access, credentials, API keys, target configuration, request rates, and exported data securely.
• Respond to data-subject requests and provide required notices where the customer determines the collection purpose.

For data-processing, security, deletion, or enterprise questions, contact [email protected].