Beacons & SDKs
Sites, apps, videos, emails, and other services may contain a small snippet of code called a beacon or in mobile apps contain an SDK or Software Development Kit. In their simplest form, beacons and SDKs allow a service to transfer or collect information through a server request. Services may use beacons and SDKs for many purposes, including counting the number of users who visit a webpage, download an app, or read an email; site usage analytics; advertising auditing and reporting; and content and advertising personalization.
Oath’s Practices Regarding Beacons & SDKs
Oath may collect information through beacons and SDKs on or off of Oath brands, websites, apps, advertising services, products, services or technologies (“Services”) about your online activities, such as the Service you are visiting, the address of the referrer page for the site you previously visited, the time you are visiting the Service, and your browsing or device settings. We may use the information we collect through beacons and SDKs:
- To understand traffic patterns and how you use and interact with products and services.
- To improve Oath products and services.
- To optimize your experience.
- To provide auditing, research, modeling and reporting for our advertisers and other partners.
- To offer Oath Analytics, including Flurry.
- To provide you relevant advertising and content.
- Your Choices
Learn more about your choices.
Other Companies’ Beacons & SDKs on Oath
- Some Third Parties may have technology enabling them to act as "containers" for additional beacons, typically these are called piggyback beacons. Oath may not always be aware of these piggyback beacons, however, you can check what beacons exist on a webpage using privacy tools.