IP addresses, encrypted DNS and network tracking

An IP address is part of the connection

Apple describes IP addresses and DNS records as information that network providers and websites can use to build a location or browsing profile. A network privacy feature changes which party can see particular information; its exact coverage matters. Apple: Private Relay design

HTTPS protects data in transit

The FTC explains that most websites now encrypt traffic, making public Wi-Fi generally safer than it was when unencrypted sites were common. HTTPS protects the connection to a site. A fraudulent site can still receive information entered into its encrypted pages. FTC: HTTPS and public Wi-Fi

Encrypted DNS protects a lookup

DNS translates a website name into a network address. Mozilla explains that DNS over HTTPS encrypts this lookup to the chosen resolver. That resolver can see the queries; its handling of them remains part of the privacy question. Mozilla: encrypted DNS scope

A VPN changes the intermediary

The FTC explains that a VPN can route traffic through its servers and present its server address to a website. Its 2018 guidance emphasizes the trust placed in the VPN operator and the need to examine encryption, permissions and sharing practices. Websites can still use identifying information supplied to them. FTC: VPN trust and limits

Private Relay separates two parts of the route

Apple describes a two-relay design: the first sees the original IP address, while the second connects to the destination using a temporary address. This is the company's description of its design. Availability varies by country or region. Apple: Private Relay design

Apple identifies Safari browsing, DNS resolution and insecure HTTP app traffic as the covered traffic. Do not treat that list as a promise that every application connection is covered. Apple: covered network traffic