Privacy Policy

JJT Automation Privacy Policy

1. Data Controller and Scope

This Privacy Policy explains how JJT Automation, part of CV. Jaka Jaya Teknik (“JJT”, “we”, “us”, or “our”), handles information when you use the JJT Automation-branded mobile application (“App”) and its related features.

The App is a white-label application based on the ThingsBoard platform and is used to access customers’ IoT environments, including through https://iot.jjtautomation.com. The App may support device monitoring, dashboards, notifications, device configuration, reporting, and features enabled in a customer environment.

The App is intended for business use by authorized users. The release version described in this policy is intended not to provide open self-registration. Accounts should be created or authorized by an administrator. If Google sign-in is enabled, production configuration should restrict access to authorized accounts.

This policy applies to the JJT Automation-branded App. Processing on the company website, cloud services, or other products may be covered by additional notices where necessary.

2. Roles of JJT Automation, Customers, and Service Providers

JJT manages the JJT Automation-branded App, user support, access security, and the processing needed to provide the service. For account, support, and security data whose purposes and means are determined by JJT, JJT acts in accordance with applicable data protection requirements.

Business customers and tenant administrators select devices, entities, dashboards, widgets, telemetry data, location settings, and users who receive access. For employee data, location data, photos, or other information entered into a customer environment, the customer may determine the purposes and means of processing. Each party’s responsibilities depend on the context, purposes, and applicable service agreements.

ThingsBoard provides the cloud platform and technical processing under the applicable service configuration and agreements. Google/Firebase provides certain functions, including push notifications and other Google services used by the App. Each provider’s legal role depends on the service used and the relevant agreements.

3. Types of Information Processed

A. Account and authentication information

Account information may include name, email address, phone number if provided in the profile, username, roles and access permissions, authentication information, session tokens, and information needed to verify an account. If Google sign-in is enabled for authorized accounts, Google may process information required for authentication according to the sign-in configuration.

B. Device and application technical data

The App and its SDKs may process the App version, platform, device model, operating system version, User-Agent, app identifier, push notification token, and installation identifiers used by Firebase services. These technical data help route notifications to the correct device, maintain connections, support authentication, and operate the service.

According to the release configuration confirmed by the ThingsBoard team, Firebase Analytics, Crashlytics, Performance Monitoring, and other analytics or crash-reporting SDKs are not used. Firebase Cloud Messaging (FCM) still processes technical data required to provide push notifications. The App may also request Google Fonts when an online font is required by a dashboard; such network requests may disclose standard connection metadata to the service provider.

C. IoT telemetry and operational data

Operational data may include sensor readings, device status, energy, current, voltage, flow, pressure, temperature, alarms, events, timestamps, entity attributes, device configuration, and other data defined by a device, dashboard, widget, or customer. The data may vary by use case and tenant configuration.

D. Precise location and live tracking sessions

If a user actively starts the live location tracking feature from a dashboard action and grants the requested location permission, the App may send latitude and longitude coordinates to a selected entity in ThingsBoard. Depending on the action configuration, data may also include accuracy, altitude, speed, and heading. The App also writes a tracking-active indicator and the email address of the user who started the session to that entity.

Tracking may continue while the App is minimized or the screen is locked while the session remains active. On Android, a foreground service and persistent notification are displayed while tracking is active; on iOS, the system location indicator may appear. Tracking stops when the user taps Stop, a dashboard stop action runs, the configured maximum duration is reached, the user logs out, or the App is dismissed from recent apps or stopped by the system. Tracking does not automatically restart when the App is reopened.

The App stores a summary of the most recent session locally on the device (start and end times, number of points, and last coordinates) to display the tracking screen. This local summary is deleted when the user logs out. Location data already sent to a server entity remains subject to that entity’s retention settings and access permissions; deleting the local summary does not delete server-side location data.

E. QR codes, photos, and dashboard content

QR scanning uses Google ML Kit on the device. In the scanning flow confirmed for this release, the App uses the decoded text and does not store camera frames or send those frames to the server through the QR-scanning function.

If a user takes or selects a photo through a dashboard widget action, the App passes the image to the relevant widget/action. The App does not independently send the photo to a server without that widget action and configuration. Depending on dashboard configuration, a photo may be stored as an attribute or telemetry on a ThingsBoard entity, or uploaded to the tenant Image Gallery. Photos stored there follow the access rules for the relevant entity or gallery: tenant administrators and customer users granted access may view them. The App may retain a temporary copy in its private cache; that copy may be removed when the cache is cleared or the App is uninstalled.

F. Audio and video in custom widgets

The core App code confirmed by the ThingsBoard team does not independently record or transmit audio or video. Dashboards run in an embedded browser view, and custom widgets created or configured by a customer may use standard camera or microphone APIs if enabled. The purpose, transmission, access, and retention of data processed by such custom widgets depend on the widget implementation and customer configuration. Administrators should review the data processed and ensure appropriate notices and permissions are in place before enabling such widgets.

G. Device provisioning

When Bluetooth or Wi-Fi provisioning features are used, the App and related provisioning libraries communicate with a local IoT device to configure it. According to the ThingsBoard team, the Espressif library in the reviewed build communicates with the local device being configured. Additional flows created by a customer or widget should be reviewed separately.

H. Push notifications

FCM delivers notifications from ThingsBoard to the device. The payload may contain the title and body rendered from a notification template, the action taken when tapped, notification type, related entity ID, and alarm fields included in the template. Accordingly, information included in a notification template may be transmitted through Google/Firebase. Historical telemetry is not sent as a telemetry stream through FCM, but values or alarm details may appear in the payload if included in the template.

If a device is unavailable, FCM may temporarily store a message for delivery. Because no custom time-to-live (TTL) was set in the reviewed configuration, the default maximum period may be up to four weeks. Notifications may also be stored separately in the ThingsBoard notification center, depending on tenant configuration.

4. Purposes and Legal Bases for Processing

Information is processed to: (a) verify identity and manage authorized accounts; (b) display telemetry, dashboards, alarms, and reports; (c) deliver notifications; (d) operate location features only after the user starts them and grants the relevant permission; (e) receive QR codes or photos through features selected by the user; (f) provision local devices; and (g) maintain security, prevent unauthorized access, troubleshoot technical issues, perform service agreements, and comply with legal obligations.

The legal basis depends on the context and the role of each party and may include performance of a service agreement, valid consent for optional features, compliance with legal obligations, or another basis permitted by law. For location, camera, photos, microphone, or other sensitive features, operating-system permission does not replace the need for clear notice and any consent or other legal basis required by law.

5. Data Recipients and Sharing with Third Parties

Data may be processed or accessed by the following parties where necessary to provide the service:

  • JJT Automation/CV. Jaka Jaya Teknik, for management of the App, accounts, security, support, and service administration within its responsibility.
  • Customers and tenant administrators, including users granted access to the relevant entity, dashboard, attributes, telemetry, photos, or gallery.
  • ThingsBoard, Inc., through ThingsBoard Cloud, to operate the IoT platform and store tenant data according to the applicable configuration and service agreements.
  • Google LLC/Firebase, for FCM, technical metadata required to operate FCM, and other Google functions used, such as Google sign-in or Google Fonts when enabled.
  • Other providers or parties where necessary to comply with law, protect service security, respond to claims, or follow lawful instructions from an authorized customer.

We do not sell personal data for advertising. According to the release configuration confirmed by the ThingsBoard team, Firebase Analytics and Crashlytics are not used. Depending on the service, region, and provider terms, data may be processed on infrastructure outside Indonesia. Where an international transfer applies, the responsible party must ensure that safeguards required by applicable law and relevant agreements are in place.

Further information about provider processing is available in Google’s Privacy Policy (https://policies.google.com/privacy), Firebase data disclosure documentation (https://firebase.google.com/docs/android/play-data-disclosure), and the ThingsBoard Cloud Data Processing Agreement (https://thingsboard.io/products/paas/dpa/).

6. Storage, Retention, and Deletion

Retention depends on the purpose of processing, tenant configuration, data type, and applicable legal obligations. The currently confirmed rules include:

  • Entity telemetry follows the time-to-live (TTL) or retention period configured in the ThingsBoard tenant profile.
  • Entity attributes and images in the Image Gallery remain stored until an authorized administrator deletes them or deletes the related entity/gallery, subject to platform functionality.
  • FCM may temporarily store undelivered push messages until they expire. In the confirmed configuration, the default may be up to four weeks when no TTL is specified.
  • The live tracking session summary stored locally on the device is deleted when the user logs out. Location data already written to a server entity are not automatically deleted with the local summary.

User accounts are managed by authorized administrators. Deleting a user through the ThingsBoard administrator interface removes the user’s settings and associated push token according to the confirmed mechanism. However, deleting an account does not automatically delete all telemetry, entity attributes, location data, photos, or operational records stored separately in a customer entity. Where appropriate and lawful, the customer administrator must review and delete those records separately.

To request access, correction, restriction, or deletion of personal data, contact hello@jjtautomation.com and/or the customer administrator managing the tenant. Requests will be verified and handled according to authority, service agreements, technical configuration, and applicable law. If certain data must be retained for legal obligations or other legitimate reasons, we will explain the scope and reason for retention to the extent required.

7. Data Security

According to technical confirmation from the ThingsBoard team, communication between the App and the server uses HTTPS and secure WebSocket with TLS, and certificates are validated using the operating system’s standard trust store. Access to entities and dashboards is controlled through authentication and tenant permission settings. Users should keep their credentials secure and not share them.

We and our service providers apply technical and organizational controls appropriate to our respective roles and services. No electronic transmission or storage can be guaranteed to be completely risk-free. If a personal data breach occurs, it will be handled and notified in accordance with applicable legal requirements.

8. User Rights and Privacy Requests

Subject to applicable law and the role of the party controlling the data, users may request information about data processing, access to or a copy of their data, correction, withdrawal of consent where processing is based on consent, restriction or cessation of processing, and deletion where legal requirements are met.

Users may send requests to hello@jjtautomation.com For data managed by a customer within its tenant, JJT may forward or coordinate the request with the authorized customer administrator. Deleting an account does not necessarily delete telemetry records or assets belonging to the customer organization; those data will be reviewed in light of access rights, purposes, legal obligations, and applicable agreements.

9. Changes to This Policy

We may update this Privacy Policy when there are changes to features, use cases, device permissions, SDKs, service providers, processing purposes, retention, or legal requirements. The latest version will be published on the official privacy policy page. Where a change requires additional notice or consent, that step will be completed before the new processing begins, as required by law.

10. Contact

App operator: JJT Automation, part of CV. Jaka Jaya Teknik

Privacy and support email: hello@jjtautomation.com

Website: https://www.jjtautomation.com

IoT platform: https://iot.jjtautomation.com

Available features may differ depending on the customer tenant and dashboard configuration. This policy will be updated if data-processing practices materially change.