How to Export All Your Data From Google and Apple (and Verify It)

To export everything from Google, sign in at takeout.google.com, keep every product ticked, choose a delivery method, file type and archive size, and download the archive Google emails you within about 7 days. To export from Apple, sign in at privacy.apple.com, select "Request a copy of your data", pick the categories, and download the files from the same page within 14 days of Apple posting them. Then test every archive, record SHA-256 hashes, encrypt at least one offline copy, and only after that consider deleting either account.

Below: each step as Google and Apple document it, the formats, what neither export includes, how to prove the export is complete, safe storage, and each company's stated deletion timelines. Every step and number comes from Google's or Apple's help pages or the checking tools' official documentation, linked under Sources.

Key takeaways

• Exporting does not delete anything. Google says so at the top of its Takeout help page. Deletion is a separate, later step.
• Google archives expire in about 7 days and can be downloaded 5 times. Apple keeps your files on its page for 14 days.
• Neither export is everything. Google leaves out data that is mid deletion and some recent changes. Apple leaves out end to end encrypted data it cannot decrypt, Messages content and the purchased media itself.
• Verify before you trust it. Test each archive, count items against what the service shows, and keep a SHA-256 manifest so you can prove later copies are intact.
• Your export is now the most sensitive file you own. Encrypt it, keep one copy offline, and remove it from any cloud folder you used for delivery.
• Deletion timelines differ. Google states that deletion "generally takes around 2 months" plus up to 6 months in encrypted backups. Apple states no day count for account deletion.

Google Takeout and Apple Data and Privacy compared

Before the step by step, here is how the two exports differ on the points that decide how you plan the job. Every cell comes from the companies' own help pages.

Before you start: a ten minute preparation checklist

1. Use a desktop or laptop computer. Google recommends "downloading and viewing Takeout exports from a desktop computer, not a mobile device." Apple says to "use a Mac or Windows PC to download and view your data files."
2. Find every account. Each Apple Account is separate, and Apple says you must "sign in to each account individually and submit a request for each account." On Google, YouTube channels can sit under a Brand Account, which you have to switch to before exporting its videos.
3. Check for work and school accounts. Google Workspace administrators can block Takeout for a product. A school managed Apple Account needs the administrator to allow sign in to the Data and Privacy page first.
4. Make sure you can pass a security prompt. Google asks you to re-enter your password before download, and may ask for a 2-Step Verification step. Have your phone or security key nearby.
5. Free up disk space and prepare encryption. Plan for twice the export size, and set up the encrypted destination described later before downloading.
6. Pause clean up. Google warns that items "still in the process of being deleted are not included in your archive." Empty the trash later, not now. Restore anything in Google Photos trash or Locked Folder that you want to keep before a Photos transfer.
7. Note your current numbers. Write down today's counts of photos, contacts, events and mail to compare during verification.

How to export your Google data with Takeout, step by step

These steps follow Google's help page "How to download your Google data". The page notes that if your actions "seem risky", Google may delay them to protect your account.

Step 1: select the data to include

1. Sign in to your Google Account.
2. Go to the Google Takeout page. Products that hold your data are selected automatically.
3. Untick any product you do not want. For a full export, leave everything ticked.
4. Some products offer a button such as All data included. Use it to drop specific data from a product, for example particular photo albums.
5. Select Next step.

Takeout does not support date ranges. Google states, "we do not currently support exporting data for certain time frames," and the same applies to Gmail.

Step 2: choose delivery, frequency, file type and size

Delivery method. Google offers five:

For each non Google destination, Google states that once the files are uploaded "Google is no longer responsible for the files," and the destination's own terms apply. The email link keeps the fewest copies in the fewest places.

Export type. Choose a one time archive, or scheduled exports that "automatically create an archive of your selected data every 2 months for one year." For Google Photos alone, scheduled exports can cover only new and updated items. Scheduled exports are not available with the Advanced Protection Program.

File type. Zip "can be opened on almost any computer". Tgz may need extra software on Windows, and Google notes that tgz files "can't have unicode characters in the file names." If your Drive or Photos contain file names in non Latin scripts, zip is the safer choice.

Archive size. You pick a maximum size. Anything larger is split into several archives. Google suggests the 50GB option to reduce splitting.

Select Create export.

Step 3: download the archive

Google emails you when the archive is ready. "Most people get the link to their archive the same day that they request it," but it can take a few days for a large account. If you use the Advanced Protection Program, the archive is scheduled two days in the future.

Open the link, sign in again when asked, and download every part. Remember two limits from Google's page:

• The archive "expires in about 7 days."
• Each archive can be downloaded 5 times.

If an archive fails, Google's advice is to create another one, or to export one product at a time.

What Takeout leaves out

Google's help pages list several gaps you should know before you treat Takeout as complete:

• Data being deleted. Items from My Activity, photos or documents that are mid deletion are not included.
• Changes during the export. Your archive "may not include changes made to your data between when you request a download and when you create your archive," for example Drive sharing changes, resolved Drive comments, and photos or albums added or deleted.
• Brand Account content. YouTube videos uploaded through a Brand Account need the Brand Account selected.
• Google Groups. Only owners can download a group's messages and membership.
• Workspace restrictions. Your administrator can block Takeout for work or school accounts.
• Purchased content. Google's account deletion page warns you lose apps, movies, music and other purchases from Google Play and YouTube. Takeout gives you your data, not a licence to keep that media.

Moving Google Photos directly to another service

To move photos rather than archive them, Google offers a transfer from the Takeout photos view: choose albums, pick a destination, sign in and authorise. Google lists what does not move:

• Failed videos and broken photos that cannot be displayed
• Locked Folder content, unless you move it out first
• Unsaved memories and creations
• The video portion of Motion Photos and Live Photos, unless you save them as videos
• Manually edited metadata, such as comments
• Trash content, unless you restore it

Transfers are not available for children's, work or school, or Advanced Protection accounts. A transfer copies to another cloud; it is not an offline backup.

How to export your Apple data, step by step

These steps follow Apple's support article "Get a copy of the data associated with your Apple Account". Apple notes that access to this feature "varies by country and region."

Step 1: request the copy

1. Sign in to your Apple Account on Apple's Data and Privacy page, privacy.apple.com.
2. Select Request a copy of your data.
3. Select the data you want. If the option is missing, Apple says the feature "is not available in your country or region."
4. In the EU, UK or Japan, you can schedule a one time or recurring download for certain data, daily for 30 days or weekly for 180 days.
5. Select Continue.

Step 2: wait for verification and preparation

Apple first verifies that you are the account holder. It then organises the data and posts it to your Data and Privacy page, and notifies you. Apple's help page does not give a number of days for this stage. Its privacy policy says that, in most cases, substantive privacy contacts "receive a response within seven days", which covers inquiries about access or download requests, not the preparation time itself.

Step 3: download within 14 days

Apple states: "You have 14 days to download your data, after which it is removed from that location, and you will need to request it again." Download every file to a Mac or Windows PC.

If you want to add categories later, you can, but for a second request for a category you already asked for, Apple says to wait until the current request "is completed and removed from your Data and Privacy page."

What Apple's copy includes

Apple lists, among other things:

• Apple Account details, profiles created for Apple TV, and sign in records
• iCloud data: contacts, calendars, notes, bookmarks, reminders, email, photos, videos and documents
• App usage information for iCloud, Apple Music, Game Center and other services
• A record of App Store, iTunes Store and Apple Books purchases and downloads, and your browsing history in those stores
• Apple Store and support transaction records
• Marketing communication records and preferences

What Apple's copy leaves out, and why it matters

Apple's page is explicit that data is not provided when it is not personally identifiable, is "stored in an end-to-end encrypted format that Apple cannot decrypt," or is not stored by Apple at all. That has practical consequences:

• Messages. Apple says Messages content is not in the data request because messages "are encrypted on your device."
• Health. Health data is always end to end encrypted. Apple also lets you export it in the Health app: tap your profile, then Export Health Data.
• Advanced Data Protection. Apple's iCloud security overview lists 15 data categories that are always end to end encrypted, including passwords and Keychain, Health, Journal, Home, Messages in iCloud, payment information and Wi-Fi passwords. Turning on Advanced Data Protection raises that to 25 and adds iCloud Backup, iCloud Drive, Photos, Notes, Reminders, Safari Bookmarks, Voice Memos, Wallet passes and more. Putting Apple's two pages together, if Advanced Data Protection is on, expect to copy those categories from a trusted device signed in to your account rather than from the Data and Privacy request.
• Purchased media. Apple provides the list of what you bought, not the files. "The actual content that you purchased is not personal data." Redownload what you need from the App Store, iTunes Store, Apple TV app and Apple Books before you delete anything.
• Masked details. Card and bank details, device identifiers and email addresses are masked "for your security".
• Separate requests. AppleCare case notes and call transcripts, Retail Customer Care transcripts (in some countries) and FaceTime invitation logs are requested separately; Apple names privacy_response@apple.com for the first two.

Transferring iCloud Photos or Apple Music playlists

Apple's Data and Privacy tools can also transfer a copy of your iCloud Photos collection and Apple Music playlists to another service. Keep a local archive too.

What formats will you get?

Knowing the formats tells you which apps will open the files and how to count what is inside.

Google's archive includes a file named archive_browser.html that explains the format of each folder and how to open it. Read it first. Apple provides PDF file guides for files created by its apps and services, though not for your own content such as emails, notes or photos.

Two traps: Apple warns some spreadsheet apps "might automatically round certain large numbers", such as account numbers. Google warns downloaded photos may get a new file timestamp while the embedded metadata keeps the original, so sort by capture date.

How do you verify the export is complete and intact?

Neither company gives you a "your export is complete" check, so build one in four layers: did every file arrive, does every archive open, does the content match the service, and can you prove later copies are identical.

Layer 1: confirm every part arrived

When Takeout splits an export, you get several archive files. List the folder and check that the file names form a complete sequence with no gaps and that no part is suspiciously small. The file names in the commands below are examples; use the names in your download. Partial downloads often leave a file with a temporary extension or a size far below the others.

For Apple, compare the list of files on your Data and Privacy page with what is in your download folder.

Layer 2: test that every archive opens

Do not just double click one archive and assume the rest are fine. Test each one.

For zip archives on macOS or Linux, Python's built in zipfile module has a documented test option:

# Test one Takeout zip without extracting it
python3 -m zipfile -t takeout-20261023T120000Z-001.zip

# Test every zip in the folder
for f in takeout-*.zip; do echo "$f"; python3 -m zipfile -t "$f" || echo "FAILED: $f"; done

For tgz archives, GNU tar can list an archive's contents, which reads it end to end:

# A clean listing that ends without errors means tar could read the whole archive
tar -tzf takeout-20261023T120000Z-001.tgz > /dev/null && echo OK

On Windows, extract each zip with File Explorer into its own folder and watch for errors. Takeout's tgz files may need extra software on Windows, as Google notes, which is one reason to choose zip there.

Layer 3: check the content against what the service shows

1. Open archive_browser.html. It lists the products in your Google archive. Compare that list with the products you selected.
2. Compare against your Google Dashboard. Google's "Get a summary of data in your Google Account" page shows the services you use and the data saved in each. Not every service appears there.
3. Count contacts. Every vCard object begins with a BEGIN:VCARD line, per RFC 6350, so you can count them:

grep -c "BEGIN:VCARD" Takeout/Contacts/*/*.vcf

4. Count calendar events. In the iCalendar format (RFC 5545), each event begins with BEGIN:VEVENT:

grep -c "BEGIN:VEVENT" Takeout/Calendar/*.ics

5. Count mail. If archive_browser.html says your mail is in the mbox format, RFC 4155 explains that each message begins with a line starting "From ". A count of those lines is a close estimate, because the RFC describes body lines that start with "From " being escaped with an extra character so they are not mistaken for a new message:

grep -c "^From " "Takeout/Mail/All mail Including Spam and Trash.mbox"

The exact file name can differ; use the one in your archive. For Apple's .eml export, count files instead:

find ./AppleData -type f -name "*.eml" | wc -l

6. Count photos and videos. Count files by extension and compare with the item count in Google Photos or the Photos app. Remember that Google Photos exports often include a JSON file per item for extra metadata, so exclude .json from the count:

find ./Takeout/"Google Photos" -type f ! -name "*.json" | wc -l

7. Open samples. Open a handful of documents, a few videos, an old email and a recent one in a different app from the one you used before. A file that counts correctly but will not open is not backed up.

Small mismatches usually have honest causes: items mid deletion, items added after your request, or shared albums you did not own. Large mismatches mean a product or part failed; request a fresh export for that product alone.

Layer 4: record hashes so you can prove later copies are identical

Once the archives pass layers 1 to 3, record a SHA-256 hash of every archive file. Then, every time you copy the export to another drive, you can check that nothing changed in transit or in storage.

On Linux, GNU coreutils provides sha256sum, and its check option reads a manifest and reports whether each file still matches:

cd ~/exports/google-2026-10-23
sha256sum takeout-*.zip > ../google-2026-10-23.sha256

# Later, on the backup drive
cd /media/backup/google-2026-10-23
sha256sum -c ~/exports/google-2026-10-23.sha256

On macOS, the shasum tool takes the algorithm as a number and supports the same check mode:

cd ~/exports/apple-2026-10-23
shasum -a 256 * > ../apple-2026-10-23.sha256
shasum -a 256 -c ../apple-2026-10-23.sha256

On Windows, PowerShell's Get-FileHash uses SHA256 by default:

Get-ChildItem C:\Exports\google-2026-10-23 -File |
  Get-FileHash -Algorithm SHA256 |
  Select-Object Hash, Path |
  Export-Csv C:\Exports\google-2026-10-23-sha256.csv -NoTypeInformation

Re-run the same command against the copy and compare the two CSV files.

Keep the manifest file next to every copy, and keep one more copy of it somewhere separate. A manifest stored only on the drive it describes cannot catch that drive being swapped or rewritten.

How should you store the export safely?

A full export holds your mail, contacts, location history, photos and often scans of identity documents, with none of the account's sign in protection. Treat it accordingly.

Encrypt it at rest

Use the encryption your operating system already documents:

Apple's Disk Utility guide warns, "If you forget this password, you won't be able to open the disk image." Store the passphrase somewhere separate and durable, such as a sealed paper copy.

For a single archive file, GnuPG's symmetric mode is portable across platforms:

# Encrypt with a passphrase; produces takeout-001.zip.gpg
gpg --symmetric takeout-20261023T120000Z-001.zip

# Decrypt later
gpg --output takeout-20261023T120000Z-001.zip --decrypt takeout-20261023T120000Z-001.zip.gpg

Hash the encrypted file too, and add it to your manifest, so you can check the encrypted copies without decrypting them.

Keep at least one copy offline

CISA's ransomware guidance tells organisations to "maintain offline, encrypted backups of critical data" and to test them regularly, because ransomware tries to find and encrypt reachable backups. The same logic applies at home: an unplugged drive cannot be encrypted by malware on your laptop.

We cover the reasoning and the routine in why offline backups on removable media still matter, and the trade-offs of drives with their own keypad and encryption in hardware encrypted USB drives and bootable recovery media. A simple, defensible personal setup is:

1. One encrypted working copy on your computer, used while you migrate.
2. One encrypted copy on an external drive kept unplugged at home.
3. One encrypted copy on a second drive kept somewhere else, such as with a family member.
4. The SHA-256 manifest stored with each copy, plus one separate copy of it.

Check each drive against the manifest once a year; drives fail quietly.

Clean up the places the export passed through

• Cloud delivery folders. If you used Drive, Dropbox, OneDrive or Box, delete the archive there once your offline copies verify. Google notes that a Drive archive counts toward your storage and must be moved before you delete your Google Account.
• Connected app access. Google says "Google Download Your Data" stays listed as an app with access in OneDrive and Box. Remove that access when you are done.
• The Downloads folder. Move the archives into your encrypted destination, then delete the unencrypted originals and empty the trash.
• Password exports. If you exported saved passwords to move them, that file is plain text. Google's own import guide tells you to delete the .CSV password file after importing it. Do the same with any password export.

Watch for lookalike emails

Both companies email you when an export is ready, which makes a copied "your data is ready" email an easy lure. If anything looks off, type takeout.google.com or privacy.apple.com yourself instead of clicking.

How do you delete your Google and Apple accounts properly?

Delete only after the export passes all four layers and two encrypted copies exist.

Order of operations

1. Move every account that uses your Gmail or iCloud address for sign in, password resets or two factor codes to a new address. Google specifically says to add a new email address for online banking, social media and apps.
2. Move any authenticator app or security key enrolments that depend on the old account.
3. Redownload purchased media you want to keep and cancel subscriptions.
4. For Apple: cancel AppleCare plans that block deletion, spend or transfer Apple Cash, settle any balance, and sign out of iCloud on every device so Activation Lock does not trap you later.
5. Request deletion.

Deleting your Google Account

Google's steps from "Delete your Google Account":

1. Go to the Data and Privacy section of your Google Account.
2. Scroll to "Your data and privacy options."
3. Select More options, then Delete your Google Account.
4. Follow the instructions.

Deleting one Google Account does not delete others you own. If you only want to drop Gmail, Google lets you delete the Gmail service while keeping the account, as long as you add and verify another email address for sign in. If the account was hacked, run Security Checkup first; you cannot review that activity after deletion.

Deleting your Apple Account

Apple's steps from "How to delete your Apple Account":

1. Sign in on Apple's Data and Privacy page on a Mac, Windows PC, iPhone, iPad or Apple Vision Pro.
2. Select Request to delete your account.
3. Keep the unique alphanumeric access code Apple gives you. "For a short period of time" while the request is processed, Apple Support can use it to cancel the request.

Apple also offers temporary deactivation in some countries and regions, which keeps your data intact but blocks access, and is reversible with the access code. If you are not certain, deactivate first.

Read Apple's consequences in full: iCloud content is permanently deleted, a Family Sharing group is disbanded, and child accounts in the group are included in the deletion unless you transfer them first.

What deletion timelines do Google and Apple state?

These are the companies' own statements. Neither gives a guaranteed date for your specific account, and both list exceptions for legal and financial records.

Two practical points follow. First, Google's numbers mean copies can persist in its encrypted backups for months after you delete, so do not count on deletion as a quick fix. Second, an Apple Account email address may not be reusable for a new Apple Account "for several years", and an address on a custom email domain can never be reused for a new Apple Account.

For how organisations handle deletion inside backups, see deleting personal data from backups.

What do you lose, and what are the security trade-offs?

Exporting is low risk; deleting is where the trade-offs live. After Apple deletion you cannot turn off Activation Lock, and DRM protected purchases stop working or updating. Google warns you lose Play and YouTube purchases. Your old address may be the recovery route for dozens of other services. And once the account is gone, your data has only the protection you give the export: no provider sign in checks, no 2-Step Verification, just your encryption and your drawer.

Common mistakes

• Deleting before verifying. An archive that downloaded but will not open is not a backup. Run all four verification layers first.
• Letting the window expire. Google archives expire in about 7 days and allow 5 downloads; Apple's files go after 14 days. Start the download as soon as the email arrives.
• Choosing tgz on Windows, or with non Latin file names. Pick zip unless you have a reason not to.
• Assuming Apple's copy contains everything. Messages content is not included, and with Advanced Data Protection on, Photos, iCloud Drive and Notes are end to end encrypted, so copy them from a trusted device.
• Emptying the trash before exporting. Items mid deletion are left out of Takeout.
• Leaving the archive in the cloud destination. If you exported to Drive, Dropbox, OneDrive or Box, the archive stays there until you delete it, under that provider's terms.
• Keeping an unencrypted copy in Downloads. Encrypt, then remove the plain copy.
• Storing the only manifest on the backup drive. Keep a separate copy so it can catch the drive itself changing.

Where Safeguard fits, honestly

Safeguard does not export, store, encrypt or delete personal data from Google or Apple, and it is not a replacement for any consumer service in this guide. Exporting and leaving an account is a job for the tools Google, Apple and your operating system provide.

The connection is one step back: the apps you install next, and the software your team builds, are a supply chain of open source components with vulnerabilities of their own. For that code, Safeguard scans repositories, container images and SBOM files, matches components against vulnerability databases, uses reachability analysis to rank the findings your code actually calls, and can open fix pull requests when a safe version exists. Remediation ships switched off by default.

Fix it without waiting for upstream

Verifying an export is about not trusting a copy until you have checked it. The same principle applies to the open source your software is built from: knowing a vulnerable version is in your build is only useful if the fix arrives quickly.

Whatever the vulnerability, most of the risk sits in two gaps. The first is the time between a fix being published and that fix actually running in your production builds. The second, and worse, is the time before any fix exists at all, while a maintainer works out a patch and a release schedule. Waiting through both gaps is a habit, not a requirement. Safeguard gives teams three ways to close them.

1. Autonomous remediation: pull requests, not tickets

When a fixed version exists, Safeguard's Griffin models open a tested, policy gated pull request that moves the affected dependency to the safe version. You can run it on one repository or in bulk across every project that carries the vulnerable version. Remediation covers eight categories, including dependencies, licenses, security posture and findings. Reachability analysis ranks the vulnerable code paths your application actually calls first, so the first pull requests you merge are the ones that matter most. Autonomous remediation ships switched off, with every category set to Manual, so your team decides how much runs on its own and what still needs a human approval.

2. Gold Open Source: the safe version in seconds, free

gold.safeguard.sh is free and needs no login. Search any CVE or package to see affected and fixed versions, CVSS, EPSS, CISA KEV status and a recommended safe version, or use the "Am I affected?" checker. The same data is available through a free read API, README status badges and RSS threat feeds. The safeguard-sh/gold-scan-action GitHub Action can fail a build on a known exploited vulnerability, on any known vulnerability, or never, so a version you have just removed cannot quietly come back in next week's merge.

3. Gold Registry: start from components that are already fixed

registry.safeguard.sh provides hardened, drop in replacements for upstream packages and container images. Every Gold artifact is held continuously to zero exploitable critical or high CVEs, zero malware and a completed license check, with SLSA L3 or higher provenance, a Sigstore signature and a public evidence page you can hand to an auditor. An artifact loses its Gold badge if it regresses. Teams can point their own package directory at the registry so hardened equivalents resolve without changing how developers install anything.

When upstream has no fix yet, or will not ship one, Safeguard first works to get the fix accepted upstream. If the issue is severe or upstream will not move, Safeguard builds a fork, fixes the vulnerability there and publishes a hardened Gold build, so you are not stuck on a maintainer's release schedule. You can also request a hardened, compatibility tested build of a specific package. This fork and patch flow is in early access today, so ask which packages it covers before you plan around it.

One honest limit: when the vulnerable code lives in a vendor appliance, a hosted service or an operating system runtime you do not build yourself, the fix still has to come from that vendor or distribution. The steps above apply to the open source dependencies and container images you build and ship, which is where most teams carry the largest and least tracked share of their exposure.

FAQ

How do I download all my Google data at once?

Go to takeout.google.com, leave every product selected, choose Send download link via email, a one time export, zip and the 50GB archive size, then select Create export. Download every part from the email within about 7 days. Each archive can be downloaded 5 times.

How long does Google Takeout take?

Google says it can take "from a few minutes to a few days" depending on how much data you have, and that most people get the link the same day. Accounts in the Advanced Protection Program have archives scheduled two days in the future.

How do I get a copy of all my Apple data?

Sign in at privacy.apple.com, select Request a copy of your data, choose the categories and select Continue. Apple verifies your identity, posts the files to the same page and notifies you. Download them within 14 days.

Why are my iMessages not in my Apple data download?

Apple says messages are encrypted on your device and cannot be accessed without your device passcode, and Messages in iCloud is always end to end encrypted, so Apple cannot provide it.

How do I know my Google Takeout export is complete?

Test every archive, confirm each product in archive_browser.html, compare item counts against what Google shows, and spot check files in a different app.

How long does Google keep my data after I delete my account?

Google says deletion "generally takes around 2 months," often including up to a month long recovery period, and data can remain in encrypted backups for up to 6 months. Some data is kept longer for legal, financial and security reasons.

How long does Apple keep my data after I delete my Apple Account?

Apple gives no day count. Data is permanently deleted after Apple verifies the request, except legal, regulatory and transaction records. A one way hash of your email address is kept, deleted after six years for third party domain accounts.

What is the safest way to store my Google and Apple export?

Encrypt it with your operating system's tools, keep at least one copy on a drive that stays unplugged, store a SHA-256 manifest with each copy, and delete unencrypted and cloud copies once the offline ones verify.

See how Safeguard would help

None of these demos export Google or Apple data. They apply this guide's habit, check before you trust, to software. To try the CLI yourself, download it from https://safeguard.sh/download and read the setup guide at https://docs.safeguard.sh/docs/cli .

The first demo is a real CLI session. After install, safeguard opens the interactive terminal, you ask it to fix the lodash CVE in a repo, and it reads the finding and advisory, asks before each command, edits package.json to lodash 4.17.21, runs npm install and npm test with your approval, prints a summary and pushes nothing. It is the verification habit above, applied to code: confirm, change deliberately, test.

Click through it at your own pace, or open it full screen.

The second demo sets up the Safeguard runner on your own machine, approves it with its device code, and then scans from the terminal. If you are taking more of your work under your own control, it shows dependency checks running on a machine you own.

Click through it at your own pace, or open it full screen.

The third demo is a real Android session: you send work to a computer running the CLI and approve the command on the phone with Allow once, Allow for turn or Deny. It applies the same principle as Google's re-authentication before a Takeout download: nothing sensitive runs without an explicit approval from you.

Click through it at your own pace, or open it full screen.

Quick check

Sources

• Google Account Help: How to download your Google data
• Google Account Help: Copy your photos and videos to a service outside of Google
• Google Account Help: Delete your Google Account
• Google Account Help: Get a summary of data in your Google Account
• Google Account Help: Import passwords
• Google Privacy and Terms: How Google retains data we collect
• Apple Support: Get a copy of the data associated with your Apple Account
• Apple Support: How to delete your Apple Account
• Apple Support: How to deactivate your Apple Account
• Apple Support: Understand and control the personal information that you store with Apple
• Apple Support: iCloud data security overview
• Apple Privacy Policy
• Apple Data and Privacy page
• Disk Utility User Guide: Create a secure disk image
• Microsoft Learn: BitLocker FAQ (BitLocker To Go)
• Microsoft Learn: BitLocker overview
• Microsoft Learn: Get-FileHash
• GNU coreutils: sha2 utilities
• GNU coreutils: md5sum invocation
• GNU coreutils: cksum common options
• GNU tar manual: How to list archives
• Perl documentation: shasum
• Python documentation: zipfile command line interface
• GnuPG manual: Operational GPG commands
• cryptsetup project README
• CISA: #StopRansomware Guide
• RFC 4155: The application/mbox Media Type
• RFC 6350: vCard Format Specification
• RFC 5545: iCalendar

Last reviewed: 23 October 2026. Google and Apple update their export and deletion pages often; check the linked help pages for current steps and timelines.