2026.10.28
Check what a Grok Bot backup includes and what is missing
An example of requesting private storage and distinguishing captured information from missing data.
Good news: you can export a Grok Bot’s context to make a backup!
To share context between dots and Grok Bot, it seems worth exporting and saving the Grok Bot’s context first.
There have been reports of data disappearing around Grok account linking, so making a backup before changing a subscription plan also seems important.
Note: This example records a request specifying a private destination and the Bot’s completion report. The captured scope was distinguished from missing information such as inaccessible notes, intermediate conversation history, and large attachments. The stored contents, completeness, effectiveness of secret exclusion, successful restoration, and successful context sharing with dots have not been independently verified. A causal link between account linking or subscription changes and data loss has not been established either. The name “dots” in the attached screenshots refers to a Bot within Grok. Screenshots containing private information and the specific storage destination are not reproduced here.