Apple

Overview

Apple's presence on third-party websites arises from two distinct integrations: the Apple Maps JavaScript API for embedding interactive maps, and Apple Pay JS for enabling in-browser payment on e-commerce sites. Both are functional tools serving user-initiated purposes and are architecturally separate from Apple's advertising products.

What This Script Does

Apple Maps JavaScript API Apple Maps JS is loaded from cdn.apple-mapkit.com and renders interactive map tiles for store locators, event venues, contact pages, and location-based features. The script:

• Contacts tile.maps.apple.com for map tile assets
• Contacts api.apple-mapkit.com for geocoding, routing, and search queries
• Authenticates using a MapKit JS token issued by the site operator's server
• Logs map interaction events (pan, zoom, marker selection) to Apple's infrastructure for service operation
• Does not set persistent tracking cookies for cross-site advertising or behavioral profiling
• May store transient session state in memory to support smooth map rendering

Apple Pay JS Apple Pay JS is loaded from applepay.cdn-apple.com and enables in-browser Apple Pay payment flows. The script:

• Calls ApplePaySession.canMakePayments() to detect whether the user's device and browser support Apple Pay — this occurs without any network request and is local-only
• Contacts apple-pay-gateway.apple.com (or cn-apple-pay-gateway.apple.com for China) to initiate and validate payment sessions when the user taps Pay
• Exchanges encrypted payment tokens with Apple's servers — the merchant server never sees raw card data
• Handles the user's biometric (Face ID, Touch ID) or passcode authentication for payment authorization
• Sets session-scoped cookies only for the duration of the payment flow
• Communicates transaction details (merchant ID, amount, currency, domain) to Apple for session creation

Neither Apple Maps nor Apple Pay is used for cross-site behavioral tracking, audience building, retargeting, or advertising profiling.

Domains contacted:

• Maps: cdn.apple-mapkit.com, tile.maps.apple.com, api.apple-mapkit.com
• Pay: applepay.cdn-apple.com, apple-pay-gateway.apple.com, cn-apple-pay-gateway.apple.com

No persistent tracking cookies are set by either integration. Session storage during the payment flow is transient and scoped to completing the transaction.

Consent & Compliance

GDPR/ePrivacy: Apple Maps serves a functional purpose directly requested by the user — viewing a location on a map. Apple Pay processes a payment transaction initiated by the user, covered by contractual necessity under GDPR Article 6(1)(b). Neither script performs behavioral profiling or sets advertising cookies. The ePrivacy Directive's strictly necessary exemption applies to cookies and storage used exclusively for completing a user-requested transaction or rendering a user-requested map.

CCPA/CPRA: Apple Pay's payment processing is a necessary transaction function, not a sale or sharing of personal information for advertising purposes. Apple's privacy practices contractually limit data use to service provision.

EU-US Data Transfers: Apple Inc. participates in the EU-US Data Privacy Framework (DPF) and uses Standard Contractual Clauses for international transfers of personal data.

Consent category: Essential (Apple Pay payment processing) and Functional (Apple Maps).

Should You Block This Without Consent?

No. Apple Maps and Apple Pay serve functional purposes directly initiated by users — location display and payment processing respectively. Neither performs advertising tracking or cross-site behavioral profiling. They can load without prior consent under the strictly necessary and contractual necessity grounds. Disclose these services in the site's privacy policy to explain payment processing and mapping service providers.