Privacy Policy

This page explains what BoardUI collects when you use boardui.com or the BoardUI CLI, why, and what you can ask us to do about it.

Last updated 10 November 2026

Who is responsible

BoardUI operates this website and is the data controller for the processing described here. For anything in this policy — including access, correction or deletion requests — write to hi@boardui.com and we will respond within 30 days.

Website analytics

We measure how the site is used: which pages are visited, which install and Pro buttons get clicked, where on a page those clicks land, and which template previews get opened. That is how we know what to build next. This runs on PostHog, hosted in the EU.

What it does depends on where you are, and on what you chose. If you are in the EU, the EEA or the UK, you are shown a prompt asking whether anything may be kept on your device. Until you accept, and for good if you decline, it is configured to leave nothing behind at all:

  • No cookies and no local storage. The identifier that groups your actions within a visit exists only in your browser tab's memory and is gone when you close or reload it. Outside those regions it is instead saved in your browser, so a second visit is recognised as the same one as the first. If you accept the prompt, you get that same treatment by choice. You can change your mind at any time, and declining costs you nothing: the measurement still happens, it just keeps no record of you between visits.
  • No profiles in the EU, the EEA or the UK. In those regions nothing groups your visits together, so there is no record of you to build. Elsewhere, the identifier saved in your browser lets us see that a return visit came from the same browser as an earlier one, and the pages and clicks from both are grouped under it. That record is built on the identifier and nothing else: we hold no name, no email address and no account against it, and we cannot tell who you are from it.
  • Click and scroll maps. We collect where clicks land on a page and how far down it people scroll, as plain coordinates attached to the page address. They are pooled across visitors and are not tied to you.
  • No session recording in the EU, the EEA or the UK. If you are in those regions we do not record your session at all: replay is switched off in code and never starts. Elsewhere it may record how the page is used, including scrolling and mouse movement, with every form field masked so that what you type is never captured. Your region is worked out from your IP address as the page loads, and is not stored. Either way, nothing is written to your device.
  • No data selling. These analytics are ours, and are not sold or handed to anyone else. Advertising is separate, and is covered in the next section.

Your region is worked out from your IP address as the page loads and is not stored. If it cannot be established, you get the EU treatment. Vercel's audience and performance measurement, which runs alongside all this, is cookieless everywhere. The Meta Pixel and the Google tag described next follow the same prompt: in those regions neither loads at all until you accept it.

Advertising and the Meta Pixel

We advertise BoardUI on Facebook and Instagram. So that we can tell which of those ads actually bring people who install components or buy Pro, this site loads the Meta Pixel, a piece of Meta's code, on every page.

In the EU, the EEA and the UK it does not load at all unless you accepted the prompt described above, because it does not leave your device untouched:

  • It sets a cookie, which is why it is behind the prompt. The pixel stores an identifier called _fbp in your browser, and reads one called _fbc if you arrived here by clicking one of our ads. Both persist until they expire or you clear your browser data.
  • It sends your visit to Meta. Each page you open here reports the page address, the referring page, your browser and your IP address to Meta in the USA. We use it only for the pageview, and for knowing that an install or a purchase happened.
  • Meta may connect it to your account. If you are signed in to Facebook or Instagram in the same browser, Meta can match the visit to you, and will use it under their own terms as well as ours. We never see your Meta account, and we do not upload email addresses or customer lists to them.
  • It is used to show you ads. That includes showing BoardUI ads again to people who have been here, and helping Meta find people similar to them.
  • Starting and completing a purchase are reported. When you begin a checkout, and again if a Pro licence is bought, Meta is told it happened, with the amount, the currency and the plan. Some of that is sent by our own server rather than by your browser, so a tracking blocker will not always stop it. It is matched to you by the pixel identifier described above, and by the same IP address and browser your visit already reports. Your name, your email address and your billing details are not part of it, and never go to Meta.

If you would rather it did not run: any content or tracking blocker stops the pixel loading, as does the tracking protection built into Firefox, Safari and Brave. What Meta does with data they already hold is controlled in your Meta ad settings, and their side of it is described in the Meta Privacy Policy. Blocking it costs you nothing on this site: every page works exactly the same without it.

Advertising and the Google tag

We also advertise BoardUI on Google. So that our ads can be shown again to people who have already been here, this site loads the Google tag, a piece of Google's code, on every page.

It follows the same rule as the Meta Pixel: in the EU, the EEA and the UK it does not load at all unless you accepted the prompt described above. Google asks for the same consent in Switzerland, where we do not show the prompt, so there it does not load at all.

  • It sets cookies. The tag stores an identifier called _gcl_au in your browser, and one called _gcl_aw if you arrived here by clicking one of our Google ads, keeping the same ad-click details in your browser's local storage under _gcl_ls. They last up to 90 days, or until you clear your browser data.
  • It sends your visit to Google. Each page you load here reports the page address, the referring page, your browser and your IP address to Google in the USA.
  • It is used to show you ads. Google can add you to a list of people who have visited BoardUI and show you our ads on Google Search, YouTube and other websites and apps that carry Google ads. If you are signed in to Google in the same browser, Google can connect the visit to your account under their own terms. We never see your Google account, and we do not upload email addresses or customer lists to Google.
  • Purchases are not reported through it. If you arrived by clicking one of our Google ads, the purchase report described under BoardUI Pro purchases is sent by our own server, as before.

If you would rather it did not run: any content or tracking blocker stops the tag loading. How Google uses data for ads is controlled in your My Ad Center settings, and their side of it is described in the Google Privacy Policy. Blocking it costs you nothing on this site: every page works exactly the same without it.

Affiliate links

Some creators recommend BoardUI and earn a commission when someone they sent buys Pro. To know who sent a buyer we use Affonso, an affiliate service based in Germany. Its code loads only when the page address carries one of the parameters affiliate links use, such as ?via=, or the affonso_id described below, and on no other visit.

  • Outside the EU, the EEA and the UK it sets a cookie. It is called affonso_referral, with a companion called affonso_data that holds any discount the link carries. Together they record which creator's link you used, and they last 30 days unless you clear them. Affonso also records the click itself, with your IP address, browser, approximate location and the page that sent you here.
  • In the EU, the EEA and the UK nothing is stored until you accept the prompt described above, and from then on it works as just described. Until you accept, and for any creator's link you open after declining, your browser tells Affonso only that the link was clicked, along with the link's own tags, such as campaign tags or an ad's click id. Affonso says it records this without your IP address, browser or location. While you have not answered, that click is carried in the page address as affonso_id, so that accepting on a later page still credits the creator. It stops being carried once you answer, and we remove it from the page addresses our own analytics record. If you withdraw your consent, the cookies are deleted.
  • Buying credits the creator. If the cookie is there when you start a checkout, its identifier is passed to Stripe, our payment processor, with your order, and Affonso reads it from there. Our own record of the sale notes that it came from an affiliate click.
  • Affonso sees our orders, creators do not see you. Through its connection to Stripe, Affonso is told about Pro orders and refunds, including each order's amount, the email address it was placed with, and the details our checkout attaches to it, such as your browser and any ad click id. It records the orders that came from a creator, works out the commission, and reduces it if the order is refunded while the commission is still pending. It never receives your full card number. Creators see that a sale happened and what they earned, under an anonymous label, never your name or email address.

If you would rather it did not run: a content or tracking blocker that lists Affonso stops it loading, and the site works exactly the same without it. A purchase still reaches Affonso through Stripe, as described above.

If you join as a creator, you sign up with Affonso, which holds your account. When you do, Affonso tells us your name, email address and referral code, and we receive a private notification with them so we know someone joined.

Waitlist

If you submit your email address to join the waitlist, we store that address, and we receive a private notification containing it so we know someone signed up. We use it only to tell you when BoardUI is available and about significant changes to it — no unrelated marketing, and no sharing with anyone else. Ask us at any time and we will delete it.

If you join the Canvas waitlist at boardui.com/canvas, we also record, at the moment you sign up, the country your connection comes from (looked up from your IP address, which we do not keep), how you reached the site (the website that sent you, and any source or campaign tag in the link you followed) and how long you had the Canvas page open. We keep these with your address to understand where interest in Canvas comes from, and delete them with it.

The BoardUI CLI

Installing components with npx boardui records an anonymous, randomly generated installation identifier, the CLI version, the package manager, and the names of the components installed. It exists to tell us which components people actually use.

The CLI never sends your source code, file paths, dependency lists, email address or anything else you have written. The identifier is not linked to your website visits or your purchase.

BoardUI Pro purchases

Pro is sold by BoardUI, and the payment is handled by Stripe: you enter your card on Stripe's checkout page, and we never see your full card number. Stripe works out the VAT and issues your invoice, for which you give your name, email address, billing address and, if you have one, a VAT number.

We keep your licence key with your name and email address, so that we can email it to you through Resend, help you if you lose it, and check it whenever the CLI installs a Pro component. Activating the key on a computer also records that computer's network name. When a sale comes in, we get a private notification with the buyer's name, email address, country and plan. If you arrived by clicking one of our Google ads, Google is told that a purchase followed that click, and its value; what Meta is told is described above.

Purchases made before September 2026, or while our own checkout is unavailable, go through Lemon Squeezy as the seller of record, which holds those orders and their licence keys.

Server logs

Like any website, our host records requests — IP address, timestamp, page, browser — to serve pages, keep the site up and defend against abuse. These logs are short-lived and are not used to profile you.

Legal bases

Under the GDPR we rely on:

  • Legitimate interests for anonymous analytics, anonymous CLI counts and server logs: understanding and securing our own product. For visitors in the EU, the EEA and the UK this involves nothing stored on your device.
  • Legitimate interests for advertising: telling Google that a purchase followed one of our ads, and the Meta Pixel and the Google tag above outside the EU, the EEA and the UK. Inside them both run only with your consent, and the Google tag does not run in Switzerland at all. They and the affiliate links are the only things here that store an identifier on your device and share your visit with a third party. You can block any of them as described in their sections, decline or withdraw through the prompt, or object by writing to us.
  • Consent for the affiliate cookie in the EU, the EEA and the UK, given through the prompt. Legitimate interests for the rest of affiliate tracking there, which is the cookieless click record and the order details Affonso receives from Stripe, and for all of it elsewhere: paying the creators who recommend us for the sales they bring.
  • Consent for the waitlist: you give us your address by choosing to submit it, and you can withdraw at any time.
  • Legitimate interests for the details kept with a Canvas waitlist signup (the country, how you reached the site and how long the Canvas page was open): understanding where interest in Canvas comes from.
  • Contract for Pro purchases — we cannot deliver a licence without processing the order.
  • Contract for creators who join the affiliate program — we cannot credit and pay you without your details.

Who else processes this data

ServiceWhat forRegion
VercelHosting and delivery. Server logs, plus privacy-friendly audience and performance measurement.USA
PostHogProduct analytics for this website, configured to store nothing on your device.EU (Frankfurt)
MetaThe Meta Pixel: measures which Facebook and Instagram ads bring people who install or buy.USA
GoogleGoogle Ads: the Google tag, which lets us show our ads to people who have been here, and a note when someone who clicked one of our ads starts a checkout or buys Pro, with the value.USA
AffonsoAffiliate tracking: records which creator's link led to a Pro purchase, and works out their commission.EU
StripePayment for BoardUI Pro: checkout, card processing, VAT and invoices.EU (Ireland) and USA
ResendSends the email that carries your Pro licence key.USA
NeonThe Postgres database holding waitlist email addresses (and, for the Canvas waitlist, each signup's country, how the visitor reached the site and how long the Canvas page was open), anonymous CLI counts, and Pro licence keys with their buyer's name and email address.EU
TelegramA private message to us when someone joins the waitlist, joins our affiliate program or buys Pro, with their email address and, for the Canvas waitlist, their country, how they reached the site, how long the Canvas page was open and whether they are also on the BoardUI waitlist; for an affiliate, their name and referral code; or for a sale, their name, country and plan.Outside the EU
xAI (Grok)A notification to a member of our team, through a Grok automation, when someone joins the Canvas waitlist, with the same details as the Telegram message: their email address, their country, how they reached the site, how long the Canvas page was open and whether they are also on the BoardUI waitlist.USA
Lemon SqueezySeller of record for Pro purchases made before September 2026, or while our own checkout is unavailable, and their licence keys.USA

Where a provider is outside the EU, transfers rely on the European Commission's Standard Contractual Clauses or an equivalent safeguard in that provider's terms.

How long we keep things

  • Waitlist addresses — until we launch and have told you, or until you ask us to delete yours, whichever comes first.
  • Analytics events — retained by PostHog on our plan's standard schedule. They are anonymous, so they cannot be traced back to you.
  • Purchase records — as long as tax and accounting law requires.
  • The affiliate cookie — 30 days on your device, or until you clear it or withdraw your consent. Affonso keeps its click and commission records while we use the service. When we leave, we will have them deleted, which its terms commit it to within 30 days, except where the law requires them to be kept.
  • Server logs — a short rolling window set by our host.

Your rights

If you are in the EU or UK you can ask us for a copy of the personal data we hold about you, have it corrected or deleted, object to or restrict how we use it, and take it elsewhere in a portable form. Email hi@boardui.com and we will action it within 30 days, free of charge.

One honest limitation: our website analytics are anonymous by design, so we have no way to find “your” events in them — there is nothing tying them to you. That protects you, but it does mean we cannot extract or delete them individually. Waitlist and purchase data we can, and will. Anything the Meta Pixel or the Google tag sent about your visit sits with Meta or Google rather than with us, so requests about it go to them, through the settings linked above.

You also have the right to complain to your local data protection authority if you think we have got this wrong.

Changes to this policy

If we start collecting something new, we will update this page and move the date at the top. Material changes affecting waitlist subscribers will be emailed.

Questions? hi@boardui.com — or come and ask in the Discord. Back to boardui.com.