Legal: Privacy policy
Privacy policy
Who is responsible
Motorbay is run by Lukas Ryborg Dreier and Simon Christensen as a partnership (interessentskab). We are the data controller for the personal data described here. Our address is in the footer of every page. Write to support@motorbay.app about anything in this policy.
What we collect, and why
Your account
When you sign up: your email address, a hash of your password (never the password itself), whether you are a private individual or a business, your language, and which version of these terms you accepted and when.
If you turn on two-step verification, we also store the secret for your authenticator app and hashes of your recovery codes.
Why: to give you an account and the service you signed up for (GDPR art. 6(1)(b), the contract).
Limits on free accounts
Every account gets the same Free plan, and we want one Free plan per person. So we keep a few small things, and refuse one kind of address.
A hash of your email address. With your account we keep a code worked out from your email address with a
secret key that only our server has. Before it is worked out, the address is written in lowercase and any
+tag is removed (for Gmail, the dots in the name too), so name+shop@example.com and name@example.com give
the same code. It is not the address, and it can't be turned back into the address without our key. If someone
signs up with another address for an inbox that already has an account, we create no second account, and the
owner of the first account gets an email about it.
Sign-ups per network. To stop one network opening many accounts in a day, we keep, for 7 days, a count for each network and day: a code worked out in the same way from the network part of the IP address and the date, and the number of sign-ups. We don't store the IP address itself, and the code is different every day, so it can't be used to follow you from one day to the next.
We also don't accept addresses from temporary email services, when you sign up. Nothing is stored about that.
A verified card, for the Free plan's monthly lookups. The Free plan's monthly lookups go to one account per person. Until you verify your account, it has a small number of starter lookups, once. To verify, you add a card in Stripe's checkout: Stripe checks that the card is real, and nothing is charged. Stripe tells us its fingerprint for the card, a code that is the same for the same card, and we keep a hash of the card's fingerprint worked out with our secret key, never the card number and never the fingerprint itself. The card is not saved for payments. One card verifies one account at a time, so if a card already verifies another account, we say so, without saying which. We also keep when the account verified, how many starter lookups it has used, and when it last tried a card that was already in use.
Across all Free accounts we count the lookups served each day, to keep the Free plan within what we can serve. That count has no account and no address in it.
Why: our legitimate interest in stopping the Free plan from being used over and over, so it can stay free for everyone else (art. 6(1)(f)). You can object by writing to us, and we then weigh it against that interest.
Your API keys and requests
For each API key: its name, a hash of the key (the key itself is shown to you once and never stored), when it was created and when it expires.
For each request made with a key: the time, the method and path, the query, the status, the size and duration, and the caller's IP address and user agent. We count your requests per day to bill you and to show you your usage.
Why: to run and bill the service (the contract), and to find abuse and keep the service secure (art. 6(1)(f), our legitimate interest in a secure service).
Payment
Payment happens on Stripe's checkout page. Your card details go to Stripe, never to us. We store the IDs of your Stripe customer and subscription, your plan, and the dates of your trial and subscription. If you are a private individual and asked us to start before the withdrawal period ended, we store when you asked.
Why: the contract, and our duty to keep accounting records (art. 6(1)(c), bogføringsloven).
Withdrawals
If you withdraw from your subscription, we store your name, email address, the subscription, when you withdrew, and what was refunded.
Why: our legal duties under forbrugeraftaleloven and bogføringsloven (art. 6(1)(c)).
Emails we send you
We send you emails to confirm your address, reset your password, tell you about changes to your account or its security, and send receipts. Our server logs the address and the subject of each email it sends. We don't send marketing emails.
Why: the contract, and our legitimate interest in keeping your account secure.
Support
If you email support@motorbay.app, we keep the email and our reply.
If the support desk on your account page is turned on and you ask it a question, we store the question and the answer with your account. To write the answer, the question is sent to Anthropic (Claude), and first to a system of ours that checks it for misuse. Don't put personal data in your questions.
Why: to answer you (the contract), and to review misuse (our legitimate interest).
Cookies
The console sets the cookies it needs to work: your session, and your choice of language. Our analytics sets one more, only if you say yes to it (see Analytics below). They are listed on the cookies page.
Sign-up check
The sign-up form has a check from Cloudflare Turnstile, to stop scripts from creating accounts automatically. It is loaded only on the sign-up form, not on sign-in or anywhere else. While you fill in the form, the check runs in your browser and looks at signals such as your browser and device, and how it responds to small tests. Cloudflare processes these signals, together with your IP address, to decide whether a person or a script is signing up, and sends us a single-use token with the answer. We send the token and your IP address back to Cloudflare to confirm it, and keep neither. Sometimes the widget shows a checkbox. Nothing you type in the form is sent to Cloudflare.
Cloudflare runs the check for us as our processor. Cloudflare also uses the signals to improve Turnstile's bot detection, and for that it is the controller itself, under its own Turnstile privacy addendum.
Why: our legitimate interest in stopping automated sign-ups, which would use up the free plan and cost real people their service (art. 6(1)(f)). If the check cannot run, for example because the script is blocked, you cannot create an account here; write to support@motorbay.app and we will help.
Page views
To see which pages are read, the console counts page views without cookies. For each page you open, it sends
us the page, the language, the domain of the site that linked to it (for example www.google.com, never the
full address), and we add one to that day's count. That is all we keep: a number per page, language,
referring domain and date.
We use no cookies for this and store nothing in your browser. We don't store your IP address, and nothing we keep can identify you or your device. Pages behind sign-in, and the links in our emails, are not counted.
If your browser sends Global Privacy Control or Do Not Track, nothing is sent at all.
Analytics
To see how the console is used and where it falls short, we use PostHog. It runs in PostHog's EU cloud in Frankfurt, and the browser sends to it through our own domain.
Without cookies, for every visitor. Until you answer the cookie question, and after a no, PostHog counts which public pages you open, where you came from (the linking site and any campaign tags in the link), what you click, how long you stay, how fast the page loads, and your browser, device type and country. It stores nothing in your browser. It tells visits apart for one day only, by a code its server works out from your IP address, your browser and a random value it changes and deletes every day. The IP address is not stored.
With your yes. PostHog also sets a cookie, so a later visit is recognised as yours, and makes a session recording of the public pages: what is on the screen, and how you move, scroll and click. Everything you type is hidden, and so are email addresses, API keys and anything we mark as secret. Pages behind sign-in, and the links in our emails, are never recorded, and counted only after a yes.
Before anything leaves your browser, email addresses, API keys and the tokens in our links are removed from it. If your browser sends Global Privacy Control or Do Not Track, PostHog is not loaded at all.
Your account. When you have an account, our server also tells PostHog the steps it takes, under the account's ID and nothing else that names you: that it signed up (and as a business or a private person, in which language), confirmed its email address, made an API key, made its first API request, and started, changed or ended a subscription (the plan and its status). Never your email address, your name, your IP address, your keys, what you look up, or your payment details. With your yes, the browser you use is tied to the same ID once you sign in, so the pages you saw before signing up count towards the account; without a yes it never is, and signing out ends the tie. When you delete your account, we ask PostHog to delete everything under its ID, recordings included.
Why: counting without cookies is our legitimate interest in knowing which pages are read and where the console fails (art. 6(1)(f)); the cookie and the recordings need your consent (art. 6(1)(a), and cookiebekendtgørelsen). You can withdraw it at any time under Cookie settings at the bottom of every page, as easily as you gave it. The account's steps are our legitimate interest in knowing where new customers stop on the way to using the API, which we can't learn any other way, and which tells PostHog nothing it could use to recognise you elsewhere (art. 6(1)(f)). You can object to it by writing to us: we then stop sending it for your account and delete what PostHog has.
PostHog keeps events for 1 year and recordings for 30 days.
Google Sheets add-on
The Motorbay add-on for Google Sheets lets you look up vehicles with =MOTORBAY() formulas. It runs on
Google's Apps Script, in your own Google account.
What it stores. Your Motorbay API key, which you enter yourself, saved in the add-on's settings for your own Google account and never in the spreadsheet. The answers it gets from Motorbay, cached for up to 6 hours in the spreadsheet's add-on cache so the same lookup doesn't cost you another request.
What it sends, and to whom. Only the plate, VIN or vehicle id in your formula, with your API key, to
api.motorbay.app. From there it is an API request like any other (see "Your API keys and requests" above).
The add-on reads only the cells your formula gives it. It reads nothing else in your Google account, and
sends nothing to anyone but Motorbay.
Who we share it with. We don't sell Google user data. We don't share, transfer or disclose it to anyone, except to the providers that run Motorbay for us and when the law requires it. The cells the add-on reads go only to Motorbay's API. We use them to answer your formula and, as for any API request, to bill you and to keep the service secure. Of the providers in "Who else handles your data" below, two handle them: Contabo, whose server answers the request, and Cloudflare, whose R2 storage holds our encrypted nightly backup, which Cloudflare can't read. Google runs the add-on itself (see "Google" below). We never use Google user data for advertising or to train AI models.
How it is protected. The add-on sends the lookup and your key only over HTTPS. Google keeps the key in the add-on's settings for your own account, which only you can read and only from this add-on. Not even those you share the spreadsheet with can see it. At Motorbay the request is handled like any other API request (see "Your API keys and requests" above), and protected like this:
- In transit: the add-on can call
api.motorbay.apponly over HTTPS (TLS). - Your key: we keep only a hash of it, never the key itself, and our server logs leave it out.
- On the server: the database is reachable only from Motorbay's own services on the server, not from the internet. The server takes logins only with an SSH key, never a password, and never as root.
- Backups: the nightly copy that leaves the server is encrypted before it leaves, and our storage provider can't read it.
- How long: the request log with the plate, VIN or vehicle id is deleted after 90 days, and server logs are overwritten as new lines come in, as "How long we keep it" below says.
Google. The add-on asks Google for three permissions: to work in the spreadsheet you use it in, to call
api.motorbay.app, and to show its sidebar and menu. Its use of information it receives from Google APIs
adheres to the Google API Services User Data Policy,
including the Limited Use requirements. Google processes the add-on's settings and cache on our behalf.
Remove the add-on under Extensions, Add-ons, Manage add-ons in Google Sheets. To delete the saved key first, open Extensions, Motorbay, Set API key and choose Remove key. You can also revoke the key itself in the console.
Why: to give you the lookups you ask for (the contract).
The vehicle data
The vehicle data in the API comes from Motorstyrelsen's public statistics extract. It holds no owners, keepers or insurance details. The technical details of some vehicles carry a free-text comment from Motorstyrelsen that can contain a company's CVR number, and a sole trader's CVR number can identify a person. We serve those comments as they are in the public extract.
We keep a copy of each weekly extract, as Motorstyrelsen published it, in Cloudflare R2 in the EU. We use these copies to provide vehicle history: how a vehicle's registered details have changed from week to week. We keep them with no end date, because the history goes back as far as the copies do.
If your CVR number appears in such a comment and you want it removed from our copy, email support@motorbay.app. We check that the number is yours, and then it is removed from the API and stays removed after every weekly update. It is removed from everything we serve, including vehicle history. The stored weekly copies stay as Motorstyrelsen published them, but we don't serve the number from them. Motorstyrelsen's own register is not affected.
Who else handles your data
We use these providers. Each processes data only on our behalf.
| Provider | What for | Where | Safeguard for data leaving the EU |
|---|---|---|---|
| Contabo | The server and databases that run Motorbay | Germany and France (EU) | Not needed: stays in the EU |
| Migadu | Sending and receiving email | France | Not needed: stays in the EU |
| Stripe | Payments | EU and the US | The EU-US Data Privacy Framework, and the EU's standard contractual clauses |
| Cloudflare | The domain's DNS; R2 storage for an encrypted nightly copy of the account database, which Cloudflare can't read; and R2 storage for a copy of each weekly vehicle extract from Motorstyrelsen | EU for both copies; DNS is global | The EU-US Data Privacy Framework, and the EU's standard contractual clauses |
| Anthropic | Answering support desk questions, only when the desk is turned on | US | The EU's standard contractual clauses |
| Cloudflare Turnstile | The check on the sign-up form that tells people from scripts | Cloudflare's global network; the check runs in your browser | The EU-US Data Privacy Framework, and the EU's standard contractual clauses |
| Running the Google Sheets add-on, if you use it: its settings with your API key, and its cache | Google's data centres; Google decides where | The EU-US Data Privacy Framework, and the EU's standard contractual clauses | |
| PostHog | Analytics, and session recordings after a yes | EU (Frankfurt) | Stored in the EU. PostHog Inc. is in the US and can reach the data, under the EU-US Data Privacy Framework and the EU's standard contractual clauses |
We don't sell your data, and we don't share it with anyone else unless the law requires it.
Each provider's data processing agreement covers the safeguard named above. Ask us for a copy.
How long we keep it
| Data | How long |
|---|---|
| Your account, keys and usage counts | Until you delete your account |
| Request logs with IP addresses | 90 days |
| Hash of your email address | As long as your account |
| Verified card or phone (a hash) | As long as your account |
| Signup counts per network | 7 days |
| Support desk questions and answers | 90 days, or until you delete your account |
| Server logs, including the email addresses we sent to | Until the log is rotated. Each service keeps its last 30 MB of log, so older lines are overwritten as new ones come in |
| Backups | 14 days |
| Weekly vehicle extracts from Motorstyrelsen | Kept with no end date, to provide vehicle history |
| Withdrawal records | 5 years after the end of the financial year, as bogføringsloven requires |
| Payment records at Stripe | As long as Stripe must keep them by law |
| Analytics events at PostHog | 1 year |
| Session recordings at PostHog | 30 days |
| Watched vehicles and webhook endpoints | Until you remove them or delete your account |
| Webhook delivery log, including up to 1 KB of your server's answer and our own note of any connection error | 30 days, or until you delete your account |
When you delete your account, we delete it, your keys, sessions, request logs, usage, the hash of your email address, the hash of your verified card or phone, your watched vehicles, webhook endpoints and delivery log, and support questions at once. The card can then verify a new account. Copies in backups are gone within 14 days.
Your rights
You have the right to:
- see the data we hold about you. Download data, under "Download your data" on your account page, gives you a copy at once;
- have wrong data corrected;
- have your data deleted. Delete account on your account page does this at once;
- object to what we do on the basis of our legitimate interest;
- restrict what we do with your data while a question is being settled;
- get your data in a machine-readable form. The download is JSON.
Write to support@motorbay.app for anything else. We answer within a month.
You can complain to Datatilsynet, the Danish Data Protection Agency, at datatilsynet.dk.
Changes
If we change this policy, we update this page and the date below. If a change matters for you, we tell you by email.
Last updated: 30 October 2026.
Questions about the text? Email support@motorbay.app.