Privacy Policy

This website

This website sets no cookies and has no ads, trackers or analytics. The fonts are stored with us, so browsing sends no request to anyone else.

The website is hosted on Cloudflare, which sees your IP address in order to deliver the page, as any host does.

When you sign in

You can enter the dashboard with a Google account, or with an email and password.

If you sign in with Google, we take only your name, your email and your account number there, and we ask for no other permission. We keep no sign-in key from Google, so we cannot reach your Google account. Each time you sign in, the name and email are refreshed from Google.

If you sign in with an email and password, the password is not stored as it is: it is stored only as a slow, salted hash (Argon2id), so nobody can read it, not even us.

We send you emails from no-reply@bosla.shop through Amazon SES: a link that finishes sign-up and works for a day, a link to choose a new password that works for 30 minutes and once, or a notice that this email already has an account. Signing up makes no account until you open the link.

Under “Sign-in methods” in Settings you can add Google or a password to your account, or remove one. For any method that is added we send an email to your address, so you notice if someone else added it. When you choose a new password from a link, you are signed out of every other device.

Each sign-in attempt with an email and password, and each email we send, is logged with a hash of the email (SHA-256) and the IP address, to stop anyone guessing passwords or sending many emails.

Your restaurant’s data

We store what you and your cashiers enter so that the till and the dashboard work:

• —The restaurant’s name, shops, menu, prices and settings.
• —The cashiers’ names and the role of each. A sign-in passcode is stored in a way nobody can read, not even us.
• —Orders, bills, voids and drawer openings, with the time and the name of who made them. Orders are never deleted, because they are your restaurant’s sales record.
• —The time and IP address of each attempt to sign in with a passcode at the till, to stop anyone guessing passcodes.

Your restaurant’s page in the catalogue

If you publish your restaurant, its page is public on menu.bosla.shop: the restaurant’s name, the area and logo you set, your shops’ names, addresses and map positions, and the menu with each shop’s prices and what is sold out. Anyone can read it, and search engines too.

If you unpublish, or the account is suspended, the page comes down at once. If you replace the logo, the old one stays stored with us.

A visitor to the catalogue does not sign in, gets no cookie, and nothing about them is stored. The catalogue is hosted on Cloudflare, which sees the visitor’s IP address as any host does. If they open a shop on Google Maps, they go to Google and its terms apply.

When you set a shop’s position on the map in the dashboard, the map loads from OpenStreetMap’s servers.

Your restaurant’s customers’ data

When the cashier records a delivery order, the customer’s name, number, address and the identifying mark, if one is written, are stored and printed on the bill. The customer is kept so the cashier can find them next time.

The restaurant’s owner can delete any customer from the dashboard, and old orders keep the address they were ordered to. If you are a customer of a restaurant that uses Bosla and want your data deleted, ask the restaurant or write to us.

If you connect an AI assistant

You can connect an AI assistant to your account: ChatGPT from OpenAI, Claude from Anthropic, or Gemini from Google. The assistant reads your menu, prepares changes in your draft and publishes them for you. Connecting is optional, and happens only when you sign in and agree.

What reaches the assistant’s provider is your menu: the categories, items, prices, choices and the draft that the assistant reads from Bosla, and what you write to the assistant or send it, such as a photo of your paper menu. The assistant’s tools in Bosla reach the menu and its draft only, so it does not see your orders, your customers’ data, your cashiers or your password.

We send the menu to the assistant so that it can do what you asked, and for that only. Once it reaches the assistant’s provider, it is stored by that provider and runs under its terms and its policy, not ours, and the provider decides how long it keeps it and how you delete it.

Linking the assistant to your account (WorkOS)

We use WorkOS (WorkOS, Inc.) so that the assistant gets in with your permission: it shows your consent page, and gives the assistant its access key and renews it. Bosla itself issues and stores no key for the assistant.

When you connect an assistant, we send WorkOS your Bosla account number and a sign-in address we make from it, owner-id@owners.bosla.shop, and never your email. WorkOS keeps both as your user with it, along with each assistant you allowed. The assistant itself can learn at most that account number and that address, not your email. WorkOS’s consent page shows you that address.

When you revoke the last assistant, Bosla deletes your user at WorkOS, and then the link between it and your account. It checks this an hour after each connection, and after each revoke that WorkOS confirms. If you connected but did not allow any assistant, the user is deleted after an hour as well. If you change your password from a link, it is deleted too and every assistant is disconnected.

Bosla keeps which user is yours at WorkOS until it is deleted, and each revocation until 7 days after WorkOS confirms it, so a revoked assistant cannot start working again. It writes a line in its server log for each connection and each revocation, and server logs are deleted after 30 days.

You can revoke any assistant at any time from “Connected assistants” in Bosla’s Settings, and it stops working at once. You can ask at data@bosla.shop for a copy of what Bosla keeps about the link, or for it to be deleted. What is with the assistant’s provider you control from there.

When you leave your details in a Bosla ad

Bosla’s ads on Facebook and Instagram reach us in one of two ways: a form where you leave your details so we can contact you, or a button that opens a chat with the Bosla team on WhatsApp.

If you send the form, Meta sends us only what you wrote in it:

• —Your name and mobile number.
• —The restaurant’s name, area and number of shops, your role in it, and the system you use now.
• —Which ad you sent the form from, and when you sent it.

If you talk to us on WhatsApp from an ad, we keep your name and number, which ad you came from and when you wrote to us, and what you tell us in the chat about your restaurant: its name, area, number of shops and your role in it.

We use this data to contact you on WhatsApp about trying Bosla, and to learn which ad brought more restaurants. We never send your number back to Meta, and never use it in any ad.

It is stored on a Bosla team device, and the WhatsApp messages are stored on our server on Amazon Web Services in Frankfurt. They are kept until you ask for them to be deleted: tell us in the same WhatsApp chat, or write to data@bosla.shop. If you tell us you are not interested, we will not contact you again.

Meta itself sees the form and keeps it under its own policy, because it was filled in on Facebook or Instagram, and it knows you opened a chat with us from its ad.

Cookies in the till and the dashboard

The till and the dashboard use cookies for signing in only, not for tracking:

• —Signing in with Google, or adding Google to your account: 10 minutes, deleted when you come back from Google.
• —The restaurant owner’s sign-in: 7 days.
• —Pairing a till device with its shop: 365 days.
• —A cashier’s sign-in: 12 hours, or the time the restaurant sets.

The till device also keeps the order still being written, so it is not lost if the internet drops, and your choice of language and look.

Where it is stored

Bosla’s data is stored on Amazon Web Services in Frankfurt, Germany. If you connect an assistant, your user at WorkOS (your account number and the address we make from it, nothing more) is stored by WorkOS, not on our servers, and the menu the assistant reads is stored by the assistant’s provider. The database is encrypted and not reachable from the internet, and each restaurant’s data is separate: one restaurant cannot see another’s.

There is an automatic backup we can restore from to any moment in the last 14 days. Server logs, including IP addresses, are deleted after 30 days.

Emails sent to any address on bosla.shop, data@bosla.shop included, are stored there in full too, and kept until we delete them.

Who else sees it

We do not sell your data and do not use it for ads. The only parties we deal with are those that run the service: Amazon Web Services for the server, the database and email, Cloudflare for the website, the catalogue and the till’s files, Google for signing in if you choose it, and OpenStreetMap for the map in the dashboard. If you connect an AI assistant, WorkOS runs the link, and the assistant’s provider (OpenAI, Anthropic or Google) sees the menu and what you write to it. If you came from a Bosla ad, Meta sees the form you sent or the chat you opened from it, and WhatsApp carries the messages between us.

Your rights

You can ask for a copy of your data, ask for something wrong in it to be corrected, or ask for it to be deleted. Send the request from the email you signed up with, so we can be sure it is you.

If this page changes

If we change something here, we will put the new date at the top.