{"id":69241,"date":"2026-06-16T03:11:00","date_gmt":"2026-06-16T01:11:00","guid":{"rendered":"https:\/\/www.apfelpatient.de\/?p=69241"},"modified":"2026-06-16T03:12:18","modified_gmt":"2026-06-16T01:12:18","slug":"apple-bundles-two-privacy-services-under-one-domain","status":"publish","type":"post","link":"https:\/\/www.apfelpatient.de\/en\/news\/apple-buendelt-zwei-datenschutz-dienste-unter-einer-domain","title":{"rendered":"Apple bundles two privacy services under one domain"},"content":{"rendered":"

Those who use "Sign in with Apple" or "Hide email address" will in future receive addresses from a single, shared domain. For most users, the change will go unnoticed \u2013 however, in one respect it is anything but insignificant.<\/strong><\/p>\n\n\n\n

With \"Sign in with Apple,\" users can create accounts with apps and services without revealing their email address<\/a>. This login service and the iCloud+ \"Hide Email\" feature will merge their previously separate address domains. Apple announced the change in a message to developers: This summer, both services will migrate to the new, shared domain private.icloud.com<\/code>.<\/p>\n\n\n\n

What's changing about the domains<\/h2>\n\n\n\n

Previously, the two functions operated using different address spaces. \"Sign in with Apple\" issued its anonymized addresses via the domain privaterelay.appleid.com<\/code>, while \"Hide your email address\" used icloud.com<\/code>. Going forward, both services will issue newly generated addresses uniformly under private.icloud.com<\/code>.<\/p>\n\n\n\n

The randomly generated forwarding addresses from "Hide email address"<\/a> still redirect to the personal inbox \u2013 just under a uniform domain. The functionality itself remains unchanged; only the last part of the new address is standardized.<\/p>\n\n\n\n

Existing addresses remain active<\/h2>\n\n\n\n

Users who have already created email addresses on the existing domains don't need to do anything. Apple clarifies that the old addresses will continue to work and messages will be forwarded without interruption. All other processes will also remain unchanged for end users \u2013 both privacy features will continue to function as usual.<\/p>\n\n\n\n

This new feature joins the ranks of iCloud+ tools that allow users to specifically secure an iPhone<\/a> \u2013 from Private Relay to concealing the real email address.<\/p>\n\n\n\n

What developers and email providers need to know<\/h2>\n\n\n\n

The situation is different on the technical side. Developers whose apps or websites use "Sign in with Apple" must ensure that their account systems, email validation, and any allowlists accept the new domain private.icloud.com<\/code> in addition to existing domains. Otherwise, login attempts with the new addresses may be rejected.<\/p>\n\n\n\n

Email service providers also have a responsibility: Domain-based filters, blocklists, or routing rules that explicitly list the existing relay domains should be updated to include private.icloud.com<\/code>. If the new domain is not registered there, messages may be incorrectly filtered out.<\/p>\n\n\n\n

Routine for users, mandatory for developers<\/h2>\n\n\n\n

The main reason for the change<\/a> is consistency: Instead of two separate address spaces, Apple is consolidating its private forwarding services under a clearly named domain. For most users, this is a change that happens in the background \u2013 while app providers and email services should follow suit in a timely manner so that addresses on private.icloud.com<\/code> work smoothly from the start. (Image: Apple)<\/p>\n\n\n\n