Different Requests

Privacy

What leaves the device, so you can fill in an App Store privacy label.

What the SDK collects

Only what your app hands over, plus what a person types on the board.

  • The identifier you pass to createSession. Linked to that person, because the same identifier is what keeps their votes.
  • Their email address and display name, if you pass them. Both are optional, and the board works without either.
  • Any traits you pass โ€” plan, cohort, install date โ€” which a triager sees beside the request.
  • What they type into a request or a comment, and which requests they voted for and follow.
  • Their device token, if you register one for push.

What it does not do

  • No tracking. Nothing is joined to data from other companies' apps, and no tracking domain is contacted.
  • No required-reason API is called โ€” no UserDefaults, file timestamps, disk space, boot time or keyboard list.
  • Nothing is written to the device. The session lives in memory and is gone when the process is: no Keychain entry, no file.

The privacy manifest

The package ships PrivacyInfo.xcprivacy declaring exactly that, so Xcode folds it into your app's privacy report without you writing one.

Filling in your App Store label

Declare a user id, and an email address and name if you pass them, each linked to the person and used for app functionality. Declare user content for what people write. Declare no tracking.

Somebody who asks to be forgotten

Their requests, votes and comments belong to the board they were written on. Ask us and we remove them; there is no button for it yet, and saying so is better than implying there is.