Skip to content
TACKO

AI Chat Handoff privacy policy

Last updated: November 12, 2026. This policy covers the AI Chat Handoff Chrome extension by Tacko (Sanja Malović), available from the Chrome Web Store and as a manual Chrome install. It applies to both versions.

What the extension accesses

The extension’s content script loads on chatgpt.com, chat.openai.com, and claude.ai, but it reads the conversation only when you click Read current chat. It does not run on other websites and does not access your browsing history.

Local processing and storage

Conversation extraction, preview, and editing happen locally in your browser. Conversation content is not uploaded to Tacko.

On your device, chrome.storage.local may hold: your preamble text, your message-scope preference, the daily free-transfer count, your Pro license key (if you activate one), your usage-statistics preference, a randomly generated installation identifier used only for optional usage statistics, a flag that the one-time first-use report was sent, and—if you choose Save—reviewed handoff drafts (see Saved drafts below).

The current extract and working draft are kept in chrome.storage.session, which Chrome clears when the browser closes. You can also clear the working draft with Clear saved draft. Clearing the working draft does not delete separately saved handoffs, your preamble, or the daily count.

Uninstalling the extension removes its local storage under normal Chrome behavior. The extension writes to your clipboard only when you click Copy draft; clear your clipboard separately if needed, since clipboard history is managed by your operating system.

Saved drafts

You can explicitly save a reviewed handoff draft on this device. Up to 20 drafts can be stored locally. A saved draft may contain conversation content you chose to keep. Saved drafts persist after you close the browser. They are not uploaded to Tacko. The extension does not encrypt them separately from Chrome’s own storage. You can delete individual saved drafts in the extension. Uninstalling the extension removes its local storage, including saved drafts, under normal Chrome behavior.

Sharing and transfers

We do not sell, share, or transmit your conversation, draft, preamble, or daily transfer count to Tacko. The extension does not use AI APIs or remote code. When usage statistics are enabled, the extension does make limited network requests for those statistics only (see below).

When you click Open with draft, the extension opens a new ChatGPT or Claude chat and places your draft in its message box. It never presses Send. Once the text is in that site’s message box, the site (OpenAI or Anthropic) can see it even before you send it, and its own privacy policy applies. If you prefer, use Copy draft and paste the text yourself.

Usage statistics

From version 0.1.8, when usage statistics are enabled, the extension sends limited pseudonymous usage and reliability events to tacko.io. Tacko forwards those events to Telemetry Tracker, our own monitoring service. That path is: extension → Tacko telemetry endpoint → Telemetry Tracker. This is separate from conversation content, which is not included.

Events may include: that the extension was installed or updated; that the first successful transfer completed (once per install); transfer or placement errors; and selected feature events such as keeping an existing destination draft. Each report may include the extension version, the browser family, the transfer direction (for example chatgpt→claude), an error or event type, and a persistent randomly generated installation identifier created by the extension. It never contains conversation content, prompts, summaries, chat URLs or IDs, your email, or your license key.

Usage statistics are on by default in the current implementation. You can turn them off at any time under Settings → Anonymous usage statistics; when they are off, nothing is sent. To prevent abuse, the tacko.io relay uses the sender’s IP address briefly as an in-memory rate-limit key; it is not stored or forwarded to Telemetry Tracker. Legal basis: our legitimate interests in measuring and fixing the extension (GDPR Art. 6(1)(f)); you can object at any time with that switch.

The Tacko website is separate

This extension policy does not describe website analytics. The tacko.io website loads Google Analytics and optional Tacko page-view telemetry only after analytics consent. It also uses cookieless Vercel Web Analytics and Speed Insights. Those website integrations can send visit and performance data to their providers; they are not part of the extension’s local processing. See our website privacy notice.

The extension does not send conversation content to these website analytics services. If you contact support by email, your email provider and ours process the message to handle your request. We handle email correspondence based on our legitimate interests in answering inquiries and support requests (GDPR Art. 6(1)(f)). See the website privacy notice for your rights.

Payments and license restoration

Website purchases are processed by Stripe. Stripe Checkout collects cardholder name, email, card details, billing address (at least country and postal code) and, optionally, a business VAT ID for invoicing. No VAT is charged (small taxpayer, Art. 94 ZDDV-1). Stripe issues an invoice/receipt. Stripe handles card details; we never see full card numbers. Tacko receives your name, email, billing country/postal code, amount, and purchase ID to fulfill your purchase and handle refunds (GDPR Art. 6(1)(b), contract). Payment records are retained by Stripe and as required by applicable tax law (Art. 6(1)(c)). We use your email and our SMTP email provider to send requested restore links, valid for 30 minutes, under the same contract basis. We use Resend (Plus Five Five, Inc., USA) as our processor for transactional email: after payment, and when you request it on the restore page, we send your purchase email address and your license key (with order reference, amount and date) to Resend to deliver the license to you (Art. 6(1)(b), contract). Resend stores message data and logs in the United States; transfers are covered by the EU Standard Contractual Clauses in Resend's DPA and the EU-U.S. Data Privacy Framework. We disable open and click tracking for these emails. We record the delivery status and time in Stripe customer metadata to avoid duplicate emails. We store a lowercase email in Stripe customer metadata for restore lookup (Art. 6(1)(b), contract). For fraud and duplicate-payment review, we record purchase session IDs in Stripe customer metadata and send a notice to info@tacko.io (Art. 6(1)(f), legitimate interests). To prevent abuse, transient in-memory rate limits use IP addresses and email hashes; these are not persistently stored (Art. 6(1)(f), legitimate interests). The signed license key contains no personal data. License verification happens offline in the extension; the extension never sends your license key to Tacko.

Contact and updates

For privacy questions or requests, contact info@tacko.io. Please avoid including private conversations in your message.

We will update this page if the extension’s data practices change.