Compare two customer-owned browser trace exports and preserve observable request and storage-key changes. No compliance badge. No upload. Prefer raw HAR files from DevTools? Use the HAR before/after diff.
Does this tell me whether my site is GDPR or CCPA compliant?
No. It only reports observable differences between two trace exports you supply — requests added or removed and storage keys added or removed. The generated record says explicitly that it does not determine compliance; that judgment needs a person who knows your legal basis and traces from every relevant browser and region.
What exactly gets compared — just requests and storage keys?
Yes, and only what's in the trace JSON: each request's URL and method, and each storage entry's key. Cookie values, third-party pixels the trace didn't capture, in-memory state, and anything that happened outside the capture window are invisible to this comparison.
Do the before and after traces have to be the same site?
Yes, if both traces include a site field — the tool refuses to compare a before-trace from one site against an after-trace from another. Omit the field on either side and that check is skipped, so keeping site populated is what catches an accidental cross-site comparison.
Do the traces I paste in get uploaded anywhere?
No. Comparison happens entirely in this browser tab; nothing is sent anywhere. Prefer working from real captured traffic instead of hand-typed JSON? The HAR before/after diff takes raw DevTools exports the same way, locally.