Privacy Policy

Your clipboard history never leaves your Mac. There is no Tucket account, no cloud sync, and no server of mine that ever receives what you copy. The data I do handle is limited to website analytics, what is needed to sell you a licence and keep it activated, and anything you choose to send through the feature request page.

Everything Tucket captures is written to a local database (SwiftData) inside the app’s own folder on your Mac. That includes clip contents, the app each clip came from, timestamps, and any tags or pinboards you create.

• None of it is uploaded, backed up to a server, or shared with me or anyone else.
• I cannot see your clipboard history. There is no mechanism by which I could.
• Deleting a clip in Tucket deletes it locally. Deleting the app’s data folder removes the history entirely.
• If you back up your Mac (Time Machine, for example), your Tucket data is included in that backup like any other local file.

Tucket runs a detector over everything it captures and refuses to store content that looks like a secret: API keys, passwords, credit card numbers, private keys and .env dumps. When that fires, the clip is blocked rather than saved.

You can also add specific apps to an ignore list, so Tucket never captures anything copied from them, and you can pause capture entirely at any time.

Reading text out of images and any AI summarising happen on your Mac, using Apple’s own Vision and Apple Intelligence frameworks. Your images and text are not sent to me, to Apple’s servers, or to any third-party AI service for those features.

There are exactly three cases, and none of them carry your clipboard contents:

• Link previews (opt-in). If you turn this on, Tucket fetches the page behind a copied link to build a preview. That means the site you copied a link to can see a request coming from your IP, as it would if you opened the link yourself. It is off unless you enable it.
• Update checks. Tucket asks trytucket.com/appcast.xml whether a newer version exists. Like any web request this carries your IP address and app version. I do not use it to build a profile of you.
• Licence activation. Activating or deactivating a Mac sends your licence key and a device identifier to Dodo Payments, who run the licensing, so the three-device limit can be enforced.

Separately from the app, trytucket.com uses two analytics tools:

• Microsoft Clarity — records anonymised session replays and heatmaps of how people move through this site, so I can see where the page confuses people. It sets cookies and the data is processed by Microsoft.
• Google Analytics 4 — aggregate traffic and conversion numbers (visits, which sections get read, whether checkout was started).

The demo video at the top of the homepage is hosted on YouTube. Until you press play, all that loads is its thumbnail image — the player itself, and any cookies that come with it, only load if you actually start the video, and then through youtube-nocookie.com rather than the usual domain.

All of this is about the website, not the app, and none of it has any access to your clipboard. If you would rather not be measured, a content blocker or your browser’s tracking protection will stop it, and the site works exactly the same without it.

Checkout is hosted and handled by Dodo Payments, who act as the merchant of record for the sale. They collect your name, email address, payment details and the billing country needed to charge the right tax, and they issue and email your licence key.

Your full card details go to Dodo and their payment processors, never to me. What I can see is limited to the order record: your email address, what you bought, and whether it succeeded, which is what lets me support you and process a refund if you want one.

After a successful payment Dodo sends you back to this site with details in the URL, which is how the confirmation page can greet you by email address. That happens in your browser and is not stored anywhere by me.

If you request a feature on the feature request page, I store what you write, any screenshot you attach, your name and your email address in a database hosted by Supabase.

• Your request, its screenshot and your name appear publicly on that page as soon as you send them. I can switch on review, edit, or remove any request.
• Your email address is never shown to anyone, and is only used to follow up on that request.
• Upvoting is anonymous. Your browser keeps a random identifier so one browser counts once, and I keep a one-way scrambled form of your IP address to spot vote stuffing, never the address itself.
• Declining a request deletes its screenshot. To have a request and your details removed entirely, email me.

If you email me, I keep the thread so I can help and so I have a record of any refund or licence issue. I do not add you to a mailing list, and there is no newsletter to unsubscribe from.

Depending on where you live you may have the right to see the personal data held about you, correct it, have it deleted, or object to it being processed. In practice, for Tucket that means your order record, any feature request you sent, and any email thread, since everything else stays on your own machine.

Email hello@arpitchandak.com and I will action it. For data held by Dodo Payments as merchant of record, or by Microsoft and Google as analytics providers, their own policies apply as well, and I am happy to point you in the right direction.

Tucket is a developer and designer tool. It is not directed at children under 16.

If what Tucket collects ever changes, this page changes first and the date at the top moves. Anything that would meaningfully alter what leaves your Mac would ship as a visible change in the app, not quietly.

Tucket is made by Arpit Chandak. Questions about any of the above, or about your own data, go to hello@arpitchandak.com and I will reply.