← Back

Privacy Policy — InboxLingo

Last updated: 2026-07-03

InboxLingo is a browser extension that helps marketplace sellers translate buyer messages and compose replies. This policy explains exactly what the extension does and does not do with your data. It is written to be true of the code in this repository.

The short version

• We do not run our own server. The extension has no backend of ours to send your data to.
• We do not collect, store, sell, or share your personal data or your buyers' messages.
• Your Anthropic API key and your snippets stay in your browser.
• Message text you choose to translate is sent only to Anthropic, using your own API key, and only at the moment you translate.
• Upgrading to Pro is handled by ExtensionPay (a third-party payment service); we never see or store your card details.

What is stored, and where

All storage is local to your browser (chrome.storage.local) and never leaves it except as described below:

Data	Purpose	Location
Your Anthropic API key	Authenticate translation requests	Your browser only
Your snippets	Your saved reply templates	Your browser only
Settings (model, default language, shop name)	Your preferences	Your browser only
Monthly translation count	Enforce the free-plan limit	Your browser only

There is no account, no login, and no sync to us.

What is sent to Anthropic

When you press Translate (or use the on-page/right-click translate action), the text you are translating and a system instruction are sent to the Anthropic API using your API key, so that Claude can return the translation. This is the only outbound transmission the extension makes.

• The request goes directly from your browser to Anthropic. It does not pass through any server of ours.
• Anthropic's handling of that request is governed by Anthropic's own privacy policy and terms: https://www.anthropic.com/legal/privacy.
• We do not retain the message text after the translation is returned. It is not written to storage or logs.

Buyer personal data

Buyer names, order IDs, tracking numbers and message contents are handled in memory only for the purpose of translation and template filling. They are not persisted by the extension. Variable values you type into the Compose tab are used to fill your reply and are not saved.

Permissions and why

• storage — save your API key, snippets, settings, and usage count locally.
• sidePanel — show the translate/compose panel.
• clipboardWrite — copy a localized reply to your clipboard.
• contextMenus — the right-click "Translate with InboxLingo" action.
• host access to eBay/Etsy — inject the optional on-page "Translate" button on message pages. The extension reads message text on those pages only when you click that button.
• host access to extensionpay.com — used only by the ExtensionPay library to manage your Pro subscription and confirm payment. No buyer messages or API keys are sent there.

Payments

Pro subscriptions are processed by ExtensionPay (extensionpay.com), which uses Stripe for card processing. Your payment details are entered on ExtensionPay's / Stripe's pages and are handled under their privacy policies; InboxLingo neither receives nor stores your card information. The only data associated with a purchase is the subscription status the extension reads back to unlock Pro features.

Changes

If this policy changes, the "Last updated" date will change and the new version will ship with the extension update.

Contact

Questions: contact the developer via the Chrome Web Store listing support link.