Privacy Policy

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

This Privacy Policy explains how ETL Console (“Service”, “Platform”, “we”, “us”, “our”) collects, uses, stores, and protects personal data and related information when users access or use the Platform.

By using the Service, you acknowledge this Privacy Policy.

1. Our Role

For account, billing, security, support, and platform usage data, we act as the data controller.

For customer data processed through user-configured connections, staging jobs, transformations, and target systems, we generally act as a data processor acting on behalf of the customer.

The customer is responsible for determining whether they have the legal right, authority, and lawful basis to connect data sources and process data through the Platform.

2. Data We Collect and Store

We may collect and store the following categories of data.

2.1 Account and User Data

name;\ email address;\ password hash;\ organization or workspace membership;\ user role and permissions;\ settings and preferences;\ subscription plan;\ billing status;\ login, session, and security records;\ support communications;\ major user actions in the Platform.

Major user actions may include page views inside the application, creation or deletion of connections, mappings, staging configurations, transformations, job runs, settings changes, and similar product activity. We use this information to operate the Service, improve usability, troubleshoot errors, maintain security, and resolve disputes.

2.2 Connection and Credential Data

We may store connection settings and encrypted credentials or secrets required to operate user-configured connections.

Connection credentials are used only to perform operations requested or configured by the user.

Where technically supported:

credentials are encrypted at rest;\ credentials are not displayed back in plain text after saving;\ access to credentials is restricted to what is necessary to operate the Service.

2.3 Metadata and Configuration Data

We may store metadata and configuration data required to operate the Platform, including:

connection names;\ schema names;\ table names;\ column names;\ data types;\ nullable flags;\ primary key and index information where available;\ mapping configuration;\ staging configuration;\ transformation configuration;\ job configuration;\ job status and execution history.

This metadata is used for discovery, mapping, validation, job execution, troubleshooting, and user experience inside the Platform.

3. Customer Source Data

ETL Console is designed primarily to process customer data according to user-configured connections, mappings, staging jobs, transformations, and target destinations.

By default, we do not intentionally store full customer source records in the Platform’s internal database, except where specific Platform features require temporary or limited storage as described in this Policy.

Customer source data may be temporarily processed in memory, workers, queues, logs, or other technical components as necessary to perform user-configured operations.

The Platform may write data to customer-configured staging, target, or destination systems. Such destinations are selected and configured by the customer.

4. Table Details, Analysis, and PDF Export

The Platform may allow users to view table details and basic field analysis, such as:

number of columns;\ column names and types;\ primary keys;\ nullable information;\ record counts;\ duplicates count;\ unique count;\ unique values;\ minimum and maximum values;\ average or median;\ sample first records.

This information is displayed to the user for analysis and validation. Table contents, analysis results, and sample records are not stored by us as part of this feature, unless otherwise stated.

If the user exports this information as a PDF, the PDF is generated on demand for immediate download and is not stored by us.

5. Rejected Rows

The Platform may include a feature for storing rejected rows for troubleshooting failed write operations.

Rejected row storage is disabled by default for each staging or transformation. Users may enable it in Advanced Settings by explicit consent.

When enabled, ETL Console may store rejected source rows in its internal database together with technical context, such as:

source row text or failed values;\ error message;\ target schema and target table;\ job ID or log ID;\ staging or transformation ID;\ batch number;\ timestamp;\ user ID.

Rejected rows may contain customer source data, including personal data.

Rejected rows are stored only for troubleshooting failed write operations, such as duplicate keys, length limits, invalid formats, encoding issues, constraint violations, or target database errors.

Rejected rows are retained according to the retention period configured by the user. The default retention period is 3 days, and the maximum retention period is 30 days. Rejected rows are automatically deleted after the configured retention period following job completion.

If rejected row storage is disabled, ETL Console may be unable to provide detailed diagnostics for failed rows.

6. Logs and Error Records

We may collect and store logs and error records necessary to operate, secure, debug, and improve the Service.

Logs may include:

user ID;\ timestamps;\ page or feature activity;\ connection name;\ mapping, staging, or transformation name;\ job status;\ job duration;\ row counts;\ source and target object names;\ error messages;\ technical stack traces;\ SQL fragments;\ metadata;\ limited data fragments where included in error messages or rejected row diagnostics.

We use logs for troubleshooting, security, audit, usage analysis, service improvement, and dispute resolution.

7. Payment and Subscription Data

Payments for online paid subscriptions and eligible add-ons are processed by Paddle, which acts as the merchant of record for such transactions.

We do not store full payment card details.

We may receive and store subscription and payment-related information from Paddle, including:

plan; billing status; billing interval; payment confirmation; customer or subscription identifiers; transaction references; invoice references; amounts; currency; subscription dates; renewal and cancellation status; refund, credit, chargeback, or payment dispute information where applicable.

Paddle processes payment and billing information according to its own terms and privacy policies.

8. How We Use Data

We use collected data to:

provide, operate, and maintain the Service;\ authenticate users and secure accounts;\ manage organizations, roles, permissions, and workspaces;\ create and manage connections, mappings, stagings, transformations, and jobs;\ process user-configured ETL operations;\ store user settings and preferences;\ provide support and troubleshoot errors;\ monitor security, abuse, fraud, and unauthorized access;\ improve product usability and performance;\ manage subscriptions and billing;\ send service, technical, security, billing, and support communications;\ send marketing communications where permitted;\ comply with legal obligations;\ resolve disputes and enforce agreements.

9. Legal Bases for Processing

Where applicable data protection law requires a legal basis for processing personal data, we rely on one or more of the following bases depending on the purpose and circumstances:

Performance of a contract — where processing is necessary to create and manage accounts, provide the Service, operate subscriptions, process user-configured Platform functions, provide support, and administer the contractual relationship.

Legitimate interests — where processing is necessary for security, fraud and abuse prevention, troubleshooting, service reliability, product improvement, administrative operations, dispute resolution, and protection of our rights, provided that such interests are not overridden by the rights and interests of affected individuals.

Legal obligations — where processing is necessary to comply with applicable tax, accounting, regulatory, legal, or other mandatory requirements.

Consent — where consent is required for particular processing activities, such as certain non-essential cookies, analytics, marketing communications, or optional data-storage features.

Where processing is based on consent, consent may be withdrawn at any time, without affecting the lawfulness of processing performed before withdrawal.

10. Analytics

We may use analytics tools, including Google Analytics and Google Tag Manager, to understand website and product usage and improve the Service.

We do not send customer source data, rejected rows, connection credentials, table contents, SQL results, or database record values to analytics providers.

Analytics events may include general product usage events, such as page views, button clicks, feature usage, and job-related actions. We aim to keep analytics events general and not include customer source data or database contents.

Where required by law, we will provide appropriate cookie or consent controls.

11. Emails and Communications

We may send:

service and transactional emails;\ billing and subscription emails;\ security notices;\ technical and support communications;\ product updates;\ marketing emails.

Service, billing, security, and technical emails may be necessary for the operation of the Service.

Marketing emails may include an unsubscribe option. Unsubscribing from marketing emails does not prevent us from sending necessary service, billing, security, or support communications.

12. Cookies and Similar Technologies

We may use cookies and similar technologies for:

authentication;\ session management;\ security;\ user preferences;\ product analytics;\ website analytics.

Essential cookies are required for the Service to function.

Analytics or non-essential cookies may be used to understand website and product usage and improve the Service. Where required, we will provide appropriate notice or consent mechanisms.

13. Third-Party Service Providers

We use third-party service providers where necessary to operate, secure, support, and bill for the Service.

These providers may include infrastructure hosting, email delivery, payment and billing, analytics, backup, and other service providers actually used by ETL Console.

Our current providers and their relevant purposes are identified on our Subprocessors page.

These providers may process limited personal data as necessary to perform their services.

We do not sell personal data.

We do not intentionally provide customer source data, rejected rows, connection credentials, table contents, SQL results, or database record values to analytics providers.

14. International Data Transfers

Personal data may be processed in countries other than the country where the user, Customer, or relevant data subject is located.

Where an international transfer requires additional safeguards under applicable data protection law, we use an appropriate lawful transfer mechanism, which may include applicable Standard Contractual Clauses, adequacy decisions, or other legally recognized safeguards.

Additional information concerning providers involved in data processing is available on our Subprocessors page.

15. Security

We apply reasonable technical and organizational measures designed to protect data processed by the Platform.

These measures may include:

encrypted storage of connection secrets;\ password hashing;\ access controls;\ HTTPS/TLS where applicable;\ restricted access to operational systems;\ logging and monitoring;\ backup and recovery procedures;\ separation of user workspaces and permissions.

No system is completely secure. We cannot guarantee absolute security, uninterrupted operation, or error-free processing.

Users are responsible for securing their own accounts, passwords, data sources, credentials, target systems, and organization access permissions.

16. Data Retention

We retain personal data and operational data only for as long as reasonably necessary for the purposes described in this Privacy Policy, unless a longer retention period is required or permitted by applicable law.

While an account or organization workspace is active, we may retain account data, configuration data, logs, settings, workspace records, and other information necessary to provide and operate the Service.

When an individual account or organization workspace is deleted, tenant-owned operational assets are deleted or anonymized according to the applicable deletion process.

Application logs associated with deleted users are normally deleted within 14 days after the applicable account or organization deletion, subject to any longer retention required for legal, security, fraud-prevention, dispute-resolution, or other legitimate purposes.

Rejected rows are retained according to the Customer-configured retention period, with a default of 3 days and a maximum of 30 days, and are automatically deleted after the configured period following job completion.

Limited billing, subscription, consent, security, fraud-prevention, tax, accounting, and legal records may be retained for longer where necessary or required by law.

Data deleted from active systems may remain in backups for a limited period until the applicable backup retention cycle expires.

Where appropriate, retained records may be minimized, anonymized, or pseudonymized.

17. Account and Organization Deletion

Standalone users may request deletion of their own accounts where supported by the Platform.

Users who belong to an organization may be subject to organization-level account and access controls.

An organization owner may request deletion of the organization and its associated user accounts, subject to the applicable Platform permissions and deletion process.

When an account or organization is deleted, related data is deleted, anonymized, or retained according to the retention rules described in this Privacy Policy, the Data Processing Agreement, and applicable law.

Deletion of an ETL Console account or organization does not delete data stored in external customer-controlled source systems, target systems, databases, files, or other external destinations.

18. Sensitive Data

The Platform is not specifically designed for processing highly sensitive categories of personal data unless the customer has ensured all required legal basis, safeguards, permissions, and compliance obligations.

Customers are solely responsible for determining whether data connected to or processed through the Platform is suitable for use with the Service and whether additional safeguards or agreements are required.

19. Children

The Service is not intended for persons under 18 years old.

We do not knowingly collect personal data from persons under 18. If we become aware that such data has been collected, we may delete it.

20. AI and Model Training

The Service does not currently include AI features unless expressly identified in the Platform.

We do not use customer source data to train AI models.

If AI features are introduced in the future, additional notices, settings, or terms may apply.

21. On-Premise Deployments

For Enterprise on-premise deployments, some data may remain within customer-controlled infrastructure.

However, depending on the applicable agreement and configuration, we may still process account, license, support, billing, diagnostic, security, or technical information related to the deployment.

On-premise deployments may be subject to separate terms, security documentation, and data processing arrangements.

22. Your Rights

Depending on your location and applicable law, you may have rights to:

access your personal data;\ correct inaccurate personal data;\ request deletion of personal data;\ restrict processing;\ object to processing;\ request data portability;\ withdraw consent where processing is based on consent;\ complain to a data protection authority.

These rights are subject to the conditions, limitations, and exceptions provided by applicable law.

To exercise these rights, contact us at:

support@etlconsole.com

We may need to verify your identity before responding.

For customer data processed on behalf of an organization, requests may need to be directed to the relevant organization administrator or data controller.

23. Changes to This Privacy Policy

We may update this Privacy 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 Privacy Policy becomes effective means you acknowledge the updated Policy.

24. Contact

For privacy questions, requests, or notices, contact us at:

Igor Bobritskii PR Novi Sad Gajeva 3A 21000 Novi Sad Serbia Email: support@etlconsole.com