Privacy

Two things, both in your browser's local storage, neither of them ever sent anywhere:

• buttoncraft:favorites — the button styles you marked with the heart icon. Written only when you click that control, so it exists only if you asked for it.
• buttoncraft:consent — your answer for each of the two items below, when you decided, and which version of this disclosure you saw. Without it the site could not remember a refusal.

Clearing your browser storage for this site removes both. ButtonCraft sets no cookies of its own; the only cookie this site can cause is the sign-in session cookie described further down, and only after you have signed in.

Audience measurement and the support button are different things done by different companies, so you answer for each one separately. Allowing one does not allow the other, and both start switched off. If you change this disclosure — for example by adding a third-party service — the stored answer is discarded and you are asked again rather than carried over.

With your permission the site loads Vercel Web Analytics to count page views. What the browser sends is the page pattern and path — for example /button/[id] and /button/aurora — plus a small number of named events such as opening the Pro page. Those events carry only catalog identifiers and numbers: which button style, which component kind, a price already shown on the page. No search terms, no text you type, no identifiers of you.

The same permission also loads Vercel Speed Insights, which measures how fast pages load and respond — the standard Core Web Vitals, timings taken from your browser's own performance API. It is the same company, measuring the same visit, for the same purpose, which is why it is one choice and not two. What it sends are durations in milliseconds and the page pattern — nothing about you is attached.

Vercel is the processor here and runs the collection script; what it derives on its side, and for how long it keeps it, is governed by Vercel's own privacy policy. If you decline, the script is never loaded and no event leaves your browser.

The floating Buy Me a Coffee button is a script served by buymeacoffee.com. They act as an independent controller, not as a processor for ButtonCraft: what their script stores or sends is decided by them and cannot be established from this site's own code — which is precisely why it is behind a separate permission. See their privacy policy. Decline and the script is never requested.

Accounts are optional. Browsing, customizing and copying every free button works without one, and nothing on this site asks you to sign in to read it. An account exists for two things: carrying a Pro purchase between machines, and syncing the themes you compose in Pro Studio.

Sign-in is handled by Clerk, who act as processor. Your email address, password and login history live with them, not here. Clerk sets a session cookie when — and only when — you sign in; it is strictly necessary for the account to function, so it is not part of the optional choices above.

What this site stores about an account is deliberately thin: the opaque Clerk user id (user_…), the orders that id has made, any access granted to it, and the Studio themes you chose to sync. No email address, no name, no payment details. When support needs to know who an id belongs to, that is looked up in Clerk.

Deleting your account in Clerk removes your identity there. To have the rows keyed to your id removed here as well, write to the address below and say so.

No advertising, no advertising networks, no profiling, no cross-site tracking, no session recording or heatmaps, no A/B testing, no newsletter tracking pixels. Nothing is sold or shared for marketing. Accounts hold an identifier and a purchase history — never a behavioural profile.

Buying ButtonCraft Pro happens entirely on Lemon Squeezy, who act as merchant of record and handle payment data. ButtonCraft never sees your card details. Those pages link out to Lemon Squeezy; nothing of theirs is embedded here.

Withdrawing permission is exactly as easy as giving it — one click, from the footer of any page, or right here:

Cookie settings

If anything is switched on, that button turns everything off in one click and reloads the page — a reload is necessary because neither script can be removed once it has loaded. If everything is already off, it reopens the banner with nothing pre-selected. Either way the answer is also discarded after six months, so a decision made once does not bind you forever.

Under the GDPR you can ask for access to, correction of, or deletion of personal data relating to you, object to processing, and complain to a supervisory authority — in Poland that is the President of the Personal Data Protection Office (UODO).

In practice ButtonCraft holds no account and no contact record for you, so the fastest route for most requests is your own browser storage. For anything else, write to michal@zt1.io.

Every button in the free catalog is plain HTML and CSS under the MIT license. It contains no scripts, no network requests and no tracking of any kind — nothing from this page follows the code into your project.