Privacy · Mobile app

Privacy Policy for TRLLN Link

Last updated: November 10, 2026

Introduction

TRLLN Link (“we”, “our”, or “us”), formerly known as TRLLN QRs in some store listings, is a mobile field application for scanning asset identifiers, validating nearby nodes, and synchronising operational scan data with TRLLN services. This Privacy Policy explains how the app handles information when you use it.

Who we are

The controller of the personal data described in this policy is TRLLN S.L., Plaça de Pau Vila, 1, Ciutat Vella, 08039 Barcelona, Spain. Contact: customer-support@trlln.io.

You use TRLLN Link through your organisation’s TRLLN account. Your organisation decides who uses the app and which workflows are enabled; for that operational data we act on your organisation’s behalf under our agreement with it. How TRLLN handles your platform account is described in our main Privacy Policy.

Information we collect

Camera scans

  • Purpose: we request camera access to scan QR codes, Data Matrix codes, and other supported barcode formats used for asset and node identification.
  • What: captured scan identifiers may include node MAC addresses, crate or asset external identifiers, RFID/EPC identifiers when supported by the build, capture timestamps, scan format, capture method, target type, sync status, and retry state.
  • Transmission: captured scan data may be sent to TRLLN services when you submit scans manually, when kiosk mode auto-submits scans, when connectivity is restored, or during periodic retry processing.

Additional details and form data

  • What: when a tenant form is displayed, information you enter or lock for the session, such as field number, crew number, commodity, grower, or other tenant-specific operational fields, may be attached to scan submissions and telemetry where configured as safe for reporting.
  • Purpose: this information helps associate scans with the correct field operation, crew, tenant, and shipment context.

Bluetooth and nearby device context

  • Purpose: we request Bluetooth access to discover nearby Bluetooth Low Energy (BLE) nodes and validate scan context during field operation.
  • What: BLE observations may include device identifiers such as hardware MAC addresses or iOS device UUIDs, signal strength, timestamps, and related node telemetry.
  • Transmission: BLE telemetry matching configured criteria may be transmitted to https://api.trlln.io/* as part of operational telemetry snapshots.

Location

  • What: when permission is granted and a location fix is available, the app may collect GPS coordinates during active app use, scanning sessions, or kiosk operation.
  • Purpose: location helps associate scan and telemetry events with the field location where the work occurred.
  • Transmission: GPS coordinates may be included in telemetry payloads sent to https://api.trlln.io/*, formatted as latitude and longitude.
  • Platform note: on Android, location permission may also be required by the operating system for Bluetooth scanning.

Device identifier

  • What: the app generates a stable device identifier (device_id) and includes it in authenticated requests and telemetry payloads.
  • Format: the identifier is derived from platform hardware information, hashed, truncated, and prefixed by platform, such as a_XXXXXXXXXXXX or i_XXXXXXXXXXXX.
  • Storage: the identifier is stored in secure storage on your device so it remains stable across app sessions.
  • Purpose: it supports device attribution, operational troubleshooting, sync reliability, and telemetry correlation. Because it is linked to your signed-in account and sent with location data, it is treated as personal data.

Authentication and tenant access

  • The app authenticates users through Auth0, a third-party authentication provider.
  • User credentials are handled by Auth0’s hosted login page. The app does not process your password directly.
  • Auth0 issues access tokens that are stored in secure storage on your device and used for authenticated API requests.
  • The app calls TRLLN backend services to resolve your authorised tenants, accounts, and roles before allowing access to tenant-specific workflows.
  • For details on how Auth0 handles your data, see Auth0’s privacy policy: https://auth0.com/privacy.

Operational telemetry

  • The app sends operational telemetry to help monitor scanner reliability, sync health, hardware state, permissions, connectivity, scan counters, and drain summaries.
  • Telemetry may include snapshot events, capture-event lifecycle records, and incident logs for failures such as permission, connectivity, scanner, or sync errors.
  • Telemetry may include device and app metadata such as device ID, app version, platform, manufacturer, model, tenant ID, operation mode, GPS when available, and selected tenant form metadata.
  • The app does not include advertising SDKs.

How data is submitted

  • Manual submission: in handheld workflows, scan data and additional details may be submitted when you choose to register or submit scans.
  • Kiosk operation: in kiosk mode, scans may be submitted automatically after capture or when the camera session closes.
  • Connectivity recovery: pending scan and telemetry data may be submitted automatically when network connectivity is restored.
  • Periodic retry: pending data may be retried automatically to ensure field data is not lost during temporary connectivity issues.

Local storage and offline operation

  • Scan data, capture-event records, BLE observations, telemetry payloads, sync status, and retry state may be stored locally in a database on your device.
  • When connectivity is unavailable, pending data is queued locally and transmitted automatically when connectivity resumes.
  • The app uses retry and retention rules to avoid losing operational data during temporary network failures.
  • Authentication tokens, device identifiers, and kiosk/session preferences are stored in secure storage where applicable.

Legal basis

  • Sign-in, scans, additional details, BLE observations and the device identifier: our legitimate interest, and your organisation’s, in operating the asset-tracking service it has contracted and keeping it reliable (Art. 6(1)(f) GDPR).
  • Location during active use: the same legitimate interest, to associate scans with the place where the work happened. The app does not collect location in the background.
  • Operational telemetry: our legitimate interest in monitoring scanner reliability and fixing errors.

How long we keep it

  • On your device: pending data until it is submitted, until you clear it in the app, or until you uninstall the app.
  • Raw telemetry received by our ingestion service: deleted after 7 days.
  • Scan records and asset associations: part of your organisation’s asset data, kept while its TRLLN account is active; processed observations are kept as operational telemetry for up to about 9 months.

Who we share it with

  • https://app.trlln.io/api/* — TRLLN platform API for access resolution, tenant/account data and scan / additional-detail submission.
  • https://api.trlln.io/* — TRLLN telemetry and operational scanner data endpoint.
  • Google Cloud — hosting of TRLLN services and data (EU, Frankfurt). Telemetry from the app may pass through an ingestion point in the USA on its way to the EU, where it is stored.
  • Okta (Auth0) — sign-in (EU). See Auth0’s privacy policy.

The app does not include advertising SDKs. We do not sell personal data.

Transfers outside the EU

Where data passes through Google infrastructure outside the European Economic Area, the transfer is protected by the EU–US Data Privacy Framework and the European Commission’s Standard Contractual Clauses.

Your rights

You can ask us to give you a copy of your personal data, correct it, delete it, limit how we use it or object to processing based on legitimate interest. E-mail customer-support@trlln.io from the address linked to your account; we answer within one month and may involve your organisation’s administrator.

  • You can delete locally stored scan data with the clear function in the app, where provided.
  • You can uninstall the app to remove all locally stored app data from your device.

You also have the right to lodge a complaint with a data-protection authority, in particular the Spanish Agencia Española de Protección de Datos (aepd.es) or the authority of the EU country where you live or work.

Changes to this policy

We update this policy when what the app does with personal data changes, and change the “Last updated” date at the top.

Contact us

Questions about this policy or your data: customer-support@trlln.io.