Privacy, in plain words.
- What we keep: your email, your restaurant's details, your menu, and what you make here.
- Who else handles it: the companies that host the app, take payments, send our emails and check pictures. They are named below, under Companies that work for us.
- What we never do: sell your data, or use your photos or posts to train anything.
- Leaving: download everything, then delete your account. Everything you made is deleted; we keep only the payment records tax law asks for.
Who we are
Restobesto is run by Vinch, Welnastraat 320, 1096 GJ Amsterdam. KvK 42011455, VAT NL003792193B77. Write to restobesto@mailbox.org.
We decide what happens with the information in this notice, so under the EU's privacy law (the GDPR) we are responsible for it. Restobesto is for businesses; the people whose details we handle are mostly restaurant owners and their staff.
What we keep, and why
- Your email address, to sign you in and to send you the emails below. If you sign in with Google, Google also tells us the name on your Google account.
- Your restaurant's details: name, kind of place, story, address, phone, booking and Google links, opening days, language, look and voice. We use them to make your posts.
- Your menu (dishes, descriptions, prices, allergen notes) and your photos (of dishes, the place, your logo, a menu you scanned).
- What you make here: posts, captions, pictures, posters and printed menus, and what you asked for when making them.
- Accounts you connect (Instagram, Google): the account's name or handle, the Google listing you chose, and the access key Instagram or Google gives us to post for you. We store the key encrypted, and only the program that sends your posts uses it. We also keep which post went where, and the link to it.
- Payments: which pack you bought, when, and for how much. The card details go to Stripe, never to us.
- Messages you send us through Help.
- How the app is used, in small counts we keep ourselves: for example that setup was finished, a post was shared or the top-up sheet was shown. No outside analytics.
- To stop abuse of the free posts: a scrambled form (a one-way hash) of your email address and of your network address. We never store the network address itself.
On our public pages we count visits per page and per day, with the tag of the link that brought someone there. That count holds no cookie, no address and no name.
Why we may: most of this is needed to give you the service you signed up for. Payment records we keep because tax law requires it. The abuse checks, error reports and usage counts rest on our legitimate interest in keeping the service working and fair.
Companies that work for us
These companies handle data for us, only to do their part of the job:
- Supabase (EU, Ireland): our database and sign-in. Their sign-in service keeps a short security log, which includes the network address.
- Cloudflare (EU storage): keeps every file, photo and picture, and protects the connection to our own machine.
- Railway: runs our website and the program that makes your posts.
- Stripe: takes payments on its own page. We send it your email address, the pack and the amount. During the Ship or Die hackathon (until 16 December 2026), the hackathon's revenue checker can read our Stripe totals.
- Resend (EU): sends our emails, so it sees your address and the email.
- Anthropic (Claude, USA): helps direct and check the pictures we make. It receives your restaurant's name, the dish's menu line, what you asked for, and the picture we drew to check it. It also reads up to five photos of your place once, to describe the room, and may look at the pictures you add to a picture (to change, as a reference or as a look's sample) to plan it or to check them for unsuitable content. It never receives your email.
- TypeSafe (USA): checks that what you type for a picture, a look or a caption is about your business, sorts a picture request as simple or not, and checks the pictures you add (to change, as a reference or as a look's sample) for unsuitable content such as nudity, violence or hate symbols. It receives that text, the dish's name, description and section, and those pictures. It never receives your email.
- OpenAI (USA): when you tap the microphone in a box where you tell us what you want (for example “Anything specific?”), turns what you say into text. It receives the recording, at most a minute, with your restaurant's name and dish names so they are spelled right. We send the recording on as it is and keep nothing: not the recording, and not the text, until you send it as your instructions. OpenAI doesn't use it to train its models.
- Sentry: tells us when something breaks. We set it up to send no names, emails, network addresses, cookies or page contents, only the error itself.
- Google: if you sign in with Google, and if you connect your Google listing. Then we read the listings your Google account manages, so you can pick yours, and send Google each post you tap Post now for: its picture and text.
- Meta (Instagram): only if you connect Instagram. Then we read your account's handle and type, and send Instagram each post you tap Post now for: its picture and caption.
We use what Google and Instagram give us only to post for you and to show you the account you connected. We never read your messages, followers or other posts, and never post anything you didn't tap Post now for. Our use of information received from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements.
Most pictures and captions are made on our own machine, which we run ourselves. It gets what it needs for one job through short-lived links and keeps nothing afterwards.
Where a company is outside the EU, we rely on the safeguards it offers for that, such as the EU's standard contractual clauses.
Until 16 December 2026 every page also loads a small script from the Ship or Die hackathon, which confirms that this site takes part. It sends the hackathon the page visited, the site that linked to it and any campaign tag in the link. It sets no cookies, and it sends nothing if your browser asks sites not to track you (Global Privacy Control).
Your photos and the pictures we make
Your photos stay yours. We use them only to make your posts, posters and menus, and to show them back to you. We never sell them, share them with other restaurants, or use them, your menu or your posts to train any model, ours or anyone else's.
Photos of your place are read once to describe the room for your pictures, and that may be done by Anthropic (see above). Please choose photos where guests can't be recognised.
Pictures you add are checked for unsuitable content before we use them, by TypeSafe or Anthropic (see above); one we can't use is refused, and you get back any posts it took.
We don't paint real, recognisable people from your words; people in a photo you upload stay in the picture as they are. Nothing is shared anywhere unless you tap Share, Download or Post now, and Post now goes only to the accounts you ticked.
Emails we send
- The sign-in code, when you ask for one.
- “Your menu, in pictures” and “It's ready”, only when something took over two minutes and you had left the app. At most three of these a day. Switch them off in Settings, or with the link at the bottom of each one.
- “Your download is ready” after Download everything, and one email when your account is deleted.
No newsletters, offers, reminders to post or “we miss you” emails. Receipts and refund notices come from Stripe.
How long we keep it
- What you make stays until you delete it or your account. Something that failed and wasn't tried again is removed after 7 days.
- Download files are removed after 7 days. Email buttons stop working after 7 days.
- Backups of the database are kept for 14 days, so deleted data can remain in a backup for up to 14 days.
- When you disconnect an account, in the app or by removing Restobesto in Instagram's or Google's own settings, we delete its access key at once.
- Voice recordings are not kept: each one is turned into text and dropped straight away. We count only how many you made today.
- The scrambled network address is kept for about a day. The scrambled email address that stops the free posts being given twice is kept for good, and holds nothing else.
When you delete your account, we delete your sign-in, your restaurant, everything you made and every file. We keep only a record of each payment (the pack, amount and date, no longer linked to you) because tax law requires it, and your answer to “What was missing?” if you gave one, without your address.
Cookies
We use only the cookies sign-in and your language choice need. For sign-in: one that keeps you signed in, and one that remembers your email address for the 10 minutes between asking for a code and typing it. While you pay, the app also remembers in that browser tab what you were doing, and forgets it when you close the tab.
A cookie for your language remembers which language you want the app in (English or Dutch). It is set when you pick a language, go to sign-in from a Dutch page, or sign in, and lasts a year. It holds only the language. Our public pages set no cookies.
No tracking or advertising cookies. That's why there is no cookie banner.
Your rights, and how to use them
You can see, download, correct or delete your information, and object to how we use it.
- Download everything and Delete account are in Settings, and work at once.
- To change your email address or anything else, write to restobesto@mailbox.org. We answer within one working day.
If you think we handle your information wrongly, tell us first. You can also complain to the Dutch data protection authority, the Autoriteit Persoonsgegevens.