Add Chrome payments customer data artifact - #1134
Merged
Merged
Conversation
Reads the payments_customer_data table in Web Data across the Chromium based browsers and the WebView copies, reporting customer_id as stored with the browser resolved from the path. The table is checked for rather than assumed, since many WebView Web Data files do not carry it. Files are deduplicated on the evidence-relative path so the copies an extraction holds at data_mirror and at /data/data next to /data/user/0 are read once. A Web Data file left with a hot rollback journal cannot be opened read-only, so it is logged and skipped rather than ending the run. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
abrignoni
force-pushed
the
feat/chrome-payments-customer-data
branch
from
August 16, 2026 20:37
19415d3 to
94f727b
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds a Payments Customer Data artifact for Chromium based browsers on Android.
The browser stores at most one row per profile. The table is checked for rather than assumed, since many WebView Web Data files do not carry it. Files are deduplicated on the evidence-relative path, so the copies an extraction holds at data_mirror and at /data/data next to /data/user/0 are read once. A Web Data file left with a hot rollback journal cannot be opened read-only, so it is logged and skipped rather than ending the run.