Insighteo App

Legal document

Terms of Service

English working translation. The service is provided in Poland and the Polish version is the primary version.

§1. General provisions

  1. These Terms govern the use of Insighteo App, a SaaS application provided electronically.
  2. The service provider is Insighteo Tomasz Łabędzki, tax ID: 8951863348, contact e-mail: [email protected].
  3. The Terms are made available free of charge before using the application in a way that allows the user to obtain, reproduce and store them.
  4. The Terms apply from 2026-05-13 and are governed by Polish law.
  5. Items concerning the final payment model, refunds, withdrawal rights, plan limits and the exact list of providers require final business decisions and legal verification.

§2. Definitions

  1. Application - Insighteo App, a web application used to import CSV files, map columns, generate product rankings and download CSV results.
  2. User - a natural person, legal person or organisational unit using the application, including an entrepreneur, consumer or entrepreneur with consumer rights where applicable.
  3. Account - individual user access to the application protected by login credentials.
  4. Import - uploading a CSV file to the application and creating a processing job.
  5. Mapping template - a saved user mapping of CSV columns to application fields, available for files with the same header layout.
  6. Tokens or import credits - billing units assigned to the user's account and used to start CSV file processing.

§3. Scope of services

  1. The application allows users to create an account, log in by password or Google OAuth, complete account and invoice data and use the user panel.
  2. The application allows users to upload CSV files with e-commerce product data, map file columns to fields required by the algorithm and save mapping templates.
  3. The application processes the CSV file, creates a product ranking, shows import status, provides import history, result preview and CSV result download.
  4. The user may delete imports and related files from history. The user may also delete saved mapping templates.
  5. The application administrator may have access to an admin panel covering users, imports and company-data settings used in legal documents.

§4. Account and login

  1. Using some features requires creating an account.
  2. The user may log in with e-mail and password or, if enabled, through Google OAuth.
  3. When Google login is used, the application may receive the user's e-mail address, Google account identifier and e-mail verification information.
  4. The user should protect login credentials and must not share the account with third parties.
  5. The provider may block the account if the user breaches the law, these Terms, application security or third-party rights.

§5. CSV files, data and user obligations

  1. The application is intended for e-commerce product data, such as product_id, product_name, category, sold, views, sales_value and cogs.
  2. The user may upload a file with different column names and map them in the mapping interface.
  3. The user is responsible for the legality, accuracy and scope of data uploaded to the application.
  4. The user should not upload personal data, trade secrets or other data that is not needed to generate a product ranking.
  5. If the user nevertheless includes personal data in a CSV file, the user is responsible for having a proper legal basis for processing and transferring it to the application.
  6. It is prohibited to upload unlawful content, content infringing third-party rights, harmful software or data intended to bypass security measures.

§6. Product ranking

  1. The application calculates rankings based on product data, in particular sales, views, sales value, cost of goods, profit and conversion.
  2. The ranking is analytical and supportive. It is not legal, tax, accounting, financial or business advice and does not guarantee sales results.
  3. The user should independently verify the result before using it in a store, campaign, pricing, product exposure or other business decisions.
  4. The provider is not responsible for the effects of incorrect input data, incorrect column mapping or use of the result contrary to its purpose.

§7. Import statuses, errors and retention

  1. An import may have the following statuses: mapping, queued, processing, done or failed.
  2. Processing is handled by a separate worker component. If processing fails, the application may show a friendly message, allow retrying or allow returning to column mapping.
  3. Import files and result files are stored for the configured retention period. The default planned retention period is 7 days unless the provider configures another period.
  4. Deleting an import by the user should remove related import and result files from the storage system, subject to technical limitations, backups and legal obligations.
  5. The provider may automatically delete imports older than the configured retention period.

§8. Payments, Stripe, subscriptions and tokens

  1. Paid features may be provided through a Premium subscription with an import-credit token allowance. Stripe integration is used for payment handling, payment method management, subscription status and payment-related webhooks.
  2. Tokens are charged when the user confirms column mapping and starts CSV processing. Uploading a file and reviewing mapping before processing does not by itself charge tokens.
  3. The import cost depends on the number of products in the CSV file and is calculated according to the current rules shown in the application before processing starts. The application shows the token cost before the user confirms mapping and starts the import.
  4. Retrying or fixing mapping for the same already charged import does not charge additional tokens.
  5. Tokens may be refunded for technical failures of the application or infrastructure. Incorrect CSV data, incorrect mapping or deletion of an import by the user does not automatically create a refund, unless the provider decides otherwise or mandatory law requires it.
  6. Payments are handled by Stripe. Stripe may process payment data under its own legal terms. The application does not store full payment card details.
  7. Billing and invoice data are collected and stored in the application. Invoices are issued by the provider outside Stripe or in a separate accounting process. Stripe is not the place where the user manages invoice data or receives invoices for the service, unless the provider explicitly enables such a process in the future.
  8. If payment fails or a plan limit is exceeded, access to paid features may be limited.
  9. Details of prices, limits, billing periods, refunds and consumer withdrawal rules should be presented before purchase. These items require final business and legal confirmation.

§9. Consumers and withdrawal from the agreement

  1. If the application is offered to consumers or entrepreneurs with consumer rights, the user may have rights under consumer protection laws.
  2. As a rule, a consumer may have the right to withdraw from a distance contract, unless a statutory exclusion applies, for example starting the provision of digital content or a digital service with the user's express consent and after informing the user about losing the withdrawal right.
  3. The exact model of withdrawal, refunds and settlement of used tokens/import credits requires final business decisions and legal verification before launching paid services.

§10. Third-party providers

  1. The application may use DigitalOcean App Platform, DigitalOcean Managed PostgreSQL and DigitalOcean Spaces or compatible S3 storage for hosting, database and file storage.
  2. The application may use Google OAuth for login and Stripe for payments.
  3. The provider may also use accounting, invoicing, e-mail, monitoring, backup and security providers where needed to operate the service and comply with legal duties.

§11. Complaints and contact

  1. Complaints and reports concerning application operation may be sent to [email protected].
  2. The report should include a problem description, account e-mail, import ID if applicable and information allowing the provider to reproduce the issue.
  3. The provider reviews complaints within 14 days of receipt, unless the nature of the case requires more time.

§12. Termination of use and account deletion

  1. The user may stop using the application and request account deletion by contacting the provider at [email protected].
  2. Account deletion may not include data that the provider must retain under law, in particular accounting, tax, settlement data or data needed to pursue or defend claims.
  3. Deleting an import by the user is separate from deleting the account and concerns a specific import and its related files.

§13. Changes to the Terms

  1. The provider may change these Terms in particular due to changes in application features, payment model, providers, law, security requirements or the way services are provided.
  2. The user should be informed about changes in a way that allows them to read the new content.
  3. If the law requires a specific procedure for changing terms towards a consumer, the provider will apply that procedure.