TL;DRCreators

Privacy Policy

Version 1.2. Last updated 1 November 2026.

This covers TL;DR Creators, at creators.tldrbrands.com. It explains what we hold about you, why, and what you can make us do about it.

The short version: we hold what we need to cast you, pay you, and run your bookings. We do not sell it, and we do not share creator contact details with brands, except the delivery address on a booking where that brand sends the product themselves. If you accept cookies, Google and Meta also receive the measurement described under Cookies and measurement.

Who is responsible

TL;DR Brands is the data controller for everything described here. To contact us about your data, email the TL;DR Brands team or message us in the app.


If you are a creator

What we hold

  • **Who you are:** name, email, phone, location and postcode, age band, gender.
  • **Your work:** social handles and follower counts, niche and interest tags, links to past work, your intro video, and the videos you deliver to us.
  • **Your account:** applications, bookings, messages, delivery scores, and the fees agreed.
  • **Getting paid:** the payment details you give us, and what we have paid you.
  • **Delivery:** your address, when a brief means posting product to you.
  • **Technical:** sign-in records and basic usage logs.

Most of this you typed into the application form. Follower counts and delivery scores are added by us.

Why we hold it

  • To run TL;DR Creators: matching you to briefs, casting, and messaging you about work. This is our legitimate interest in operating the business you asked to join.
  • To perform the agreement between us once you accept a brief: managing the booking and paying you.
  • To meet our legal obligations, mainly tax and accounting records.

We only email you about work: matched briefs, your applications, your bookings, and payment. That is the service, not marketing.

What brands see about you

This is the part creators care about most, so it is precise.

A brand using the platform sees your **first name and last initial**, your city, age band and gender, your niche and interest tags, a **band** for your follower count rather than the number, your star rating, and how many bookings you have completed.

A brand never sees your email address, phone number, social handles, personal links, intro video or payment details. That is enforced in the software, not by policy alone.

If you deliver a video for a brand's brief, that brand sees the video: it is what they paid for.

One exception, and you are told at the moment it applies: if a brand sends you a physical product themselves (a paid booking or gifted product) and they choose you, we share the delivery address you gave, with your full name on the address line, with that brand, so they can post it. That is all they get, and they may only use it to send it. Where TL;DR arranges delivery, the brand does not see your address.

Who else we share it with

The suppliers who make the platform work, plus Google and Meta if you accept cookies:

  • **Supabase** (database and sign-in links)
  • **Vercel** (hosting)
  • **Brevo** (the emails we send you)
  • **Cloudflare R2** (storage for the videos you upload)
  • **Google** (Google Analytics, only if you accept cookies)
  • **Meta** (the Meta pixel and the Conversions API, only if you accept cookies)
  • Our accountants, for payments

We do not sell your data, and we do not share it with brands beyond what is listed above.

How long we keep it

  • Your profile stays while you are on TL;DR Creators. Ask us to remove you and we do.
  • Bookings, invoices and payment records: 7 years, because tax law requires it.
  • Delivered content: kept as long as the client who paid for it holds usage rights.
  • Messages: for as long as your account is open.

If you are a brand

What we hold

  • **Your account:** your name, work email, company name and website.
  • **Your activity:** the briefs you post, who you shortlist, decline and book, and your messages with creators.
  • **Billing:** your subscription status, and a record of every charge. Stripe holds your card details; we never see or store a card number.
  • **Technical:** sign-in records and basic usage logs.

Why we hold it

  • To provide the service you are paying for, and to take payment for it.
  • To keep the marketplace safe: brief moderation, and looking into a problem when one is raised.
  • To meet our legal obligations, mainly tax and accounting records.

Who else we see it with

The suppliers above, plus **Stripe** for payments. Your company name is visible to creators on your briefs, because a creator deciding whether to work with you is entitled to know who you are.

How long we keep it

Account records for as long as your account is open, plus 7 years for anything that is part of a financial record.


Your rights, whoever you are

Under UK data protection law you can ask us to:

  • show you what we hold about you
  • correct anything wrong
  • delete it, where we do not have to keep it for tax or contractual reasons
  • stop using it for a particular purpose
  • send it to you in a portable form

Email us and we will answer within one month. If we get it wrong, you can complain to the Information Commissioner's Office at ico.org.uk.

Cookies and measurement

We use a cookie to keep you signed in. The site works if you reject everything else.

If you accept, we load:

  • **Google Analytics 4**, to measure how the site is used. That includes a sign-up event when a brand account is created, and a lead event when a creator application is created.
  • **Meta**, in the browser (the Meta pixel) and from our server (the Conversions API), to see whether an advert led to that new account or application. For a record we actually created, the server sends Meta a SHA-256 hash of the email address, not the address itself. The Meta browser identifiers (_fbp and _fbc) are included only if you accepted. We also send the IP address and the browser of that request, so Meta can match the conversion to the advert click.

Google and Meta are US companies and may process this information in the United States. A transfer of personal data from the UK to the United States needs a mechanism under UK GDPR. Email us if you want to know which mechanism applies to a supplier.

The public marketing pages also use Vercel Analytics. That does not use cookies and does not set an identifier on your device. It stays on if you reject.

Separately, we store in your browser the first page you opened on this site, the address of the page that linked you here, and the campaign parameters on that first address (utm_source, utm_medium, utm_campaign, utm_content, utm_term, fbclid and gclid). If you create a brand account or submit a creator application, we save those values on your record so we know which visit it came from. Clearing site data for this site removes them from the browser. Rejecting cookies does not delete a value already saved on your record. Ask us if you want that removed.

Changing your mind

Use Cookie settings in the footer, or the banner while it is open, and choose Reject. We then stop loading Google Analytics and Meta on later visits. Cookies those tools have already stored stay in your browser until you clear them. Email us if you want us to stop holding the campaign details on your record. We answer within one month, as with any other request in this policy.

Sign-in links

We sign you in with a link sent to your email rather than a password. Anyone with access to your inbox, or to a link you forward, can sign in as you until it expires. Do not forward sign-in emails.

Changes

If we change this policy we update the date at the top and, where the change matters, tell you in the app.


Written to be read. It is a plain-English description of what we actually do, and it does not reduce your rights under UK data protection law.