Applies to the custodian extension and licensed requestor workspace
The Chrome extension
MyDataPreserver does not upload evidence, access email or Drive through account APIs, request passwords, or communicate with a MyDataPreserver backend. Optional screenshots include whatever page content is visible when you capture. It has no analytics or telemetry. Workflow data is stored in chrome.storage.local, not Chrome Sync.
Optional webpage screenshots
Capture visible webpage uses temporary active-tab permission after you open the extension. It saves the visible page as a PNG with its URL, title, local capture times, pixel dimensions, extension version, and SHA-256 fingerprint. Browser controls and offscreen content are excluded. Images can contain sensitive information; review them before sharing. Captures, request references, and notes are stored locally in extension IndexedDB. Nothing is uploaded. Delete removes a local capture; uninstalling removes this database. Downloaded copies remain.
Packages contain original images, a manifest, and a report. Local verification checks image fingerprints against the manifest. It does not prove page authenticity or independently establish capture time, and cannot detect replacement of both the image and manifest. Notes and report HTML are not authenticated.
What is stored locally
- Random request and collection IDs, source names, timestamps, guide progress, and confirmed export settings.
- Custodian names or reference codes provided by a requestor, prepared instructions, and delivery methods.
- Local activity logs, multi-source collection groups, and manually updated requestor statuses.
Use a reference code when a name is unnecessary. Do not enter passwords, access tokens, evidence, or confidential case details into instruction fields. The extension does not verify custodian labels against service accounts.
Access to service pages
The Google Takeout guide runs only on takeout.google.com. It checks narrowly associated selection labels, states, and page headings to assist the guide; raw page text is not stored or logged. The other source guides open in an extension tab. They do not inject scripts into or inspect those service pages.
When you open a provider link or sign in, you connect directly to that provider under its own policies. MyDataPreserver does not create exports, download archives, or open archive contents.
Files and reports
Instruction JSON files are read locally, validated, and shown for review before you save them. They are not signed and their authors are not authenticated by the extension. Files and reports are not automatically sent to anyone. You choose how to share them.
Retention and deletion
Archiving retains a collection in local history. Clearing saved setup removes the plan for future collections, not collection history or tracker records. Uninstalling the extension removes its local records. Downloaded instruction files, archives, and saved reports remain separate copies until you delete them yourself.
Local activity records are not encrypted or tamper-evident. People or software with access to your Chrome profile may access or change them. There is no backend backup or cross-device synchronization.
Licensed requestor workspace
The website stores license labels and expiry, prepared instructions, custodian references, delivery instructions, and manual status history in Cloudflare D1. People using the same license share its workspace. Use reference codes where possible and never enter evidence, passwords, or access tokens. Custodian activity, archives, and screenshots are not uploaded automatically.
Requests remain until deleted. Expiry or revocation blocks access but does not delete records. You can delete requests while licensed; contact the person who issued your code for renewal or deletion after expiry. Sessions last up to eight hours or license expiry. Signing out invalidates the current session. Existing downloaded instructions and custodian collections continue to work after expiry.
License administration
The owner stores customer names, company names, contact emails, manual payment status, suspension reasons, and administrative notes in D1 to manage licenses. Owner-page changes retain before-and-after history, including previous contact information and notes. This data is restricted to owner access. No payment card data is collected. Contact your license issuer about correcting or deleting these records and their history.
Owner sign-in uses a separate essential secure cookie with a one-hour session. The owner key and session tokens are validated using stored hashes. Customer license codes do not grant owner access.
This website
The public pages have no advertising, evidence-upload forms, or site-added analytics. The licensed requestor workspace uses an essential secure session cookie. License codes are sent over HTTPS for validation and stored only as hashes. Session tokens are also stored as hashes. Sign-in protection temporarily stores a hashed IP-and-time-window identifier to limit repeated attempts. When hosted on Cloudflare Pages, Cloudflare handles normal connection information, such as IP addresses and request details, to deliver and protect the site under its privacy policy.
Links to external services take you to websites governed by their own policies. Downloads from this website contain the extension; they do not send your export archives to this site.
Questions about a collection
Contact the person who requested your collection for scope, delivery, or retention instructions. See Support for product troubleshooting and known limitations.