{"action":"opened","issue":{"url":"https://api.github.com/repos/fumc-pensacola/transept/issues/60","repository_url":"https://api.github.com/repos/fumc-pensacola/transept","labels_url":"https://api.github.com/repos/fumc-pensacola/transept/issues/60/labels{/name}","comments_url":"https://api.github.com/repos/fumc-pensacola/transept/issues/60/comments","events_url":"https://api.github.com/repos/fumc-pensacola/transept/issues/60/events","html_url":"https://github.com/fumc-pensacola/transept/issues/60","id":132051664,"number":60,"title":"Write a Privacy Policy","user":{"login":"andrewbranch","id":3277153,"avatar_url":"https://avatars.githubusercontent.com/u/3277153?v=3","gravatar_id":"","url":"https://api.github.com/users/andrewbranch","html_url":"https://github.com/andrewbranch","followers_url":"https://api.github.com/users/andrewbranch/followers","following_url":"https://api.github.com/users/andrewbranch/following{/other_user}","gists_url":"https://api.github.com/users/andrewbranch/gists{/gist_id}","starred_url":"https://api.github.com/users/andrewbranch/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/andrewbranch/subscriptions","organizations_url":"https://api.github.com/users/andrewbranch/orgs","repos_url":"https://api.github.com/users/andrewbranch/repos","events_url":"https://api.github.com/users/andrewbranch/events{/privacy}","received_events_url":"https://api.github.com/users/andrewbranch/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":{"login":"JebHunt","id":12077563,"avatar_url":"https://avatars.githubusercontent.com/u/12077563?v=3","gravatar_id":"","url":"https://api.github.com/users/JebHunt","html_url":"https://github.com/JebHunt","followers_url":"https://api.github.com/users/JebHunt/followers","following_url":"https://api.github.com/users/JebHunt/following{/other_user}","gists_url":"https://api.github.com/users/JebHunt/gists{/gist_id}","starred_url":"https://api.github.com/users/JebHunt/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/JebHunt/subscriptions","organizations_url":"https://api.github.com/users/JebHunt/orgs","repos_url":"https://api.github.com/users/JebHunt/repos","events_url":"https://api.github.com/users/JebHunt/events{/privacy}","received_events_url":"https://api.github.com/users/JebHunt/received_events","type":"User","site_admin":false},"milestone":null,"comments":0,"created_at":"2016-02-08T04:46:55Z","updated_at":"2016-02-08T04:46:55Z","closed_at":null,"body":"We use Crashlytics and Answers as part of Fabric.io to collect crash reports and analytics anonymously. Using these services require that we disclose to users what we are collecting ([Answers Agreement Section 9.1](https://answers.io/img/terms.pdf)). Planned updates would potentially give us the opportunity to track users *non*-anonymously, which we should not do, but once those systems are in place it becomes especially important that we’re transparent about what we’re doing.\r\n\r\nWe should write a brief, plain-English privacy policy as soon as possible. To sum it up in my own words, we anonymously collect information about the device, conditions leading to a crash, and certain actions users take while using the app. We use that information to fix bugs and make informed decisions about improvements we can make, new features we can add, and the overall future of the app. This kind of information can’t be used to personally identify anyone. If we do gather information that can identify a user (e.g. in the future registering for a Wednesday night dinner or something), it will be prompted by the user’s actions that clearly indicate their (plural “their” was the word of the year in 2015) consent and intent to share that information, and will only share it with church staff and volunteers for administrative purposes at our discretion.\r\n\r\nA non-exhaustive list of things we might collect during a crash:\r\n\r\n- iOS version\r\n- iPhone model\r\n- What screen was active or what action was taking place\r\n- Battery level\r\n- Available hard drive storage\r\n- Memory usage\r\n- Whether the device was jailbroken\r\n\r\nExamples of user actions we might track:\r\n \r\n- Watching a video\r\n- Viewing a bulletin\r\n- Viewing a calendar event\r\n\r\nWe should also eventually amend this privacy policy with a description of how we treat the distribution of personally identifying information (PII) from the church directory... once we decide that, which will be the subject of an upcoming phone call. So far, my idea is to authenticate devices to access the directory data by an in-person request process. So basically, “we keep your directory contact information safe by only granting access to church members who we can personally verify, just as if we were physically handing them a printed copy. You can request the removal of your entry at any time by emailing [whoever].” Or something.\r\n\r\nI think I want to remove the prayer request form, as it seems a bit of a privacy liability. What email it is sent to is controlled by an option in the database, and during testing it went to me. If we changed it back to me for more testing and forgot to change it again after that, or that email alias was deleted and it went to Kyle as the catchall, I don't want any of us to inadvertently become an eavesdropper on someone’s confession or something."}}