Google Play's Data Safety Guidance.

This page provides information on Ogury with respect to Google Play’s Data safety Section.

Category	Data type	Description	Ogury SDK Data Collected	Data Handling	Purpose	Comment, external
Location	Approximate location	User or device physical location to an area greater than or equal to 3 square kilometers, such as the city a user is in, or location provided by Android’s ACCESS_COARSE_LOCATION permission.	NO			Ogury does not collect position data through this permission; Ogury IP geolocation data is within 50 square kilometers; Ogury servers collects the IPs during the Ad requests;
Location	Precise location	User or device physical location within an area less than 3 square kilometers, such as location provided by Android’s ACCESS_FINE_LOCATION permission.	NO
Personal info	Name	How a user refers to themselves, such as their first or last name, or nickname.	NO
	Email address	A user’s email address.	NO
	Personal identifiers	Identifiers that relate to an identifiable person. For example, an account ID, account number, or account name.	NO
	Address	A user’s address, such as a mailing or home address.	NO
	Phone number	A user’s phone number.	NO
	Race and ethnicity	Information about a user’s race or ethnicity.	NO
	Political or religious beliefs	Information about a user’s political or religious beliefs.	NO
	Sexual orientation or gender identity	Information about a user’s sexual orientation or gender identity.	NO
	Other personal info	Any other personal information such as date of birth, veteran status, etc.	NO
Financial info	Credit card, debit card, or bank account number	Information about a user’s financial accounts such as credit card number.	NO
	Purchase history	Information about purchases or transactions a user has made.	NO
	Credit info	Information about a user’s credit. For example their credit history or credit score.	NO
	Other financial info	Any other financial information.	NO
Health and fitness	Health information	Information about a user’s health, such as medical records or symptoms.	NO
Health and fitness	Fitness information	Information about a user’s fitness, such as exercise or other physical activity.	NO
Messages	Emails	A user’s emails including the email subject line, sender, recipients, and the content of the email.	NO
	SMS or MMS messages	A user’s text messages including the sender, recipients, and the content of the message.	NO
	Other in-app messages	Any other types of messages. For example, instant messages or chat content.	NO
Photos or videos	Photos	A user’s photos.	NO
Photos or videos	Videos	A user’s videos.	NO
Audio files	Voice or sound recordings	A user’s voice such as a voicemail or a sound recording.	NO
	Music files	A user’s music files.	NO
	Other audio files	Any other user-created or user-provided audio files.	NO
Files and docs	Files and docs	A user’s files or documents, or information about their files or documents such as file names.	NO
Calendar	Calendar events	Information from a user’s calendar such as events, event notes, and attendees.	NO
Contacts	Contacts	Information about the user’s contacts such as contact names, message history, and social graph information like usernames, contact recency, contact frequency, interaction duration and call history.	NO
App activity	Page views and taps in app	Information about how a user interacts with your app. For example, the number of page views or the screen coordinates of taps.	NO
	In-app search history	Information about what a user has searched for in your app.	NO
	Installed apps	Information about the apps installed on a user’s device.	NO
	Other user-generated content	Any other user-generated content not listed here, or in any other section. For example, user bios or notes.	NO
	Other actions	Any other user activity or actions in-app not listed here such as gameplay and likes.	NO
Web browsing	Web browsing history	Information about the websites a user has visited.	NO
App info and performance	Crash logs	Crash log data from your app. For example, the number of times your app has crashed, stack traces, or other information directly related to a crash.	YES	Required Collect	Analytics	When a Crash occurs, we send its code to a database to improve our SDK performances and stability; Datas collected are the following: Date and time Advertising ID API key/Ad Unit ID Ogury Script Version Page locale Mobile web address App package name and version Browser name and version Device model and OS version Error message: “Ad Execution and Crash Reporting Information”
	Diagnostics	Information about the performance of your app. For example battery life, loading time, latency, framerate, or any technical diagnostics.	NO
	Other app performance data	Any other app performance data not listed here.	NO			Only crash reports
Device or other identifiers	Device or other identifiers	Identifiers that relate to an individual device, browser or app. For example, an IMEI number, MAC address, Widevine Device ID, Firebase installation ID, or advertising identifier.	YES	Required Sharing	Advertising or marketing, Fraud prevention, security, and compliance	We collect Advertising ID, Cookie ID and IP Adress

Movatterモバイル変換

Google Play's Data Safety Guidance.