Scan history

What is saved

Every time a GDriveKit scan completes, GKit saves a history point to your account:

• Scan date - when the scan ran
• Files scanned - total number of files checked
• Duplicate groups - number of groups with more than one copy
• Wasted bytes - total storage consumed by duplicates at scan time
• Bytes reclaimed - storage freed from confirmed deletions in that session

This lets you track progress over time - for example, comparing wasted space before and after a cleanup.

Viewing history

Open the GDriveKit dashboard and scroll to the History section. Each row shows a past scan with the date and key metrics.

Clicking a row does not re-open the old scan results - deleted files are gone and re-querying them would be stale. The history view is a summary log, not a replay.

Retention

Scan history is kept indefinitely in your GKit account. If you delete your account, all history is removed permanently.

Saved configs

You can save a scan configuration - scope, filters, and keep-rule - so you don't have to reconfigure each time.

Saved configs appear on the GDriveKit dashboard. Clicking Run on a config starts a new scan with those settings immediately.

Keep rules

The keep rule determines which file in a duplicate group GDriveKit marks as the one to keep:

Rule	Behaviour
newest	Keep the file with the latest modification date
oldest	Keep the file with the earliest modification date
largest	Keep the largest file by byte size
smallest	Keep the smallest file by byte size

The default is newest.

Scopes

Scope	What is scanned
my_drive	Files in your personal Google Drive
shared_with_me	Files shared to you (read-only files excluded from deletion)

Saved configs store one scope value.