Privacy Policy

The privacy policy for Setblue QR.

Setblue QR was designed from the ground up with privacy in mind. An important principle of Setblue QR is to only save the least amount of data it absolutely needs, and to not save any data that can be used to identify specific users' identities.

That is why the Setblue QR is completely open source, so that users and developers can see for themselves the data that Setblue QR saves.

Data Transmitted

Any data that is transmitted to the analytics server consists of the following:

1. An anonymized user identifier. The identifier is constant for each app install but cannot be traced back to any personally identifiable information.

2. An action taken, such as “App Launched” or “Settings Opened”. The developer defines these actions.

3. A time stamp when the action was taken.

4. Device metadata, namely platform, system version, app version, build number, if the build was downloaded via App Store or TestFlight, and the device model type (i.e., iPhone X, iPad Air, or iPhone 12).

5. IP addresses are never stored on the Setblue QR, neither in the database nor in any log files, nor at any other place.

Terms Used

A developer is a person who creates or maintains an app which includes the Setblue QR. They are responsible for making sure they only hand anonymized data to the Setblue QRt.

The Setblue QR Client is the code that transmits data to the Setblue QR Server.

A user is a person who uses any app created by a developer. It is our job to make sure their data stays safe.

A signal is one instance of data sent from the app to the Setblue QR Server using the Setblue QR Client.

Setblue QR Viewer is the app that developers use to see signal data, both raw and in aggregated form, as Insights.

User Identifiers

Developers have three choices on how to identify users. They should note which they are using in their app's privacy policy:

1. Using no user identifier at all. This will give them the greatest piece of mind, while still allowing Setblue QR to help them out with statistical analysis.

2. Using Apple's “IdentifierForVendor” API. This is the default behaviour for Setblue QR. The identifier generated out with this method has no relation to any of the user's identifiable information or private data. Deleting and reinstalling the app will generate a new identifier and sever any connection to the old one.

3. Using a custom string identifier, such as the user's username or email address. This string will never be transferred directly to the server. Instead, the Setblue QR Client will create a hash out of that string and only ever transmit that hash. This allows Setblue QR to detect the same user on multiple devices, but it is impossible for both the developer and any person having access to Setblue QR database to retrieve the original custom string identifier.

Metadata

Developers can include any metadata they wish with signals they send using Setblue QR Client. They are urged to not send any data that might identify their users. They must include the types of data they send in their own apps' privacy policies.

Using Setblue QR Viewer

Developers using the Setblue QR Viewer app are sending signals to the Setblue QR Server as well. These do not contain any user data. The types of data are:

• App was launched

• Which part of the app was navigated to?

• Standard metadata: platform, system version, app version, build number, if the build was downloaded via App Store or TestFlight, and the device model type (i.e. iPhone X, iPad Air, or iPhone 12).