WEBVTT

00:00:01.763 --> 00:00:04.553 align:middle line:84%
As I said earlier,
most users do not

00:00:04.553 --> 00:00:05.993 align:middle line:90%
create Android backup files.

00:00:05.993 --> 00:00:08.723 align:middle line:84%
It is so rare that you're going
to stumble upon a computer that

00:00:08.723 --> 00:00:10.883 align:middle line:90%
has backup.ab and shared.ab.

00:00:10.883 --> 00:00:16.133 align:middle line:84%
This is most often created
for forensic examination.

00:00:16.133 --> 00:00:19.153 align:middle line:84%
Now, something to consider--
if you are an Android user,

00:00:19.153 --> 00:00:21.313 align:middle line:84%
and you're like, yeah,
I don't do backups.

00:00:21.313 --> 00:00:23.593 align:middle line:84%
Do you truly know what
Google collects on you?

00:00:23.593 --> 00:00:27.523 align:middle line:84%
Have you ever done a security
check of your Google settings?

00:00:27.523 --> 00:00:29.833 align:middle line:84%
Have you ever tried to pull
your own Google Takeout

00:00:29.833 --> 00:00:31.873 align:middle line:90%
to see what it knows about you?

00:00:31.873 --> 00:00:34.456 align:middle line:84%
I want you to look at
your Google Takeout,

00:00:34.456 --> 00:00:36.373 align:middle line:84%
and then compare it to
some of the other tools

00:00:36.373 --> 00:00:39.493 align:middle line:84%
that we're going to use
to create these backups

00:00:39.493 --> 00:00:41.053 align:middle line:90%
and see what is really there.

00:00:41.053 --> 00:00:42.673 align:middle line:90%
I'm going to show you mine.

00:00:42.673 --> 00:00:45.193 align:middle line:84%
I recently just did
another Google Takeout

00:00:45.193 --> 00:00:46.993 align:middle line:84%
I think a few days ago
I'm going to compare

00:00:46.993 --> 00:00:49.033 align:middle line:84%
to what ElcomSoft
extracts for me,

00:00:49.033 --> 00:00:51.043 align:middle line:90%
what Cellebrite extracts for me.

00:00:51.043 --> 00:00:53.431 align:middle line:84%
It may differ in
what Google releases

00:00:53.431 --> 00:00:55.723 align:middle line:84%
for you to see versus what
some of the commercial tools

00:00:55.723 --> 00:00:58.113 align:middle line:84%
can get for you
behind the scenes.

00:00:58.113 --> 00:01:01.183 align:middle line:84%
These backups could
contain legacy information.

00:01:01.183 --> 00:01:03.873 align:middle line:84%
So if I go on a mass deleting
spree right now on my Android,

00:01:03.873 --> 00:01:06.573 align:middle line:84%
it does not mean that
all of those files

00:01:06.573 --> 00:01:08.343 align:middle line:84%
are going to be
removed from cloud.

00:01:08.343 --> 00:01:09.723 align:middle line:90%
It could be a period of time.

00:01:09.723 --> 00:01:11.433 align:middle line:84%
It may require an
additional sync.

00:01:11.433 --> 00:01:15.305 align:middle line:84%
But what happens if the syncing
just creates a new backup?

00:01:15.305 --> 00:01:16.513 align:middle line:90%
What's going to happen there?

00:01:16.513 --> 00:01:20.703 align:middle line:84%
So there are many things that
you can do if you create .ab

00:01:20.703 --> 00:01:22.993 align:middle line:84%
file standing for
Android Backup.

00:01:22.993 --> 00:01:25.788 align:middle line:84%
It is simply a tar format that
you can look in and extract.
