Farlatch

Privacy Policy

How the current Farlatch release uses and stores information.

Effective date: 13 October 2026

Publisher and contact

Farlatch is published by CGRENEWABLES LLC, doing business as Kentrix Technologies. Contact jerry@tradesmatepro.com for privacy questions. This policy covers the standalone Farlatch app and its communication with compatible site boards. The separate camera/weather kiosk and unrelated Kentrix apps have their own behavior and policies.

Information used by the app and site boards

  • Device enrollment and access: a name chosen for the device, site and device identifiers, invitation data, access credentials, approval/revocation state and administrator/operator roles. The app stores its device credential in platform-protected storage. An administrator PIN verifier and preferences may also be saved locally; the PIN is not a shared gate credential.
  • Nearby board information: Bluetooth identifiers and advertised names, board role, firmware version, readiness, radio-link status and cooldown. These support discovery, authentication and troubleshooting.
  • Site activity: boards maintain limited records of access commands and administrative changes, including device/actor names and identifiers, event type, affected device, board identity, sequence and uptime. Where the app estimates an event time, it may use the phone’s clock. These are not guaranteed records of physical gate position or commands issued through unrelated keypads/remotes.
  • Local files: you can select a signed firmware file or enrollment information for the app to process. The selected firmware is transferred to the chosen board over Bluetooth.

Camera, Bluetooth and location permissions

The camera is used to recognize invitation QR codes. Scanning is processed on the device; Farlatch does not intentionally save or upload camera images. Bluetooth is used to communicate with nearby controller boards. Some older Android versions require location permission for Bluetooth discovery; the current app does not use this permission to obtain GPS coordinates or track your location. You can deny or withdraw permissions in system settings, although related features may not work. Invitation text can be entered instead of using the camera.

Where information goes

Credentials and app preferences are stored on your phone/tablet. Enrollment requests, names, permissions and commands are sent to the site’s boards over local Bluetooth, and relevant permissions/commands may be transmitted between those boards over LoRa. Authorized site administrators can view the records exposed by their site’s management functions. Downloading Farlatch does not give us remote access to your gate or the boards’ records.

The current standalone app has no Kentrix cloud login, advertising SDK or developer-operated analytics/upload service. We do not receive local site records unless you choose to provide them to us for support. Third-party libraries provide Bluetooth, secure storage, cryptography and on-device QR recognition; the current scanner uses a bundled recognition model.

Optional support, websites and app stores

If you email support, we receive the information you send and use it to respond and troubleshoot. Email providers process those messages. If you open a download link or visit our website, the browser, hosting provider and relevant app store may process network/request information such as IP addresses and browser details under their own policies. Apple and Google may process installation, purchase or diagnostic information through their platforms. These activities are distinct from the app’s offline board communication.

Use and sharing

Information is used to authenticate devices, enforce site permissions, operate requested commands, maintain configuration and help administrators troubleshoot. We do not sell local gate records or use them for targeted advertising. Information voluntarily provided to support may be handled by our email/service providers and disclosed when legally required. A workplace/site owner may have additional policies for its access records; contact that owner about their use of those records.

Retention, revocation and deletion

Local enrollment/settings remain until removed or reset through supported device/app controls. Platform-protected storage may persist differently from ordinary app files, so uninstalling alone is not a reliable way to revoke access or erase a credential. Ask the site administrator to revoke a lost or retired device.

Board authorization records persist through power cycles. Removing a person from the visible list may retain a disabled internal record until its storage slot is reused; limited audit history may remain. Revocation must reach each relevant board, and an offline board may not yet have received it. The app’s local activity list and board audit history are bounded rather than a complete permanent history. Contact the site administrator for board-data removal/reset options; do not reset operational hardware without a safe recovery plan.

There is no Kentrix-hosted Farlatch account to delete in this release. You may request deletion of support information we hold by contacting us; we may retain records needed for legal obligations or unresolved support matters. Never include secret credentials in the request.

Security and changes

Access requests use authenticated protocols and platform storage protections. These protections do not guarantee security against a compromised phone, physical board/wiring access or every operational failure. Keep devices updated and protect administrator access. If Farlatch introduces cloud services, accounts or different data practices, this policy and the store disclosures will be updated to describe them.

Farlatch & support · Privacy · Terms