ToBid SDK Compliance Guidelines

1. ToBid SDK Integration Standards

Developers integrating the ToBid SDK need to comply with the following integration specifications.

Compliance Matters	Legal Requirements	Integration Specifications and Recommendations
SDK Initialization Timing and Information Collection Specifications	Upon the app's login or registration page and its first launch, it should inform users of the personal information processing rules through a clear and easily accessible method such as pop-ups, text links, or attachments. This information should be conveyed in clear and understandable language, allowing users to make voluntary and explicit consent under fully informed circumstances.	- Important!! ToBid SDK initialization should only occur after the user explicitly agrees to the app's privacy policy/terms of service. Otherwise, the developer will bear all privacy-related disputes. - Do not invoke ToBid SDK-related services when the app is in the background or inactive. - Before the user explicitly agrees to the privacy policy/terms of service, it is prohibited to collect, report, or transmit user information without authorization. Especially sensitive information such as IMEI, Android ID, MAC address, and installed application lists. - Before the user explicitly agrees to the privacy policy/terms of service, do not prompt system permission dialogs to request system permissions from the user.
Disclose ToBid SDK Name, Official Website, and Privacy Policy Information in the App's Privacy Policy and Information Sharing List	When transmitting personal information to third-party servers through methods such as embedding third-party SDKs, developers should disclose the name of the third-party SDK and the official website address of its privacy policy in the product's third-party SDK directory and privacy statement.	After integrating the ToBid SDK into the product, the normal operation of the ToBid SDK will collect necessary user information for purposes such as advertising data calculation, aggregation, and diversion services. Developers should disclose the ToBid SDK in the product's third-party SDK directory and privacy statement according to the actual integration situation of the ToBid SDK. It is recommended to refer to the template appended after the table below. Name: ToBid SDK Third-party Name: Beijing Chuangzhi Technology Co., Ltd. Main Functions: Provides the functionality to fetch and display ads from third-party advertising alliance SDKs. Types of Personal Information: Approximate location information, device information (such as device manufacturer, device model, operating system version, etc.), device identifiers (such as IMEI, Android ID, OAID, IDFA, etc.), application information (package name, version number), advertising data (such as exposure, click data, etc.). SDK Privacy Policy URL：ToBid SDK Privacy Policy Official Website URL：https://www.tobidad.com/home
One-Click Close for Advertisements	When displaying advertisements and information pop-ups to users, or when users are browsing advertisements and information pop-ups, there should be a "Close" or "Skip" button available. Clicking on this button should immediately close the advertisement display.	When rendering ad spaces, the app needs to ensure that the skip or close buttons are not obscured.
Self-Rendered Advertisements Must Have Clear Ad Identifiers and Ensure the Legality and Compliance of Ad Content and Style	Internet advertisements should clearly indicate their source. Ad content should comply with the provisions and policy requirements of the Advertising Law and other relevant laws and regulations.	- Do not use any technical means to modify or delete ad identifiers, including but not limited to the size, position, and color of ad identifiers. Otherwise, the consequences of such actions will be the responsibility of the developer. - Developers are not allowed to modify or adjust the advertising content and style provided by the advertising alliance SDK on their own. This includes but is not limited to displaying overlapping ads, changing ad elements, adjusting click hotspots, configuring fake buttons, and any other violations that may affect user experience or induce users to click. Otherwise, the consequences of such actions will be the responsibility of the developer.
Personalized Ad Close Functionality	Developers should comply with legal requirements to create a personalized ad close button for users on the client side, making it easily accessible. Upon clicking the close button, developers must ensure that the ToBid SDK's close capability interface is called. ToBid will then transmit the corresponding information to the advertising alliance SDK and restrict the information collection by the ToBid SDK itself.	After developers call the ToBid interface, ToBid will be compatible with the personalized advertising functionality of the advertising alliance. If some advertising alliance SDKs do not support the personalized ad close function, ToBid SDK will no longer request this alliance SDK after the user chooses to close the personalized ad.

2. APP Compliance Requirements

	Compliance Matters	Compliance Requirements
Privacy Policy and personal information collection and use	The independence and readability of the privacy policy.	- The app must provide a separate privacy policy. - The privacy policy must be independently written and cannot exist as part of other documents such as user agreements.
	The privacy policy should be easily accessible and users should have the option to independently choose whether to agree to it or not.	- Your product's privacy policy should be displayed to users in an online format when they first open your product or on the registration/login interface. Users should have the option to independently choose whether to agree to this policy, and it should not be obtained through default pre-selection of "Agree". Bundling multiple business functions and permissions together and requiring users to accept them all at once is not permissible. - Once end users access the main function interface of your product, they should be able to access your product's privacy policy through no more than 4 clicks/swipes.
	If there is a situation where personal information is transferred to third parties, it should be clearly disclosed to users.	In the "Personal Information Sharing" section or the section explaining the integration of third-party SDKs in your product's privacy policy, users should be informed that certain functionalities/services are provided by ToBid SDK. Referencing the relevant privacy policy of ToBid SDK, list the types of personal information collected, the purposes and usage, and provide a clickable link to the privacy policy of ToBid SDK to ensure accessibility.
	The timeliness, updates, and notifications of privacy policies.	- The privacy policy should clearly indicate the date of publication, effectiveness, or updates. - In the event of changes in business functions, outbound personal information scenarios, changes in purposes of use, changes in contact information of the person responsible for personal information protection, etc., the privacy policy should be revised accordingly, and users should be promptly informed through email, mail, phone calls, push notifications, etc.
	Collection of personal information should meet the minimum necessary principle	- The types of personal information collected must not exceed the scope described in the privacy policy. - The app should not collect any personal information unrelated to its business functions. - After a user explicitly refuses, the app must not continue to frequently request permissions or disturb the user. - After updating or upgrading the app, the original system permission settings should not be altered.
User Rights	Personalized exit mechanism	An option to refuse or disable the use of personal features within the app should be provided. Upon user refusal or closure, such features should not be utilized for information push or commercial marketing.
	Support for User Account Deletion	Provide a clear pathway for users to deactivate or delete their accounts, and promptly delete their personal information or anonymize it upon account deactivation.
	Users must not be induced, deceived, or forced into jumping, clicking, or downloading.	When the app displays advertisements or launches other pop-up windows, it should provide prominent and effective close or skip functionality. It must not utilize text, images, videos, or any other means to deceive or mislead users into navigating to other pages.