# \[SOLVED\] Google Data Safety Violation - Thunkable Android Build Issue **URL:** \ **Category:** Questions about Thunkable X\ **Created:** [July 2, 2024, 2:54am UTC](https://community.thunkable.com/t/solved-google-data-safety-violation-thunkable-android-build-issue/3082295 "2024-07-02T02:54:44Z")\ **Posts on this page:** 13\ **Page:** 1
**Author:** ![raviragas7y0ecx](https://avatars.discourse-cdn.com/v4/letter/r/779978/32.png) [@raviragas7y0ecx](https://community.thunkable.com/u/raviragas7y0ecx)\ **Post date:** [July 2, 2024, 2:54am UTC](https://community.thunkable.com/t/solved-google-data-safety-violation-thunkable-android-build-issue/3082295/1 "2024-07-02T02:54:44Z")
I keep getting this violation from Google Play for my app. We found an issue in the following area(s): - **Version code 4: Policy Declaration - Data Safety Section** : Location Data Type - Precise Location - The only thing I have added was Admob and have already declared the use of Device ID in the Data Safety form. I am not sure how Location features were added to my App. can anyone advise on how to resolve this? Thanks! ---
**Author:** ![ioannis](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/ioannis/32/146956_2.png) [@ioannis](https://community.thunkable.com/u/ioannis)\ **Post date:** [July 2, 2024, 7:55pm UTC](https://community.thunkable.com/t/solved-google-data-safety-violation-thunkable-android-build-issue/3082295/2 "2024-07-02T19:55:12Z")
Hello @raviragas7y0ecx Could you please share the specific project URL with us so we can investigate it further? ![](https://downloads.intercomcdn.com/i/o/759644115/d4a89684a0bda74ab75c59e6/Screenshot+2023-06-08+at+4.13.55+PM.png) You could copy it from the top of your browser. This way we could find the best solution for you. ---
**Author:** ![raviragas7y0ecx](https://avatars.discourse-cdn.com/v4/letter/r/779978/32.png) [@raviragas7y0ecx](https://community.thunkable.com/u/raviragas7y0ecx)\ **Post date:** [July 3, 2024, 3:57am UTC](https://community.thunkable.com/t/solved-google-data-safety-violation-thunkable-android-build-issue/3082295/3 "2024-07-03T03:57:45Z")
Hi @ioannis Here is the link: [https://x.thunkable.com/projects/666120c8604b788955dab0c2/openProject/designer](https://x.thunkable.com/projects/666120c8604b788955dab0c2/openProject/designer) Interestingly, my initial submission was approved. My update (which was only UI-specific) is being rejected for this reason. \*\*\* An Update \*\*\* I am having the same issue with another App Update. The original version was approved and now the update has been rejected for the same reasons. Has Thunkable changed something for the Android Build in the last few weeks that could cause this issue? My iOS submissions are being accepted. Thanks! ---
**Author:** ![ioannis](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/ioannis/32/146956_2.png) [@ioannis](https://community.thunkable.com/u/ioannis)\ **Post date:** [July 3, 2024, 6:15pm UTC](https://community.thunkable.com/t/solved-google-data-safety-violation-thunkable-android-build-issue/3082295/4 "2024-07-03T18:15:48Z")
Hello @raviragas7y0ecx Thank you for sharing your project URL. I will take a look at your project and will follow up as soon as possible. ---
**Author:** ![raviragas7y0ecx](https://avatars.discourse-cdn.com/v4/letter/r/779978/32.png) [@raviragas7y0ecx](https://community.thunkable.com/u/raviragas7y0ecx)\ **Post date:** [July 3, 2024, 9:44pm UTC](https://community.thunkable.com/t/solved-google-data-safety-violation-thunkable-android-build-issue/3082295/5 "2024-07-03T21:44:02Z")
Dear @ioannis Thanks! Hope it can be resolved soon as I am unable to publish the Android App updates for ALL my Apps because of this issue. \*\*\* An Update \*\*\* My earlier apps that were submitted have also been flagged for the same issue. They all use AdMob but nothing related to “Precise Location”. So far Apple Appstore hasn’t reported this for my Apps. Thanks! ---
**Author:** ![ioannis](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/ioannis/32/146956_2.png) [@ioannis](https://community.thunkable.com/u/ioannis)\ **Post date:** [July 4, 2024, 7:33pm UTC](https://community.thunkable.com/t/solved-google-data-safety-violation-thunkable-android-build-issue/3082295/6 "2024-07-04T19:33:07Z")
Hello @raviragas7y0ecx Thank you for sharing more information. I sent you a copy of your project into a personal message Could you please check it? ---
**Author:** ![raviragas7y0ecx](https://avatars.discourse-cdn.com/v4/letter/r/779978/32.png) [@raviragas7y0ecx](https://community.thunkable.com/u/raviragas7y0ecx)\ **Post date:** [July 5, 2024, 4:35am UTC](https://community.thunkable.com/t/solved-google-data-safety-violation-thunkable-android-build-issue/3082295/7 "2024-07-05T04:35:29Z")
Dear @ioannis @matt_conroy My App has ads and I already went through the whole process of waiting for it to be approved some time back. Now to test a copy, I have to go through the whole process again. I have other Apps in the PlayStore all being flagged for the same issue. It will be very frustrating for any developer to go through the whole process of copying a project again and again, and then go through the approval process of AdMob every time there is a rejection from PlayStore which Thunkable is not able to resolve. Can you please check the original project again and see if there is an issue as to why Location Services are being enabled even though I am not using them. The current solution that you suggested doesn’t solve the root cause of the problem and it may just keep resurfacing to the annoyance of developers. Thank You! ---
**Author:** ![matt\_conroy](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/matt_conroy/32/150843_2.png) [@matt\_conroy](https://community.thunkable.com/u/matt_conroy)\ **Post date:** [July 5, 2024, 3:06pm UTC](https://community.thunkable.com/t/solved-google-data-safety-violation-thunkable-android-build-issue/3082295/8 "2024-07-05T15:06:47Z")
Hi @raviragas7y0ecx, thanks for reaching out. I certainly understand your frustration here. From what we have seen with URL to your project, there is nothing in your app should merit having their app rejected by google for location collection issues. Sometimes, this issue comes into play if there is a remnant of information from a component used and then deleted (in this case, something involving a location sensor) that is still showing up. This could happen even if you only momentarily add a component into your app and then delete it. Making a copy of the app, like Ioannis had done, will alleviate this issue as what might have been there before is not present at the time the new copy of the app is created. Looking over the logs, these are the components present in the app when it was published, do you mean for all them to be in here? Screen Lottie Button Label AdMob Banner Image PDFReader Label RichText Timer AdMob Interstitial Amplitude Sound ---
**Author:** ![raviragas7y0ecx](https://avatars.discourse-cdn.com/v4/letter/r/779978/32.png) [@raviragas7y0ecx](https://community.thunkable.com/u/raviragas7y0ecx)\ **Post date:** [July 6, 2024, 6:57am UTC](https://community.thunkable.com/t/solved-google-data-safety-violation-thunkable-android-build-issue/3082295/9 "2024-07-06T06:57:00Z")
Dear @matt_conroy and @ioannis Thank you for looking into this. The components you listed are what I need for my app. I can confirm that I didn’t add any component related to location-based services. The same App has not been flagged for any issue (so far) in the Apple AppStore. My current theory is this: - When AdMob is used on Android Devices, location-tracking is included to further personalize the delivered Ads. - This does not happen for iOS devices, maybe due to privacy-related restrictions. I am not sure, but this is the only explanation I can think of. I can update the Data Safety form to state this, but I want to be sure that this is indeed the reason. Thanks! ---
**Author:** ![ioannis](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/ioannis/32/146956_2.png) [@ioannis](https://community.thunkable.com/u/ioannis)\ **Post date:** [July 19, 2024, 9:22am UTC](https://community.thunkable.com/t/solved-google-data-safety-violation-thunkable-android-build-issue/3082295/10 "2024-07-19T09:22:29Z")
Hello @raviragas7y0ecx We have successfully identified the root cause and created a solution. Currently, we are in the process of testing it and working on a plan to release it in production, ensuring that everything will function as usual. I will provide an update as soon as possible. Thank you for your time and patience in this matter. ---
**Author:** ![ioannis](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/ioannis/32/146956_2.png) [@ioannis](https://community.thunkable.com/u/ioannis)\ **Post date:** [July 30, 2024, 4:18pm UTC](https://community.thunkable.com/t/solved-google-data-safety-violation-thunkable-android-build-issue/3082295/11 "2024-07-30T16:18:18Z")
Hello @raviragas7y0ecx Hi , thank you again for your patience. I would like to let you know that we have now officially released a fix for this bug. Please keep in mind that you may need to do a [hard refresh](https://docs.thunkable.com/getting-started/data-sources/data-sources#hard-refresh-your-browser) of your browser for the changes to take effect in your project. If your [downloaded or published app](https://docs.thunkable.com/publishing-apps/publish) is affected by this bug, you will need to re-download or re-publish your app for these changes to take effect. ​ ---
**Author:** ![raviragas7y0ecx](https://avatars.discourse-cdn.com/v4/letter/r/779978/32.png) [@raviragas7y0ecx](https://community.thunkable.com/u/raviragas7y0ecx)\ **Post date:** [July 30, 2024, 6:00pm UTC](https://community.thunkable.com/t/solved-google-data-safety-violation-thunkable-android-build-issue/3082295/12 "2024-07-30T18:00:32Z")
Dear @ioannis Thank You for looking into this and providing a permanent solution. Appreciate the efforts by yourself and the Thunkable team! Thanks! Ravi ---
**Author:** ![ioannis](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/ioannis/32/146956_2.png) [@ioannis](https://community.thunkable.com/u/ioannis)\ **Post date:** [August 16, 2024, 11:45am UTC](https://community.thunkable.com/t/solved-google-data-safety-violation-thunkable-android-build-issue/3082295/13 "2024-08-16T11:45:52Z")