Skip to content

Privacy policy

Last updated

Contents

This policy explains, in plain language, what Hungry Vegan knows about you, why, who can see it and how to change or delete it.

Who we are

Hungry Vegan Limited, a company registered in England and Wales (company number 17473102), with its registered office at Flat 1, 28 Manor Road, Westcliff-on-Sea, SS0 7SS, United Kingdom (“Hungry Vegan”, “we”, “us”), runs hungry-vegan.com and the Hungry Vegan apps for iPhone and Android, and is responsible for the personal data described here. On the website you can find vegan and vegetarian places and read their menus; in the apps you can also request a table. Restaurants sign up on the website and manage their listing and bookings there or in the apps.

Questions about your data go to hello@hungry-vegan.com, or by post to Hungry Vegan Limited, Flat 1, 28 Manor Road, Westcliff-on-Sea, SS0 7SS, United Kingdom.

The website and the apps

  • Diners don’t sign in on the website. You can browse every restaurant and menu without an account. While you do, we keep the short-lived technical logs every website has and, unless you turn them off, anonymous statistics about how the site is used (see Website and app statistics). Diner accounts, profiles, allergies, cards and table requests live in the apps, where you sign in with Apple or Google.
  • Restaurants apply to join on the website, with an email address and password. Once we approve the application, the same account manages the listing and the bookings it receives, on the website or in the apps.

What we collect

We keep only what Hungry Vegan needs to work:

What we collect, why, and how long we keep it
Diner account (apps): the name and email address Apple or Google share with us, and an account IDWhyTo sign you in and keep your bookings with youKept forUntil you delete your account in the app
Profile (apps): name, phone number (optional)WhyTo fill in the name on your table requests, and so we can reach you about a booking if we need to. Your phone number isn’t shared with restaurantsKept forUntil you change it or delete your account
Allergies (apps, optional)WhyTo pass them on to restaurants when you request a tableKept forUntil you remove them or delete your account
Bookings: restaurant, day, time, party size, the name for the booking, notes, allergies, and who changed or cancelled itWhySo you and the restaurant can manage the tableKept forAs the restaurant’s record of the booking (see below)
Card for bookings that need one (apps): held by Stripe. We keep the card type, its last four digits and any fee chargedWhyTo hold the table and charge the restaurant’s fee for a no-show or a late cancellationKept forThe card until you remove it. Deleting your account doesn’t remove it from Stripe, so a booking it holds can still be settled; payment records as long as the law requires
Messages to us and reports: what you write, with your name and email addressWhyTo answer you and keep listings accurateKept forAs the history of the conversation, until you ask us to delete it
Your phones (apps): an installation ID for each phone you’re signed in onWhyTo send you notifications about your bookings and our repliesKept forUntil you sign out on that phone or delete your account
Crash reports (apps): crash details, app version, device model and systemWhyTo find and fix crashesKept for90 days
App statistics (apps, on unless you turn them off): screens opened and what you do in the app, such as searches, restaurants viewed and bookings requested, changed or cancelled (not what you write in them); session length, app version, device model and system, approximate location and a random ID for the appWhyTo see how the apps are used, so we can improve themKept forNo more than 14 months
Website statistics (on unless you turn them off): pages viewed, searches, links followed, the site that sent you, browser, device type, approximate location and a random ID kept in a cookieWhyTo see how the website is used, so we can improve itKept forNo more than 14 months
Restaurant application (website): the restaurant’s details, a contact person’s name, email address and phone number, dishes, a photo and a card for our feesWhyTo review the application and set up the listingKept forDrafts until you delete them; sent applications as our record of the sign-up
Restaurant account: email address and password sign-inWhyTo let the people who run a restaurant manage itKept forUntil the restaurant leaves or asks us to close it
Restaurant payouts and billing: Stripe account status and balance, subscription, and the type, last four digits and expiry of the card for our feesWhyTo pay restaurants their booking fees and charge our subscriptionKept forWhile the restaurant is listed; payment records as long as the law requires
Restaurant listings, menus and photosWhyTo show the restaurant to dinersKept forUntil the restaurant changes or removes them
App waitlist (website): your email address, when you signed up and on which page; for a few days, a scrambled form of your IP addressWhyTo email you when the apps are out, because you asked us to, and to stop abuse of the formKept forUntil you remove it with the link in our emails, or we’ve told you both apps are out, whichever comes first
Technical logs: IP address, account ID, time of each requestWhyTo keep the service running and secureKept forAbout 30 days

If you use Sign in with Apple and choose to hide your email, we only receive the relay address Apple creates for us. We don’t run advertising, we don’t sell or share your data for advertising, we don’t track you across other companies’ apps or websites, and we never collect your phone’s advertising ID.

Your allergies

Allergies are information about your health, so we treat them with extra care. They’re entirely optional, kept in your profile in the app, and used for one thing only: when you request a table, the allergies on your profile are copied into the request so the restaurant can see them. We use them only with your explicit consent, which you give by adding them and withdraw by removing them.

  • You add, change and remove them yourself in the app.
  • Restaurants only see the allergies attached to requests you send them. A request you’ve sent keeps the allergies it was sent with.
  • Menus and ingredient lists come from restaurants and can be incomplete. Always check with the restaurant before you order.

Table requests and bookings

You request tables in the app. A request contains the name for the booking, the party size, the day and time, any note you write and your allergies. It goes to the restaurant you chose, which can confirm it or decline it, sometimes with a short reason that you’ll see. You can change an upcoming booking, which sends it back to the restaurant to confirm, and you can withdraw a request or cancel a booking. We record who changed or cancelled it, so both of you see what happened, and we let the other side know with a notification.

The restaurant keeps the booking as its record of your visit, even if you later delete your account. If you’d like old bookings removed, email hello@hungry-vegan.com and we’ll arrange it with the restaurant.

Cards and payments

Some restaurants ask for a card to hold a table. Before you add one, the app shows the restaurant’s fee and terms. The fee is charged only if you don’t turn up, or if you cancel later than the restaurant allows, and the app tells you before you cancel late.

Cards are handled by Stripe, our payment provider. Your card number and security code go straight from the app to Stripe: we never see or store them, and neither do restaurants. We keep the card type and its last four digits, to show you which card holds a booking, and a record of any fee charged. The restaurant receives the fee, less our commission.

Restaurants that take card-held bookings are paid through Stripe Connect. Stripe asks them for identity and bank details directly, as the law requires, and keeps them; we only see whether the account is ready and its balance. Our subscription for restaurants is charged to a card the restaurant adds, also through Stripe.

Stripe also uses payment information to prevent fraud and meet its own legal duties, as its privacy policy explains.

Restaurant accounts and photos

Restaurants apply to join on the website. An application holds the restaurant’s details, a contact person’s name, email address and phone number, a few dishes, a photo and a card for our fees. We review every application, and an approved one becomes the listing. The person who applies creates the restaurant account with an email address and password; the password is handled by our sign-in provider, and we never see it.

The listing is public, because that’s the point of a listing: the restaurant’s name, description, address, phone number, location on the map, opening hours, menu and photos. The bookings a restaurant receives are visible only to the account that manages it, and to us.

Photos uploaded from the website or the apps are stored with our hosting provider and shown publicly on the listing. Before a photo is uploaded, it’s resized and saved as a fresh copy, which drops hidden details such as where it was taken. Please only upload photos you have the right to use, and avoid photos where guests can be recognised.

Emails we send to restaurants

To invite restaurants to list, we email restaurants about Hungry Vegan. We write only to business addresses a restaurant publishes itself, usually on its own website or in a public listing, and every email says where we found the address and how to stop our emails.

For each restaurant we email, we keep:

  • its name, the area it’s in, whether it’s vegan, vegetarian or neither, and the address we wrote to (often a general one such as info@, sometimes a person’s work address);
  • which of our emails we sent and when, and what our email provider tells us about each one: whether it was delivered, bounced or marked as spam, and whether the restaurant unsubscribed;
  • for emails that count opens, when one was opened. A tiny image in the email tells us when it’s displayed. Some email apps load it by themselves and others block it, so this is only a rough guide;
  • when someone opened our join page through the restaurant’s own link in the email. The link carries a short code for that restaurant, and we record when the visit happened, not who visited. It also names the email campaign, so our website statistics can count visits from our emails; the restaurant’s code never reaches them;
  • replies, and our notes about the conversation.

We don’t track any other link in these emails or follow anyone around the web, and we share none of this except with the providers that send and store it for us. Every email has an unsubscribe link. Using it, replying “stop” or emailing hello@hungry-vegan.com ends our emails straight away, and we keep a note of the address so it isn’t emailed again. We also stop by ourselves once a restaurant applies, replies, or has had the last email in the sequence.

Messages and reports

You can message us from Contact us in the app or the restaurant dashboard, and report a restaurant or a dish that looks wrong. We keep what you write, with your name and email address, so we can answer and follow up. We’re told about new messages by email, and our replies reach you in the app with a notification. Reports come only to us, never to the restaurant.

Notifications, location and app statistics

  • Notifications. If you allow them, the apps tell you about your bookings and our replies, and tell restaurants about new requests. We store an installation ID for each phone you’re signed in on, so notifications reach the right one, and remove it when you sign out. Notifications are delivered by Firebase Cloud Messaging and Apple’s push service.
  • Location. If you allow it, the map shows where you are, to help you find places nearby. Your position stays on your phone: it isn’t sent to us or stored. The map itself comes from Apple Maps on iPhone and from OpenFreeMap on Android, and like any map they see the area you’re looking at and your IP address. The website never asks for your location.
  • App statistics. The apps use Google Analytics for Firebase to count which screens are opened and what people do in them (see Website and app statistics). It’s on unless you turn off Share app statistics in Account → Privacy. Turning it off stops it straight away and clears the statistics ID on your phone.
  • Crash reports. When the app crashes, Firebase Crashlytics sends us a report so we can fix it.
  • Statistics and crash reports record the app version, the device model and system, an approximate location and a random ID for the app on your phone, never your name, email address, phone number, notes or allergies. We use them only to improve the apps, never for advertising.

Website and app statistics

To learn which pages, features and restaurants people find useful, the website and the apps use Google Analytics. It counts pages and screens viewed, searches, restaurants opened, links followed and, in the apps, bookings requested, changed or cancelled, together with the browser or app version, the type of device, the site that sent you, an approximate location and a random ID. It never receives your name, email address, phone number, notes, allergies or card, and on the website we strip anything personal from page addresses before they’re counted.

  • Google uses your IP address to work out an approximate location, then discards it: the statistics don’t contain it. We’ve turned off Google Signals and every advertising feature, and Google processes the statistics on our behalf, under its data processing terms, and not for its own advertising.
  • On the website, Google Analytics keeps a random ID in two cookies, _ga and _ga_…, which last up to 13 months. In the apps, the ID is stored on your phone. We never link it to your account.
  • We keep the detailed statistics for no more than 14 months. We look at them as totals (how many people opened a page, for example), not person by person, and we don’t use them to make decisions about you.
  • Statistics are on unless you turn them off. In the apps, use Share app statistics in Account → Privacy. For the website, use the switch below; it applies to this browser and removes the cookies. If your browser sends Global Privacy Control, the website treats it as turning statistics off. Google also offers a browser add-on that stops Google Analytics on every site.
Off in this browser.

Who can see your information

  • You can see your profile, allergies, bookings and the card you’ve saved in the app.
  • Restaurants see the table requests you send them: the name, party size, day and time, note and allergies, and whether a card holds the table. They don’t see your email address, phone number or card number.
  • Everyone can see restaurant listings, menus and photos.
  • We: the small Hungry Vegan team with admin access can see accounts, bookings, applications, messages, reports and the app waitlist, and uses that access only to run the service, help you or keep it safe.
  • Our providers (below) process data only to provide their service to us. We’d share data with the authorities only if the law required it.

Data protection law asks us to have a reason for each use of your data:

  • To provide what you asked for: your account, table requests, card-held bookings and their fees, and for restaurants, the listing, payouts and subscription.
  • Your consent: your allergies (your explicit consent, as health information), notifications and location, which your phone asks you about first, and the app waitlist, which you join yourself. You can withdraw consent at any time.
  • Our legitimate interests: keeping the service secure and free of abuse, fixing crashes, measuring how the website and apps are used with statistics you can turn off, answering messages and checking reports, and emailing restaurants about Hungry Vegan at the business addresses they publish. We only do this in ways you’d reasonably expect, and you can object at any time.
  • The law: keeping payment records for tax and accounting.

Services we rely on

We use a few trusted providers to run Hungry Vegan. They process data only to provide their service to us:

  • Google Firebase and Google Cloud host the website and the server, store accounts, profiles, bookings, listings, messages and photos, and provide sign-in, notifications and crash reports.
  • Google Analytics measures how the website and the apps are used (see Website and app statistics).
  • Apple and Google confirm who you are when you sign in to the apps, deliver notifications, and check that requests come from our genuine apps (Apple’s App Attest on iPhone, Google Play Integrity on Android).
  • Stripe handles cards, fees, restaurant payouts and our subscription.
  • Google reCAPTCHA Enterprise helps keep bots and abuse away from our data on the website. It runs only on the restaurant sign-up, login and dashboard, and checks that requests come from a real browser by sending information about the browser and device, and how the page is used, to Google. Google’s Privacy Policy and Terms of Service apply to reCAPTCHA. The public pages diners browse don’t load it.
  • Mailgun sends our emails, for example about an application or a payment, to say the apps are out, or to invite a restaurant to list, and tells us what happened to them: delivered, bounced, unsubscribed and, for emails that count opens, opened.
  • OpenFreeMap provides the map tiles on the website and in the Android app; your device fetches them directly, so they see your IP address.
  • Photon by Komoot turns an address into a map position when a restaurant searches for theirs, and tells us which country a restaurant’s map position is in.
  • Unsplash serves some of the stock photos on restaurant pages, so your device contacts it to load them.

Our database and photos are stored in the United States, with Google Cloud, and some providers process data in other countries. When data leaves the UK or the EU, we rely on the legal safeguards these providers offer for international transfers, such as standard contractual clauses or the Data Privacy Framework.

Storage on your device

On the website, browsing stores the two Google Analytics cookies described in Website and app statistics (unless you turn statistics off, when a small note of your choice is kept instead), and your recent searches if you use search. When a restaurant signs in, the browser also keeps the sign-in session (so they stay signed in), a short-lived App Check token, a small note that a restaurant account is signed in (so the site can link straight to the dashboard), and a backup of an unfinished application. On pages with a card form, Stripe sets its own cookies to prevent fraud. The bookings a restaurant looks at are kept in memory only while the page is open, and are gone when it’s closed or the restaurant signs out.

The apps keep your sign-in session and a few settings on your phone, such as your choice about app statistics. None of this is used for advertising or to track you across other companies’ apps or websites, and you can clear it at any time in your browser or phone settings. The website sets no advertising cookies.

How long we keep things

  • Your diner account, profile and allergies: until you delete your account, which you can do yourself in the app. That removes your profile and sign-in straight away. A saved card stays with Stripe, with your name and email address, so a booking it holds can still be settled. Remove the card first if you’d like it gone, or email hello@hungry-vegan.com and we’ll have it deleted.
  • Bookings: kept as the restaurant’s record. Ask us if you’d like old ones removed.
  • Payment records (fees charged, payouts, subscriptions): as long as tax and accounting law requires, usually six years in the UK.
  • Messages and reports: as the history of the conversation. Ask us if you’d like them deleted.
  • Website and app statistics: no more than 14 months. Crash reports: 90 days. Technical logs: about 30 days.
  • Restaurant applications: drafts until the applicant deletes them; sent ones as our record of the sign-up.
  • App waitlist: until you remove your address with the link in our emails, or we’ve told you both apps are out. We send a confirmation when you sign up and an email when each app is out, and use your address for nothing else.
  • Restaurant accounts, listings, menus and photos: until the restaurant changes or removes them, or leaves Hungry Vegan.
  • Emails to restaurants: a restaurant’s record and email history for up to two years after our last email to it, unless it joins Hungry Vegan, when its restaurant account takes over. If a restaurant opts out, we keep the address and the fact that it opted out for as long as we send these emails, so it’s never emailed again.

Your choices and rights

You’re in control of your information:

  • In the app, change your name, phone and allergies whenever you like, change or cancel your bookings, and remove your card.
  • Delete your diner account in the app. Your profile and sign-in are removed straight away.
  • Turn statistics off in the app under Account → Privacy, and on the website with the switch in Website and app statistics. Turn notifications and location on or off in your phone’s settings.
  • Restaurants can change their listing from the dashboard, reset their password from the login page, and ask us to close their account.
  • Restaurants we’ve emailed can stop our emails with the unsubscribe link in any of them, by replying “stop”, or by emailing hello@hungry-vegan.com.
  • Email hello@hungry-vegan.com to ask for a copy of your data, to correct or delete something, to limit or object to how we use it, or to take your data to another service. We’ll reply within a month.

We don’t make decisions about you by automated means alone. If you’re in the UK or the EU, you also have the right to complain to a data protection authority. In the UK that’s the Information Commissioner’s Office (ico.org.uk). We’d appreciate the chance to put things right first.

Children, changes and contact

Hungry Vegan isn’t meant for children under 13, and we don’t knowingly collect their data. If we make important changes to this policy, we’ll update the date at the top and tell you in the apps.

For anything about your privacy, email hello@hungry-vegan.com.