Privacy policy

Last updated

This policy covers dashboardblocks.com, its accounts and its emails. Dashboardblocks is owned and operated by Gregory Lebret, a sole trader based in the United Kingdom, who decides what happens to your data (the "controller"). Questions and requests go to support@dashboardblocks.com.

We keep as little as we can. We don't sell your data, show ads or use advertising cookies.

If you only read the site

You don't need an account to read the docs or install the free blocks.

  • Analytics. We use PostHog, in cookieless mode, to count page views, copies of a block's install command, and clicks on our GitHub and X links. PostHog stores nothing in your browser and keeps no profile of you. To count unique visitors, it combines your IP address and browser with a value that changes every day, so a visit can't be linked to the next day's. PostHog also keeps your IP address with each event, which tells us roughly which country a visit came from. It stores this data in the EU.
  • Hosting. Every request reaches Vercel, which hosts the site. Vercel logs the request, with your IP address and browser, to run and protect the site, and keeps those logs for a short time.
  • Installs. When the shadcn CLI installs a free block, Vercel logs the request like any other.
  • Your browser. The site keeps your theme and preview settings in your browser's local storage, and a block preview with a sidebar remembers whether it's open in a cookie. We don't collect them or use them to identify you.

If you have an account

What we keep

  • Your account. When you sign in with GitHub or Google, we receive your name, email address, profile picture and that account's ID, along with sign-in tokens from GitHub or Google that we use for nothing else. We don't get your password. Each sign-in creates a session, stored with your IP address and browser to protect your account. A cookie keeps you signed in.
  • Purchases. For each purchase, Stripe tells us what you bought, the amount, the date, Stripe's IDs for it, and whether it was refunded or disputed. We also store when you ticked the box at checkout and its wording. We never see your card details. Stripe is the merchant of record for your purchase and sells All-Access through Link, its checkout. It holds your payment and billing details under Link's privacy policy.
  • Your token. We store only a hash of it, never the token itself. Each time it's used, we log the time, the item installed, the start of your IP address with the last part dropped, and the user agent. Template downloads are logged the same way. We use these logs to spot a token or account shared between people, and delete each entry after 90 days.
  • Teams. If you buy a team, we store its seats and who holds them. If you invite someone, we store the email address you typed until the invite is accepted, revoked or expires. An invite expires after 7 days, and an address whose invite wasn't accepted is deleted then. We log who was added to or removed from a seat, and when, to stop seats being passed around. The log records account IDs, never names or email addresses.
  • Release emails. We store whether you've opted in. Resend, which sends the emails, holds the addresses of everyone who opted in.
  • Support. We keep the emails you send to support@dashboardblocks.com and our replies.

Who sees what

  • If you hold a seat on a team, the team's buyer sees your name and email address on their account page.
  • Nobody else sees your account. We don't publish anything about you.

Why we use it

  • To run your account and deliver what you bought: the account, purchases, token, team seats and invites. This is needed to perform our contract with you.
  • To keep records of sales, as tax and accounting law requires.
  • To protect the site and the code: sessions, the token usage log and the seat change log. This is in our legitimate interest in stopping abuse.
  • To answer support emails and send team invites to the addresses a buyer types. This is in our legitimate interest in running the service.
  • To understand how the site is used, with analytics that keep no profile of you. This is in our legitimate interest in improving the site.
  • To send release emails, only with your consent, which you can withdraw at any time.

Emails we send

  • Purchase confirmation, after you buy, confirming you asked for immediate access and that your right to cancel has ended.
  • Team invites, to the address a team's buyer types.
  • Release emails when we publish new paid blocks or templates, only if you opt in on your account page. Each one has an unsubscribe link. Unsubscribing turns the opt-in off, and Resend marks your address as unsubscribed.
  • Important notices about your account, your team or a change to our terms.

Stripe sends receipts and refund notices from Link. We reply to support emails from support@dashboardblocks.com. Resend keeps a log of each email it sends for a limited time, set by its plan.

Who processes your data

These companies process data for us, each only for the job listed:

CompanyWhat it doesWhere
VercelHosts the site and runs its server codeUnited States
NeonHosts the databaseUnited States
GitHub and GoogleSign you in, when you choose them. GitHub also serves template downloads.United States
Stripe (Link)Takes payments as the merchant of recordUnited States and Ireland
ResendSends team invites and release emails, and holds the release listUnited States
PostHogAnalytics, without cookiesEuropean Union
Google WorkspaceHolds support emailUnited States

Where data goes to the United States, these providers rely on the UK Extension to the EU-US Data Privacy Framework, or on the UK Addendum to the EU standard contractual clauses.

How long we keep it

  • Your account, sessions, token and team seats: until you delete your account. Sessions end when you sign out or after they expire.
  • The token usage and download logs: 90 days.
  • Invites: until accepted, revoked or expired (7 days).
  • Analytics events and hosting logs: PostHog and Vercel keep them for the time their plans set.
  • Purchase records: as long as tax and accounting law requires, even after you delete your account.
  • Seat change logs: as long as the team's purchase record, by account ID only.
  • Release email list: until you delete your account. After you unsubscribe, Resend keeps your address marked as unsubscribed, so it isn't emailed again.
  • Support emails: as long as we need them to help you and for our records.

Deleting your account

Delete your account from your account page. It signs you out everywhere, revokes your token, frees your team seat, removes your address from Resend's release list, and deletes your account data. We keep only the purchase record Stripe and tax law need, and the seat change log, which holds your account ID but not your name or email address. A team's buyer must remove the people on their seats first, or email support. You can also email support@dashboardblocks.com and we'll do it for you.

To delete your payment data held by Link, ask Link support.

Your rights

Depending on where you live, you can ask us for a copy of your data, to correct it, to delete it, to move it to another service, or to stop or limit how we use it. You can withdraw consent at any time. Email support@dashboardblocks.com and we'll answer within a month. You can also complain to the UK Information Commissioner's Office (ico.org.uk) or the data protection authority where you live.

Children

Dashboardblocks is for developers. It isn't meant for anyone under 16, and we don't knowingly keep data about them.

Changes to this policy

We'll update this page when what we keep or who processes it changes, and change the date at the top. If a change affects how we use data we already have, we'll email account holders before it applies.