UNKNOWN DATA SENT OFF-DEVICE

Vendor Requirements: - Vendor must speak English clearly. - Vendor must be available to interact during some part of the Eastern U.S. working day (8:30 AM to 5:30 PM). - Vendor must have current availability so as not to drag out completion of this project. Target completion of all work is three weeks from signing of contract. - Work for Hire: Vendor agrees that this is a contract for services with the resulting products being a work for hire. Thus, the resulting work (and all rights therein, including without limitation, copyright) belongs to and shall continue to be the sole and exclusive property of BattleGear, LLC. Input: BattleGear will provide - Letter from Google defining their issues with the existing app, specifically the Data Safety Section of their User Data Policy. It is attached below. - Current functioning Android code for a generic Bible-memory app. There are 9 variants built into the code. For starters, please focus on the NTM variant which is for an adult audience. [Note the size of the app folder is 1.47 GB, so BattleGear will use vendor’s preferred tool for data transfer.] App intentions: - Google has an issue with data sent from this app (described below), so that is the focus of this discussion - BattleGear allows users to send emails from two places within the app. (1) the Info screen has a Feedback button which allows the user to send questions and comments directly to BattleGear. (2) On the Memorize page, under the Activities button is a button labeled Mail-a-Friend which allows the user to tell a friend about this app. - Except for the two emails described above, BattleGear’s intention is not to transmit any data off of the user’s device to BattleGear or to anybody else. Google seems convinced that the app does in fact transmit some unauthorized data. It is possible that the original developer included a generic module which transmits data unintentionally or intentionally. - It is not clear to BattleGear whether Google has an issue with the variants designed for children being able to send email. If vendor believes that Google has such an issue, we can discuss alternatives to address that. Variants designed for children are probably recognized in the code by the word “awana”, but BattleGear is not sure of this. Output: - Since the Google issues are invisible to BattleGear, vendor will investigate the issues described by Google and propose fixes to BattleGear. Vendor should be aware that some of the variants are for children, and thus may have additional exceptions required by Google. - BattleGear needs to know what data other than the emails described above, is sent out of this app, where the data is sent, and how that data might be used by the recipient. - Upon BattleGear’s approval of proposed fixes, vendor will produce Android code using Android Studio that will remove the offending code from the app without affecting any other app functionality - Vendor will advise BattleGear if there are particular responses necessary for this app when submitting the required Data Safety form to Google - In addition to the above, vendor will update the Android code to Android API 33 - Vendor will provide the updated code to BattleGear. If the vendor chooses, this may be done in phases with initial focus on the NTM variant (adult audience) and then on AWHG (child audience) to test Google’s approval. See uploaded file for project completion information and Google issues description