TECHHow to check a GROX data export before sharing it
A portable founder record needs the right scope, a sample you can reopen, and a privacy pass before anyone else sees it.
How should a founder check a GROX export?
Choose the smallest export that serves the handoff, open it yourself, inventory its contents, and inspect it for private details before sharing. A readable chat is useful for one decision; a full archive is more suitable for preserving work across conversations, files and builds. Neither format alone proves that a standing agent job completed correctly. For that, inspect the job history and the resulting work separately.
Source check — 3 November 2026: IAI Tech reviewed GROX’s new chat-export guide, current data-rights help, privacy page, and related job-history documentation. Product behavior below is GROX’s public description; we did not sign in, download an account archive, test its masking, or share a link.
What does GROX say can be taken out?
GROX’s 31 October guide describes two export shapes: a readable page for one selected conversation, and a zip archive that includes chats, memories, files and builds. It says sensitive numbers, passwords and keys are masked or omitted, and also describes read-only share links that can be turned off. The current help article points to Settings → Privacy → Your data to request a copy; the privacy page also states an export control in Settings. These are documented capabilities, not a verified inventory of any particular account.
Do not assume every kind of conversation is present in a server archive. GROX’s privacy page describes Ghost chat as not stored in readable form on its server, with local history and an optional separately encrypted sync. Treat those conversations as a separate case and check the controls that apply to the actual session. Likewise, an export intended for portability may omit secrets by design; that is a privacy feature, but it means the archive cannot be treated as a complete credential backup.
GROX’s 30 October job-history guide describes another record: a standing job’s History view, with session times, actions, costs, and reasons for failed or skipped runs. The current Reports help also describes job reports and credits. Check that view separately when the handoff depends on whether work really ran; the export guide does not establish that its zip is an execution audit.
A small founder handoff to adapt
Fictional example: Larch Studio is preparing to hand a website launch plan from its founder to a colleague. They need the final decision, the approved files and the status of a recurring launch-watch job. This example was not performed in a GROX account and is not a customer result.
Handoff request: “Give Mira the approved launch position and the latest design file, plus a clear note on whether the launch-watch job ran last week. Share only the final decision conversation and approved file. Keep unrelated chats, private notes, credentials and the full account archive private. If a run was skipped or a result link is missing, state that gap instead of calling the job complete.”
The request does not ask GROX to decide what may be disclosed on its own. The founder should choose the exact conversation and file, inspect them locally, and use an approved sharing method. A full archive can be kept as a private continuity copy, while a scoped handoff contains only the material the colleague needs.
A four-pass export and handoff check
Use pass, gap, or untested for each line. This is an original IAI Tech review sheet, not a GROX scoring feature. Open a sample export yourself before relying on it. NIST’s contingency-planning guidance includes testing backup information by restoring a sample; the general lesson here is to check that your saved material is usable, rather than treating the presence of a zip file as proof of continuity.
| Pass | What the founder checks | Decision |
|---|---|---|
| Scope | The one-chat page contains the final launch decision. The private zip’s inventory includes the expected conversations and approved work files, with missing items noted. | Pass / gap / untested |
| Usability | Open the readable page and at least one archive file. Check that headings, dates, filenames and linked artifacts are intelligible without the original chat screen. | Pass / gap / untested |
| Privacy | Review the selected share material for personal data and confidential plans. Confirm masked or omitted fields, then share only the approved conversation and file. | Pass / gap / untested |
| Job evidence | Open the standing job’s History view. Record the last run, any skipped or failed entry, credit use and a link to the actual output. Leave unknowns explicit. | Pass / gap / untested |
If the archive opens but the final design file is absent, record a gap and fetch the approved file through its original GROX workspace before sending the handoff. If the job report says “complete” but the result link cannot be opened, do not claim the launch-watch output was reviewed. These are hypothetical failure examples, not observed GROX behavior.
What does an export not prove?
An export preserves a copy of what it contains; it does not establish that every item in the account was included, that masking caught every sensitive phrase, or that an agent’s work was correct. The job-history guide makes a useful distinction between a session that ran and one that was skipped or failed. A founder still needs to inspect the actual deliverable and, where relevant, the target system’s state.
GROX’s people-notes guide describes short notes derived from emails and meetings, plus controls in Settings → Memory. If a handoff archive contains memory, treat it as context to review for relevance and privacy, not as a verified record of another person’s intentions. If you share a read-only link, confirm the recipient and later turn it off when the review ends; the export guide documents revocable links but does not remove the need to inspect what the link reveals.
The current GROX pricing page is the place to check plan terms before relying on an ongoing workflow. This guide makes no fixed price or plan-access claim about exporting.
Frequently asked questions
What can a founder export from GROX?
GROX’s 31 October guide describes a readable download of one chat and a zip archive of chats, memories, files, and builds. Its help and privacy pages also describe a data-copy request in Settings → Privacy. Check the actual archive contents for your account.
Does a GROX chat export prove an agent completed a job?
A chat export records conversation content. For a standing job, check its separate History view for session timing, actions, costs, and failed or skipped runs, then inspect the linked work itself.
Should I share the complete zip archive with a collaborator?
Usually start with the minimum relevant material. Inspect the archive and any masked or omitted fields, then share only the conversation or files the collaborator needs through an approved channel.
Will Ghost chat appear in a full account export?
Do not assume so. GROX’s privacy page says Ghost chat is not stored as a readable server conversation; check any local or sealed copy under its own controls.
Sources and editorial method
Sources checked 3 November 2026. IAI Tech is the company behind GROX. Larch Studio, its handoff request, and the review sheet are fictional editorial guidance. The described product controls have not been independently tested in an authenticated GROX account.
- GROX export guide, 31 October 2026
- Job-history guide, 30 October 2026
- People-notes guide, 29 October 2026
- Data-rights help
- Job reports help
- Privacy and Ghost chat controls
- Current pricing
- NIST backup-testing guidance
Related reading: How to verify a GROX scheduled task.
Keep the handoff smaller than the archive
Open the copy, check one real item, and share only the work the next person needs.
Explore GROX data controlsCheck current plans