Privacy. We both like it.

I don't want your data, but I need some to make Tappd That better. Below, I've tried to be as transparent about what data I collect as possible. Contact me if you think I can improve.

• Tappd That records minimal analytics to aid in future development. Data is always sent over an SSL-secured connection. The data is not written to web server log files. Data is sent only once per revision posted to the App Store, and there is zero loss of functionality if the data is never sent. The following is the only information recorded:
  • A unique identifier
    • This identifier is not your device’s UUID. It is generated uniquely every time you re-install Tappd That on any device.
  • App version and build number
  • iOS name and version
  • iOS device name and platform
  • Preferred language
  • Current date/time
• OAuth tokens for Untappd and Foursquare are handed out via Tappd That's server over HTTPS. Your access code and token are never saved.
• If you are not authenticated to Foursquare, venue search queries are proxied to Tappd That's server. This includes your current location and search query. These values are both encrypted in transport and never recorded, nor are the responses from Foursquare. Remember, this is only if you are not authenticated to Foursquare. When authenticated, venue search requests go straight to Foursquare.
• When communicating in any way with Tappd That’s servers, your IP address is recorded in a web server log (as an incoming request only), but is not linked to your unique identifier. Where possible, requests are POSTed, meaning the data is encrypted in transport and not visible in web server logs.
• Tappd That’s servers are backed up in a variety of ways, and the above information will exist in those backups for a number of days after being deleted, until the backups have been cycled.

---