Privacy

In short

• We keep what it takes to run your menus: your email address and password, your restaurant’s menus, details and logo, and the state of your subscription. Your card is held by Stripe, never by us.
• A menu is public once you publish it. Drafts, past versions and the people on your restaurant are not.
• Menus you import are read by Anthropic’s AI, and the files are deleted once they have been read. Dishes you ask KØRT to spot possible allergens in are read by it too.
• If your restaurant records allergens, we keep a permanent record of every change and confirmation, with who made it and when.
• We keep nothing about the people who read your menus. Menu pages set no cookies, run no analytics and load nothing from any other company. The allergens a guest chooses to avoid stay in their own browser.
• KØRT’s own site and app count their visits with Umami, which sets no cookies and is never sent your name, your email address or anything you type. No advertising, and we don’t sell data.

Who we are

Render In Progress Ltd, trading as KØRT (“we”, “us”) runs kortmenu.com and is responsible for the personal data described here: its controller, under UK data protection law (the UK GDPR and the Data Protection Act 2018). Registered in England and Wales, company number 17496266, registered office 71–75 Shelton Street, Covent Garden, London WC2H 9JQ. Questions and requests about your data go to hello@kortmenu.com, or by post to 71–75 Shelton Street, Covent Garden, London WC2H 9JQ.

What we keep, and why

Your account. Your email address and a password. The password is stored by our sign-in provider only as a one-way hash, so nobody can read it back, us included. Alongside them: when the account was created and last signed in, the sessions that keep you signed in, and the IP address and browser each sign-in came from, which our sign-in provider records to keep accounts secure. When a password, a sign-in code or an emailed link is wrong, we count it against the email address, the IP address it came from, and the two together, each kept only as a one-way code made with a key only KØRT holds, so that anyone guessing can be stopped; each count is deleted within a day. We use these to let you in, and to email you a link to confirm your address, a link to reset your password, a code to sign in with, and a note when your password changes. Those are the only emails KØRT sends automatically; emails about payments come from Stripe (see “Who else handles it”).

Your subscription. Whether the account has one and where it stands (active, ending, a payment overdue), monthly or yearly, how many restaurants it pays for and when the current period ends, with the references to your customer and subscription records at Stripe. Also which account pays for each restaurant, any restaurants we have added to an account free, and any note we add to it. We never see or keep your card.

Your restaurant. Its name and web address; the details you choose to add (address, phone, email, website, Instagram); its logo and its colour; and everything in its menus: sections, items, descriptions, prices, marks, item types, views, what is off the web menu and since when, the template, the paper size and print settings, with your printer’s email address if you add one (it only fills in an email your own mail app sends; we send nothing to it). Each time you publish, we keep a copy of the menu as published, and which account published it, so you can reprint it or go back to it.

The people on it. Who is on each restaurant, and whether they are an owner or an editor. Owners invite people by email address, and someone joins only by accepting when they sign in with that address. For a restaurant on a paid plan we email the invited address once, with the restaurant’s name and the inviting owner’s email address, so they know to accept. We keep an invited address until the invitation is accepted, declined or cancelled; only the restaurant’s owners and the account with that address see it. Everyone on a restaurant can see the email addresses of the others on its settings page.

When KØRT helps. KØRT’s own account (studio@kortmenu.com) sees a restaurant’s menus and settings only when it is on that restaurant’s team: because the restaurant invited it (“Let KØRT help”), or because KØRT set the restaurant up and the restaurant has not yet removed it. You see it on your settings page and can remove it at any time. Beyond that, our staff look at a restaurant’s data only where it is needed to keep the service running, to fix a fault, or where the law requires it.

Menus you import. The files and text you bring to import a menu, while they are read. The files are deleted from our database as soon as the reading ends, whether or not it worked. We keep what was read, any text you pasted and which account asked, with your restaurant, and count each restaurant’s readings to apply the daily limit.

Allergens. If your restaurant records allergens, each dish’s allergens as your team has flagged them, the set last confirmed, and when, by whom and of which wording of the dish it was confirmed; the line your menus print about allergens and your kitchen statement; and a log of every change and confirmation, with the account that made it and the time, as your restaurant’s record of what it declared. Each time someone asks KØRT to spot possible allergens, we keep what was sent, the AI model and the answer, and which account asked.

What you send us. If you email us, we keep the conversation so we can deal with it. If you send us your menu to set up (Send us your menu), or ask about Studio, we keep what you send: the files, your restaurant’s name and where it is, your email, and any link or note, so we can set it up and reply. We also keep a one-way code made from your IP address, so one visitor cannot send too many.

Why we may. Most of this is needed to provide the service you signed up for (in UK GDPR terms, to perform our contract with you). Keeping KØRT secure and working, counting visits to KØRT’s own pages, keeping out automated sign-ups, keeping a reliable record of the allergen information each restaurant confirmed (in its interest and ours) and answering your emails are our legitimate interests. Where the law requires us to keep something, such as records of payments for tax, we keep it for that reason. Nothing here depends on your consent, and we make no automated decisions about you.

What is public

A menu is meant to be read, so a published menu is public: its page at kortmenu.com/your-restaurant/your-menu, its PDF, its QR code, any copy embedded in your own website, and your restaurant’s page at kortmenu.com/your-restaurant, which lists its published menus. Anyone with the address can open it, and search engines may list it. Those pages show your restaurant’s name, the details you have added, and your logo if the menu carries it. Where your restaurant has a logo, it is also the icon those pages show in a browser tab and the picture on a link to them shared elsewhere, whether or not the menu carries it.

Everything else stays private to the people on your restaurant: drafts, past versions, the people on it and their email addresses, and the pages where you manage it all. The database itself keeps each restaurant’s data apart from every other’s, not only the pages in front of it.

People reading your menus

When someone reads your menu, on kortmenu.com, from its QR code or embedded in your own site, the page sets no cookies, runs no analytics (not even the counting KØRT’s own pages do) and loads nothing from any other company: even its typefaces come from KØRT itself. As with any website, the request reaches our host, Netlify, with the reader’s IP address and browser details, which it needs to deliver the page, and like any host it keeps technical logs for a short time to run and secure its service. We keep no record of who read what.

On a menu’s allergen page, the allergens a guest chooses under “I’m avoiding…” are kept in their own browser, so the page remembers them. They are never sent to KØRT, to the restaurant or to any analytics.

Visitors to this site

KØRT’s own pages (this one, the home and pricing pages, sign-in, and the pages where you manage your menus) are set in Gotham, from Adobe Fonts. Your browser fetches the fonts from Adobe, which receives your IP address in order to deliver them (Adobe says it does not store it), sets no cookies, and records which fonts it served to which site, to run the service and pay the foundries that make them. Menu pages, and menus embedded in a restaurant’s own site, never load Adobe Fonts.

Counting visits. KØRT’s own pages (the same ones: the site, the doors into it and the pages where you manage your menus) are counted with Umami, an analytics service built to work without cookies. For each page you open, your browser sends Umami the page’s address, its title, the address of the page you came from, your screen size and your browser’s language. From those and the request itself, Umami works out your browser, operating system and kind of device, and an approximate location (country, region and city) from your IP address. We also count a few things done in KØRT, such as creating a restaurant or publishing a menu, with small details like which template or paper size was chosen.

What Umami is never sent: your name, your email address, anything you type, or which restaurant or menu you are working on. In the pages where you manage your menus, the restaurant’s and the menu’s names are taken out of the address and the title before anything leaves your browser, and no page’s address is sent with anything after a “?” or a “#”, which is where an emailed link carries its code. Umami sets no cookies and we store nothing for it in your browser: it tells one visitor from another with a code worked out from details such as your browser’s, mixed with a value that changes at the start of every month. If your browser has Do Not Track switched on, nothing is sent to Umami at all. Menu pages, and menus embedded in a restaurant’s own site, never load it, and a menu opened from this site is never counted.

Keeping out automated sign-ups. The sign-in, sign-up and password reset pages use Cloudflare Turnstile to tell people from programs that make accounts or try passwords in bulk. On those pages your browser loads a script from Cloudflare, which checks it, usually without asking you anything, from details such as your IP address, your browser and the connection it makes, and hands the page a one-time pass that our sign-in provider confirms with Cloudflare. It is not used to identify you or for advertising. Menu pages, menus embedded in a restaurant’s own site and the rest of KØRT never load it.

The try-it on the home page is not saved. What you type is set in your browser (or, without JavaScript, sent in the page’s address to set the preview) and we store none of it.

Cookies and browser storage

Cookies, for signing in only. When you sign in we set a cookie that keeps you signed in, and signing out removes it. Signing up, or asking for a password reset or a sign-in code, can set one more, which our sign-in provider adds; the emailed link or code works in any browser without it. Opening an emailed link sets one for a quarter of an hour, so that a password refused on that page can be tried again without the link, which is used up by then; it holds your account’s number, signed so it cannot be made up, and setting the password or signing out removes it. Scripts on the page cannot read these.

One that says you are signed in. Signing in also sets a small cookie that holds only the fact that this browser is signed in, so KØRT’s own pages can offer “Your menus” in place of “Sign in”. It holds nothing that identifies you or your account, and it is read only by KØRT’s own pages, in your browser. It never lets anyone in: that is the sign-in cookie’s job alone. Signing out removes it, and so does KØRT finding that you are no longer signed in.

A few remembered choices. Your browser’s storage remembers whether you chose the light or the dark appearance, the last template you looked at on the home page (so the sign-in pages can show it), and which columns you chose to show in your restaurant’s catalogue. In the design view it holds which item you were editing, for a moment, while the page reloads. All of it stays in your browser, and none of it is sent to us.

There are no analytics, advertising or tracking cookies, which is why there is no cookie banner: the counting on KØRT’s own pages (see “Visitors to this site”) sets none. People reading menus get no cookies at all.

Who else handles it

These companies run parts of KØRT for us. Each handles data only to provide its part, under its data processing terms with us.

• Supabase: our database, file storage and sign-in. It holds everything under “What we keep”, in Ireland.
• Netlify: runs the website, including the reading of imports, and emails us what is sent through Send us your menu and the Studio page, with links to its files (it keeps a copy, which we delete within 30 days). KØRT’s code runs in Ireland; pages are delivered through Netlify’s network from wherever is nearest the reader.
• Google Cloud: makes PDFs, and the icon and shared-link picture made from your logo, in Belgium, and keeps none of them.
• Stripe: takes payment for subscriptions, and emails receipts and word of a failed payment or an expiring card. We give Stripe your email address and a reference to your account; your card and billing details are collected and held by Stripe, never by KØRT, and we receive back only what is under “Your subscription”. Stripe also uses payment details to prevent fraud, for which it answers itself.
• Resend: sends the emails that confirm a new account’s address, reset passwords, carry sign-in codes and say a password has changed, and the invitation to join a restaurant’s team. It handles your email address and the message.
• Adobe: Adobe Fonts, on KØRT’s own pages only (see “Visitors to this site”).
• Umami: counts visits to KØRT’s own pages, never menu pages (see “Visitors to this site”). Umami is Umami Software, Inc., a US company. Its data processing agreement is part of its terms and applies to KØRT’s account without a separately signed copy; it was last updated on 2 August 2026. Umami and some of the companies it uses are in the United States (its list, at umami.is/subprocessors, names companies in the US and the EU). Where data about you leaves the UK for them, it is covered by the EU Standard Contractual Clauses as modified by the UK Addendum, which that agreement includes.
• Cloudflare: Turnstile, on the sign-in, sign-up and password reset pages only (see “Visitors to this site”). Cloudflare, Inc. is a US company. It also uses what its check sees to get better at spotting automated traffic, for which it answers itself.
• Anthropic: reads the menus you import, and the dishes you ask it to spot possible allergens in, below. Anthropic, PBC is a US company.

Reading imported menus. To read a menu you import, KØRT sends what you bring to Anthropic’s API: the PDF or photo itself, the words of a Word, Excel, PowerPoint or OpenDocument file with its file name, or the text you paste. With it go the names of your restaurant’s item types and their fields, and what comes back is the menu, sorted into sections, items and prices. Nothing about you or your account goes with it, and Anthropic’s commercial terms do not allow it to train models on what we send. If the AI cannot read pasted text, KØRT may read it without AI. Either way nothing is added to your menus until you have checked what was read.

Spotting possible allergens. When someone on your restaurant asks KØRT to spot possible allergens, KØRT sends Anthropic’s API each dish’s name, size or variant, description, item type and details (such as producer or region), and nothing else: nothing about you, your account or your guests. What comes back are suggestions, which reach no guest unless someone on your restaurant accepts them and confirms the dish.

Where it goes. Our database and servers are in Ireland and Belgium, which UK law recognises as protecting personal data adequately. Some of these companies are based in the United States and data may be handled there; where it leaves the UK and the EEA, it is covered by the safeguards UK law requires, set out in each company’s data processing terms.

We don’t sell personal data, and we don’t share it with anyone else unless the law requires us to.

How long we keep it

• Your account, until you ask us to close it. Closing it deletes it, and any restaurant only you own with everything in it; you leave the restaurants you share with other owners.
• Your restaurant and its menus, until they are deleted. Anyone on a restaurant can delete a menu, which deletes its published versions and history with it, and any item no other menu uses. Closing a restaurant deletes all its menus, details, logo and people, and its public pages and QR codes stop working.
• Imported files, only until they have been read. What was read is kept with the restaurant.
• The allergen record, for as long as the restaurant has an account with us: nobody can edit or delete it, so it stays a true record. When your account is closed, the record stops naming you; when the restaurant is closed, it is deleted with it.
• Sign-in sessions, until you sign out or they expire.
• Counts of wrong sign-in tries, a day at most.
• Emails you send us, for as long as we need them to deal with what you asked.
• Menus sent to us to set up, and Studio enquiries, with everything sent with them, 30 days. What we set up from them is kept with the restaurant.
• Records of payments, held by Stripe, for as long as UK tax law requires, even after an account is closed.

Closing an account or a restaurant is not in the app yet: email hello@kortmenu.com from the account’s address and we will do it. Deleted data leaves our database straight away, and any backup copy as that copy expires.

Your rights

Under UK data protection law you can ask us to give you a copy of the personal data we hold about you, to correct it, to delete it, to restrict or stop using it, or to give it to you in a form you can take elsewhere. You can also object to anything we do on the basis of our legitimate interests: to stop your visits being counted, switch on Do Not Track in your browser, and nothing is sent to Umami.

You can correct most of it, and delete menus, your logo and your details, yourself in KØRT. For anything else, email hello@kortmenu.com, from your account’s address if you have one. It is free, and we will reply within one month. We may ask you to confirm who you are first.

If you are unhappy with how we have handled your data, please tell us first. You can also complain to the Information Commissioner’s Office, the UK’s data protection regulator, at ico.org.uk.

Children

KØRT is a tool for restaurants and other food businesses, and is not meant for children. Menu pages collect nothing about anyone who reads them, whatever their age.

Keeping it safe

Everything travels over encrypted connections. Passwords are stored only as hashes, the sign-in cookie cannot be read by scripts on the page, and each restaurant’s data is kept apart from every other’s by the database itself. If you think someone else has used your account, reset your password and tell us at hello@kortmenu.com.

Changes to this notice

When this page changes, the date at the top changes with it. If a change affects how we use data you have already given us, we will email account holders before it takes effect.

Contact

Render In Progress Ltd, trading as KØRT, 71–75 Shelton Street, Covent Garden, London WC2H 9JQ. Email hello@kortmenu.com. The terms KØRT is offered under are at Terms of service.