Apple Updates Private Relay Domain for Sign in with Apple: Why Email Cannot Serve as Account Identity
Apple announced that new Private Relay addresses issued through Sign in with Apple will use the private.icloud.com domain later in 2026. Previously issued addresses on the privaterelay.appleid.com domain will continue to forward mail without any interruption or required migration.
At the mail-delivery level the change appears minor, yet it exposes a common architectural mistake: treating the email address returned by Apple as a stable user identity instead of a contact channel. The signed identity token, the verified subject, and the optional relay email must remain separate entities throughout the authentication and account-management layers.
What exactly is changing
Private Relay lets users hide their real email address. The application receives a relay address and Apple forwards messages to the userβs actual mailbox. Apple now states that future relay addresses will be issued under private.icloud.com. Existing addresses keep working, so no database rewrites or allow-list updates are required for mail delivery.
The relay address is never a proof of permanent identity. Users may later disable forwarding, and the sending infrastructure must still be correctly registered with Apple. These facts affect only the mail subsystem, not the authentication flow.
Identity versus contact channel
Sign in with Apple returns a signed identity token containing a stable subject identifier. The email claim is optional and may be absent for managed Apple Accounts or on subsequent logins. Therefore the server must resolve the internal account exclusively from the verified provider and subject pair.
- Identity token β proves the request originated from Apple for the expected application.
- Subject (sub) β stable identifier that links the Apple identity to an internal account record.
- Email (including relay) β used only for message delivery when the user permits it.
Storing only the email or searching accounts by email address creates fragile logic that breaks when domains change or when the email claim is empty.
Recommended data model
Maintain a dedicated auth_identities table with a unique index on (provider, subject). On first successful login the server creates both the internal account and the identity record inside a single transaction. Subsequent logins locate the existing identity by provider and subject, then issue a session for the linked account. No automatic merging occurs on matching email addresses.
Verification steps that must remain on the server
The mobile client sends the identity token, authorization code, and nonce. The server alone performs signature validation, checks issuer, audience, nonce, and expiration, then extracts the subject. Only after this step does the authorization service resolve or create the internal account. Client-supplied subject strings must never be trusted.
Common anti-patterns to avoid
- Searching accounts by the email claim from the token.
- Storing only an email address as the account key.
- Hard-coding checks for the old relay domain.
- Automatically linking accounts when email values appear similar.
Each of these patterns risks duplicate accounts or unauthorized merges and will surface problems the moment Apple alters relay domains again.
Testing strategy
Tests should assert behavior around the verified subject rather than any specific domain suffix. Key scenarios include first login creating a single account, repeated logins returning the same account, parallel first-login attempts producing only one record, and tokens with invalid issuer or nonce being rejected before any account operation occurs.
When the system already uses email as a key, the migration path begins by adding the proper identity model and stopping new incorrect linkages. Existing conflicts are resolved through explicit user confirmation rather than automated scripts.
Related articles
Pocket Android: Open-Source App Uses Work Profiles to Isolate Apps Behind Dedicated Proxies
A developer has released Pocket Android, a free open-source application that leverages Android's built-in Work Profile feature to create an isolated environment for selected apps. The tool routes traffic from cloned applications exclusively through user-defined proxies while keeping banking, delivery, and government services in the main profile on direct connections. It addresses common failures of per-app exclusion lists by enforcing strict lockdown policies that prevent leaks after reboots or proxy drops. The project builds on the Shelter codebase and integrates Xray for protocol support including VLESS, REALITY, and Hysteria 2. Battery impact is minimized through event-driven status checks rather than constant timers. The approach provides practical privacy separation for services sensitive to IP changes such as Claude and ChatGPT without requiring manual proxy switching throughout the day.
Telegram Beta for macOS Introduces Hidden Chats Feature Protected by Secret Passphrase
The beta version of Telegram 13.2.0 for macOS now includes a Hidden Chats function that lets users move selected chats and channels out of the main list into a separate section accessible only via a secret passphrase. Users configure the feature in the privacy settings by entering a passphrase of at least eight Latin characters twice. Multiple passphrases can be created, each unlocking its own set of hidden conversations. The hidden section automatically closes after screen lock, sleep mode, or five minutes of inactivity, and calls from hidden chats are silenced. The passphrase is not stored anywhere on the device, so forgotten credentials require logging out and back in to regain access on that computer. The feature is device-specific and does not sync across platforms, meaning hidden chats remain visible in the main list on smartphones and other clients.
Windows 11 Telemetry Secretly Tracks AI Coding Agents and Developer Tools via MissionControlAggregator
Reverse engineering of Windows 11 binaries revealed a hardcoded list of coding agents and developer tools inside MissionControlAggregator.dll. The component monitors launches of applications such as codex.exe, claude.exe, copilot.exe, cursor.exe, python.exe, gcc.exe and code.exe through existing ETW events from KernelProcess and Win32kTraceLogging. Detected usage is stored as bit flags in SubCohorts reports and sent to Microsoft when optional diagnostic data is enabled, which remains the default on US installations. Researchers confirmed the mechanism by renaming cmd.exe to codex.exe and observing the corresponding bit set in Segments.SubCohorts events queued by DiagTrack. The feature CLICodingAgentUsage (ID 62580080) categorizes both CLI and desktop agents without collecting prompts or source code. Data collection occurs on standard Windows 11 ARM64 builds and persists in AggregatorStorage even without user interaction with the listed tools.
Meta Fined β¬805 Million by Italian Data Protection Authority for Unauthorized Access to Android Photo Gallery
The Italian data protection authority Garante has imposed an β¬805 million fine on Meta for improper access to users' photo galleries via the Facebook Android app. The feature, active by default since 2023, allowed continuous reading of images and metadata without explicit, separate consent from approximately 20 million Italian Android users. The authority ruled that the single broad permission request violated Article 122 of the Italian Privacy Code, which implements the EU ePrivacy Directive and treats device storage as part of private life. Meta must now implement separate consent mechanisms, provide clear explanations, and keep the feature disabled by default within 60 days or face further restrictions. The company plans to appeal the decision, describing the penalty as disproportionate, while the investigation originated from a consumer complaint in Bolzano and included technical analysis by the regulator. The fine accounts for the scale of affected users, the ongoing nature of the violation, prior enforcement actions, and limited cooperation.