Codeks Smart House – Privacy Policy

Effective Date: 19 December 2025

Introduction

This Privacy Policy explains what data is collected and stored within the App, as well as on related devices and cloud services, and clarifies that we do not have access to data stored on your devices or your Jantar Smart House Hub (“Hub”).

Short overview

Codeks Smart House system can operate in two modes: “WiFi mode” or “Cloud mode”.
When configured as “WiFi mode” it operates strictly localy and doesn’t interact with any Jantar services and no data is stored on Jantar servers.

When configured as “Cloud mode” it uses Jantar MQTT broker service to exchange messages between Smart House App and Codeks Smart House Hub to control “Hardware”.
Minimal authentication info (identification, password and email) used for connecting to our MQTT broker service is stored on MQTT broker itself.
Jantar d.o.o. has no access to data on Smart House App or Codeks Smart House Hub.

1. General terms

Jantar d.o.o. (“we,” “us,” or “our”) is committed to clearly informing you about our data practices related to your use of our Smart House app (“App”) and associated hardware devices (“Hardware”).

Codeks Smart House App (or short App) = Codeks Smart House App program installed on Android or iOS device

Device = phone, tablet or any other device which can be used to install Smart House App.

Hardware = Jantar hardware devices which are used to control home devices. They are called Codeks Smart House Master and Codeks Smart House Slave devices.

Smart House System (or short System) = A system with all the data needed to operate a Smart House. The user can switch between multiple Systems on the Device, but only one can be active at a time.

Codeks Smart House Hub (or short Hub) = application installed on a PC in local network, it stores a System’s configuraton and takes care of communication between users Devices and System in “Cloud mode”

User = A person which uses Codeks Smart House App on their own Device.

Owner = User with permisson to change configuration of their Smart House System.

WiFi mode = Local only configuration. Device communicates directly with Hardware over local network. Only one Device can communicate at a time.

Cloud mode = Configuration where multiple Devices can communicate with System at a time and communication is not limited to local network.
Every Device, that should work in Cloud mode, must register into Jantar MQTT broker service.

Jantar MQTT broker service = MQTT broker server operated by Jantar d.o.o. used for message exchange between “App” and “Hub” in Cloud mode.

2. Information Collected by the App

a. Location Data

  • Geofencing Functionality: The App uses background location services to support geofencing features. The app saves only the current system/building location—specifically, one location per system—to determine when you are within a set distance (x meters) of the system location. That’s why the App uses the background location service to monitor your Device location and your system location (Geofencing).
  • Storage Locations: This location data is stored either in the App database on your Device or is synced between your Device and your Hub (Cloud), depending on your setup.

Important: All location data originates from you, and we do not have access to the data stored on your Device, Hub or Hardware.

b. Camera Usage

  • QR Code Scanning: The App uses your Device camera exclusively to scan QR codes for setup and configuration purposes. No images captured during this process are permanently stored or transmitted beyond the immediate scanning function. Data read from QR code is transformed into a user data entity which is then stored on Device App data or Hub (Cloud), depending on your setup.

Important: All QR/user data entity originate from you, and we do not have direct access to the data stored on your Device or Hub.

c. Pictures/Gallery Access

  • Customizing Layout: You can select images from your Device gallery to customize your Smart House layout. By default, these images remain solely on your Device. If you are connected to a Hub (Cloud), these images are uploaded to your Hub.

Important: All image data originates from you, and we do not have direct access to the data stored on your Device, Hub or Hardware.

d. Notification Services

  • Push Notifications: The App uses push notifications to alert you about important events, such as alarms or fires. During the signup or status checking for push notifications, the App accesses your notification token. This information is transmitted directly to Azure Notification Hub solely for managing notification routing. Your notification token is retrived from the App and is not stored anywhere.

Important: When using the Azure Notification Test Send functionality, we see a registration ID for each test push notification sent to the Device; however, we can not match this registration ID to your specific Device as we do not have your unique Device ID.

e. Background Operations for Geofencing

  • System-Level Permissions: To ensure continuous geofencing functionality, the App requests permissions such as RECEIVE_BOOT_COMPLETED and BATTERY_STATS. These permissions ensure that geofencing services continue to operate after Device reboots and help monitor battery status for efficient operation. They do not result in additional personal data collection.

f. Connectivity Data

  • Internet and WiFi Connectivity: The App uses mobile internet and/or WiFi connections solely to establish and maintain communication links between your Device, our MQTT server, and your Hub.
  • Wi-Fi: Data related to Wi-Fi setup is stored in the App database. We do not have direct access to the data stored on your Device.
  • Hub: This refers to the Hub that you receive; we do not have direct access to the data stored on your Device. The App creates your mqtt client unique identifier. This information is used for secure communication over MQTT protocol between user Hub and App.
  • Azure Hub: Azure Notification Hub is used only for push notifications. Notification token is read directly from your Device and sent to Azure for notifications routing purposes with no data storage on our end.

g. Badges

  • Badges: Are used to show if you have new notifications when the app was inactive on your Device. We do not store any badge information. When the notification is received in the background, the badge count is set to 1.

h. IP Camera Images

  • Images: Are used to show current camera image. They are not stored anywhere, unless you manually click “Save Image” to store it to your Device.

3. How the Information Is Used

  • Enabling App Functionalities: The information collected—such as background location, Device identifiers, and selected images—is used exclusively to power core functionalities of the App, including geofencing, secure hardware connectivity, and timely push notifications during critical events.
  • MQTT Secure Communication: Communication between your Device and your Hub is facilitated by our MQTT service. This connection is secured by an authentication data by an external registration service hosted on Jantar.
  • Hardware Secure Communication: Communication between your Device and hardware, or between your Hub and hardware, is secured by a proprietary Jantar communication protocol.

Our Data Usage: Aside from storing the authentication info such as username, name, last name, email, and Device name which are required for registering with our MQTT server when using the Cloud functionality, we do not use any other personal data.

4. Data Storage and Security

  • Your App Storage: Certain data—such as the current system and your authentication info— is stored in the App (on your Device) in a plain text database to support immediate functionalities.
  • Your Hub (Cloud) Storage: For customers opting in for the Hub (Cloud) service, all data (including location information and uploaded images) is stored exclusively on your Hub in a plain text database to support immediate functionalities.
  • Registration service hosted on Jantar Storage: The only information stored on our cloud systems is the authentication info (required for registration with our MQTT server). The data is stored in SQL database and is stored until:
    • user delete the Jantar identity or
    • account deletion is requested or
    • 12-months of account inactivity.
  • Your Hardware Storage: Certain data—is stored in the Hardware in a plain text database to support immediate functionalities for Hardware devices to control Smart Home devices based on I/O and user configuration of the current system. The data from Hub or App (both are your devices) is sent by user command to transform current system database to Hardware compatible data.

Important: We do not have direct access to data on your Device, Hub or Hardware. We can not access the MQTT server without your authentication info, so we are not able to listen to your Device and Hub communication.

Important: We do not have direct access to data on your Hardware. We can not access the Hardware data without your WiFi info or Hub authentication info, so we are not able to listen to your Hardware data communication without direct connection to your Hardware.

5. Data Sharing and Disclosure

  • Third-Party Sharing: We do not sell, share, or otherwise distribute your personal data with third parties for commercial purposes. Data exchange occurs only when required by law or as necessary to deliver a service you have allowed (Azure Hub – push notification token).
  • Legal Obligations: In cases where disclosure is mandated by applicable law or a valid legal process, only the minimum necessary information will be shared.

6. Your Rights and Control

  • User Data Management: All data collected by the App remains under your control. You can delete the App and all its associated data from your Device at any time. Similarly, you are responsible for managing and deleting any data on your Hub.
    • The only data maintained on our end is the authentication info stored in our Smart MQTT registration helper service.
    • If you wish to have this authentication information deleted from our system, please delete Jantar Cloud accounts from the App or use web page https://mqtt.jantar.si/UserAccountDeletion.html or contact us using the details provided below.

7. Changes to This Privacy Policy

We may update this Privacy Policy from time to time to reflect changes in our practices or legal requirements. The most current version will always be available within the App and on our official website (both options require internet access).

8. Contact Us

If you have any questions, concerns, or requests regarding this Privacy Policy or our data practices—including requests to delete the authentication info from our Smart MQTT registration helper service—please contact us at https://jantar.si/en/contact/.

Conclusion

This Privacy Policy outlines our practices regarding the data generated by our Smart House App and clarifies that your data remains under your control. By using our App, you acknowledge and agree to the data practices described herein.