Required and suggested information when publishing Naviga news apps on stores.
Loading...
Loading...
Loading...
Loading...
When publishing News apps Google and Apple have some specific requirements to verify publisher ownership.
Suggestions and example how to configure your app and Google play.
There will likely be requirements for information inside the app. Here are a couple of examples that has been successfully published.
This is how Naviga suggest you enter privacy details when publishing a Naviga news app.
This is how Naviga suggest you enter privacy details when publishing a Naviga news app for iOS.
Read more: App Store privacy details
Fast track:
To skip the manual config, use the csv file below as a quickstart.
CSV file contains below settings, for a Naviga Standard config Android app.
To help users better understand your app's privacy, security and data handling practices before they download it, provide information about your app's safety. The information that you provide is shown on your Store Listing so that users can learn how you collect and share their data.
Google Developer Program Policy
This info is required from 20 July 2022
https://play.google.com/console
App activity
App interactions are sent to statistics
App info and performance
Crash logs and diagnostics are sent to Firebase Crashlytics and Google Play.
Device or other IDs
Firebase installation ID is used by Firebase Crashlytics and statistics.
You might need to mark more, if customer app is using 3rd part tools or has addition config.
Location
Ads and statistics
Personal info: Email
Email used as key if provisioning is used in app.
Personal info: User ID's
User ID can be sent to statistics provider, if configured.
Save!
Naviga don't provide an end user interface for deleting data, we are a "ombud".
​​​​
​​​​​​
​​​
