TriggerIt

Privacy Policy · Informativa sulla Privacy

Last updated: July 2026

At a glance

  • Your device list and encryption keys live only on your phone, inside its secure hardware storage.
  • No ads, no analytics, no trackers — none are built into the App.
  • Bluetooth, camera, and NFC access are used only for the feature they're named after.
  • The one exception is the optional Web Portal — see Section 8 for exactly what it sends and where.
  • Uninstalling the App deletes everything it stored.

1 Introduction

TriggerIt ("the App") is a Bluetooth Low Energy (BLE) application that lets you control access devices — garage doors, gates, entry points — from your phone, Android Auto, Apple CarPlay, or an NFC tag. This policy explains what data the App handles, and, for the one feature that talks to a server, exactly what leaves your device.

Developer: Daniele F.
Contact: dfacchin@gmail.com

2 Data stored on your device

The App stores the following locally, inside your phone's secure hardware-backed storage (Android Keystore / iOS Keychain):

  • Device configuration: names, Bluetooth MAC addresses, and the cryptographic keys used to authenticate with your access devices
  • Usage counters: how many times you've triggered each device
  • Icon preferences for each device
  • Optionally, names and phone numbers you choose to attach to people you've shared access with (e.g. adding a "friend" or "user") — this is information you enter yourself for your own key management, not something the App collects about you

3 What we don't do

  • No analytics, advertising, or tracking SDKs of any kind
  • No account or sign-in — we have no way of knowing who you are
  • No collection of your location (see Permissions below for why the App still requests location-related access on some OS versions)
  • Outside of the optional Web Portal (Section 8), nothing the App stores ever leaves your device

4 Permissions used

  • Bluetooth: to discover and communicate with your access devices, and briefly to pair a smartwatch companion. Never used to identify or track other Bluetooth devices around you.
  • Location (older Android/iOS only): the OS ties Bluetooth scanning to this permission on older versions. The App never reads your GPS coordinates — this exists only because Bluetooth scanning requires it at the system level.
  • Camera: to scan QR codes when adding a device or importing a key. No photo is stored or transmitted.
  • Photo library: only to let you pick an existing QR code image instead of scanning live.
  • Biometric authentication: to gate sensitive actions behind your device's own Face ID / Touch ID / fingerprint check. Handled entirely by the OS — the App never sees or stores your biometric data.
  • NFC: to read and write tags for the "tap to trigger" feature. A tag stores only a device's MAC address — see Section 9.

5 Storage and security

  • All device keys and configuration are stored using your device's hardware-backed secure storage
  • All cryptographic signing happens locally on your phone — your private keys are never exported in plain form except when you explicitly create a backup (Section 10)
  • Outside of the optional Web Portal (Section 8), nothing described in this policy is sent to any server we operate or any third party

6 Android Auto & Apple CarPlay

The App supports Android Auto and Apple CarPlay so you can trigger devices hands-free while driving. No additional data is collected for this — the same locally-stored device list is simply shown on your car's screen.

7 NFC tags

You can write a compatible NFC tag (e.g. an NTAG213/215/216 sticker or card) with a device's Bluetooth MAC address, so tapping the tag triggers that device. The tag stores only the MAC address — never a key or any personal data — and works the same regardless of which phone wrote it.

On iPhone, this also uses Apple's "Universal Links" mechanism, backed by a small verification file hosted on our own site (nfc.triggerit.eu) that Apple's servers fetch periodically — not on every tap — purely to confirm which app a link belongs to.

8 Web Portal — the one feature that talks to a server

The Web Portal lets you provision devices from a browser. It's off by default — using it requires you to open the Portal screen and scan a QR code shown in your browser. When you do use it:

  • Your device's root/admin private key never leaves your phone. It only signs a one-time code from our relay server; the signature, not the key, is what gets sent.
  • Our relay server writes nothing to disk — session data lives only in memory and is discarded when you disconnect, or after 30 minutes.
  • To check whether a device has an active Portal subscription, we send that device's public key only — never its MAC address, and not tied to your identity — to Supabase, a database provider we use for that one purpose. The MAC address stays on our relay server, used only to match the subscription result back to the right device in your own session.
  • If you export a user or friend key through the Portal rather than as a file, the exported data and its decryption key travel together, in the same connection, to your browser so it can offer the download. In practice this means that connection could technically be observed in transit, the same as any web request — we don't log or store the content, but we want you to know exactly how it moves.
  • If you've given names or phone numbers to people you've shared devices with, that information passes through our relay the same way while you're managing them in the Portal.

The App is fully functional without ever opening the Portal.

9 Backup and export files

You can create a backup file (.tib) protected by a password you choose, or export a single user/friend key (.tiu/.tifriend) protected by a random encryption key. These are created only when you choose to, and shared only through your phone's own share sheet — we never see them. A .tib backup's security rests entirely on the strength of the password you pick, since — unlike the single-key exports — there's no separate key that could be lost track of.

10 Children's privacy

The App isn't directed at children. We don't knowingly collect personal information from anyone under 13 (or the higher age some countries set — 16 under GDPR by default).

11 Your rights

Because almost everything the App handles stays on your own device, most data-protection requests — access, correction, deletion — are things you can already do yourself, locally, at any time. For the one exception, the device identifier sent to Supabase for Portal subscription checks, you can stop this immediately by not using the Web Portal; contact us if you'd like that record removed regardless.

12 Deleting your data

Everything the App stores is local. Uninstalling it deletes all of it. You can also remove individual devices from within the App at any time.

13 Changes to this policy

We may update this policy from time to time. Changes will appear on this page with a new "last updated" date.

14 Contact

Questions about this policy: dfacchin@gmail.com