DATA HANDLING
Keep the evidence, not unnecessary copies.
NBT keeps enough to show what was tested and explain the result. We avoid larger or more sensitive captures when a smaller piece of evidence will do.
What we keep
Our declared content-use level is reference. We keep the smallest useful evidence we can: status codes, timings, hashes, parsed values, short excerpts and other diagnostics needed for an authorised QA result. Screenshots or larger captures are kept only when they help explain what happened.
What we avoid
We do not run a public copy of the sites we test, and we do not keep full response bodies when a smaller observation is enough. Retention follows the customer’s account policy.
Secrets
Passwords, payment data, session cookies, private API tokens, merchant crawler signatures and private Web Bot Auth keys must not appear in public evidence or normal logs.
Use with models
We do not use pages we crawl to train models. If a customer turns on a feature that analyses content with a model, we only do that where the site’s Content Signals allow it. ai-input=no blocks that use. use=immediate means the content should not be kept for later reuse.
Between customers
Public resources may be safely reused or revalidated to avoid unnecessary repeat requests. Authenticated, session-bound or private customer responses are never shared between customers.