LOTPIXEL COOKIE POLICY

Last Updated: 6 March, 2026

INTRODUCTION

We believe in being transparent about how we collect and use data. This Cookie Policy explains what types of cookies and similar tracking technologies we use across our Services, including the LotPixel website, the LotPixel Hub desktop application, and our digital content creation add-ons (such as the LotPixel Blender Add-on, LotPixel 3ds Max Add-on, and other supported DCC integrations). It also explains why we use these technologies, what information they store, and how you can manage or disable them.

When we refer to "we", "our", or "us", we refer to the relevant LotPixel entity listed in the Contact section. When we refer to the "Services", we mean our websites, software applications, licensed digital assets, and all tools and platforms provided to our customers.

Please also read our Privacy Policy for more details on how we process personal data. You may adjust your privacy preferences at any time to prevent non-essential cookies or tracking technologies from being used.

COOKIES AND LOGS

Cookies

A cookie is a small piece of data stored on your device by a website or application. Cookies allow us to remember your preferences, identify returning users, and make your experience more efficient.

On the LotPixel website, cookies may store:

  • Login details
  • Language preferences
  • Subscription-related choices
  • Session information

In the LotPixel Hub application, traditional browser cookies are not used. However, the application uses local configuration files, authentication tokens, cache data, and user settings that perform similar functions, such as:

  • Keeping you logged in
  • Remembering your download directory
  • Preserving interface and feature preferences
  • Improving application performance

These app-level storage mechanisms are considered "cookie-equivalent technologies" for transparency and compliance purposes.

Local Storage, Authentication Tokens, and App-Level Tracking (LotPixel Hub & Add-ons)

In addition to website cookies, the LotPixel Hub and official DCC add-ons (including the LotPixel Blender Add-on and LotPixel 3ds Max Add-on) use local storage systems and technical logs that operate similarly to cookies.

These technologies include:

  • Authentication tokens used to maintain login sessions
  • Local configuration files storing preferences, UI settings, and language choices
  • Cached data to reduce loading times
  • Session state files allowing the application to resume your last environment
  • Diagnostic logs created by the Hub or add-ons to help troubleshoot technical issues

These tools are used to:

  • Authenticate your LotPixel account inside the Hub
  • Support secure asset downloads and one-click imports
  • Maintain your preferred settings across sessions
  • Prevent service abuse or automated misuse
  • Improve usability, stability, and performance

These technologies do NOT collect or transmit:

  • Names of your local folders or directories
  • Filenames of your project files (e.g., Blender, 3ds Max, or other DCC files)
  • File contents such as textures, models, scenes, or any local assets
  • 3D project or scene data stored inside DCC software

All such content remains strictly local on your machine and is never uploaded to LotPixel.

EU/EEA Compliance
Where required by law, optional analytics and diagnostic data generated by the Hub or Add-ons will only be collected with explicit opt-in consent.
Consent can be withdrawn at any time.

Log Files

Log files record technical actions that occur within a website, application, or addon. We use logs to:

  • Monitor system activity
  • Diagnose technical issues
  • Analyze performance
  • Maintain stable operations

Log entries may include device type, non-fatal errors, timestamps, and add-on activity.

Logs are anonymized whenever possible and are never used to access, inspect, or track the contents of your project files, including Blender scenes, 3ds Max scenes, textures, models, or other creative assets.

Web Beacons and Tracking Technologies

Our website and services may use web beacons, pixel tags, and similar tracking tools. These technologies help us:

  • Analyze traffic flow
  • Measure feature usage
  • Improve performance and reliability

Some data may be transmitted to LotPixel or to trusted third-party service providers. Where possible, collected information is anonymized or non-identifiable.

HOW WE USE COOKIES

Essential Cookies

Essential cookies (and essential local storage mechanisms in the Hub) are required for core functionality, such as:

  • Account creation
  • Login sessions
  • Subscription and payment processing
  • Hub authentication
  • Secure asset downloads and imports

Without these tools, critical functionality including downloading assets through the Hub would not work reliably.

Performance Cookies

Performance cookies and equivalent analytics tools help us understand how users interact with the Services by measuring:

  • Visit duration
  • Frequently accessed pages
  • Device type (desktop/mobile)
  • Hub and plugin feature usage

All data is aggregated and anonymized whenever possible. These insights help us improve the website, Hub performance, and addon behavior.

Functionality Cookies

Functionality cookies and local storage entries remember your choices, such as:

  • Interface layout
  • Asset filtering preferences
  • Theme options
  • Language selection
  • Preferred download locations

These enhance usability and maintain convenience across sessions.

Advertising / Targeting Cookies

Advertising cookies may be used to deliver relevant promotional content. They:

  • Activate only with explicit user consent
  • Do not collect sensitive personal data

THIRD-PARTY COOKIES

We rely on trusted third-party providers for analytics, performance, advertising, and security. These providers may set their own cookies.

Examples include:

  • Google Analytics – traffic & behavior statistics
  • Yandex Metrica – usage analysis
  • Google Ads / DoubleClick – advertising tracking
  • Meta Pixel – campaign performance
  • Cloudflare – security & speed optimization

Each provider has its own cookie policy. Please refer to those policies for more information.

Microsoft Store Distribution & App Telemetry

If you download and use the LotPixel Hub through the Microsoft Store, the application does not rely on traditional website browser cookies. However, the Microsoft Store platform and Windows operating system may collect their own diagnostic, licensing, performance, and security data in accordance with Microsoft's Privacy Policy. This data is controlled by Microsoft, not LotPixel.

The LotPixel Hub itself may use local storage, authentication tokens, cache files, secure session data, and technical logs as described in this Cookie Policy. These are "cookie-equivalent technologies" used only to support authentication, maintain preferences, enable secure downloads, improve performance, and ensure stability.

LotPixel does not collect or upload your local project files, directory names, Blender scenes, 3ds Max scenes, textures, models, or any creative content stored on your device. Where required by law (such as in the EU/EEA), optional analytics or diagnostics will only be collected with explicit user consent, and consent may be withdrawn at any time.

LotPixel does not control and is not responsible for any cookies or telemetry technologies that are set or managed directly by Microsoft, the Microsoft Store, or the Windows operating system.

Any such platform-level cookies or telemetry are governed exclusively by Microsoft's own terms and privacy statement.

DISABLING COOKIES

You may disable cookies through your browser settings. Modern browsers allow you to block, delete, or limit cookies.

However, disabling essential cookies or Hub local storage components may cause parts of the Services to stop working, including:

  • Login sessions
  • Download authentication
  • Hub import functionality

Guides for major browsers:

  • Google Chrome
  • Mozilla Firefox
  • Safari (Desktop)
  • Safari (Mobile)

CONTACT

If you have any questions regarding this Cookie Policy, please contact:

[email protected]