Frogpost

Privacy Policy

Effective November 7, 2026 ยท Terms of Service

Frogpost is a Chrome extension that turns an AI chat or email thread into a handoff and drops it into the next chat box. It is made by GhostEngine LLC, a Wyoming limited liability company ("GhostEngine", "we", "us"). This policy explains what Frogpost reads, where it goes, how long it's kept and what you control. It covers the extension, our server, the phone page and frogpost.app.

The short version

1. What we process and why

Frogpost has no accounts. It makes a random license key when you install it (not tied to your name or email). That key is how our server tells installs apart.

DataWhere it isWhyHow long
Chats you grab: the conversation, email thread, document or selection on the tab you grabYour device. Sent to the AI that writes the handoff (section 2)To write the handoff you asked forKept on your device with the handoff it made. Never stored on our server
Open chats on Claude, ChatGPT and Gemini (only when Chrome's built-in AI is available)Your device only. Read and summarized by Chrome's built-in AISo a grab is instant, and, unless you turn off Remember my chats, to keep each chat's handoff in your libraryThe summary lasts while the tab is open. Remembered handoffs stay until you delete them
Handoff library: handoffs, their title, source page address, time and project nameYour device (free: newest 50; Pro: all), including handoffs saved by Remember my chats. Our server too, if you turn on Pro syncSo you can find and reuse past work, on all your devices and in AI tools you connect over MCPUntil you delete them
Search queries (Pro sync)Sent to Voyage AI to search by meaningTo find handoffs by meaningNot stored by us
Settings and your own API keyYour device only. Never synced, never sent to usTo run Frogpost the way you set itUntil you change them or uninstall
License keyYour device. Our server when you use hosted handoffs, Pro or purchasesTo apply your plan and limitsWhile you use Frogpost
Subscription and purchases: Stripe customer and subscription IDs, status, rare frogs boughtOur server. Payment details are with StripeTo run Pro and unlock what you boughtWhile active, then as tax and accounting law requires
Usage counters: hosted handoffs per license key, free ones per IP address (per /64 network on IPv6), and hosted AI cost per license key per monthOur serverTo enforce daily and monthly limits and prevent abuseDaily counts: 2 days. Monthly cost: 40 days
Usage counts: how many grabs, drops, phone sends, library searches, reuses and remembered chats a day, under a random install ID that is not your license key; how often a phone page is opened, under a scrambled form of its link's channel. Numbers only, never any textOur serverTo learn whether people keep using Frogpost and which parts they use (legitimate interests; in the EU and EEA, your consent: off until you turn it on)Until you delete them. Turn them off in Settings โ†’ Your data; Delete everything removes them
Encrypted phone handoffs, and an encrypted copy of your newest saved handoffs for the phone's Library and ProjectsOur server, as ciphertext onlyTo deliver handoffs and your library to your paired phoneEach handoff is deleted 7 days after it was sent (newest 20 kept). The library copy is replaced whenever your library changes and deleted 7 days after the last change. New code or Delete everything deletes both at once
Connection data: IP address, browser and device typeCloudflare (our server) and Lovable (frogpost.app), when you connectTo deliver pages and requests securelyWe don't log requests. Hosts keep short-lived security logs under their policies
Emails you send usOur inboxTo answer youAs long as needed to help you

Our legal bases under the GDPR: contract for handoffs, sync, phone delivery and your subscription; legitimate interests for limits, abuse prevention, security and usage counts outside the EU and EEA; consent for usage counts in the EU and EEA, which you can withdraw any time with the switch in Settings; legal obligation for tax records.

2. Where a chat goes when you grab it

Frogpost uses the first writer available, and after every grab the frog tells you which one wrote it:

  1. Your own API key. The chat goes from your browser straight to Anthropic or OpenAI under your own account and their terms. It never touches our server.
  2. Chrome's built-in AI. The chat never leaves your device.
  3. Our server (a free daily allowance, or Pro). The chat goes to our server on Cloudflare, which sends it to Anthropic's API and streams the handoff back to you as it is written. Neither the chat nor the handoff is stored or logged. Under its commercial terms Anthropic does not train on this data and deletes it within 30 days, unless it is flagged for a usage-policy review.
  4. Offline builder. If none of these is available, Frogpost builds the handoff on your device.

Background summaries. On Claude, ChatGPT and Gemini, if Chrome's built-in AI is already available on your computer, Frogpost reads the chat you have open after each reply and folds it into a running summary, written by that on-device AI, so a grab can hand it over at once. It pauses while the tab is hidden and on low battery. The chat and the summary stay on your device. Remember my chats (on by default, everywhere, because it stays on your device; turn it off in Settings, Your data) also saves that summary to your library as the chat grows, one entry per chat, without a grab. Remembered handoffs are handled like any other: on your device, and on our server only if Pro sync is on.

On Claude and ChatGPT, a grab may load the full conversation from that site's servers using the session you're already signed in with. That request goes from your browser to the site, not to us. A chat or email can contain other people's personal data. Frogpost processes it only to make the handoff you asked for.

3. Phone links

When you pair a phone, Frogpost encrypts each handoff on your computer with AES-256-GCM. The key is in the part of the QR link after "#", which browsers never send to a server, and the phone page keeps it in that phone's browser storage. Our server stores only the encrypted copies, so we can't read them. Anyone who has the link can, though, so treat it like a password. New code in Settings unpairs the old phone and deletes what it could still fetch.

A paired phone also gets your newest saved handoffs (as many as fit in one message), encrypted the same way, so it can show your Library and Projects. When you send a handoff to the phone, Frogpost also writes a short text message and an email draft from the same chat, with the AI you chose for handoffs, so the phone's Messages and Mail buttons open with the right version. In hosted mode that is one more trip through our server and Anthropic, counted like a handoff.

4. What we never do

5. Service providers

These companies process data for us, only to run Frogpost and under contracts that restrict them to that. We'll update this list before adding a new one.

ProviderPurposeDataLocation
CloudflareHosting: Workers, D1, KV, Vectorize, Durable ObjectsLicense key, counters, usage counts, subscription status, synced library, encrypted phone handoffs, connection dataGlobal, US company
AnthropicWrites hosted handoffs (Claude)Chat text from hosted grabsUS
Voyage AISearch by meaning (Pro sync)Synced handoff text, search queriesUS
StripePayments and billing portalPayment details, email, billing address, license keyUS
LovableHosts frogpost.appWebsite connection dataSweden, EU

If you use your own API key, your chat goes to Anthropic or OpenAI under your agreement with them, not ours. We may disclose data if the law requires it, to protect people's safety or our rights, or to a successor if GhostEngine or Frogpost is sold, and this policy keeps applying to it.

6. Your controls

7. Your privacy rights

Everyone. You can ask us to access, correct, export or delete your data, or to stop processing it. Email zoltan@frogpost.app with your license key, because we have no accounts and that is how we find your data. We'll reply within 30 days. If you ask, we won't charge you or treat you differently.

EEA, UK and Switzerland. You also have the right to object to processing based on legitimate interests, to restrict processing, and to lodge a complaint with your data protection authority. GhostEngine is the controller.

California and other US states. In the past 12 months we collected identifiers (license key, IP address), commercial information (purchases) and the content you chose to grab, for the purposes in section 1, from you and your device. We don't sell or share personal information as the CCPA/CPRA defines those terms, and we don't use sensitive personal information to infer anything about you. So there is nothing to opt out of, and we honor Global Privacy Control by default. You can use an authorized agent. We'll reply to California requests within 45 days.

8. International transfers

We and most of our providers are in the United States. When EU, UK or Swiss data is transferred, we rely on the EU-US Data Privacy Framework (and its UK and Swiss extensions) where the provider is certified, and otherwise on the European Commission's Standard Contractual Clauses.

9. Security

All traffic uses HTTPS. Phone handoffs are end-to-end encrypted, payment cards never reach our servers, and our server stores the minimum listed above. Your license key unlocks your Pro library and MCP access, so keep it private. No system is perfectly secure. If a breach affects your data, we'll notify you and the authorities as the law requires.

10. Children

Frogpost is for adults. You must be 18 or older to use it. We don't knowingly process children's data. If you believe a child has used Frogpost, email us and we'll delete what we hold.

11. Cookies

Frogpost and our server set no cookies and use no third-party analytics or tracking. The extension keeps its data, including the random install ID for usage counts (section 1), in Chrome's extension storage, and the phone page keeps its pairing key in the phone's browser storage. Stripe sets its own cookies on its checkout and billing pages. frogpost.app sets no cookies and loads no trackers. If that changes, we'll ask your consent first.

12. Chrome Web Store disclosure

Frogpost's use of information received from Chrome APIs adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements. We use data only to provide Frogpost's single purpose: grabbing, writing, keeping and dropping handoffs, and to improve it (usage counts, which hold no content). We never transfer it for advertising, credit decisions or data brokering, and humans don't read it except as described in section 4.

13. Changes

When we update this policy we change the date at the top. For a material change, we'll give notice before it takes effect, for example in the extension.

14. Contact

Questions or requests: zoltan@frogpost.app
Mail: GhostEngine LLC, 390 NE 191st St STE 17348, Miami, FL 33179, United States