Setblue QR Privacy Policy

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:

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:

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: