numen

Privacy

What this site collects, who processes it, what happens when we call you, and what you can ask me to do about it. Last updated 1 October 2026.

Who is responsible

Numen is the data controller for this website. Numen is run by Raj Dhillon and operates in the United Kingdom. For anything on this page, including any request set out below, the contact is raj@numenai.co.uk.

What this site collects

Two things collect data on this site, and nothing else does. There is no contact form, no newsletter sign-up, no chat widget and no advertising network on any page.

1. Analytics, on every page

This site can use Google Analytics 4 (property G-ZL8F4WYKY4) to count visits and see which pages get read. It runs only if you accept it in the banner shown on your first visit. Until you accept, the Google Analytics tag is not loaded at all: no request is made to Google and no cookie is set. If you accept, Google sets cookies in your browser and receives your IP address, the pages you view, the approximate location those suggest, and basic device and browser information. Google Analytics is configured to record this on https://numenai.co.uk only.

Google Ireland Limited and Google LLC act as processors for this, and the data may be transferred outside the UK under the UK extension to the EU-US Data Privacy Framework. Google's own notice is at policies.google.com/privacy.

2. The booking calendar, on the sourcing review page

The sourcing review page embeds a booking calendar provided by Cal.com, served from its European instance at cal.eu. It loads only on that page. If you book, you give Cal.com your name, your email address, the time you picked and anything you type into the booking form, and a video meeting link is created for the call. Cal.com acts as a processor for that booking.

A record of the booking is also kept in Numen's own customer records, so that the call can be prepared for and followed up.

Email you send me, and how it is sorted

Since 1 October 2026, email arriving at Numen's inbox is sorted automatically, so that receipts, enquiries, newsletters and the rest end up in the right place. Only two things about your message are sent out for that: the domain your email came from, and the subject line. Your name, your full email address and the body of your message are not sent.

Those two details go to OpenRouter, which routes the request to TypeSafe AI's Jev model. Both act as processors. TypeSafe hosts the model in the United States (West Coast), and that transfer runs under the UK International Data Transfer Addendum over the EU standard contractual clauses, at clause 6.3 of TypeSafe's data processing agreement.

Neither keeps it. Zero data retention is switched on account-wide at OpenRouter and sent again with every single request, and training and prompt publishing are switched off. TypeSafe states that Jev is not trained on customer requests. Nothing else is sent to it.

If we called you

Why we called you. We called you because you are named publicly as the owner or a director of a UK specialist car dealership, and we sell a business service to dealerships of exactly that kind: a system that brings the right stock in, so the owner is not the only person who can find cars. Your name and business number came from public sources — your own dealership website, and public vehicle listings.

We do not withhold our number. If you ask who is calling and how to reach us, we tell you.

The call is recorded and transcribed. We say so at the start of every call, before anything else is discussed. If you would rather not be recorded, say so and we stop the recording or end the call — whichever you prefer — and it makes no difference to anything else.

What we record:

  • The audio of the call, both sides.
  • A written transcript, produced automatically, with each line labelled as either us or you.
  • The call details — the number called, the date and time, how long it lasted, whether it was answered, and which contact record it belongs to.
  • Whatever you say on the call. That part is yours to control, so please do not tell us anything you would not want written down.

Why we record it. Three reasons, and no others. To have an accurate record of what was said — what your dealership needs, what was promised, what was agreed. To review our own side of the call so the next one is better and shorter. And to work out automatically what happened on the call: whether we reached the right person, whether an appointment was offered and booked, and what objection came up. That last one is how our own sales figures get counted without anyone typing them in.

A machine reads the transcript. We would rather say this plainly than bury it. An automated system reads the transcript of your call and scores it against a fixed list of sales measures — the ones listed above. A person can read it too; in practice that person is Raj. It does not build a profile of you, and it does not decide anything about you. We do not sell recordings or transcripts, and we do not share them for anyone's marketing.

Our lawful basis for calling you, and for recording and transcribing the call, is our legitimate interests (UK GDPR Article 6(1)(f)): finding and serving dealerships that need what we sell, and keeping an accurate record of what was said. We have carried out and documented an assessment weighing that against your interests, and we keep it on file. Using this basis puts the obligation on us, not on you.

Who handles the call. Three processors are involved in a recorded call, and no others:

  • CloudTalk — our phone system: it places the call, records it and produces the transcript. EU (Germany).
  • Google — reads the transcript to work out what happened on the call, and nothing else. It is not allowed to train on it. Processing may take place outside the UK, under the standard legal safeguards for that.
  • OpenRouter, and through it TypeSafe AI — an alternative to Google for the same job: reading the transcript to work out what happened on the call. Neither is allowed to train on it, and neither keeps a copy once the answer comes back. Processing takes place in the United States, under the standard legal safeguards for that.

How long we keep it. Recordings, transcripts and call logs are kept for 24 months, then deleted. If we end up doing business together, the record is kept for the life of the engagement and six years afterwards, because HMRC requires business records to be kept that long. If you ask us not to call you again, we keep the minimum needed to honour that — normally your name and number — indefinitely, because the only way to reliably not call you is to remember not to.

Telling us to stop is absolute. You can tell us to stop calling you and we cannot argue with it. Say it on the call, or email raj@numenai.co.uk. You go on our do-not-call list and that is the end of it. You can also ask for a copy of your recording and transcript, ask us to delete them, or ask us to correct anything we have recorded about you that is wrong — all free of charge, and answered within one month. Your do-not-call entry stays either way.

Why, and on what legal basis

  • Analytics — to understand how the site is used and improve it. Legal basis: consent, given in the banner and withdrawable at any time in the cookies section below.
  • Bookings — to hold the call you asked for and to contact you about it. Legal basis: taking steps at your request before entering a contract.
  • Email you send me — to reply to you, and to sort the inbox as described above. Legal basis: legitimate interests, in answering someone who has got in touch and in keeping the inbox in order.
  • Calls we make to you — to reach dealerships that need what we sell, and to keep an accurate record of what was said. Legal basis: legitimate interests, as set out above.

How long it is kept

  • Analytics data: retained by Google for 14 months, then deleted automatically.
  • Booking and enquiry records: kept for as long as we are talking, and for two years after the last contact, unless you ask for them sooner.
  • Sender domains and subject lines sent for inbox sorting: not retained by OpenRouter or TypeSafe AI.
  • Recordings, transcripts and call logs from a call we made to you: 24 months, as set out above.

Who else sees it

Google, Cal.com, CloudTalk, OpenRouter and TypeSafe AI, in the roles described above, and the hosting and email providers that run this site and my inbox. Nobody else. Your details are not sold, rented, or passed to anyone for their own marketing.

Your rights

Under UK GDPR you can ask me for a copy of the personal data I hold about you, ask me to correct it, ask me to delete it, ask me to restrict or stop using it, and object to my using it. You can also ask for it in a portable format. There is no charge, and I will reply within one month.

Ask by emailing raj@numenai.co.uk. If you are not happy with how I have handled it, you can complain to the Information Commissioner's Office at ico.org.uk.

Cookies, and how to change your mind

On your first visit this site asks whether Google Analytics may run. Nothing analytics-related happens before you answer: the Google tag is not loaded, no request goes to Google, and no cookie is set. Accepting loads the tag and lets it set its cookies. Refusing loads nothing, and if you had accepted before, refusing also deletes the analytics cookies already in your browser.

Your answer is kept in your browser's local storage under the key numen-analytics-consent, not in a cookie, so that refusing cookies does not require setting one. It stays on this device only and is never sent to me or to Google. Clearing your browser storage clears it, and you will be asked again.

Advertising is switched off permanently. Google Consent Mode is set on this site with advertising storage, advertising user data and advertising personalisation all denied, and accepting the banner raises analytics storage only.

The booking calendar on the sourcing review page sets its own cookies to work, and those are not covered by the banner. You can block or delete every cookie in your browser settings. Nothing on this site stops working if you do, apart from the booking calendar.

Changes

If what this site collects changes, this page changes with it, and the date at the top changes too.