- PALP does not access or store any personal inforamtion of the users except thier name, and that too only when they want to create and advertize thier own posts.
- When users want to create and advertize their own Posts, PALP requests thier permission to look them up using their identity, so it can retreive their name
- PALP requires users of the app to be logged into their iCloud account (thru iPhone Settings),if they want to create and advertise their own Post.
- PALP does not collect iCloud username or password within the app. iCloud sign-in is done thru iPhone Settings.
- PALP retrieves the display name on the iCloud account using the identity of the logged in user. It uses Apple provided CloudKit API to do that.
- PALP uses the user's display name to tag the Post records in Cloudkit database, so it can display the name on the Post, when the Nearby PALP users discover the advertized Post. PALP doesn't use the user's names for any other purpose.
- PALP doesn't access or store user email or any information other than the name.
- PALP does not require users of the app to be logged into iCloud account, if they just want to discover and browse Nearby Posts.
- PALP requests user's permission for notiifcations and location access first time they use the app. User's have the ability to tunr on and off these settings.
- PALP does not collect or store user's location. All the discovery of the Nearby Posts is done using Apple's iBeacons framework and SDK (Low energy Bluetooth based).
- PALP does background iBeacon region monitoring and briefly wakes up the app to do beacon ranging as per Apple's guidelines