SafeRedact
Onboarding · export step

Google Vault export settings
for your SafeRedact case

The Google Vault export settings that produce an export SafeRedact processes completely. The message format decides whether the mail can be read at all, and the conversion error files decide whether every message reaches the case.

The export settings

This page covers one step: producing a Google Vault export from Google Workspace that SafeRedact can process completely. It is written to be forwarded to whoever operates Vault, who is often not the person running the case. The rest of the case is covered in Your first case. For Microsoft 365, the Purview export guide covers the same step.

Choose PST as the message format. Vault offers PST or mbox for Gmail. SafeRedact reads PST and does not read mbox. With PST, each message is expanded locally and every attachment of a type SafeRedact reads is scanned as a document in its own right. Attachments of other types, such as images and older .doc or .xls files, are not read, and the pack lists each one.
SettingChooseWhy
Export format (Gmail)PSTEach message is expanded locally and its attachments are read as documents in their own right. Mbox files are not read
Include Gmail confidential mode messagesOnWith it off, those messages export as metadata only, without their content
Export linked Drive filesOn, when in scopeWith it off, a Drive file shared as a link in a message never reaches the disclosure. Google notes that it can significantly increase volume
Conversion error filesAdd to the caseMessages Vault could not write to PST arrive as EML files in these zips, and EML is read
Result counts fileKeep beside the caseThe independent count of messages to reconcile against at the end

Google Takeout, the tool for an individual’s own account, exports Gmail as mbox, which SafeRedact does not read. Use Vault for a subject access request.

Settings that decide completeness

  • Vault counts a message as exported even when it could not be converted to PST. Each such message is written as a separate EML file, named with its Message-ID, inside export_name-conversion_errors-N.zip. Add those zips to the same case as the PSTs, and SafeRedact reads each EML as a full message with its attachments. If they are left out, those messages are missing from the disclosure, and the pack has no record of them because they were never added to the case.
  • Files shared as links are separate from the message. Vault collects them only when Export linked Drive files is on. It then creates a Drive export grouped with the Gmail export and lists every link it found in export_name-drive-links.csv, including links to files it had no permission to export. Decide this with the request scope in hand.
  • Large exports can stop with partial results. If an export has not finished after 24 hours, Vault stops it, marks it as containing partial results and lists the accounts that were not exported. Choose Continue export before treating the download as complete, or split the search by account or date range.
  • Reconcile against the result counts. export_name-result-counts.csv lists each account with the number of messages exported and the number with errors, and its success figure includes the messages in the conversion error zips. export_name-errors.xml lists messages Vault could not retrieve. Compare both with the processed count, the failure manifest and the list of files not in the case at the end of the case. Keep these files and the metadata files beside the case as control documents; they are not for disclosure.

Timing and download

  • Download within 15 days. Export files are available for 15 days after the export starts. After that Vault deletes them, and the export has to be created again.
  • Mail arrives in several zips. Vault splits an account’s PST output into numbered zips once it passes 1 GB, and an export that covers more than one account also arrives as several zips. Each PST is named with the custodian’s email address, so mailboxes stay separable in the case.
  • Drive exports are packed up to 10 GB per zip. A zip over 2 GB cannot be opened in the browser, so extract larger zips with 7-Zip and add the extracted files. Zips under 2 GB can be loaded whole, and nested archives are expanded automatically.
  • Check the download. Vault includes an MD5 hash for every file in the export, which confirms a large download arrived intact before it is extracted.
  • Load one custodian first. Process the smallest mailbox first to confirm the subject’s details and aliases before the full volume runs.

What is processed and what is not

SafeRedact processes PDF, Word, Excel, CSV, JSON, text, HTML, email (PST, MSG, EML) and the contents of zip archives including nested ones. Vault converts Google’s own file types as it exports them, and the converted type decides whether a file is processed.

Processed

Exported itemArrives asWhat happens
Gmail, PST format.pstEvery message is read, with its attachments
Messages that failed PST conversion.emlEvery message is read, with its attachments. They arrive in the conversion_errors zips
Google Docs.docxRead
Google Sheets.xlsxRead, every worksheet
Google Drawings.pdfRead
Google Sites.pdf per pageRead
Google Forms.zip of HTML, CSVThe zip is unpacked and both files are read

Not processed

Exported itemArrives asWhat to do
Gmail, mbox format.mboxExport again with PST as the format
Google Slides.pptxConvert to PDF before adding, or review outside SafeRedact
Google Vids.mp4Review outside SafeRedact
Standalone images.jpg, .pngListed in the pack by name; review outside SafeRedact
  • Files that are not processed are listed. They are not added to the case, and the pack lists each one by name with the reason in internal-audit/files-not-in-case.csv. Attachments that are not read are listed in internal-audit/attachments-not-read.csv. Scanned pages inside a PDF are a different matter and are OCR'd locally in the browser.
  • Large Google files may not export at all. Vault cannot export Google Docs, Sheets and Slides files if their total size after conversion to Office formats exceeds 500 MB, so those files never reach the case and need handling separately.
  • Client-side encrypted messages stay encrypted. Google’s route to reading them in a PST export is importing each user’s p7m file into Outlook. Review them outside SafeRedact.
What has been tested. SafeRedact reads a Vault PST with the same reader it uses for every PST, and each of the other files above with the reader for its type. A complete case built from a Vault export has not yet been run through our own release checks. If part of a Vault export behaves differently from this page, write to support@saferedact.app with the build stamp shown in the app header.

Handing it over

Once the files are downloaded, they go to whoever is running the case: the PSTs, the conversion error zips and any Drive files, with the count and metadata files kept alongside. Each PST is expanded in the browser, and the custodian’s address in its file name keeps each mailbox identifiable.

Your first case covers what happens next: setting up the case and the subject details, processing, review, and producing the disclosure.

Questions on any of the above: support@saferedact.app.