Acceptable Use Policy

Effective Date: 10 August 2026 Service: ETL Console\ Owner: Igor Bobritskii PR Novi Sad Contact: support@etlconsole.com

This Acceptable Use Policy (“Policy”) describes permitted and prohibited uses of ETL Console (“Service”, “Platform”, “we”, “us”, “our”).

This Policy forms part of our Terms of Service. By using the Service, you agree to comply with this Policy.

1. Purpose of the Service

ETL Console may be used only for lawful and authorized data integration, transformation, staging, analysis, testing, workflow automation, and related business purposes.

You must not use the Service in any way that is unlawful, unauthorized, harmful, abusive, deceptive, or inconsistent with this Policy.

2. Authorized Use Only

You may connect to a database, API, file source, storage location, system, account, or other data source only if you have all required rights, permissions, licenses, approvals, and authority to access and process that data.

You are responsible for ensuring that your use of the Service complies with:

applicable laws and regulations;\ contracts and confidentiality obligations;\ internal company policies;\ privacy and data protection requirements;\ third-party rights;\ data source access rules;\ security policies applicable to your organization.

You must not use the Service to access, extract, process, stage, transform, or transfer data that you are not legally authorized to use.

3. Prohibited Data Access and Processing

You must not use the Service to:

access systems, databases, APIs, files, or accounts without authorization;\ process stolen, leaked, hacked, or unlawfully obtained data;\ bypass access controls, authentication, authorization, rate limits, or technical restrictions;\ violate privacy, data protection, confidentiality, or intellectual property rights;\ perform unlawful profiling, surveillance, tracking, or monitoring;\ commit identity theft, fraud, phishing, credential theft, or impersonation;\ process data in violation of sanctions, export controls, or other legal restrictions.

4. Sensitive and Regulated Data

You must not process highly sensitive, regulated, or special-category data through the Service unless you have all required legal basis, permissions, safeguards, notices, consents, and compliance controls.

You are solely responsible for determining whether connected data requires additional safeguards, contractual protections, regulatory approvals, or restrictions.

5. Security Restrictions

You must not:

scan, probe, test, or attack the security of the Service without written permission;\ perform penetration testing, load testing, or stress testing without written permission;\ introduce malware, malicious code, or harmful payloads;\ attempt to gain unauthorized access to the Service, other accounts, infrastructure, or data;\ reverse engineer, decompile, disassemble, or attempt to derive source code;\ exploit vulnerabilities or bypass security controls;\ interfere with the security, integrity, availability, or performance of the Service;\ attempt to access other users’ data, workspaces, jobs, logs, or configurations.

If you discover a vulnerability, you must report it responsibly and not exploit it.

6. Infrastructure Abuse

You must not use the Service in a way that may damage, overload, degrade, disrupt, or interfere with the Platform, infrastructure, workers, queues, databases, networks, third-party services, or other users.

Prohibited activities include:

excessive automated requests;\ abusive job scheduling;\ unreasonable parallel job execution;\ attempts to overload workers or queues;\ resource exhaustion;\ scraping the Service interface;\ circumventing technical limits;\ using bots or scripts in a way that disrupts normal operation.

7. Usage Limits and Fair Use

You must comply with all plan limits, usage limits, fair-use inserted-row limits, job limits, storage limits, connection limits, rate limits, queue restrictions, and subscription restrictions applicable to your account or organization. Where a plan displays “Fair-use inserted rows / month,” “month” means the recurring monthly usage period anchored to the applicable subscription period and does not necessarily align with a calendar month.

You must not bypass, manipulate, automate around, or attempt to avoid such limits or technical controls.

We may enforce fair use controls, queue priority, throttling, job limits, or other operational restrictions to protect the Service and other users.

8. Credentials and Secrets

You are responsible for protecting credentials, tokens, keys, certificates, private keys, passwords, and other secrets used with the Service.

You must not place passwords, API keys, tokens, private keys, or other secrets in fields not intended for secrets, including:

labels;\ notes;\ connection names;\ schema names;\ table names;\ default headers;\ query parameters;\ plain text comments;\ fields not expressly marked or designed for secret storage.

You should not embed credentials in connection URIs unless the Platform explicitly marks the field as encrypted or secret-safe.

If you choose to place secrets in unsupported or non-secret fields, you are responsible for the security consequences.

9. Source and Target Systems

You are responsible for all source and target systems connected to or used with the Platform.

You must ensure that:

source systems may lawfully be accessed and read by the Platform;\ target systems may lawfully receive data written by the Platform;\ target schemas, tables, and permissions are correctly configured;\ write, reload, truncate, delete, recreate, or transformation operations are authorized;\ Platform jobs do not violate internal policies, contracts, or legal requirements.

ETL Console does not verify whether your source or target systems are correctly configured or legally authorized for your intended use.

10. Account Security and Access Sharing

You must keep account credentials secure and must not allow unauthorized persons to access your account.

You must not:

share login credentials with unauthorized users;\ allow multiple unrelated organizations to use one account;\ create misleading, fake, or fraudulent accounts;\ use another person’s account without permission;\ attempt credential stuffing, password guessing, or session hijacking;\ misrepresent your identity or authority.

Organization administrators are responsible for managing invited users, permissions, and access removal.

11. Trial, Subscription, and Billing Abuse

You must not abuse free plans, trials, subscriptions, promotional offers, or billing systems.

Prohibited conduct includes:

creating multiple accounts to obtain repeated trials;\ using aliases or duplicate identities to avoid trial restrictions;\ deleting and recreating accounts to reset trial eligibility;\ avoiding billing limits or subscription restrictions;\ using false billing information;\ disputing valid charges in bad faith;\ circumventing payment or plan enforcement mechanisms.

We may use technical and operational measures to detect and prevent trial, billing, and subscription abuse.

12. Resale, Sublicensing, and Managed Services

You may not resell, sublicense, rent, lease, or otherwise provide access to the Service as a standalone product or subscription to third parties unless expressly authorized by us in writing.

Consultants, contractors, system integrators, managed service providers, and other professional service providers may use ETL Console to provide data integration, data engineering, analytics engineering, implementation, operational, or related services to their clients, provided that they are properly authorized to access and process the relevant systems and data and comply with these Terms and our applicable policies.

Such permitted professional use does not allow you to resell ETL Console subscriptions, provide ETL Console itself as a standalone service to third parties, white-label the Service, embed the Service into another commercial product or platform, sublicense access to the Service, or represent ETL Console as your own product without our prior written authorization.

If you wish to use ETL Console as part of a reseller, OEM, white-label, embedded, or other commercial distribution arrangement, a separate written agreement with us may be required.

13. Prohibited Content and Activities

You must not use the Service for:

malware, ransomware, spyware, or harmful code;\ phishing or social engineering;\ spam or unlawful messaging;\ fraud or deceptive practices;\ unauthorized surveillance or tracking;\ harassment, threats, or abuse;\ illegal discrimination;\ unlawful sale or transfer of data;\ violation of intellectual property rights;\ any activity that is illegal, harmful, or abusive.

14. Compliance With Laws

You are responsible for ensuring that your use of the Service complies with all applicable laws and regulations, including where applicable:

data protection and privacy laws;\ cybersecurity laws;\ confidentiality and trade secret laws;\ employment and workplace data rules;\ financial, tax, audit, or reporting obligations;\ export control and sanctions laws;\ sector-specific data regulations.

We do not provide legal, compliance, accounting, tax, audit, or regulatory advice.

15. Monitoring and Enforcement

We may monitor usage, logs, jobs, technical activity, and account behavior to detect:

abuse;\ security risks;\ excessive load;\ policy violations;\ unauthorized use;\ trial or billing abuse;\ fraud;\ operational risks;\ violations of law or third-party rights.

If we reasonably believe this Policy has been violated, we may take action, including:

warning the user;\ limiting usage;\ throttling jobs;\ pausing or blocking jobs;\ disabling connections;\ removing abusive configurations;\ suspending access;\ downgrading or restricting features;\ terminating accounts;\ preserving relevant records for investigation;\ reporting unlawful activity where required or appropriate.

We are not required to provide advance notice where urgent action is needed for security, legal, operational, or abuse-prevention reasons.

16. On-Premise Enterprise Deployments

For on-premise Enterprise deployments, Customer is responsible for enforcing acceptable use within its own environment unless a separate written agreement states otherwise.

Customer is responsible for user access, local infrastructure, source and target systems, credentials, internal security policies, local data processing, backups, and operational controls within the customer-controlled environment.

17. Reporting Abuse

To report abuse, unauthorized use, security concerns, or violations of this Policy, contact us at:

support@etlconsole.com

Please include enough information to help us investigate the issue.

18. Changes to This Policy

We may update this Policy from time to time.

If changes are material, we will make reasonable efforts to notify users through the Platform, email, or other reasonable means.

Continued use of the Service after the updated Policy becomes effective means you accept the updated Policy.