Last updated: 9 August 2026
Privacy Policy
What we collect, why we have it, who else sees it, and how to get it back or have it deleted.
We hold your name, your email, and whatever you have chosen to connect, such as Discord or iRacing. We keep a record of what you have bought and what you have saved.
We never see your card details. Payments run through Stripe, and a card number does not reach our servers.
We do not sell your data. We do not share it with advertisers. You can ask for a copy of everything we hold, or ask us to delete it, and we will.
Daniel Newman Racing Ltd is the data controller, which means we decide what is collected and why. Registered in England and Wales, company number 16801715, at 9 Byford Court, Crockatt Road, Hadleigh, Suffolk, IP7 6RD, England.
This policy covers danielnewmanracing.com and the DNR SimHub plugin. It does not cover other sites we link to, which have their own policies.
| What | Where it comes from |
|---|---|
| Name and email | You, when you create an account. |
| Profile picture | You, or the account you signed up with. |
| Linked accounts | Discord, Google or iRacing, only if you choose to connect them. We store the identifier and username, not the password. |
| Your membership | Which tier you are on, when it renews, and whether the last payment worked. From Stripe. |
| What you have saved | Favourite products and files, email preferences, dashboard layout. |
| Support messages | Anything you send us through a ticket, the contact form or email. |
| Technical data | IP address, the country that address places you in, browser, operating system and pages visited. Collected automatically, and the analytics part only if you accept it. We work the country out on our own servers from the address your request already arrives with, and we only ever report it as a total. |
| How you found us | The campaign details on the link you followed and the name of the site that referred you, for example a video or a search. Only if you accept analytics cookies. Kept against your account so we can tell which sources bring people who stay with us. We never record the full address you came from. |
| Which locked features get shown | A running count of how often each locked feature appears in the plugin and how often the button on it is pressed. Each count carries the name of the feature, the membership it asks for, whether the person looking was signed out or on a free or lower tier, and the plugin version. It carries nothing that identifies you or your machine, it is not attached to your account, and it cannot be traced back to you afterwards. We use it to see which locked features people meet and which ones we explain badly. |
| Your DNR plugin devices | Which machines you have signed DNR in on, the name each machine reports, and a record of each sign in, renewal and failure with the IP address and country it came from. This is how we keep your membership working across your rigs and stop accounts being shared. You can see and remove your devices from your account page at any time. |
We do not collect your date of birth, and we do not hold card numbers. If you have read an older version of this page that said otherwise, it was a template we had not corrected, and we are sorry it stood for as long as it did.
UK GDPR requires a lawful basis for each use. Ours are:
| What for | Basis |
|---|---|
| Running your account and giving you what you paid for | Performance of a contract |
| Answering support, keeping the service secure, preventing abuse | Legitimate interests |
| Analytics, how you found us, and marketing emails | Consent, which you can withdraw at any time |
| Counting how DNR is used, as totals across everyone | Legitimate interests. The law treats statistics as a compatible further use of information we already hold, and these totals never single anyone out. |
| Keeping records for tax and accounting | Legal obligation |
Those last two are different things and we keep them apart. The tracking you can accept or refuse is the website analytics in your browser. Counting how many people run the plugin uses records we already keep to sign you in and keep the service secure, it produces totals only, and no report we build from it names a person or shows one person's activity.
The count of how often a locked feature is shown works the same way and is worth being plain about, because it is the one thing the plugin sends purely so we can improve it. It is a tally and nothing else. Each one says which feature came up, which membership it asks for, roughly who was looking and which version of the plugin they were running, and it reaches us with no account, no device and no address attached. We cannot tell two people apart in it, we cannot tell what any one person did, and we could not link it back to you later even if we wanted to. If we ever wanted to know which member met which lock, that would be a different thing entirely and we would ask you first.
We use a small number of companies to run the service. They only get what they need for their part of it, and none of them are allowed to use it for their own purposes.
| Who | What they do |
|---|---|
| Clerk | Accounts and sign in. |
| Stripe | Payments and subscriptions. Your card details go to them, never to us. |
| Mailgun | Sending email. |
| UploadThing | Storing files and images you upload. |
| Google Analytics | Counting visits, only once you accept analytics cookies. |
| Vercel and MongoDB Atlas | Hosting the site and the database. |
We will also hand over data if the law requires it. Beyond that, we do not sell it and we do not share it with advertisers.
Some of those companies are based outside the UK, mostly in the United States. Where data leaves the UK it is covered by the safeguards UK GDPR requires, such as the International Data Transfer Agreement or the UK addendum to the EU standard contractual clauses.
Account data lives as long as your account does. Close it and we remove or anonymise your personal data.
Two things outlast that. Invoices and payment records are kept for six years because tax law requires it. Support tickets are kept while they are useful for handling repeat issues, then removed.
Plugin records clear themselves without anyone having to remember. A device disappears about five weeks after you last run DNR on it, and the sign in history behind it after ninety days. Close your account and both go straight away rather than waiting for that.
Under UK GDPR you can ask us to:
- give you a copy of everything we hold about you
- correct anything that is wrong
- delete it
- stop or limit what we do with it
- hand it over in a portable format, or send it to someone else
- stop relying on legitimate interests, where you object to that
Email support@danielnewmanracing.com and we will respond within one month. There is no charge, and you do not need to give a reason for asking.
If you are unhappy with how we have handled it, you can complain to the Information Commissioner's Office at ico.org.uk. We would rather you came to us first, but it is your right either way.
Passwords are handled by Clerk and never stored by us. Card details are handled by Stripe and never stored by us. Everything travels over an encrypted connection, and access to the database is limited to the people who need it.
No system is perfect, and anyone claiming otherwise is selling something. If a breach ever affects your data, we will tell you and the ICO within the time the law allows.
Covered in full on the Cookie Policy page, which lists every cookie we set by name. The short version is that there are no advertising cookies.
The site is for people aged 18 and over, and we do not knowingly collect data from anyone younger. If you believe a child has given us their data, tell us and we will delete it.
We update this page when what we do changes, and the date at the top tells you when that last happened. If a change materially affects you, we will tell you rather than hope you notice.
Daniel Newman Racing Ltd, 9 Byford Court, Crockatt Road, Hadleigh, Suffolk, IP7 6RD, England.
Email support@danielnewmanracing.com or use the contact form.
See also our Terms and Conditions, Cookie Policy and EULA.