Privacy Policy

For file-based tools (chat and photo exports, Takeout archives, CSV/JSON/ENEX/MBOX files, and similar), everything happens on your device. The file you upload is read, parsed, and converted entirely in your browser using JavaScript. Its contents — messages, contacts, places, highlights, health records, photos, and so on — are never uploaded to, transmitted to, or stored on our servers.

The output you download is generated in your browser as well. We never see it.

Some tools temporarily store your parsed data in your browser (using sessionStorage or IndexedDB) so that a preview survives the round trip to and from the payment provider. This data stays on your device, is automatically expired after a short time-to-live, and is deleted when you reset the tool or upload a different file.

Downloaded files are handed to your browser's download mechanism and the temporary in-memory copies are released immediately afterwards.

When you purchase a priced tool, payment is processed by Stripe. You enter your card details on Stripe's secure checkout, not on our site — we never receive or store your card number. We receive only the confirmation that a checkout session for a specific tool was paid, which we use to unlock your download.

Stripe processes your payment information in accordance with Stripe's own privacy policy.

We record aggregate, count-only usage events (for example: a tool page was viewed, a file was accepted, a download completed, or a parse failed by category). These counts contain no file contents, filenames, message text, contact details, search queries, or other personal data.

These metrics are stored either in a database (libSQL/Turso) or, in local development, in memory or a log file. They exist only to understand which tools are used and where they fail.

If you submit the "request a tool" form, we store the message you typed and, if you choose to provide it, your email address, so we can consider the request and optionally follow up. These submissions are stored in our database (or a local log in development) and may also be emailed to us via Resend as a best-effort notification. Providing an email is optional.

A small number of tools can connect to a third-party account (for example Google, for Gmail-based exports). These tools are currently paused in favor of local, file-based alternatives. Where such a connection is used, access tokens are used only to perform the export you requested and can be revoked at any time from your account's security settings with the relevant provider. We favor local file processing over account connections wherever a documented export path exists.

We do not sell your data, and file contents are never used for advertising or shared with third parties. The only third parties involved are the infrastructure providers necessary to run the site and, where applicable, process a payment (such as our hosting provider, Stripe for payments, and Resend for request-form email).

Because file processing is local, the strongest privacy control is in your hands: your export files never leave your device. You can clear a tool's temporary browser storage by resetting it, uploading a different file, or clearing your browser's site data. You may omit your email from the request form. To revoke any account connection, use the security settings of the relevant provider.

We may update this Privacy Policy from time to time. The date at the top of this page reflects the most recent revision.

If you have questions about this Privacy Policy, please reach out via the contact information on our website or the request form.