Company information

Privacy policy

Last updated: 29 October 2026

Who we are

Linkpreneur is a trading name of R.B. Projecten B.V., Slenterweg 3, 6905 DM Zevenaar, The Netherlands (Chamber of Commerce 59974907, VAT NL853716833B01), which is the controller for the personal data described here. For privacy questions, write to the address published on this website or reply to any message from us.

What we collect

Account data (name, email, company), billing data (invoices, payment status through our payment providers; we never store card numbers), usage data (pages visited inside the platform, actions in the audit log and in our own usage log, see below) and the campaign data you provide (domains, keywords, guidelines).

Why we process it

To deliver the service you pay for, to invoice you, to secure the platform, and to send you service messages about your campaigns. We do not sell personal data. The only personal data used for advertising is described under "Cookies and advertising measurement" below, and it is used only to measure our own ads.

Third parties

We use data processors for hosting (EU), email delivery, payment processing, SEO data providers and cookieless website analytics and session recording (Rybbit), and Google Ads and OpenAI (for its ads in ChatGPT) to measure our own advertising. Processors only receive what they need to perform their function and are bound by data processing agreements.

Cookies and advertising measurement

We advertise on Google Ads and in ChatGPT (ads by OpenAI), and measure which ads bring people to us; with your consent Google Ads may also show our ads again to people who visited our website (see "Remarketing" below). On our public website, the sign-in pages and the first steps after signing up we load the Google tag for Google Ads. OpenAI's measurement pixel runs on the public website and the payment step, not on the sign-in, sign-up and password reset pages. Visitors in the European Economic Area, the United Kingdom and Switzerland are asked first, and visitors whose country we cannot tell are asked too. We tell the country from your IP address with a country database kept on our own server (IP Geolocation by DB-IP, db-ip.com, CC BY 4.0); your IP address is not sent anywhere for this. Until you accept, the Google tag runs in Google's consent mode with advertising and analytics storage denied, so no Google advertising cookies are set, and OpenAI's pixel is not loaded at all. Accepting and rejecting are equally easy, and you can change your answer at any time under Cookie settings at the bottom of the page (Your privacy choices outside the regions above); your answer is kept in a first-party cookie (lp_consent) for six months. If you reject, OpenAI's pixel stays off wherever you are. If your browser sends the Global Privacy Control signal, we treat that as a rejection wherever you are, until you choose otherwise under Cookie settings or Your privacy choices. OpenAI's pixel sets two first-party cookies: __oppref, holding the reference OpenAI adds to the link of its ad (30 days), and __obref, a random reference for your browser (one year), and it tells OpenAI which of our pages you view. OpenAI's automatic advanced matching is on for our pixel: on the pages where the pixel runs, it can pick up an email address or a name you type into one of our forms and send it to OpenAI hashed (SHA-256), not as plain text. When you are signed in, on the pages where the pixel runs (our public website and the payment step), the page also gives the pixel your email address and the pseudonymous code for your account, both already hashed (SHA-256) by our server, and your billing country, so OpenAI can tie your visit to the same account as the steps our server reports. Your email address itself is never in the pixel's code or in what it sends. The same rules as for the pixel itself apply: only when you accepted cookies or were not in one of the regions above, never after a rejection or with Global Privacy Control, and never for our own test accounts. When you arrive through an ad or campaign link, we keep the click identifier and campaign parameters from that link (gclid, gbraid, wbraid, msclkid, oppref and utm values), the time, the page you landed on and the website you came from in a first-party cookie (_lp_click) for 90 days. If you then create an account or send us a form, we store that click, and the __obref reference when there is one, with your account or your message. Once a day Google Ads fetches from us the click identifier together with the name and time of what followed it: a qualified signup, the first wallet top-up, the first paid membership with its amount, or a contact or site-check request. When you arrived through a Google ad, our server also tells Google Ads (through its Data Manager API) each step that followed: a question through the contact form, the free site check or a call request (the agency form or "Book a 15-minute call"), creating an account, confirming your email address, opening the card payment, the first membership payment with its amount, your first payment of any kind (a membership payment, a card charge for a link or a wallet top-up) with its amount, the first website you add, the first wallet top-up and each link you approve, with the click identifier and your email address hashed (SHA-256, so the address itself is not sent), so Google can match it to the ad click (enhanced conversions for leads); we keep a record of what we sent so we can check it arrived. OpenAI hears from our server when you send us a question through the contact form, the free site check or a call request (the agency form or "Book a 15-minute call"), when you create an account, when you open the card payment, when your first payment goes through (a membership payment, a card charge for a link or a wallet top-up) and when a later month of membership is paid by card, with the amount where there is one, your email address hashed (SHA-256, so the address itself is not sent), once you have an account a pseudonymous code for it, also hashed (never your account number), and your billing country, the two OpenAI references when we have them, and for the steps you take in your browser (a question, creating an account, opening the card payment) also your IP address and your browser's user agent, so OpenAI can match it to an ad click. We keep a record of what we sent so we can check it arrived; your IP address and user agent are removed from that record as soon as OpenAI has received the event, and at the latest eight days after the step if it never does. We only send either of them anything when you accepted cookies or were not in one of the regions above, and never for our own test accounts. When you sign up or send us one of the forms above, the Google tag can also send your email address, hashed in your browser before it leaves, so Google can match it to your ad click (enhanced conversions); in the regions above this only happens after you accepted. The Google tag also notes when you view our pricing page or one of the pages that explain the product. For our own counting of which channels bring signups and questions, we note in your session on our server the host name of the website that sent you (never the full address) and the first page you saw, and store that with your account or your message; it is not shared with anyone. Our legal basis is your consent where it is required, and our legitimate interest in measuring our own advertising elsewhere. Neither tag ever runs inside the client portal, the agency workspace or the publisher portal, and the Search Console and Analytics data you connect is never used for advertising and never shared with Google Ads or OpenAI.

Remarketing

With your consent, we let Google Ads use your visits to our website to show our ads again to people who visited it (remarketing), on Google and on websites and apps that work with Google. We use up to three groups: people who viewed one of the pages our ads lead to, people who viewed our pricing page, and people who started signing up but did not pay. Google keeps someone in such a group for at most 180 days after their last visit; we never see who is in it. This only happens on our public website, the sign-in pages and the first steps after signing up: never inside a portal, never on a portal an agency offers on its own domain, and never with your Search Console or Analytics data. In the European Economic Area, the United Kingdom and Switzerland, and when we cannot tell your country, it only happens after you accept under Cookie settings. Elsewhere it happens unless you say no: choose Reject under Your privacy choices at the bottom of any page, or use a browser that sends the Global Privacy Control signal, which we treat as a no until you choose otherwise yourself. You can also turn off personalised ads for your Google account at myadcenter.google.com.

Website and portal analytics

To see which pages help and where people get stuck, we use Rybbit, a cookieless analytics service. It runs on our public website, the sign-in and signup pages and the payment screen, and since 24 October 2026 also inside the client portal, the agency workspace and the publisher portal, including a portal an agency offers on its own domain. It never runs in our staff panels, and never on a page you reach through a personal link: a shared report, a self-billing note, your mail preferences, a password reset, an email confirmation, the return from the card payment or the connection to Google. Rybbit's script and everything it sends pass through our own domain (or the agency's), which hands them on to Rybbit with your IP address so Rybbit can tell your country and count the visit; Rybbit does not store your IP address. It records the pages you view, the website you came from, the campaign details in the link you followed (such as utm tags and the Google click ID), your country, device type and browser, how fast each page loads, technical errors on the page, and which version of our website you saw. We also send it what you do on a page: which links and buttons you click and in which part of the page, how far you scroll and how long the page is in front of you, which questions you open, which forms you start, send or leave, which field a form refused and by which rule, repeated clicks on one spot and clicks after which nothing happened. On our public pages that includes the words on the link or button you clicked; inside the portals only the name it has in our code, never text from your screen. Never sent: what you type, text you copy, and inside the portals the addresses of the websites you open from there. We may also record your session: how the page looked and how you scrolled and clicked through it, so we can see where the site gets in the way. Everything you type into a field is masked in your browser before the recording leaves it. Inside the portals every word on the page shows as asterisks, and everything built from your Search Console or Analytics data, every chart and every figure, is left out of the recording entirely, so none of your Google data reaches Rybbit. Your name, email address, company, wallet balance, domains and profile photo are masked or left out wherever they appear, and so are the amounts on the payment screen. Never recorded: what you type, your card details (you pay on Stripe's own page, where our script does not run), and the pages named above; the recording stops before such a page appears. We only record your session after you accept, wherever you are: under Cookie settings, or Your privacy choices outside the European Economic Area, the United Kingdom and Switzerland, at the bottom of the website, and under Cookie settings in the menu of every portal. Until you accept, nothing of the page is recorded, and whoever rejects is not recorded. Once you are a client of ours directly, we link your visits and the steps of your account to a pseudonymous ID: a code starting with lp_ that we derive from your account number with a secret key, never your email address or your name. On the payment screen and in your portal, your browser keeps that ID in its local storage only after you accepted, wherever you are; signing out or rejecting removes it. Agencies, their people and their clients, and publishers, are never given such an ID. From our server we report these steps of your account to Rybbit under the same ID: your first payment, with its amount; your email address confirmed; a website added; the wallet topped up (that it happened and how often, never the amount); a link approved; a link live; a monthly membership payment, with its amount; a declined card; and your membership cancelled, each with your billing country. We report the first payment when you return from the card payment, passing on your IP address and browser details only so Rybbit can count it in the same visit; the other steps go without them. We never report our own test accounts. Rybbit sets no cookies and does not build a profile of you across websites; visits without an account are counted with a daily-changing identifier. When an agency offers its portal to its own clients, we measure and record the use of that portal for the agency, as its processor, under the same rules. Our legal basis for recording your session and for keeping the ID in your browser is your consent; for the rest of this analytics it is our legitimate interest in understanding and improving our own website and service.

Our own usage log

Inside the platform our server also keeps a short log of its own, in our own database, of what only the server sees: which actions you take and whether they went through, which field of a form was refused and by which rule (never what you typed), which requests failed, steps of your account such as a payment or a website added, and whether you followed the link in a reminder about paying your membership. Each entry holds the name of the screen or action, your account number, a code for your session made from it with a secret key, your device type (phone, tablet or computer) and the time. It is never shared with anyone, never holds your Search Console or Analytics data, and every entry is deleted after 90 days. Our legal basis is our legitimate interest in keeping the service working and finding where it gets in your way.

Call requests

When you ask for a 15-minute call, we keep your name, your email address and the website you name, and the answers you choose to give: your role, your monthly link budget, how many links a month, how you get links now, your main goal, when you want to start, and up to three times that suit you, with the time zone your browser reports (you can change it). We also note the country of your IP address (from the country database on our own server; your address is not sent anywhere for this), whether your email address is at the website's own domain, and the ad or campaign link you arrived through, as described above. To prepare the call and to decide which request to answer first, we look up publicly available search figures for the website you named, such as its estimated organic traffic, its number of ranking keywords, its referring domains and an authority rank, from the same SEO data provider as our free site check; when that check already has figures for the website, we use those. We use all of this to arrange and prepare the call, never for advertising, and we do not show the figures to anyone outside our team. You receive one short email confirming your request. We keep the request with our other enquiries until you ask us to delete it; our legal basis is your request to be contacted and our legitimate interest in preparing it well.

The price index by email

If you ask for the link price index by email on our website, we keep your email address, the page you asked on, when you asked, the IP address you asked from and which wording you agreed to. We then send you one email to confirm your address, and nothing else arrives until you confirm. Once you have confirmed, we send you one email a month with the index, which we check before it goes out; it holds figures from our own records and nothing about you. We use your address for this and for nothing else: it is not used for advertising and not shared with anyone but our email delivery processor. That processor is Postmark, a company in the United States, which delivers the emails for us and tells us whether each one was delivered, bounced or marked as spam, under a data processing agreement. Every edition has a link to unsubscribe in one click, without logging in, and you can also reply to any edition and ask. Our legal basis is your consent, which you can withdraw at any time. We keep your address while you are subscribed. An address that is never confirmed is deleted 30 days after the request. When you unsubscribe, your subscription is deleted 30 days later, and we keep only a note that the address unsubscribed, so that we never email it again.

Reminders to finish your signup

If you create an account and do not finish it (pay the membership, or on pay per link save a card or top up your wallet), we send you at most two short reminders by email, about two hours and about two days after signing up, with a link to the payment screen. They stop as soon as you pay or your account is removed, and you can unsubscribe from them with the link in each message. We note whether you followed the link (see "Our own usage log"). Our legal basis is our legitimate interest in finishing a signup you started.

Retention

Account and campaign data are retained while your account is active and for up to 24 months after closure. Invoices are retained as long as tax law requires.

Google user data

If you connect your Google account, we access your Google Search Console data (search queries, impressions, clicks and positions for the website you connect; scope webmasters.readonly) and, only if you separately connect it, your Google Analytics data (aggregated traffic metrics for that website; scope analytics.readonly). We use this data solely to show you your own search and traffic performance inside your Linkpreneur portal and in the reports we generate for you, and to measure the effect of link placements on your own pages. We only read; we never modify anything in your Google account. This data is stored on our EU servers for as long as your connection is active, is never sold, never used for advertising, never used to train machine-learning models, and never shared with third parties except the processors that host our infrastructure. You can disconnect Google at any time on the Domains page of your portal or via your Google account permissions (myaccount.google.com/permissions); on disconnect we stop reading, the stored tokens are deleted, and you can request deletion of any stored aggregates, which we honour within 30 days. The protection mechanisms described under "How we protect your data" below (encryption in transit and at rest, restricted key-based access, audit logging, EU hosting, encrypted backups and breach notification) apply in full to all Google user data. Google user data never reaches our website analytics: in a session recording it is left out in your browser, before anything leaves it (see "Website and portal analytics"). Our use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

How we protect your data

All traffic to and from the platform is encrypted in transit (TLS 1.2 or higher, enforced with HSTS). Google OAuth tokens are stored encrypted at rest with per-application keys and are never written to logs; other sensitive fields are protected the same way. Production systems live on EU infrastructure, access is limited to authorised personnel using key-based authentication with no shared accounts, and administrative actions inside the platform are recorded in an audit trail. Google user data is processed server-side only, is never exposed to other customers, and is never used to train machine-learning models. Backups are encrypted and follow the same retention rules as the live data. If a breach affecting your personal data ever occurs, we will notify you and the supervisory authority without undue delay, as the GDPR requires.

Your rights

You can request access, correction, export or deletion of your personal data at any time by contacting us. You can lodge a complaint with your data protection authority.

Publisher prices at cost. A fixed fee per link. A membership only if it pays off for you.

Get started