Last updated: June 24, 2026 · Set this to your actual publish date before going live. Publisher: Techcesories LLC (Georgia, USA) · Product: Ferry browser extension Contact: privacy@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. | To unlock Pro features for paying users |
| 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, and any Notion/GitHub tokens you enter | Stored locally on your device. Tokens are used only to call those services at your request. | To remember your preferences and run integrations |
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) for Pro status.
Only 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 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 privacy@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.
We'll update this page and its "last updated" date for any material change, and describe what changed.
This document is a carefully researched, compliance-by-design draft prepared for Techcesories LLC. It is not legal advice. Have counsel review it before launch and whenever features change.