Cloud extraction: tokens, backups and legal process

Three routes to phone data in the cloud: provider legal process, credential or token tools, and account-holder export, with Apple, Google and SWGDE sources.

Updated

In short

Data that a phone keeps in the cloud can be reached in at least three ways: legal process served on the provider, forensic tools that authenticate with an account's credentials or tokens, or an export the account holder runs; SWGDE also lists physical search of provider hardware and other authorities. The sources suggest that what each route yields depends on what the provider holds and who holds the keys; no source states this as a rule. Apple states that with Advanced Data Protection it cannot decrypt iCloud Backup, Photos, iCloud Drive or Notes, though email, contacts and calendars may still be provided on a warrant and some metadata stays under standard protection, and one tool vendor (Elcomsoft) says Apple's protocol changes regularly break forensic tools. SWGDE says legal authority must be established before any cloud acquisition, that the law on using access tokens is still developing, and that local rules may vary on the legality of using tokens, so this guide states no legal conclusion about any route.

SWGDE 23-F-004-1.1 (version 1.1, 2025-01-13) says that where compulsory process is necessary, legal process to the provider is typically the preferred option, and that the provider may be able to supply data in a common file format or provide a tool to access it (SWGDE 23-F-004).

Apple. Apple's Legal Process Guidelines for US agencies (the copy retrieved on 2026-11-10 is marked "Published October 2025") say that, outside emergencies, Apple provides content only in response to a search warrant issued on probable cause, or with customer consent. They say iCloud content under standard protection can include email, photos, documents, contacts, calendars, Messages and iOS device backups, and that a backup may include Camera Roll media, device settings, app data, iMessage, SMS and MMS messages and voicemail.

Under Advanced Data Protection (ADP), the guidelines say Apple cannot decrypt certain iCloud content, including Photos, iCloud Drive, Backup, Notes and Safari Bookmarks, while email, contacts and calendar content can still be provided on a warrant. The guidelines add that in some circumstances Apple may retain limited information related to the categories it cannot decrypt, obtainable if available with a court order under 18 U.S.C. 2703(d), an equivalent court order, or a search warrant. Apple's iCloud data security overview (published 2026-01-05) gives the category table behind this: 15 categories are end-to-end encrypted under standard protection and 25 with ADP. It also lists metadata that stays under standard protection even with ADP, for example the device name, model and serial number behind each backup and the date, time and size of each backup snapshot. Under standard protection, the overview says Messages in iCloud is end-to-end encrypted when iCloud Backup is off, and that a backup includes a copy of the key when it is on; the guidelines list Messages among producible iCloud content (standard section). Under ADP the overview says Messages in iCloud is always end-to-end encrypted, including the key inside an ADP backup; the guidelines' ADP section lists email, contacts and calendars. Neither document says how these statements apply to a given account, so this guide draws no conclusion.

Google. Google's policy page says US authorities must at least use a subpoena for basic subscriber registration information and certain IP addresses, a court order for non-content records in criminal cases, and a search warrant for content such as email, documents and photos. It says Google emails the user (or the administrator, for a managed account) before disclosing, but may not give notice when legally prohibited, when the account is disabled or hijacked, or in emergencies. Google's transparency FAQ gives examples for four services (Gmail, YouTube, Google Voice, Blogger) of subscriber, non-content and content categories, and says disclosure depends on the legal authority, the scope of the request and what is available. It says Google requires valid legal process for a government request even when the request is made on the user's behalf, absent an emergency situation.

None of the Google pages reviewed lists encryption status per data category, as Apple's overview does. For Android, the Android Developers documentation says app-data backups go to the user's Google Drive, are end-to-end encrypted on Android 9 and higher using the device PIN, pattern or password, and are limited to 25 MB per app. The sources reviewed do not say how such a backup is treated in a legal production.

What comes back. SWGDE 23-F-004-1.1 says provider data may arrive in a proprietary format, so a provider may supply it in a common file format or with a tool to read it; the sources reviewed do not describe the file format of any particular provider's return. Magnet's AXIOM 10.0 post (2026-04-20) says the release adds support for Google Search Warrant Returns, and the LEAPPs project index describes RLEAPP as a parser for ISP and provider warrant returns such as Google, Meta and Snap (LEAPPs index). See Magnet AXIOM for the directory entry.

Route 2: credential and token-based acquisition

Here a forensic tool authenticates to the provider as the account. The NIST CFTT cloud data extraction specification (version 1.1, January 2025) scopes itself to tools that work "only using account credentials" to establish connectivity, acquire authentication tokens and extract and report artifacts. It defines a token as "Authentication data similar to a password that is stored on a user's device and allows access to a cloud service", and notes that authentication can fail under two-factor authentication even when the correct credentials are supplied.

SWGDE 23-F-004-1.1, section 8.3, says some tools collect cloud data using credentials harvested from a mobile acquisition and that the cloud data may require additional legal process. It says certain tools may not bypass multifactor authentication, so access to a separate account or a physical device may be needed. On tokens it says their use to gather user cloud data is a complex legal issue, that courts may treat it as equivalent to acquiring the contents, that the law is still developing, and that local rules may vary on legality even with a search warrant; it advises consulting counsel before using the method outside consent.

What the vendors in the directory state, with dates:

  • Cellebrite. Its October 2024 FAQ describes PA Cloud as extracting cloud-based data "using device-based tokens or known credentials". A 2020-11-09 Cellebrite guide describes exporting cloud packages that contain tokens and passwords collected from the device, and says consent or legal rights are required (Cellebrite guide). See Cellebrite PA Cloud.
  • Elcomsoft. The vendor's 2026-04-30 post carries a product blurb saying the tool can use an Apple ID and password, or binary authentication tokens extracted from computers, hard drives and forensic disk images; the article text itself says Apple blocked older protocols in January and February 2026 but does not say which of these Phone Breaker 11 uses. It lists what the tool then recovered (synchronized data and iCloud Drive, and iCloud backups with a stated stability problem: larger backups may interrupt or fail after several gigabytes) and what it could not: Health data, iCloud Keychain, Messages and some Maps and Safari data, which the vendor attributes to end-to-end encryption (Elcomsoft blog). A later vendor note (2026-10-06, version 11.05) says Apple adjusts cloud protocols and storage formats regularly and without notice, which regularly breaks forensic tools, and that access requires the account credentials including the second factor (Elcomsoft news). The two vendor pages differ on tokens versus credentials and on categories: the October note's generic description lists messages and Keychain records among extractable data, which the April post says could not be extracted; neither page explains the difference. See Elcomsoft Phone Breaker.
  • MSAB. The XRY product page lists XRY Cloud, described as recovering data "from beyond the mobile device itself by examining connected cloud-based storage" (MSAB). The page names online social media and app-based data as typical targets but gives no list of services or authentication method. See MSAB XRY.

How a vendor obtains or replays a token is not documented in the sources reviewed, and this guide does not speculate. NIST's CDX specification treats token handling as an optional feature (requirement CDX-CO-01; assertions CDX-CO-01 and CDX-CO-02 cover selecting tokens and authenticating with an acquired token). NIST's CDX page lists published DHS test reports for named tools, including Cellebrite PA v10.0.100.93 with UFED Cloud v7.66.0.9 (listed 2024-11-06) and Magnet Axiom v8.0.0.39753 (listed 2024-09-19; the PDF covers say January 2024 and May 2024). Each report lists "Password, Token" among the account-profile fields in its Table 1. The Cellebrite report records unsuccessful authentication to One Drive, Facebook and Discord; the Magnet report records successful authentication to Facebook and Instagram but a search that ended in errors with no data reported. None of the pages read says whether a token was used to authenticate in those tests, or whether the tests replay tokens taken from a device or disk image.

Route 3: account-holder export and open-source downloaders

SWGDE 23-F-004-1.1, section 8.2, says provider export tools are a best practice when the collector has consent or has credentials and legal authority, and that data from native export tools may not be as complete as data received from the provider through legal process.

Apple Data and Privacy. Apple's support page says the requester is first verified as the account holder, and the data is posted for 14 days and then removed. The page's category list names iCloud contacts, calendars, notes, photos, mail and documents and does not name device backups. See Apple Data and Privacy.

Google Takeout. Google's help page says users can export data for the Google products they use and that an archive may not include changes made between the request and its creation. See Google Takeout.

Open-source downloaders. icloudpd is a volunteer-maintained command-line photo downloader, and its README at tag v1.33.0 carries a banner seeking a maintainer (README). Its documentation at v1.32.3 (2026-05-30) says ADP accounts are not supported because the tool simulates web access (v1.32.3 docs). The v1.33.0 documentation (release 2026-11-05) adds an opt-in --adp-web-access parameter that needs "Access iCloud Data on the Web" enabled on an Apple device and fails with ACCESS_DENIED without the parameter (v1.33.0 docs). Apple's overview (a different page) says iCloud.com access is disabled by default under ADP and that enabling it gives the browser and Apple temporary access to data-specific keys; neither source states whether icloudpd's "Access iCloud Data on the Web" requirement is the same setting as the iCloud.com data access the overview describes. This guide did not test any tool. GarminDB is a similar service-specific example: its README at v3.9.0 describes downloading a user's own data from Garmin Connect with the username and password in a configuration file (README).

SWGDE says data from a provider's native export tools may not be as complete as data received through legal process (section 8.2) and makes a similar remark about application-specific access protocols (section 8.3); it does not discuss third-party downloaders, and applying the caution to them is this guide's inference.

SWGDE's published listing shows the cloud document as 23-F-004-1.1; the document page gives Version 1.1 (1/13/2025). SWGDE section 8 also lists physical search and seizure of the provider's hardware and emergency disclosure requests, which this guide does not cover. The body text of SWGDE 18-F-003-2.0 (2025-08-21) still points readers to "SWGDE 19-F-002-1.0 Best Practices for Digital Evidence Acquisition from Cloud Service Providers", while its reference list names 23-F-004-1.1; the sources reviewed do not state the numbering link, so treating 19-F-002 as the predecessor is this guide's inference. Cite the version number, as SWGDE's disclaimer requires.

SWGDE 23-F-004-1.1 lists the legal-authority categories as the person seeking their own data, consent, or legal authority such as a warrant or subpoena. It says consent or process covering a local device does not by itself cover data held by a provider, and that data stored outside the collector's country can involve mutual legal assistance treaties, the Budapest Convention, letters rogatory or, in the US, the CLOUD Act. These points vary by jurisdiction, and the document says it is not a substitute for legal advice.

For phone-side context see iOS Secure Enclave and extraction and choosing a mobile forensics tool.

What was not found

No public source reviewed gives a per-service support list for token-based tools or an Android equivalent of Apple's ADP category table. NIST and DHS have published lab reports for named cloud-extraction tools (see Route 2); they test extraction with account credentials, and none of the pages read says whether they exercise tokens taken from a device. Google's pages do not state whether device backups are produced under legal process.

Sources

  1. SWGDE 23-F-004-1.1, Best Practices for Digital Evidence Acquisition, Preservation, and Analysis from Cloud Service Providers (Version 1.1, 2025-01-13)
  2. SWGDE 18-F-003-2.0, Best Practices for Mobile Device Evidence Collection & Preservation Handling and Acquisition (Version 2.0, 2025-08-21)
  3. Apple, Legal Process Guidelines: Government & Law Enforcement within the United States (published October 2025; retrieved 2026-11-10)
  4. Apple Support, iCloud data security overview (published 2026-01-05)
  5. Apple Support, Get a copy of the data associated with your Apple Account (published 2026-09-11; retrieved 2026-11-10)
  6. Google Privacy & Terms, How Google handles government requests for user information (retrieved 2026-11-10)
  7. Google Transparency Report Help Center, Requests for User Information FAQs (retrieved 2026-11-10)
  8. Android Developers, Back up user data with Auto Backup (last updated 2026-10-26)
  9. Google Account Help, Download your Google data (retrieved 2026-11-10)
  10. NIST CFTT, Cloud Data Extraction Specification, Test Assertions and Test Cases, version 1.1 (January 2025)
  11. NIST CFTT, Cloud Data Extraction (CDX) page (updated 2026-05-01; retrieved 2026-11-10)
  12. DHS S&T / NIST CFTT, Test Results for Cloud Data Extraction Tool: Cellebrite PA v10.0.100.93 - UFED Cloud v7.66.0.9 (listed by NIST as 2024-11-06; PDF cover says January 2024)
  13. DHS S&T / NIST CFTT, Test Results for Cloud Data Extraction Tool: Magnet Axiom v8.0.0.39753 (listed by NIST as 2024-09-19; PDF cover says May 2024)
  14. Cellebrite, Inseyets FAQ (October 2024, vendor)
  15. Cellebrite, How to use Physical Analyzer's new cloud feature (2020-11-09, vendor)
  16. Elcomsoft blog, Elcomsoft Phone Breaker 11 Restores iCloud Access (2026-04-30, vendor)
  17. Elcomsoft, Phone Breaker 11.05: iCloud extraction support for iOS 27 and the iPhone 18 range (2026-10-06, vendor)
  18. MSAB, XRY product page (undated; retrieved 2026-11-10, vendor)
  19. Magnet Forensics blog, What's new in Magnet AXIOM 10.0 (2026-04-20, vendor)
  20. LEAPPs project index (retrieved 2026-11-10)
  21. icloudpd, docs/authentication.md at tag v1.33.0 (release 2026-11-05)
  22. icloudpd, docs/authentication.md at tag v1.32.3 (release 2026-05-30)
  23. icloudpd, README at tag v1.33.0
  24. GarminDB, README at tag v3.9.0