All tools

Clear-Site-Data Header Builder

Network

Build a Clear-Site-Data response header from cache, cookies, storage, and executionContexts directives (or * for all of them), or parse an existing header back into its directives

Pick which directives to clear (cache, cookies, storage, executionContexts, or the * wildcard for all of them) and get back the exact quoted, comma-separated Clear-Site-Data header value to send on a logout or account-deletion response, the standard way to tell a browser to wipe a site's locally stored data without asking the user to clear it by hand. It flags the common mistake of listing other directives alongside *, since the wildcard already covers every current directive (and any the spec adds later) on its own. Paste an existing header back in to see exactly which directives it clears, whether it came from your own server or a response you are debugging.

clear-site-dataheadershttpsecurityprivacylogout

How to use Clear-Site-Data Header Builder

  • 1.Check the directives you want a logout or account-deletion response to clear, or check just * to clear everything.
  • 2.Copy the generated header value and add it to that response in your server or edge function.
  • 3.Paste an existing Clear-Site-Data header into the parse box to see exactly which directives it clears.

Frequently asked questions

Does this actually clear any data in my browser?
No, it only builds or parses the header text locally. Nothing about your own browser's storage, cookies, or cache is touched; you still need to send the generated value as a real response header for a browser to act on it.
What does the * directive clear that the others don't?
* clears cache, cookies, storage, and executionContexts together, plus any directive type the spec adds in the future. Listing other directives alongside it is redundant, which this tool flags as a warning rather than an error.
Does this work over plain HTTP?
No, browsers only honor Clear-Site-Data on an HTTPS response. Sending it over HTTP has no effect.
Is my data sent anywhere?
No, everything runs locally in your browser (or in your own process via the SDK/API).

Use via API, SDK, or MCP

cURL# Free: 1,000 req/day · Pro: 10,000 req/day
curl -X POST https://api.utilix.tech/v1/tools/clear-site-data-header-builder \
  -H "Authorization: Bearer utx_live_..." \
  -H "Content-Type: application/json" \
  -d '{"directives":["cache","cookies"],"header":"\"cache\", \"cookies\""}'

Get an API key from your dashboard · Full API docs →

Related tools

Referrer-Policy Header BuilderBuild a Referrer-Policy header value from one or more policy tokens with a plain-English explanation of each and warnings for risky choices like unsafe-urlNetworkHTTP Security Headers ScorecardScore a pasted block of raw HTTP response headers against commonly recommended security headers, with an overall 0-100 score and A-F gradeNetworkPermissions-Policy Header BuilderBuild a Permissions-Policy (formerly Feature-Policy) response header from a list of browser features and their allowlists (self, none, specific origins, or all origins), with a plain-English note on what each directive restricts, or parse an existing headerNetwork