A legal disclaimer
Privacy Policy - the basics
Having said that, a privacy policy is a statement that discloses some or all of the ways a website collects, uses, discloses, processes, and manages the data of its visitors and customers. It usually also includes a statement regarding the website’s commitment to protecting its visitors’ or customers’ privacy, and an explanation about the different mechanisms the website is implementing in order to protect privacy.
Different jurisdictions have different legal obligations of what must be included in a Privacy Policy. You are responsible to make sure you are following the relevant legislation to your activities and location.
What to include in the Privacy Policy
Generally speaking, a Privacy Policy often addresses these types of issues: the types of information the website is collecting and the manner in which it collects the data; an explanation about why is the website collecting these types of information; what are the website’s practices on sharing the information with third parties; ways in which your visitors and customers can exercise their rights according to the relevant privacy legislation; the specific practices regarding minors’ data collection; and much, much more.
To learn more about this, check out our article “Creating a Privacy Policy”.
Privacy Policy for VEGA - AllHub
Effective date: 2026-07-11
Last updated: 2026-07-11
This Privacy Policy explains how VEGA Smart Solutions / IOT TRADE (developer contact: Viktor Astafiev) handles data when you use VEGA - AllHub (net.vegasmartsolutions.allhub), a mobile app that connects to a compatible Bluetooth thermostat and related hardware.
1. What the app does
VEGA - AllHub is designed primarily as a local companion app for compatible Bluetooth thermostat hardware. The core app flow includes:
-
scanning for nearby compatible Bluetooth devices;
-
connecting to a thermostat over Bluetooth Low Energy (BLE);
-
reading device state such as setpoint, current temperature, mode, and schedule state;
-
updating thermostat settings and schedules;
-
storing schedules, chart data, and app preferences locally on the phone;
-
exporting locally stored logs or chart snapshots only when the user explicitly chooses to share them.
2. Data we process
Based on the current Android product intent, the app may process the following categories of data locally on the device:
-
Bluetooth device identifiers and device names for compatible thermostats;
-
thermostat settings and schedule data;
-
locally stored historical chart data received from the thermostat;
-
app preferences such as selected language, selected device, and interface settings;
-
optional BLE debug logs and exported chart snapshots created by the user.
The app is not designed to require a user account for the current BLE companion flow.
3. Permissions used by the app
The app may request or declare Android permissions related to:
-
Bluetooth scanning and Bluetooth connection;
-
notifications, where required by Android background or foreground behavior;
-
local storage or local file export for user-initiated log sharing;
-
Android system services that may be required for nearby device discovery on some Android versions.
Important note about location on Android:
-
On some Android versions, Bluetooth discovery may depend on Android location-related permission or system settings.
-
These permissions/settings support nearby Bluetooth device discovery, not GPS tracking for maps, advertising, or profiling.
4. How we use the data
We use the data described above only to:
-
discover and connect to compatible thermostat hardware;
-
display current device status and historical data;
-
store user preferences and schedules locally;
-
let the user export local logs or chart snapshots if the user chooses to do so;
-
maintain and troubleshoot the app.
5. Data sharing
-
We do not integrate advertising SDKs for this product intent.
-
We do not require analytics SDKs for the core BLE flow described here.
-
We do not sell user data.
-
We do not share user data with data brokers.
User-initiated sharing:
-
If the user chooses to export or share a BLE log or graph snapshot, the app uses the operating system share sheet to send the selected file to the destination chosen by the user.