GrokDoc

The pack never leaves your browser. That is the whole policy, and here is what it means.

What happens to your file

  • It is read and examined by code running in your browser. No upload happens on the normal path.
  • Nothing is stored: no database, no server logs of content, no cookies, no analytics on the checkup.
  • Closing the tab ends the checkup. There is no history unless you keep the downloaded chart yourself.

Summary links

A summary link carries the verdict, the facts table, and component names inside the link itself, after the # sign, which browsers do not send to servers. It never carries component bodies. Anyone you give the link to can read that summary.

Downloads and copies

Anything you copy or download is built in your browser from a redacted copy. Secret-shaped strings appear as <REDACTED_n> and personal data as <PII_n>. The receipt at the end of every artifact lists what was removed or changed.

The optional API

There is a server endpoint for command-line use. The website does not use it. If you call it yourself, your file is processed in memory, answered with no-store headers, and not kept. Request bodies are never logged.

Grok share links

GrokDoc never fetches a share link or any URL found inside an export. Paste the JSON, not the link.