The privacy of personal information has received significant attention in mobile software. Although previous researchers have designed some methods to identify the conflict between app behavior and privacy policies, little is known about investigating regulation requirements for third-party libraries (TPLs). The regulators enacted multiple regulations to regulate the usage of personal information for TPLs (e.g., the “California Consumer Privacy Act” requires businesses clearly notify consumers if they share consumers’ data with third parties or not). However, it remains challenging to analyze the legality of TPLs due to three reasons: 1) TPLs are mainly published on public repositories (e.g., Maven) instead of app market (e.g., Google play). The public repositories do not perform privacy compliance analysis for each TPL. 2) TPLs only provide independent functions or function sequences. They cannot run independently, which limits the application of performing dynamic analysis. 3) Since not all the functions of TPLs are related to users’ privacy, we must locate the functions of TPLs that access/process personal information before performing privacy compliance analysis. To overcome the above challenges, in this paper, we propose an automated system named ATPChecker to analyze whether the Android TPLs meet the privacy-related regulations or not. We construct a data set that contains 458 TPLs and 642 host apps. The privacy policies of 187 TPLs are collected and they are annotated with corpus labels. The privacy policies of all host apps are collected and 256 of them are manually annotated. Then, we analyze the bytecode of TPLs and host apps, design natural language processing systems to analyze privacy policies, and implement an expert system to identify the TPL usage-related regulation complaints. The experimental results show that 23% TPLs violate regulation requirements for providing privacy policies. Over 37% TPLs miss disclosing data usage in their privacy policies. Over 60% host apps share user data with TPLs while 65% of those host apps miss disclosing interactions with TPLs. Our findings remind developers to be mindful of TPL usage when developing apps or writing privacy policies to avoid violating regulations