User-, Device- and Application-Specific Identifiers

When an application that integrates the Bitplaces SDK registers itself with the Bitplaces Core Platform (BCP), the BCP issues a Bitplaces Application Token (BAT) which is unique to that application instance. This means that an end-user with the same application installed on her iPhone and iPad would have two BATs; if she were also using the application on an Android device, she would have three BATs, one for each device/app combination.

A BAT is opaque, by which we mean the token has no meaning in and of itself. The BAT is simply an identifier which one can use on certain requests to the core platform to refer to a specific installation of the SDK. For example, you may want to send a message to a specific user on a specific device, such as their Android phone, using the BAT.

This initial registration provides for “anonymous” access to the BCP. The BCP knows nothing about the user, other than very general information such as the version of the application, or the operation system version. No information specific to the individual person is stored on the platform. In addition, there is no link between any two such instances; from the perspective of the BCP, each individual instance may well represent a different person.

BATs are assigned by the core platform automatically on SDK registration and cannot be modified after the fact.

The BAT for an application installation can be retrieved at any time from the SDK via the getApplicationToken() instance method of BitplacesSDK.