Your evidence stays outside MyDataPreserver
- Evidence is not uploaded to MyDataPreserver.
- Email and Drive content are not read.
- Credentials are not collected.
- Collection activity is stored locally in Chrome using chrome.storage.local, not Chrome Sync.
- V0.1 has no analytics or telemetry.
- V0.1 communicates with no MyDataPreserver backend.
What is recorded
A random collection ID, requested source names, guide progress, timestamps, your confirmed export settings, and a local activity log. A requestor-provided custodian name or reference and a random request ID identify prepared instructions and appear in downloaded instruction files, the collection, and reports. Use a reference code when a name is not needed. These labels are not verified against the service account. Optional requestor delivery instructions are stored as plain text, together with prepared sources, settings, and transfer method. Do not enter passwords, access tokens, account identifiers, evidence, or confidential case details. A collection keeps its own copy of the prepared instructions. The guide inspects only narrowly associated Takeout selection labels and states, and page headings. Raw DOM text is never stored or logged.
Requestor tracking
Requests prepared through the requestor page are stored locally as instruction snapshots with custodian labels, request IDs, dates, manually entered statuses, and status history. This tracker does not receive custodian updates or independently verify sending, downloads, or receipt. Clearing saved setup or archiving a collection does not delete tracker records. Uninstalling removes them along with other extension storage. No backend or cross-device synchronization is used.
Collections and history
A multi-source request is stored as a local group with separate service collections. Switching services retains their progress, settings, and logs. Combined reports include all services in that request, including archived records. Existing single collections are carried forward without changing their prior activity. Only one service is selected for the guide at a time.
Storage and deletion
The activity record is not encrypted or tamper-evident. People or software with access to your Chrome profile may access or change it. Archive keeps the collection and its activity in local history. Restore makes it available to continue. Clear saved setup removes only the plan for future collections. Uninstalling removes all local collection history and tracking records. Reports you save or print are separate copies.
Instruction files
You may load a small MyDataPreserver JSON instruction file or download one to send to a custodian yourself. The file is read locally, validated against a fixed schema, and loaded for review before you explicitly save it. It is not an evidence import. Instruction files are not signed and their authors are not authenticated by the extension. Downloaded files and reports are separate copies; clearing setup does not delete those copies. No file or instruction is automatically sent to another person.
Services remain in control of exports
Opening a service or help link connects your browser to that provider under its own policies. MyDataPreserver neither creates exports nor downloads or opens archive files. You make all choices in the service. The Takeout overlay runs only on takeout.google.com. Facebook, Instagram, X, LinkedIn, TikTok, Snapchat, Reddit, and Discord guides run in a separate extension tab; no scripts are injected into those services and their pages are not inspected. Progress is based on your explicit confirmations.
MyDataPreserver provides guided export instructions. It does not perform a forensic acquisition or determine the legal scope of a collection. Collection scope and methodology should be established by counsel or an appropriate eDiscovery professional.