Skip to content
MaxEnergicMaxSCADAMaxPPCZeroexportWeather StationModbusBBIEC Gateway
ModbusBB logoModbusBBby MaxEnergic
Home Features Guides Free Tools Docs Manual CLI SCADA Cloud Android Contact Learn About ← Max Energic Download Buy $10

Privacy Policy

How we collect, use, and protect your information

Last updated: November 16, 2026

1. Introduction

Max Energic Apps ("we", "us", "our") publishes ModbusBB ("the Software") and this website, and the Android app ModbusBB Mobile (section 12). This policy explains what personal data we process when you visit the website, buy a license, activate the Software or receive email from us, why we process it, and how long we keep it.

2. What the Software does not send

  • ModbusBB talks directly to your devices over your network or serial port. Your Modbus traffic, register values, device addresses, connection settings, workspaces and log files stay on your computer and are never sent to us.
  • The only network requests the Software makes to us are license activation/verification and the update check described below.

3. Data we collect and store

3.1 When you buy a license

  • Payment: Payments are processed by PayPal. We never receive or store card or bank details. After checkout our server confirms the order with PayPal and stores the PayPal order ID and transaction ID, the amount and the payment status.
  • License record: your name and email address (as provided through the purchase), the generated license key, its status and the creation date.

3.2 When you activate or verify a license

The Software sends your license key and information about the computer so that a license can be limited to 3 devices. For each activation we store:

  • a machine ID, which is a SHA-256 hash derived from hardware identifiers, not the raw identifiers;
  • the processor ID and motherboard serial number reported by Windows, used only to recognise the same PC after a hardware change;
  • the device (computer) name;
  • the IP address of the request;
  • timestamps for activation, last check and deactivation.

Licensing events (for example activation, verification, deactivation and rejected attempts) are written to an audit log with the license key, machine ID, device name, IP address and time. You can see and deactivate your devices in the self-service license portal.

3.3 Update check

At most once a day the Software downloads a small version file from this website to see whether a new release exists. It sends no license key or personal data with that request; like any web request, it reaches our web server with your IP address.

3.4 Email

  • We send your license key by email after purchase, and service emails about your license (for example device-activation notices or a resent key on request).
  • We may send update announcements for new ModbusBB versions to license holders. Every announcement contains an unsubscribe link. If you unsubscribe, we store your email address and the date on a suppression list so that we do not email you again.
  • We keep a record of emails sent (recipient, subject, type, time and delivery status).

3.5 Security and abuse prevention

To protect the licensing and payment endpoints we apply rate limits. Rate-limit counters are keyed on a one-way hash of the IP address (not the address itself) and expire automatically after a short time window. Server error and payment logs may contain order IDs, license keys and email addresses for troubleshooting.

3.6 Support requests

If you email us, we keep your message and email address to answer it.

4. Website analytics (Google Analytics)

This website uses Google Analytics 4 (GA4), provided by Google, to measure page views, traffic sources, approximate location and device/browser type. GA4 sets first-party cookies (such as _ga) to recognise returning browsers. Google receives your IP address with each request; according to Google, GA4 does not log or store IP addresses and uses them only to derive approximate location. Analytics data is processed by Google under its own privacy terms. You can block these cookies in your browser or use the Google Analytics opt-out browser add-on. We do not send purchase details, email addresses or license keys to Google Analytics.

5. How we use the data

  • to deliver your license key and confirm your purchase;
  • to activate and verify licenses and enforce the 3-device limit;
  • to prevent fraud, key sharing and abuse of our servers;
  • to provide support and handle refunds;
  • to tell license holders about updates (you can unsubscribe at any time);
  • to understand how the website is used and improve it.

6. Sharing

We do not sell or rent personal data. It is shared only with service providers needed to run the service: PayPal (payments), Google (website analytics), our web hosting and email-sending providers, and authorities where the law requires it.

7. Retention

  • License, purchase and activation records, the audit log and the email record are kept for as long as needed to provide and enforce the license (a lifetime license has no end date) and to prevent fraud, and as required for tax and accounting.
  • Rate-limit records expire and are deleted automatically.
  • The unsubscribe list is kept so that your opt-out keeps working.
  • Analytics data is retained according to our Google Analytics data-retention setting.

8. Your rights

Depending on where you live, you may have the right to access, correct or delete your personal data, to object to or restrict its processing, and to receive a copy of it. You can unsubscribe from update emails at any time using the link in the email. Deleting license data will deactivate the license. To make a request, contact us at the address below.

9. Security

The website and licensing API use HTTPS. Access to the licensing database is restricted, and the machine ID is stored as a hash.

10. Children

ModbusBB is a professional engineering tool and is not directed at children. We do not knowingly collect data from children.

11. International transfers

Our service providers (such as PayPal, Google and our hosting provider) may process data in countries other than your own.

12. ModbusBB Mobile (Android app)

This section covers the Android app "ModbusBB: Modbus TCP RTU Tool" (package com.maxenergic.modbusbb), published on Google Play by Max Energic Apps.

What stays on your phone

  • Your connections, poll tabs, register maps, workspaces, recordings, alarm rules and the alarm event log are stored only on your phone. Unless you turn on ModbusBB Cloud (below) for a connection, Modbus traffic, register values, IP addresses, serial and Bluetooth device names are never sent to us or to any service.
  • The app talks to your Modbus devices directly over Wi-Fi/Ethernet, USB (RS-485 adapters) or Bluetooth. These permissions are used only for that.
  • Exports (CSV, ZIP, workspace files) leave the phone only when you share them yourself.

Purchases (Premium)

Subscriptions and the lifetime purchase are processed by Google Play. We do not receive your payment details. The app asks Google Play which products your Google account owns, to unlock Premium; Google gives us order information (product, date, country) for accounting and support.

ModbusBB Cloud (optional)

ModbusBB Cloud is an optional paid service. Nothing below applies unless you create a Cloud account in the app (More → ModbusBB Cloud) or at androidscada.maxenergic.com.

  • Account: your email address, an optional display name and a password (stored only as a salted hash). If you choose Sign in with Google instead, Google tells us your Google account ID, email address (only when Google has verified it), and name; we store the ID to recognise you next time and do not receive your Google password or any other Google data. Signing in with Google to an address that already has a Cloud account links the two. We send you account emails: confirmation and password-reset links, team invitations, storage and subscription notices.
  • Gateway data: only for the connections you choose to upload from a phone you add as a gateway: tag names, units and register addresses, the values read from your devices (minute summaries and the latest value), and the gateway's name, app version, battery level, charging state, network type and upload backlog.
  • Settings and devices: your preferences (language, theme, time zone, 12/24-hour clock), the names, units and display order you give tags, a gateway's description and location text, and for each signed-in device the browser or app name it reports and when it was last used, so you can see and sign out devices in Settings.
  • Alerts: the alert rules you create (limit, rate of change, unchanged value or offline; threshold, delay, reminders, chosen recipients) and a log of when each alert started and ended with the value at that moment, and who acknowledged or snoozed it. Alert emails go only to the team members chosen as recipients, and each person can turn them off in Settings.
  • Alert notifications outside email (optional): only if you set them up. Push notifications to the app: we store your phone's Firebase Cloud Messaging token and send the alert text through Google's Firebase service. Telegram: when you link a chat with our bot, we store that chat's ID and send alert messages to it through Telegram. Webhooks (for example Discord, Slack, Microsoft Teams, ntfy or your own server): we store the address you enter and send the alert (gateway, tag, value, time) to it. Those services then handle the message under their own privacy policies. Remove a channel at any time on the Alerts page; push tokens are deleted when you sign out of the app.
  • Two-factor sign-in (optional): if you turn it on, we store your authenticator secret encrypted and your backup codes only as hashes.
  • Activity log: sign-ins, settings changes, team changes and remote-control commands are recorded with the account member who did them, the time, the IP address and the browser or app name. The owner and admins of the account can see it. Entries are deleted after one year, or with the account.
  • Remote control (optional, off by default): only if you allow it on the gateway phone. We store which tags may be written and their limits, and every command sent from the Cloud (who, when, the tag, the value, and the result reported by the phone). Command history is kept for one year, or until the account is deleted.
  • Website analytics: the Cloud website loads Google Analytics 4 only if you accept cookies in its banner (change your choice any time with "Cookie settings" at the bottom of the page). It then measures page views and device/browser type as described in section 4. It is never loaded on pages opened from an email link, and we do not send your email address, tag values or gateway data to Google Analytics.
  • Subscription: the Google Play purchase token and subscription status (product, expiry, renewal), checked with Google Play to switch Cloud on. We never receive your payment details.
  • Where and how: data is stored on our server in the EU (Scaleway, France), with backups every few days copied to our cloud storage (Microsoft OneDrive) and kept for about 10 days. It is sent only over encrypted HTTPS, and every account is kept separate in the database. Only you and the team members you invite can see your data; we do not sell it, share it with advertisers or use it for ads.
  • How long: history is kept for up to one year or until the account's storage quota is full (oldest days are removed first). If Cloud is not renewed, your data is kept for 90 days so you can renew or export it, then deleted. The account's activity log is kept for one year and deleted together with the account.
  • Deletion: you can delete any tag, time range, gateway or your whole account yourself in the app or on the website, or request deletion at androidscada.maxenergic.com/delete-account. Deleting the account removes all its data within 30 days (backups included). Cancel the Google Play subscription separately in Google Play.

Ads in the free version

The free version shows ads from Google AdMob. To show and measure ads, Google may process the device's advertising ID, IP address, device and app information and approximate location derived from the IP address. In the EEA, the UK and Switzerland (and where else the law requires it) the app asks for your consent with Google's consent form before any ad is requested; you can change your choice at any time in the app under More → Privacy choices → Ad privacy options. Without consent, only limited, non-personalised ads may be shown. Premium removes ads. See how Google uses information from apps that use its services.

Crash reports

If the app crashes, Firebase Crashlytics (Google) receives a crash report: the stack trace, device model, Android version, app version, whether you use the free or Premium version, the number of active connections, and a random installation ID. Reports never contain register values, addresses or device names. You can turn crash reports off under More → Privacy choices. Crash reports are kept for 90 days.

Usage statistics

With your consent where required, Google Analytics for Firebase receives anonymous usage events, such as which screens are opened, when a Premium feature is tapped, when a recording is started or an export is made, and the connection type (TCP, UDP, USB, Bluetooth). It uses a random app-instance ID. You can turn usage statistics off under More → Privacy choices. Analytics data is kept for 2 months.

Remote settings

The app downloads a few settings (for example how often an ad may be shown) from Firebase Remote Config, which uses a random Firebase installation ID.

Your choices and deletion

  • Uninstalling the app deletes everything it stored on your phone.
  • To ask for deletion of crash or analytics data linked to your installation, email us with the date you used the app; we will delete what Google's tools let us identify.
  • The app is not directed at children under 16.

13. Changes to this policy

We will post any changes on this page and update the date at the top.

14. Contact

For questions about this policy or data requests: support@maxenergic.com

ModbusBB logo ModbusBB
Home Features Learn DocsUser ManualCLI Reference Download Buy Support Max Energic Apps Free ToolsAboutAndroid app
Terms of Service Privacy Policy
MaxEnergic products:MaxSCADAMaxPPCZeroexportWeather StationIEC Gatewaymaxenergic.com

© 2026 Max Energic Apps. All rights reserved.

Product & Download

Download ModbusBB 2.3.0 (Windows 10/11)

Download the 64-bit Windows installer or portable ZIP with SHA-256 checksums. Free 30-day trial.

Pricing & Licensing

Buy Lifetime License ($10 One-Time)

$10 one-time payment for a lifetime license on up to 3 PCs with free updates and 14-day refund guarantee.

Pricing & Licensing

Self-Service License Portal

View your active computers, deactivate an old PC to move your license, or check your key status.

Support & Contact

Contact, Support & Sales Hub

Direct email channels for technical support, licensing/invoices, volume quotes, and SCADA engineering.

Android App

ModbusBB for Android (USB RS-485, Bluetooth, TCP)

Modbus master, traffic monitor, scanner, logger and slave simulator for Android phones and tablets.

Features & Specs

All Features in ModbusBB 2.1

Complete overview of transports, 11 data types, byte orders, Device Tools, simulator, trends and CLI.

Online Tools

Free In-Browser Modbus Tools

Instant browser tools: Modbus RTU CRC-16 calculator, 4xxxx address converter, and Float32 byte-order decoder.

CLI & Automation

Command-Line Tool (ModbusBB.CLI)

Scriptable CLI reference for automated testing, JSON/CSV logging, device scans and CI pipelines.

Documentation

Documentation & Quick Reference

Technical reference covering connections, workspaces (.mbws), data types, scaling, and troubleshooting.

Documentation

Complete User Manual (HTML & PDF)

Step-by-step illustrated manual with annotated screenshots and downloadable PDF.

Diagnostics

Device Tools (FC08, FC17, FC22, FC23, FC43/14)

Read Device Identification (FC43/14), Report Slave ID (FC17), Diagnostics (FC08), Mask Write (FC22) and raw requests.

Device Library

Device Register-Map Library (Eastron, Schneider, SunSpec, ABB, SMA)

Built-in register templates for popular energy meters, solar inverters, and variable-frequency drives.

Technical Guide

Register Addressing: 40001 vs Address 0

Understand 0-based, 1-based and Modicon 4xxxx notation and fix off-by-one register errors.

Technical Guide

Modbus Function Codes Explained (FC01–FC43)

Detailed breakdown of standard read/write function codes and diagnostic function codes.

Technical Guide

Float32, 64-Bit & Byte Order (ABCD / CDAB / BADC / DCBA)

How to decode 32-bit and 64-bit integers and floats across Big-Endian, Little-Endian and word-swapped devices.

Technical Guide

RS-485 Wiring, Termination & Polarity Guide

Field guide to RS-485 2-wire daisy chains, A/B polarity swaps, 120 Ω termination and ground reference.

Technical Guide

Fix Modbus Timeouts (TCP & RTU Troubleshooting)

Step-by-step commissioning checklist for diagnosing TCP and serial RTU timeouts using raw hex frames.

Technical Guide

Modbus Exception & Error Codes (01 to 0B)

What exception responses 01, 02, 03, 04, 05, 06, 0A and 0B mean in hex frames and how to resolve them.

Technical Guide

Modbus TCP vs RTU vs RTU-over-TCP vs UDP

Compare Modbus frame structures, serial vs Ethernet transports, and when to use RTU-over-TCP.

Technical Guide

Modbus Slave Simulator Guide

How to simulate multi-unit Modbus slaves with value generators and exception injection for FAT/SAT.

Comparison

ModbusBB vs Modbus Poll Comparison

Side-by-side comparison of ModbusBB 2.1 and Modbus Poll for Windows commissioning engineers.

Studio & Engineer

About Max Energic & Mohammad Ba’ra

Meet the SCADA/SAS electrical engineer behind ModbusBB and explore other Max Energic tools.

Need Help or Licensing Support?

Contact & Inquiry Composer →Send a formatted message or copy email support@maxenergic.comTechnical support & bug reports licensing@maxenergic.comKeys, invoices & 14-day refund guarantee sales@maxenergic.comSite licenses & SCADA engineering Self-Service License PortalManage your 3 PC activations