Privacy

What we collect if you join the waitlist, why we collect it, who sees it, and how to make us delete it.

Last updated 2 October 2026.

Who is responsible for your information

Preselly is a brand of Rijksen Assets, a Delaware company in the United States. Write to bas@preselly.com and a real person reads it. For anyone in Europe or the United Kingdom, Rijksen Assets is the data controller for everything described on this page.

What we collect when you join the waitlist

The form asks for two things, your name and your email address. That is the whole form. We do not ask for a company, a phone number, a website or a card.

Along with those two, our own server records five small things. Which button on the site you pressed to open the form, the moment you pressed send, the two letter country code our host works out from your connection, which browser and device you are on, a thing every site you visit is told, and, if you came here from a link we placed somewhere, the name of that link and the address of the page it sat on. If that link was an advert on Meta or Google, the record also keeps the click code they add to it, so we can tell which advert brought you. That is the entire waitlist record. We do not store your IP address in it. What this site and X’s tag note on their own is under cookies and tracking below.

Why we collect it, and what allows us to

We collect it so we can tell you when your turn comes for your free page, and so we can write back to you personally. That is the only reason the list exists.

If you are in Europe or the United Kingdom, the lawful basis for your name and your email is your consent, which you give by typing them in and pressing send, and you can withdraw it at any time by asking us to remove you. The button, the time, the country code and the browser description are kept for one narrow reason, which is spotting automated signups, and the lawful basis for those is our legitimate interest in keeping the list free of junk. The name of the link you came from is kept for one narrow reason too, which is knowing which places are worth paying for, and the lawful basis for that is our legitimate interest in not spending money on advertising that brings nobody. If you go on to become a client, the basis becomes the contract between us. Our accounting records are kept because the law requires it.

The email we send you

We only write to you about the thing you asked about, which is the free page you are waiting for. We do not put you on a newsletter and we never send you another company’s offers. Every message comes from a real address that a person reads.

To stop them, reply to any message we send and say so, or write to bas@preselly.com. We take you off the list the same day we read it, we delete your name and your email address, and we write back to confirm it is done.

Who sees it

We do, and the few companies we need to run this. We do not sell your information and we do not rent it. Our own code never sends your name or your email address to an advertising company. Two advertising companies, X and LinkedIn, do get information about visits to this site through their advertising tags. Each uses it to measure our adverts and to show adverts, under its own privacy policy. The part on cookies and tracking below says where each tag runs and what each one gets.

Your waitlist record is written straight to a key value store run by Cloudflare, Inc., a United States company, on the same hosting as this site. To send you our welcome email, your name and your email address also go through our email, Google Workspace. Our own code sends them to nobody else. We export the list to our own records from time to time so we can work from it.

This site is hosted by Cloudflare, Inc. So are the pages we build for clients. Our email runs on Google Workspace, which is Google LLC, a United States company. If you become a client, your card runs through our payment processor, Stripe, Inc., a United States company. They hold your card number. We never do. Our accountant and the United States tax authorities see invoices and payment records, because the law requires it. Every one of these acts on our instructions, for the job in front of it, and for nothing else.

Where your information is held

Mostly in the United States. If you write to us from Europe, that means your information leaves your country when you send it. The providers above run standard contractual clauses for exactly this, and we rely on them. Notes on how our pages are used are stored with Cloudflare, which may keep them in Europe.

How long we keep it

Your waitlist record stays until you ask us to take you off, or until you tell us you are not interested. If we close the waitlist for good, we delete the whole list. Emails between us are kept while we are in touch and for two years after our last contact. If you become a client, the copy, the pages we hold for you, and the numbers our counter writes down are kept while you are with us, and deleted when you ask. Notes on how our pages are used are set to delete after 24 months, and replays of visits after 12 months, as described under cookies and tracking. Invoices and payment records are kept for as long as tax rules require. When a period ends, we delete it.

Cookies and tracking

We buy adverts on X, so this site can run X’s advertising tag. Our host guesses your country from your connection before the page is sent. If it places your connection in the European Union, the United Kingdom, Norway, Iceland or Liechtenstein, which this page calls Europe, or it can’t place it at all, the tag is left out of the page and nothing loads from X. Anywhere else, Switzerland included, the tag is in the page. Outside code also loads in one more place. The card page, which our email sends you to when you pay, loads Stripe’s payment script from Stripe’s own server, wherever you are, and your card goes into Stripe’s boxes, not ours. To check for card fraud, Stripe’s script may load a helper of its own, which can come from another company Stripe uses, such as hCaptcha. Some card links skip that page and send you straight to Stripe’s own checkout page. Apart from the X and LinkedIn tags where they run, and Stripe on the card page, our pages carry no script, picture, font or frame from another company.

Where it runs, the tag loads from X’s own server on the public pages of this site, the card page and the cancel page included. It is left out of our private staff and numbers pages, the setup pages we make for each client, and our split test addresses. It sends X the full address of each page, including anything after a question mark in it, and what any server sees on a visit, like your connection’s address and your browser. On the card page and the cancel page, that address holds the private code from the link in your email. It can set cookies, some under X’s name and some under this site’s name, that hold codes so X can recognise your browser, and the click code X added to the link if you came from one of our adverts on X. If you are signed in to X in the same browser, X can link all of this to your X account. When anyone opens our thank you page, which is where joining takes you, the tag tells X a sign up happened. It does not check that one did. Our code never hands X your name or your email address. X’s script does run on the thank you page, which shows them back to you, and we can’t control what X’s own script reads.

The sure way to stop the tag is to block it, with a tracker blocker or your browser’s settings. Every part of this site works the same without it. Turning off personalised ads in your X settings changes the adverts X shows you, but it does not stop the tag sending. On the card page, Stripe’s script can also note details about your device and how you use that page, and set Stripe’s own cookies. Stripe uses them to stop card fraud, under Stripe’s own privacy policy. Our own measuring is described below.

We also buy adverts on LinkedIn, so this site can run LinkedIn’s advertising tag. It runs only on our public pages. Those are the homepage, the pricing, free page, questions, about and privacy pages, and the thank you page you see after you join. It is never on the card page or the cancel page, and never on our private pages. It is also left out if our host places your connection in Europe or in Switzerland, or can’t place it at all. And it is never added for our own browsers, the ones that carry the leave me out note described below. Where it runs, it loads from LinkedIn’s own server. It sends LinkedIn the full address of the page, the page that sent you here, and what any server sees on a visit, like your connection’s address and your browser. It can set cookies, some under LinkedIn’s name and some under this site’s name, so LinkedIn can recognise your browser. If you are signed in to LinkedIn in the same browser, LinkedIn can link your visit to your LinkedIn account. LinkedIn uses it to measure our adverts, to show us totals about the kind of people who visit, and to show adverts, under LinkedIn’s own privacy policy. Our code never hands LinkedIn your name or your email address. LinkedIn’s script does run on the thank you page, which shows them back to you, and we can’t control what LinkedIn’s own script reads. The sure way to stop the tag is to block it, with a tracker blocker or your browser’s settings. Every part of this site works the same without it. Changing the ad settings in your LinkedIn account changes the adverts LinkedIn shows you, but it does not stop the tag sending.

One thing we do count, and it happens before you get here. When we place a link somewhere else, in a newsletter or a listing, that link goes through an address on this site that counts the visit and sends you straight on to the homepage, with the link’s name still on the address. If an advert on X sent you, the click code X adds goes along on the address too, and nothing here writes it down. The counter writes down the name of the link, the moment, the country code our host works out from your connection, which browser and device you are on, and the address of the page the link sat on. It writes down no name, no email and no connection address, it sets nothing in your browser, and it is how we tell an advert that worked from one that did not. If we ever add anything the paragraph above rules out, that paragraph changes before it goes on, not after.

We also count how many people open the public pages of this site, the homepage, about, pricing, free page, questions, terms, our two research pages and this page. Our own server does it, as it answers the page, and it writes down five things. The day and the time, which page, which site sent you if one did, the name of the link you came by if it had one, and a short scrambled string it makes from the date, your connection and the browser description so it can tell one person from two. Your connection’s address itself is never written down. The date is mixed into the string, so the same person on two days gets two different strings. Nothing is set in your browser and no part of this runs in your browser. It is stored with Cloudflare, our host, and nobody else sees it. We keep it for 45 days and then it deletes itself.

We also measure how our eligible public pages are used, and record visits to them, with a small script of our own that comes from this site with the page. Eligible means every page of this site except our private staff and numbers pages, the setup pages we make for each client, and anything that is not a page, and the script never runs for our own browsers. It does run on the card page, but Stripe’s card boxes sit in Stripe’s own frame, which our script cannot read. It notes how far down you scroll, which parts are on your screen and for how long, where you stop and what you come back to, what you click, and how long your pointer rests on a button or a price. If you select or copy something, it notes which part of the page, never the words. On the waitlist form it notes which box you were in and whether you sent it, never what you typed. It also keeps the page, the name of the link you came by, the site that sent you, your kind of device and screen size, the country code our host works out, how fast the page loaded, and short error codes. It can tell where a part of the page sat on your screen and for how long. It cannot tell whether you read it. Your connection’s address is never stored, and neither is your name, your email or the full browser description. A scrambled form of the address is used only to stop floods of traffic, and that scramble changes every minute.

Our host guesses your country from your connection before the page is sent. If it places your connection in Europe or Switzerland, or can’t place it at all, the script is left out of the page and nothing about your visit is measured or recorded. Anywhere else the script starts when the page loads. It shows nothing on the page and asks nothing. On the homepage, about, pricing, free page, questions and our two research pages, it also records a replay of your visit, which is what the page showed and how you scrolled, moved and clicked, so we can see where a visit goes wrong. Everything you type is hidden in your browser before anything is sent, and so are any words that are not part of our own page, so the replay shows stars in their place. The replay never runs on the card page, and Stripe’s card boxes sit in Stripe’s own frame, which our script cannot read. To stop it, press turn off measuring on this page. That stops the script in every tab of this site you have open, throws away anything still waiting in your browser, and our script sends nothing more. Blocking it with a tracker blocker works too. That does not touch X’s tag or our server’s count of page opens, both above. Turning it off is remembered in your browser until you clear it. To work, the script keeps three things in your browser. Whether you turned it off, a random visit code for the tab you have open, and a short queue of notes and replay pieces waiting to be sent. Anything still waiting when you close the tab, for example because you were offline, stays in your browser with its visit code, and is sent the next time you open one of our pages where our measuring runs. Turning it off, or clearing this site’s data in your browser, deletes it. None of them is a cookie, and none of them can be read by another site.

We do this to find the spot where people stop on a page, so we can fix it, to tell which adverts bring people who stay, and, from totals and never from one visit, to learn what makes a page work across pages, seasons and the brands we build for. Rijksen Assets decides what is kept and why. The notes are stored with Cloudflare, Inc., our host, which acts only on our instructions. We do not measure or record visits from Europe. You can turn it off at any time, as said above. That stops what happens next, and what was already sent you can ask us to delete. Notes are set to delete themselves after 24 months, and replays after 12 months. A small index that points to them is not on that timer yet. Totals, which hold no single visit, are kept with no end date. We never sell any of it, and a visit here is never joined to a visit on any client’s page.

To have your notes or replays deleted, write to bas@preselly.com and we will tell you what we can find and delete.

Our own cookie says one thing, and it is leave me out. There is a private page we use to read these counts, and opening it puts a small note in our own browser so that our own visits stay out of the numbers. That page sets it, and it holds one character. No reader of this site can be given it, because no reader can reach that page. X’s cookies, and the ones Stripe’s script can set on the card page, are described above.

There is one more thing, it lasts a moment, and it only happens if you join the list. Your first name and the email address you typed are put in your own browser’s memory for the second it takes to open the thank you page. That page reads them, wipes them, and then shows them back to you, so you can see we wrote your address down right. Our own code never sends that copy anywhere. X’s tag, where it runs, is on that page too, as said above. The copy is not a cookie, and closing the tab clears it anyway. Nothing is counted from it. Apart from the cookies above and the three things our measuring script keeps, that is everything this site’s own code puts in a browser.

What you can ask us to do

Email bas@preselly.com and ask us to show you what we hold about you, correct anything wrong, delete it where we are not required to keep it, restrict what we do with it, stop using it for something, or send it to you in a form you can take elsewhere. Say which one in a sentence. We answer inside thirty days. It costs you nothing and you do not have to give a reason.

If you are in Europe or the United Kingdom and you think we have handled this badly, you can complain to your own country’s data protection authority. We would rather you told us first, because we can usually fix it the same day.

If you are in California, we do not sell your personal information. X’s tag, described under cookies and tracking, may count as sharing it under California law. This site does not yet act on browser privacy signals such as Global Privacy Control, so the way to stop the tag is to block it, as described there. You can ask for the same things listed above.

If we build pages for you

This part is for clients rather than for visitors. We hold your answers about your brand, the pages we build, and the copy in them. We never ask for a login to your store or your domain. We never ask for one to your ad account either. We never hold your card number, and we never ask for anything about your customers.

There are two things we ask you to send us, and neither one is a login. First, before your page goes live, you send us your own tracking ids, your ad pixels and your analytics id, so they go on the page we build and your own tools count it. Nothing of ours goes in your store, and none of that gives us any way into it. Second, to see how the page is doing, you send us a picture of your own results screen, or an export of it. That is the only way your ad numbers ever reach us. We never ask to be added to your ad account and we are never inside it, so we can never spend a dollar, run an ad or move a budget, and there is nothing about your customers in what you send.

The page we build carries one small counter of ours. It writes down two things. That somebody arrived on that page, and that somebody clicked from that page to your store. It sets no cookie and it stores nothing in a visitor’s browser. It holds no IP address, no name, no email and nothing else that says who a person is. It can never see your checkout or anything about your customers. If that ever changes, this page changes first, and we put a data processing agreement in front of you before it does.

Your own tracking goes on the pages we build as well, next to that one small counter of ours. The visitor data from those pages is yours. It comes to you, not to us. It runs under the privacy notice and the consent setup your own site already has, because the page sits on your domain. We run no ad trackers on your pages. We do not profile your visitors and we sell nothing about them. The hosting keeps the same request logs every web host keeps. The host sets how long it keeps them, not us.

What you send us is used to do the job you asked for. We also keep a record of what wins. Every page we build adds one line to it, and that is how the next brand gets a better page.

The line is the market, how we put the page together and whether the page won. Your name, your words, your figures and your customers are never in it. Your words and your figures never go on anybody else’s page.

We do not use your page as a public example without asking you first in writing. We only ask after a win. The services we work through are bound by their own terms not to train anything of theirs on your content.

Security

We keep this small on purpose. The safest information is the information nobody collected. We do not hold your card number. We do not hold your website login or your domain login, and we hold nothing about your customers. We hold nothing at all about your ad account, because we never ask for a way into it. What we do hold sits in accounts with two factor authentication on them.

This is one person, so we are not going to claim a security programme we do not run. There is no security team here, no certification, no monitoring desk and no 24 hour incident line. If something goes wrong with information you gave us, we tell you by email as soon as we know.

Children

This is a service sold to businesses. It is not for anyone under 18, and we do not knowingly collect anything about children.

If any of this changes

The page changes with it, and the date at the top moves. If a change matters to you, we email you about it rather than expecting you to check a page.

Who to write to

Rijksen Assets
bas@preselly.com

Preselly is a brand of Rijksen Assets.