Google Locator Tag guidelines

RE: Google Locator Tag guidelines

Charlie — Wed, 17 Jul 2024 07:01:35 GMT

Hi Wayne,

If you have another Bluetooth application use case apart from the locator tag, you may not need to declare their device as a "locator tag". In this case, you wouldn't be required to follow the locator tag guidelines.

You can consider creating another Bluetooth identity to serve you second application use case and use it for pairing/bonding. However, you still need to follow the privacy requirements, as any vulnerability in the second Bluetooth use case can be leveraged to track the Bluetooth device that combines both features.

As a side note, the Bluetooth bonding is omitted for FMDN locator tags, as there is an issue on Android that causes connection delays/failure when connecting to bonded targets.

Best regards,

Charlie

RE: Google Locator Tag guidelines

Wayne — Tue, 16 Jul 2024 13:41:24 GMT

Hi,

I'm referring to the following sample and if not following 2 of the guidelines mentioned is a potential blocker to a consumer product: https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/samples/bluetooth/fast_pair/locator_tag/README.html#fast-pair-locator-tag

Thanks

Wayne

RE: Google Locator Tag guidelines

Charlie — Tue, 16 Jul 2024 13:03:25 GMT

Hi Wayne,

Have you referred the following sample? The sample works as a Fast Pair Provider (one of the Fast Pair roles) and a simple HID multimedia controller.

Bluetooth Fast Pair: Input device (nordicsemi.com)

Best regards,

Charlie