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 the following purposes: measurement and reporting, for example to count the number of users who visit a web page, download an app or read an email; site usage analytics; and to offer you more relevant, interesting and personalised content and advertising.
Oath’s Practices Regarding Beacons & SDKs
Oath may collect information through beacons and SDKs on or off 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 your online traffic patterns, and how you use and interact with Oath products and services;
- to maintain and develop relevant features, and improve Oath products and services;
- to optimise your experience within our services;
- To provide auditing, research, modelling and reporting for our advertisers and other partners.
- to offer Oath Analytics, including Flurry
- to provide you with 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, which are typically called piggyback beacons. Oath may not always be aware of these piggyback beacons, but you can check what beacons exist on a web page using privacy tools.