FoodShop FoodShop
  • How it works
  • Everything you get
  • Rewards
  • Pricing
  • What's new
  • About
Log in Start free
How it works Everything you get Rewards Pricing What's new About
Log in Start free

Privacy Policy

Last updated: 10 November 2026

1. Who we are

FoodShop is operated by Y.S.I.A. Software Solutions LTD., a company registered in Israel. In this policy, "FoodShop", "we", "our" and "us" mean that company.

This policy explains what personal information we handle, why, who else receives it, how long we keep it, and what you can ask us to do about it.

For any privacy question, or to exercise any right in this policy, email [email protected].

2. Two different relationships

FoodShop is used by two kinds of people, and our role is different for each. This distinction matters, so we state it plainly.

Bakers and other food businesses who hold a FoodShop account. For their information, we decide what is collected and why. In data protection language we are the controller.

Customers who buy from a baker's FoodShop storefront. The baker decides what she asks her customers for and what she does with it. We hold and process that information on her behalf, under her instructions, so that her shop works. In data protection language she is the controller and we are her processor.

So if you are a customer and you want your information corrected or removed, the fastest route is to contact the baker you ordered from. You can also contact us and we will help, but she decides.

FoodShop never sells personal information, to anyone, in either relationship.

3. What we collect from bakers

You give us:

  • Your name, email address, phone number, business name, country, state and time zone
  • Your recipes: ingredients, quantities, costs, yields, prices and notes
  • Your pantry: ingredient names, prices, suppliers and the allergens you record against them
  • The allergens you choose for each recipe and each product option
  • Your shop settings: pickup locations, delivery areas and fees, hours, lead times, payment methods
  • Photos you upload: ingredient labels, product photos, your logo. A photo you take so that we can read a label or a recipe for you is deleted after 90 days; see section 10.
  • Messages you send us through Ask the Founder, including any attachments
  • Your Square account connection, if you choose to connect one, so that your customers can pay you

Your subscription payment details go directly to Paddle, our payment processor. We do not receive or store your card number.

Collected automatically:

  • Pages and features you use inside the app, so we can see what works and what does not. These records do not include your IP address or browser details.
  • Error reports when something breaks, so we can fix it
  • If you turn on phone notifications, a registration for each phone you turn them on for — an identifier your browser's push service gives us so it can deliver a notification to that phone. It is not a phone number and we cannot read anything else from it. The notifications themselves carry an order number, item names and a total, never a customer's name and never the text of a message, and their contents are encrypted so that the push service cannot read them. Turning notifications off on a phone deletes its registration.
  • Session recordings of your use of the baker app, used to understand how people navigate it. What you type, and any customer or business details shown on screen, are masked, so no customer's name, email address, phone number or address is visible in them. The app's own labels and buttons stay readable.

If you ask us to set up FoodShop for you on our Switching page, we keep what you enter in the form (your email, name, shop or social link, your answers and message) and how you found us (campaign tags in the link and the page you came from). We use it only to set up your FoodShop and follow up with you.

4. What we collect from a baker's customers

When someone orders from a baker's FoodShop storefront, we handle, on that baker's behalf:

  • Their name, email address and phone number
  • Their delivery address, if they chose delivery
  • What they ordered, including any options and any note they wrote
  • Any message they exchange with the bakery about their order, including photos they attach. The bakery writes from inside FoodShop and the customer replies by email; both halves are stored with the order so the bakery can see the conversation. We do not read these messages, we do not use them to train anything, and they are never sent to an AI provider.
  • The order total, the payment method chosen, and whether payment succeeded
  • Their IP address, which our servers record in access logs in order to serve and secure the page. Those logs are deleted automatically within 45 days. It is not stored with their order, and nothing in our database holds it.

Card details are never sent to us. They are entered directly into Square's own payment form and go to Square. The same is true of Apple Pay and Google Pay, where the payment is authorised on the customer's own device.

On the customer's own device: to save them retyping on their next order, their name, email address and phone number are stored in their browser. This stays on that device, is never sent anywhere beyond what an order already sends, and clearing the browser's site data removes it. Their delivery address is not stored this way.

5. What we do with it

For bakers: to run your account, calculate your recipe costs, suggest prices, generate your labels, host your storefront, take and track your orders, notify you about your business, bill your subscription, answer your questions, keep the service secure, and decide what to build next.

We also send you occasional emails about product updates, tips and offers. Every one has an unsubscribe link, and you can turn them off in your account settings.

For a baker's customers: to take and confirm the order, tell the customer and the baker about it, let the customer look up their own order, and arrange pickup or delivery. Nothing else. We do not market to a baker's customers.

Featuring your business: we may show your public shop name and milestones, for example that a new shop opened, on our website and in marketing, as a way of showing real activity on FoodShop. You can turn this off in your account settings.

6. Artificial intelligence

FoodShop uses AI to transcribe ingredient labels you photograph, to turn a pasted recipe into structured ingredients, to suggest product descriptions and social posts, and to tidy text you write.

Where a photographed label is concerned, the AI transcribes what is printed on the packet. It does not work out allergens, and it never selects any for you.

We use two AI providers, Anthropic and OpenAI. Anthropic is used first. OpenAI is a fallback: it is called when Anthropic fails, or when Anthropic is slow to answer on the heavier tasks such as reading a photographed label. So what you send usually reaches Anthropic only, and sometimes reaches both.

What is sent to them: the photo or text you are asking us to work on, and the ingredient, pantry and recipe names it relates to. Free text you write may be included where that is the thing being processed.

What is never sent to them: any information about a baker's customers. No customer names, emails, phone numbers, addresses or orders are sent to any AI provider.

What they do with it: under the commercial terms we use, neither Anthropic nor OpenAI trains its models on what we send. Both delete what we send within 30 days. Both process it in the United States.

AI is not always right. Anything the software produces is a draft for you to check. See our Terms of Service, which is explicit about this.

7. Payments: two separate things

These are genuinely separate and the difference matters.

Your subscription to FoodShop is paid to Paddle.com Market Limited, who act as our Merchant of Record. Paddle collect your name, billing address and card details, handle the billing and any sales tax, and pay us. We see that you are subscribed and on which plan. We do not see your card.

Money your customers pay you for food goes to you, through your own Square account, which you connect yourself. FoodShop never holds, touches or has any claim on money from a food sale. We do not take a cut of it and we cannot refund it. If a customer pays you by cash, Venmo or Interac, that is arranged directly between you and them and no money passes through us at all.

8. Who else receives information

Below is every outside service that receives personal information through FoodShop, what it gets, and whose information it is. We have listed all of them rather than describing categories.

Payments

Service Whose information What it receives
Paddle (UK) Baker Email address and account id, plus the name, billing address and card details the baker enters into Paddle's own form. Merchant of Record for subscriptions. Paddle's script also loads on most pages of our marketing website, not only at checkout, so Paddle receives the IP address and browser information of anyone who opens one of those pages.
Square (US) Customer, baker The customer's card details, entered directly into Square's own form, plus the amount, the order reference and a note naming the order and the customer. The baker's connected Square account.
Venmo (US) Customer Where a baker offers Venmo, the storefront builds a payment link the customer chooses to open, carrying the amount and the order number.
Apple (US) Customer Where Apple Pay is used, the payment is authorised on the customer's own device by Apple.
PayPal (US) Customer Where a baker's payment link is a PayPal link, the storefront shows a button carrying the amount and, where the link format allows it, the order number. Nothing is sent unless the customer opens it.
Cash App (US) Customer Where a baker's payment link is a Cash App link, the storefront shows a button carrying the amount. Nothing is sent unless the customer opens it.
Stripe (US) Customer Where a baker's payment link is a Stripe payment link, the storefront shows a button pointing at it. We add nothing to the link. Nothing is sent unless the customer opens it.
Autobooks (US) Customer Where a baker's payment link is an Autobooks payment form, the storefront shows a button pointing at it. We add nothing to the link. Nothing is sent unless the customer opens it.

A baker may use a payment link of her own choosing. The services above are the ones we recognise by name, so that we can fill in a button label and put the order amount into the link. A baker is free to paste a payment link for any other service, and we cannot list those in advance: if she does, the storefront shows a button pointing at the address she gave us, and opening it takes the customer to that company's own page. We never send that company anything ourselves — the customer's browser goes there only when the customer chooses to, and what it carries is the order amount and order number, nothing more. The payment itself happens on that company's page under its own privacy policy, not ours.

Hosting and infrastructure

Service Whose information What it receives
Amazon Web Services (US) Baker, customer Everything: the database, the nightly database backups, server logs, and every photo uploaded. Amazon's CDN serves storefront pages, so it sees visitors' IP addresses.

Email

Service Whose information What it receives
Resend (US) Baker, customer Every transactional email we send and its contents: order confirmations and receipts, status and pickup messages, baker notifications, sign-in links for the customer order page, and messages between a bakery and its customers about an order, including any photos attached. Resend also receives customers' replies to those messages, which arrive at an address on our own domain before being passed to us.
MailerLite (Ireland) Baker A baker's email address, first name, most recent recipe name, shop link, and simple activity signals, used to send her the product emails she can unsubscribe from. Stored in the EU, on Google Cloud in Germany and the Netherlands.

Artificial intelligence

Service Whose information What it receives
Anthropic (US) Baker See section 6. Never customer information.
OpenAI (US) Baker See section 6. Never customer information.

Analytics and error reporting

Service Whose information What it receives
PostHog Baker Which pages and features a baker uses, and session recordings of the baker app. What a baker types, and any customer or business details shown on screen, are masked, so no customer's name, email address, phone number or address is visible in one. The app's own labels and buttons stay readable. Recordings are kept 30 days. PostHog also runs on our marketing website.
Sentry Baker, customer Error reports when something breaks. We switch off and strip request contents, cookies, headers, query strings, URLs, IP addresses and user identity before sending, but the connecting IP address necessarily reaches Sentry in order to deliver the report.
Google Analytics Website visitors Pageviews, IP address, browser and referrer, on our marketing website only. Not in the app or on any baker's storefront.

Sign-in

Service Whose information What it receives
Google (Firebase Authentication) Baker Email address and password, or your Google identity if you sign in with Google. Handles password resets and verifies your sign-in. Customers do not use this.
Google (gstatic.com) Visitor to our sign-in pages An image is loaded from Google for the "Sign in with Google" button, so Google receives an IP address and browser details from anyone who opens those pages, whether or not they use it.
Meta (Facebook) Baker, if chosen If a baker chooses to sign in with Facebook, her Facebook identity is exchanged with Meta. Separately, the share buttons in the app open Facebook with the public shop link, and only when a baker clicks them.

Fonts

Service Whose information What it receives
Google Fonts Baker, customer Our pages and every baker's storefront load fonts from Google, so Google receives the IP address, browser and page address of anyone who views them.

Phone notifications

These three only apply to a baker who has turned phone notifications on, and only to the phone she turned them on for. Which one of them is used is decided by her browser, not by us. In every case the contents of a notification are encrypted so that the push service cannot read them — what it can see is that a notification was sent, when, and how large it was.

Service Whose information What it receives
Google (Android push) Baker Chrome's push service. It issued the registration that identifies her phone, and it delivers each notification to it. It receives that registration, the time of each notification and its size. It does not receive the contents, which are encrypted so that only her phone can open them, and it never receives anything about her customers.
Apple (iPhone push) Baker Safari's push service, used when FoodShop has been added to an iPhone's Home Screen. Receives the same three things as the row above, and not the contents.
Mozilla (Firefox push) Baker Firefox's push service. Receives the same three things, and not the contents.

Website chat

Service Whose information What it receives
Crisp (Netherlands) Website visitors, including bakers who chat Live chat on our marketing website only. Crisp receives the IP address, browser information and the conversation. Crisp is not in the app, the admin, or any storefront.

Booking a call

Service Whose information What it receives
Calendly (US) Website visitors, and anyone who books a call The booking widget on our Ask the Founder page loads Calendly's script, so Calendly receives the IP address and browser information of everyone who opens that page. If you book a call, Calendly also receives your name, email address and whatever you write in the booking form.

We also share information where the law requires it, for example in response to a valid legal request, and we may share aggregated figures that identify nobody.

9. Where information is processed

Information is stored and processed in the United States, on Amazon Web Services.

We operate from Israel, so our own staff access it from there. Israel holds an adequacy decision from the European Commission.

Paddle processes subscription payments in the UK and EU. Crisp stores website chat in the Netherlands and Germany. MailerLite stores its mailing list in the EU, in Germany and the Netherlands. Every other service listed above processes in the United States.

For customers in Canada: your information is stored and processed in the United States and accessed from Israel, which means it is subject to the laws of those places, including lawful access requests by their authorities.

Where information leaves the EEA or the UK for a country without an adequacy decision, we rely on Standard Contractual Clauses or the equivalent.

10. How long we keep it

What How long
Your account and everything attached to it Until you delete your account, which also deletes every photo you uploaded. Copies survive in our backups for up to 30 days after that, then age out.
Photos you took for us to read — a label or a recipe 90 days from the scan, then the photo is deleted, along with the working files the scan produced. What it found stays: the ingredient with its nutrition and allergens in your pantry, and the recipe in your recipes, for as long as your account is open.
Orders, and the customers who placed them For as long as your account is open. There is no time limit while you are using FoodShop. When you delete your account, your customers' names, email addresses, phone numbers and addresses are removed from them, and only the amounts, the dates and the order numbers remain.
Messages between a bakery and its customers about an order, and photos in them Kept for as long as the order is. Deleted when the bakery deletes that order, and when the bakery closes its account.
Messages you send us through Ask the Founder 3 years from your last message in the conversation. Any file you attached is deleted with it.
Switch requests 1 year
The registration for a phone you turned notifications on for Until you turn notifications off on that phone, or your browser's push service tells us the registration no longer exists — whichever is first. We also delete any registration that has not been used for 180 days.
Conversations on our website chat As long as we need them to help you. Ask us and we will delete yours.
Which pages and features you used While your account is active. These records hold no IP address or browser details.
Session recordings of the baker app 30 days, held by PostHog.
Server access logs, which include IP addresses 45 days, then deleted.
A log of emails we sent, with the recipient's address 90 days, then deleted.
Error reports 30 days, then deleted.
What our AI providers hold 30 days, held by them.
What Resend holds 30 days, held by them.

11. Your rights

Whoever you are, you can ask us to:

  • Tell you what personal information we hold about you
  • Correct anything inaccurate
  • Delete your information
  • Give you a copy
  • Stop sending you marketing

Deleting your account. You can delete your account yourself, from Settings. Before you confirm, the app summarises what deletion removes. Deletion is permanent, and copies remain in our backups for up to 30 days as described above.

What survives deleting your account. This is the complete list:

  • What you paid us and when, which we keep for our accounts and in case of a card dispute, no longer linked to your name
  • A record that your account was deleted, including the email address it had, so that we can answer questions about it later
  • A note that your email address should not be sent marketing, so that deleting your account does not undo your unsubscribe
  • A record of each label you printed: when, the recipe name, the ingredient and allergen text that was on the label, your email address and the IP address you printed from, which we keep as a food-safety record because that label may still be on a package
  • The record of which version of our Terms you accepted and when, which is our only proof of that agreement

Everything else connected to your account is removed.

Getting a copy. From Settings you can download a copy of your account, which contains your profile, your recipes, your custom ingredients, your ingredient prices, your shop, your orders, your customers, and your shop settings.

Note that this file contains your customers' personal information, not only yours: their names, email addresses, phone numbers, addresses and order history. You are the controller of that information, and the copy you download is yours to protect. Keep the file somewhere safe and delete it when you no longer need it.

If you want a copy of anything else we hold about you, email us and we will send it to you.

If you are a customer of a baker, contact that baker first, since she decides what happens to her customers' information. That includes the messages between the bakery and that customer about their orders, and any photos in them: deleting the order deletes its conversation with it. Email us as well if you would rather, and we will help.

To exercise any of these, email [email protected]. We do not treat anyone worse for asking.

12. Cookies and similar technology

In the baker app, we use only what is needed to make it work and to understand how it is used: keeping you signed in, remembering your settings, and the product analytics described in section 8.

On a baker's storefront, we use only what is needed for the shop to work. There is no analytics and no session recording on any storefront. A customer's name, email and phone are stored in their own browser to save retyping, as described in section 4.

On our marketing website, we additionally load Google Analytics, PostHog, the Crisp chat, Paddle's checkout script and, on the Ask the Founder page, the Calendly booking widget. These set their own cookies. Our pages also load fonts from Google, which sets no cookies.

You can control cookies in your browser. Turning off the essential ones will stop the service working.

13. Information for people in the EEA and the UK

Why we are allowed to process your information. To perform our contract with you, where you hold an account or place an order. For our legitimate interests, in improving the service, preventing fraud and keeping it secure. With your consent, for marketing, which you can withdraw at any time. And to meet a legal obligation.

Additional rights. You may object to processing based on legitimate interests, ask us to restrict processing, withdraw consent, and complain to your own data protection authority.

Controller. For a baker's own information, Y.S.I.A. Software Solutions LTD. in Israel is the controller. For a customer's information, the baker is the controller and we act as her processor.

14. Information for residents of California

Under the California Consumer Privacy Act you may ask us what we collect, use and share, ask us to delete it, and opt out of its sale. We do not sell personal information. We will not treat you worse for exercising these rights.

The categories we collect are identifiers such as name and email, commercial information such as orders and prices, internet activity such as which pages you used, professional information such as your business name, and content you create such as recipes.

Email [email protected], or use Settings in the app.

15. Information for residents of Canada

We handle personal information in line with Canadian federal privacy law. You may ask for access to the personal information we hold about you, ask us to correct it, and withdraw consent where our processing relies on it.

As set out in section 9, your information is stored and processed in the United States and accessed from Israel. While it is there it is subject to those countries' laws, including lawful requests by their authorities.

If you are not satisfied with how we have handled a privacy question, you may complain to the Office of the Privacy Commissioner of Canada. Residents of Quebec have further rights under Quebec's privacy legislation.

Email [email protected] with any Canadian privacy question.

16. Security

We use measures appropriate to the information we hold, including encryption in transit and at rest, access controls, and separation between accounts. No system is perfectly secure and we cannot promise otherwise.

17. Children

FoodShop is not for anyone under 18 and we do not knowingly collect information from children. If you believe a child has given us information, email us and we will remove it.

18. Rewards

When a baker runs a rewards program, we process rewards information on that bakery's behalf. This may include each customer's progress toward rewards, rewards earned and used, and a history of changes to the customer's rewards.

If a baker offers a birthday reward, a customer may choose to provide their birthday month and day. We do not ask for or store the year.

If a baker offers "Bring a Friend," we create a personal referral code and record when a new customer orders through that referral. The bakery can see which customer made the referral.

To let customers securely access their rewards, we may email a one-time verification code and use a first-party cookie to remember the verified device for up to 30 days.

Bakers may use FoodShop to send communications relating to their rewards programs, such as notices that a reward was earned, reward reminders, birthday rewards, and program-change notices. Where required by law, these communications are sent only with the required consent. Marketing/rewards emails include an unsubscribe mechanism. Unsubscribing from these emails does not remove rewards already associated with the customer.

At a baker's request, we may import existing rewards balances or loyalty records provided by that baker, including records exported from another service or transferred from paper loyalty cards.

Rewards information is kept separately for each bakery and is not shared between bakeries. FoodShop does not send customer Rewards information to AI providers.

The bakery controls its customer Rewards information and FoodShop processes that information on the bakery's behalf. Customers should normally direct requests to access, correct or delete this information to the bakery. If a customer contacts FoodShop directly regarding such a request, we may assist the customer and the bakery in handling the request as required by applicable law.

19. Changes to this policy

We may update this policy. If a change is significant we will say so by email and by updating the date at the top. The current version always lives on this page.

20. Contact us

Y.S.I.A. Software Solutions LTD.

Email: [email protected]
FoodShop FoodShop

Everything you need to run your food business.

Product

  • How it works
  • Everything you get
  • Rewards
  • Pricing
  • What's new
  • Start free

Help

  • Ask the Founder
  • Blog
  • Switching to FoodShop

Legal

  • Privacy Policy
  • Terms of Service

© 2026 Y.S.I.A. Software Solutions LTD. All rights reserved.

FoodShop