Information provided by publishers to enable their use of or interaction with Google advertising systems:
- must be materially accurate and complete, without misleading omissions; and
- cannot be expressed in a deceptive or misleading manner.
Examples: The personal information or payment details provided by a publisher are materially incomplete, obscured or inaccurate. Information provided about a publisher’s website (e.g., in the ads.txt file) or app (e.g., in the app-ads.txt file) is inaccurate. Deceptively incomplete or inaccurate data in the ad requests such as partial or inaccurate URLs or AppIDs, incorrect geolocation, etc.
Tips for understanding this policy
Dishonest Declarations | Google Publisher Policies
For subtitles in your language, turn on YouTube captions. Select the settings icon at the bottom of the video player, then select "Subtitles/CC" and choose your language.
The following are additional examples that can help you understand the dishonest declarations policy:
- Providing incorrect personal information when signing up for an account, including:
- Falsifying or deliberately obscuring your address by adding emoji or non-standard capitalization or punctuation,
- Submitting an inaccurate date of birth,
- Providing a misleading phone number or bank account information.
- Modifying ad request details in ways that mislead ad serving systems, including:
- Omitting or falsifying the URL so as to mislead where the ads will appear,
- Overriding the geolocation to mislead advertisers where your users are actually located.
We strongly recommend that you use an ads.txt or app-ads.txt file. Since it can help buyers identify counterfeit inventory and help you receive more advertiser spend. If you’re dishonest with the information contained with your ads.txt or app-ads.txt file, this would be a violation of the Dishonest declarations policy.