Does Safe Archive upload your files?
Understand where FolderManifest processes file contents, what goes to the archive destination you choose, and what optional product telemetry does not collect.
Safe Archive guide
Keep the copy, keep the context, and keep a record of what arrived.
Published August 20, 2026
Scope first
Decide what you are allowed to copy before starting the archive.
Copy second
Use a destination that will remain available after access changes.
Verify last
Keep a report that names the files copied, converted, skipped, or failed.
Quick answer
FolderManifest processes file contents locally. Safe Archive sends the selected copy to the destination you choose, such as a local folder, S3-compatible bucket, or Google Drive. FolderManifest servers do not receive your file contents, and optional usage metrics do not contain file names, paths, contents, or checksums.
1. What stays on your device
The desktop app scans the selected folders and processes file metadata locally to build manifests and reports. That includes names, paths, sizes, timestamps, and checksums needed for the archive record.
The app is not a web uploader for your working folders. Your files remain on the device until you deliberately select an archive destination that needs a copy.
- File contents are processed locally.
- Manifests and reports are created on the device or in the archive destination.
- Local-to-local archives stay within the locations you choose.
2. What goes to the destination
Safe Archive must send the selected files to the destination when you choose S3-compatible storage or Google Drive. That transfer is the archive operation itself. You control the destination account, bucket, prefix, or Drive folder.
The archive report is written into the destination so the copy and its evidence stay together.
Google-native files are exported when necessary. Ordinary files receive SHA-256 values in the HTML and CSV reports, while converted or skipped items are shown as their own statuses.
3. What optional telemetry contains
Optional usage telemetry uses bucketed product metrics. It does not include file names, paths, contents, checksums, bucket names, prefixes, or account emails. You can turn usage sharing off in Settings → Privacy.
License activation is a separate service operation and may use a license ID and privacy-safe device fingerprint for seat validation. That is different from sending the contents of the folders you archive.
4. Review the destination you selected
- Confirm the archive destination belongs to the intended owner or account.
- Check the archive report for the expected source scope and exceptions.
- Review the destination permissions before handing it to another person.
- Keep the reports with the archive and follow the retention policy.
Make the archive reviewable
FolderManifest copies the folder locally or to a supported destination, then creates a report with the files that arrived and the files that need attention.
Frequently asked questions
Does FolderManifest upload my file contents to its servers?
No. FolderManifest processes file contents locally on your device. Safe Archive sends files only to the archive destination you select, such as local storage, S3-compatible storage, or Google Drive.
Does Safe Archive send files to the destination I choose?
Yes. An archive has to write the selected copy to its destination. That destination can be a local folder, NAS mount, S3-compatible bucket, or Google Drive.
What does optional usage telemetry contain?
Optional product telemetry uses bucketed metrics and does not include file names, paths, contents, or checksums. You can turn usage sharing off in Settings → Privacy.
Does the app read file metadata?
Yes. The app processes metadata such as names, sizes, paths, timestamps, and checksums locally to build manifests and reports. That local processing is different from sending file contents to FolderManifest servers.
