Last updated: June 24, 2026 · Publisher: Techcesories LLC (Georgia, USA) · Product: Ferry browser extension Contact: contactus@techcesories.com
Ferry is a browser extension that exports your ChatGPT and Claude conversations to Markdown files you save yourself. This policy explains exactly what Ferry does and does not do with data. We wrote it to be true, not reassuring. Under Georgia's Fair Business Practices Act and the FTC Act, a privacy claim that isn't accurate is itself a violation.
Using Google's data-category vocabulary:
| Category | What | Where it goes | Why |
|---|---|---|---|
| Website content / personal communications | The text of the conversation you choose to export | Processed in memory on your device, only when you click Export. Written only to the destination you pick. Not transmitted to us. | To produce the Markdown export, the extension's single purpose |
| User content stored locally (Pro: bulk queue / auto-sync) | Conversations you queue or auto-archive | Stored on your device only, encrypted at rest (AES-GCM-256). Not transmitted to us. | To let you batch-export or auto-archive |
| Pro license status | An anonymous install ID (random, no PII) | Sent to our licensing service (a Cloudflare Worker), which checks it against Stripe. No conversation content. Also mirrored through Chrome's built-in sync (still anonymous) so Pro follows your signed-in Chrome. | To unlock Pro features for paying users |
| Pro recovery (optional) | The billing email you type to restore Pro | Sent to our licensing service, which emails a one-time code to it and (after you enter the code) re-links your purchase to your new install. Not stored by us; used only for that recovery. | To let paying users recover Pro after a reinstall or device change, while proving it's really them |
| Payment (Pro only) | Your payment details | Handled solely by Stripe (PCI-DSS) on Stripe's hosted checkout. We never see or store card data. | To take payment for Pro |
| Settings | Obsidian vault name, default format, footer preference | Stored locally on your device (non-sensitive). | To remember your preferences |
| Integration tokens (Pro) | Notion / GitHub access tokens you enter | Stored locally, encrypted at rest (AES-GCM-256). Used only to call those services at your request. | To run the integrations you enable |
That is the complete list. Ferry requests only the permissions these features need: reading conversations on chatgpt.com / chat.openai.com / claude.ai, local storage, and contacting our licensing Worker (with an anonymous ID, plus a billing email only if you use Restore Pro) for Pro status.
Stripe, our payment processor, and only for Pro: Stripe handles checkout and holds payment data (we never see card details). Our own licensing service (a Cloudflare Worker) receives only the anonymous install ID to verify your status with Stripe. It stores nothing and never sees your conversations. If you use Restore Pro, that service also receives the billing email you enter, solely to send you a one-time code and (once you enter it) look up your purchase in Stripe and re-link it to your new install; it is not stored by us and never reaches your conversations. That one code email is delivered through Resend, our email provider, who process the send on our behalf and receive nothing beyond the address and the code. No card details are involved.
If you enable an integration, the conversation you choose is sent by your browser, directly to the service you picked: Notion (api.notion.com) or GitHub (api.github.com), authenticated with a token you create and store locally in Ferry. This is a transfer you initiate, to your own account; we are not in the path and never receive the content or your tokens. We do not sell or "share" personal data for cross-context behavioral advertising.
Conversation content is processed locally and not transmitted to us, which removes the largest risk entirely. There is no central store of your chats to breach. Any conversation content Ferry persists locally (Pro queue/auto-sync) is encrypted at rest with AES-GCM-256. Communication with our payment processors occurs over HTTPS. The extension loads no remote code and includes a strict Content Security Policy. No system is perfectly secure, and we don't claim otherwise; see SECURITY.md for our threat model and how to report a vulnerability.
We are a small business below the applicability thresholds of comprehensive state privacy statutes, including the Georgia Consumer Privacy Protection Act (effective July 1, 2026) and the California CCPA/CPRA. Even so, we honor the core rights those laws describe: to access, correct, delete, and opt out of any sale of personal data. Because we don't sell data and hold almost none, most requests resolve immediately. Email contactus@techcesories.com and we'll respond within 45 days.
Ferry is not directed to children under 13 and we do not knowingly collect their personal information. If you believe a child has provided us data, contact us and we will delete it.
Ferry's use of information received from Chrome APIs adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements. We use the data Ferry accesses only to provide the user-facing export feature; we do not transfer it except to provide that feature or as required by law, and we do not use it for advertising, profiling, or any purpose unrelated to the export feature.
This website uses GoatCounter, a privacy-first analytics tool, to count page views in aggregate. It sets no cookies, stores no personal information, and does not track you across sites. If you sign up to be notified at launch, the email address you enter is sent to our inbox and used once, to tell you Ferry is live. It is not added to a marketing list, shared, or sold, and you can ask us to delete it at any time via contactus@techcesories.com.
We'll update this page and its "last updated" date for any material change, and describe what changed.