Privacy notice

What personal data we collect through jvham.com and our work, why we use it, who receives it, how long we keep it and how to exercise your rights.

Who is responsible

J. van Huuksloot Asset Management B.V. (“JvHAM”, “we”), registered in the Netherlands with the Chamber of Commerce (KvK) under number 76675602, with its registered office at Herengracht 433, 1017 BR Amsterdam, is the controller of personal data processed through jvham.com. Contact: inquiries@jvham.com.

What we collect: enquiries

When you send us an enquiry form, we collect: the legal and registration details of the merchant company, the contact details of the person named as its representative (name, role, email, phone), details of the regulated provider (the counterparty), details of the merchant services agreement, an estimate of the amount in dispute, the heads of claim, how complete the documents are, and anything else you write in the form.

How you reached the form. When you send an enquiry form, it also tells us how your visit began, so that we know which of our channels and referral partners bring enquiries: the campaign tags in the link you first arrived by (for example, that it came from LinkedIn), the name of the website that linked to the first page you opened (not its full address), that first page, the page with the form, and the code of a referral partner if you came through a partner’s link. Until you send the form, these details are kept only in your browser, in its session storage for the current visit; they are not a cookie, are deleted when you close the tab, and are not sent to us unless you send the form. We keep them with your enquiry, on the basis of our legitimate interest in knowing which channels bring enquiries (Art. 6(1)(f) GDPR).

Booking a call. When you book an introductory call on this website, we collect your name, your company (optional) and the email address the invitation goes to, together with the time you chose; after an enquiry form, the call uses the contact details from that form. The call is created as a Google Calendar event with a Google Meet link, with you as a guest, in the calendar of the JvHAM colleague who takes it. We use these details to hold and prepare the call, on the basis of our legitimate interest in answering your request (Art. 6(1)(f) GDPR).

Server logs (IP address, user agent, requested page) are processed by our hosting provider for security and operational purposes.

Site statistics. To understand which pages are read and how visitors find the site, our server records each page load: the page address, the country derived from your IP address, the referring website, any campaign tags in the link, and whether the device is a mobile, tablet or desktop. Your IP address and browser details are not stored. They are combined with a random value that is replaced every day into a one-way code, which lets us count unique visitors per day; the random value is deleted once the day has passed, so the code cannot be linked to you or to your visits on other days. Nothing is stored on or read from your device for this purpose, and it does not depend on your cookie choices. Legal basis: legitimate interest in running and improving the website (Art. 6(1)(f) GDPR). The records are kept in our database at Cloudflare (D1) for 13 months.

Why we use it: enquiries

  • To assess whether we can help with the file you describe: our legitimate interest (Art. 6(1)(f) GDPR) and, where you have given us the data, steps you ask us to take before a contract (Art. 6(1)(b) GDPR).
  • To reply to you about your enquiry: the same bases.
  • To block spam with Cloudflare Turnstile: our legitimate interest in protecting the service.
  • To meet legal obligations, where they apply.

Our own prospect research

We also look for merchants ourselves. From public information, we identify merchants who appear to have claims against a regulated payment provider, and we write to their directors or senior officers, in their public business role, to say that we may be able to assess a recovery.

What we process. Company information (legal name, registered office, public register references, regulator filings), which is not personal data under the GDPR. Where we identify named directors or senior officers in their public role, we record their name, public role, the public web address where we found it and the date. We do not process special category data. We do not collect personal data from social platforms automatically; director records are entered by hand from legitimate sources.

Legal basis. Legitimate interest (Art. 6(1)(f) GDPR). Our interest is in identifying and approaching merchants about regulated activity in which both the merchant and the provider deal with the public. We write to people in their public business role, not in their private capacity. We keep a written legitimate interest assessment, which we make available to data subjects on written request.

Germany, Austria and Italy. In Germany, our research and approaches follow the stricter rules of §7 of the Act against Unfair Competition (UWG): we write only to people in publicly disclosed business roles, the opt-out appears in the first paragraph of every message, and we never write again after an opt-out. We apply the same narrower approach in Austria. In Italy, we write only to people who have agreed in advance to hear from us (opt-in), in line with the stricter Italian approach to business email.

Opting out and erasure. Every message we send has a one-click opt-out link. You can also opt out on the unsubscribe page, which offers three choices: stop the specific approach, stop all approaches from us, or have your data erased under Article 17 GDPR. We act on opt-outs straight away and keep a record of them indefinitely, separately from any other prospect data, to show that we respect them. Erasure requests sent through the data subject requests page follow the procedure on that page.

How long we keep prospect records. Where our research does not lead to a file, we keep the prospect record and related material for up to 24 months after the record is closed, and then delete it. Opt-out records are kept indefinitely as evidence that the opt-out is respected.

Referral partners, the partner portal and the PSP Health Check

Partners. JvHAM works with referral partners, typically payment consultancies, that introduce merchants to us. For each partner we process the company details needed for the referral and cooperation agreement (legal name, registration number, registered office, the signatory and a notice address) and the names and email addresses of the people who use the partner portal. When the agreement is signed in the portal, we also record, for each signer, the name and title entered, the email address the signing link was sent to, the time of signing, the IP address and a fingerprint of the signed document, as evidence of the signature; these records are kept with the agreement. The legal basis is the performance of the agreement with the partner and our legitimate interest in administering it (Art. 6(1)(b) and (f) GDPR).

Partner applications. A firm that applies on our website to become a referral partner gives us a contact name, a work email address, the company name, optionally a phone number and a few answers about its business, which we use only to assess the partnership and to reply, on the basis of our legitimate interest and of steps the firm asks us to take before an agreement (Art. 6(1)(f) and (b) GDPR), and delete 24 months after the application.

The partner portal at jvham.com/partner is used by partners to see their referral links and how they perform. Partners log in with a one-time link sent to their email address; there are no passwords. The portal shows each referral by reference number, date and a general stage only. It never shows a merchant’s name, contact details, answers or provider; that information is shared with JvHAM, not with the partner. We tell the partner the outcome of a recovery only with the merchant’s written consent. A partner may receive a referral fee from us; we tell the merchant before they sign.

The PSP Health Check. Merchants who reach us through a partner, or directly on jvham.com/check, may answer four questions about a previous payment provider on a page hosted by JvHAM. Nothing is sent to us until the merchant ticks the consent box and submits; before that, on a partner’s page, only an anonymous count that the page was shown (the partner’s code and nothing else) is recorded. A submission on jvham.com/check also records the campaign parameters of the link the merchant arrived by (for example, that it came from LinkedIn), so we know which of our channels it came through. Submitted answers, and an email address if the merchant books a call, are used to assess whether we can help, on the basis of the merchant’s consent and, once a call is booked, steps the merchant asks us to take before a contract (Art. 6(1)(a) and (b) GDPR). Consent can be withdrawn at any time by writing to us.

Introductions. A partner may also introduce a merchant who has asked to be put in touch with us, through a form in the partner portal: the company, a contact name, an email address and optionally a phone number and a short description. We use these details only to contact the merchant at their request and to assess whether we can help (Art. 6(1)(b) and (f) GDPR), and tell the merchant how we obtained them when we first write. The partner confirms that the merchant asked to be contacted.

Which partner introduced a merchant is recorded from the link the merchant arrived through; no cookie or other identifier is stored on the merchant’s device for this purpose. JvHAM and each partner act as independent controllers of the data each holds.

Who receives your data

Processors. These service providers process personal data on our behalf and on our instructions:

  • Cloudflare, Inc.: hosting, content delivery, spam protection (Turnstile), email routing and our database (D1). Data may be processed in the EU and other regions where Cloudflare operates.
  • Resend, Inc.: delivery of transactional email.
  • Google: Google Workspace, which we use for email, calendars, Google Meet for booked calls, and documents such as partner agreements.
  • Anthropic Ireland, Limited: its AI models, used through Anthropic’s API, help us draft documents that a member of our team then reviews, edits and approves before anything is used: first messages in our own prospect research, preliminary assessments of a merchant’s position, and internal summaries of public register events. For a draft, we send company information, the person’s business role and our own notes on the matter. Before notes or a call record are sent, we replace the names, email addresses and phone numbers of people that our records contain with placeholders, and we do not send the recipient’s name or email address. No decision about you is made by the model. Anthropic acts as our processor under its data processing addendum, may not use this data to train its models, and keeps it for no more than 30 days, unless its safety systems flag it, in which case it may be kept for up to two years, or the law requires longer. Anthropic processes this data in the United States and other countries where it operates; see “Transfers outside the EEA”.
  • Functional Software, Inc. (Sentry): error monitoring for our website and database. When something fails on our server, or a page fails to run in your browser, a technical error report is sent through our own server: the page or function concerned (without any search or query part of the address), the time, the error message and, for browser errors, the type of browser. Email addresses are removed from the report before it is sent; your IP address and anything you typed into a form are not included. Error reports are stored in the EU (Frankfurt) and deleted after 30 days; Sentry keeps account and project settings in the United States. Sentry acts as our processor under its data processing addendum.
  • Crisp IM SAS (France): live chat on this website. Chat transcripts and the contact details you choose to give in a conversation are processed on Crisp’s EU infrastructure.

A specialist recovery fund the firm cooperates with. The fund is not our processor. In selected cases, where our analysis indicates that a file may qualify for a purchase offer, we share the file data the fund needs to assess the claim and, if an offer is made and accepted, to complete the purchase. The fund receives that data as a separate recipient and uses it as its own controller, under its own privacy notice.

We may also disclose data to external lawyers, authorities, courts and tribunals, to the extent strictly necessary to conduct a recovery file, once a separate agreement (the Claim Assignment and Recovery Agreement or, in selected cases, a claim purchase agreement) has been signed.

Transfers outside the EEA

Where personal data is transferred outside the EEA, the transfer is protected by appropriate safeguards under Chapter V GDPR, such as Standard Contractual Clauses.

Drafting with Anthropic (see “Who receives your data”) involves a transfer to the United States under Standard Contractual Clauses in Anthropic’s data processing addendum. Sentry’s account and project settings are held in the United States; Sentry is certified under the EU-US Data Privacy Framework and its addendum also includes Standard Contractual Clauses. Microsoft, for Clarity (see “Cookies and tracking”), relies on the EU-US Data Privacy Framework and on Standard Contractual Clauses.

How long we keep it

Enquiries that do not lead to a file are kept for up to 24 months from receipt, so that we can follow up and keep an audit trail. Enquiries that lead to a signed engagement are kept for the duration of the engagement and for seven years after it ends, in line with professional record-keeping obligations.

When an enquiry is deleted, the documents uploaded with it and our notes on it are deleted with it.

Site statistics records (see “What we collect: enquiries”) are deleted 13 months after the page load.

When we send you an email (for example the confirmation of an enquiry or a booking), we keep a record that it was sent and whether it was delivered, bounced or marked as spam, linked to your enquiry. The record holds a one-way code derived from your email address, not the address itself, and not the content of the email. It is kept for 13 months.

If you download our checklist, your email address and, where relevant, the partner that referred you are deleted 24 months after the download.

Introductions made by a partner through the partner portal: the contact name, email address, phone number and description are deleted 24 months after the introduction. The company name, the partner, the date and the stage of the introduction are kept for our records with the partner. Where an introduction has led to an enquiry or a file, the periods above for enquiries and files apply to that data.

Prospect records from our own research (see “Our own prospect research”) that have had no activity for 12 months are closed automatically; the 24 months after closing then apply. Opt-out records keep the email address, the choice made, its date and how we received it; a name or company given with an opt-out is not kept, and any message added to it is deleted once we have acted on it.

PSP Health Check answers are anonymised 24 months after receipt unless they have led to a file: free text, email address, booking reference and page details are deleted, and only the anonymous answers are kept for our records with the partner. Name, company and email address of a call booked on this website are deleted 24 months after booking; the time of the call is kept. Partner portal logins and sessions are deleted when a partner relationship ends; partner company details and the signed agreement are kept for as long as claims under the agreement can arise.

Your rights

Under the GDPR you have the right to access, rectification, erasure, restriction, objection and data portability in respect of your personal data, subject to the exceptions that apply. You also have the right to complain to a supervisory authority; in the Netherlands, that is the Autoriteit Persoonsgegevens.

To exercise any of these rights, follow the procedure on the data subject requests page. We acknowledge requests within 72 hours and answer them in substance within 30 calendar days.

Cookies and tracking

You choose which categories of cookies and similar technology we may use. On your first visit, a banner lets you accept all categories, reject all non-essential ones, or choose category by category. Your choice is stored in your browser’s local storage, and you can change it at any time through the link in the page footer.

The categories are:

  • Strictly necessary: Cloudflare security cookies and the Turnstile anti-bot challenge. Always on; the site needs them to work. For partners only: jv_partner, the partner portal login session, set when a partner logs in and removed at logout (at most 30 days). It is not used on any other part of the site and not for tracking.
  • Analytics: Cloudflare Web Analytics, a cookie-less aggregate measurement of site traffic with no fingerprinting, no profile building and no cross-site tracking; Apollo website visitors, which identifies the organisation behind a visitor’s IP address and stores an identifier in your browser so that repeat visits by the same organisation can be recognised (it identifies organisations, not individuals); and Microsoft Clarity, which records how pages are used (clicks, scrolling, mouse movement) as session replays and heatmaps, with everything typed into forms masked before it leaves your browser, and sets first-party cookies (_clck, _clsk) to connect page views within a visit. Microsoft Ireland Operations Limited provides Clarity as a separate controller, not as our processor, and uses the data also under its own privacy statement. Microsoft may set its own cookies on Microsoft domains (MUID, SM, MR, ANONCHK) to recognise the same browser across Microsoft services. Recordings are kept for 30 days; a small sample, and heatmaps, for up to nine months. All three are off by default and load only with your consent.

The server-side site statistics described under “What we collect: enquiries” set no cookie and store nothing on your device, so they are not a cookie category and are not affected by these choices.

The enquiry forms keep the details of how your visit began, described under "What we collect: enquiries", in your browser's session storage (jvham-entry) for the length of the visit. It holds no identifier, nothing in it is sent to us unless you send a form, and it is removed when you close the tab, so it is not a cookie category and is not affected by these choices.

We do not use marketing or advertising cookies. Sentry, our error monitoring (see “Who receives your data”), runs on our server, sets no cookie and stores nothing on your device, so it is not a cookie category. It is used on the basis of our legitimate interest in keeping the website and database working (Art. 6(1)(f) GDPR).

Live chat. The chat widget (Crisp) loads no code and sets no cookie until you open it. Opening the chat is a request for the service; Crisp then sets a session cookie strictly necessary to keep your conversation connected across pages. If you never open the chat, nothing is loaded from Crisp.

Changes

We may update this notice from time to time. Material changes are flagged on this page.