Privacy Policy
Last updated October 31, 2026
The short version. BakeryOS is a tool for running a bakery. The bakery's owner signs in and keeps the business's records in it: sales, orders, the kitchen, the books, and the bakery's customers. BakeryOS has no ads, no analytics and no tracking, and the information in it is never sold. Customers' details are encrypted inside the business's records (the few that must stay readable to do their job, like the email list, are listed under how it is protected).
Who makes BakeryOS
BakeryOS is made by ANGL WORKS, LLC, and published on the App Store through the developer account of its founder, Nathan Anglin. Today one bakery uses it: Sadie May Scones (Sadie May, LLC). The bakery's records are kept in the bakery's own accounts.
Questions about this policy: dev@anglworks.com.
Who this policy covers
- The owner: the person who signs in to run the bakery.
- The bakery's customers: people whose details the bakery keeps in BakeryOS, for example to deliver an order or send a receipt. Customers never sign in to the app. The bakery decides what it keeps about them and why; BakeryOS stores and handles it for the bakery.
If you are a customer of Sadie May Scones, the bakery's own privacy policy is at sadiemayscones.com/privacy, and the bakery is the one to ask about your information.
What BakeryOS keeps
About the owner
- The owner's email address. Signing in uses a six-digit code sent to it.
- A signed-in session on each device, so the owner stays signed in there.
The business's records
- Sales at markets and in person, orders, bakes, stock and supplies, expenses, mileage, tips and money set aside for taxes.
- The owner's home address, if entered to measure mileage. It is stored encrypted.
About the bakery's customers
Only what the bakery enters, or what the bakery's website sends when someone orders:
- Name, email address, phone number and city.
- Delivery and billing addresses, and delivery instructions.
- What they ordered, their rewards points, account credit and subscriptions, and gift details (the recipient's name, address and message).
- Food allergies given with an order, and the bakery's record of confirming them with the customer.
- Notes and preferences the bakery writes down.
- Whether they agreed to get emails or texts, when, and the exact words they agreed to.
- The cards they paid with, as described next.
Payments
Card payments are handled by Stripe, through Stripe's card reader or Stripe's own payment form. BakeryOS never sees or stores a card number. It keeps only what Stripe sends back: the card's brand, its last four digits, its expiry month and year, and Stripe's card "fingerprint" (a code that lets the same card be recognized again within the bakery's own Stripe account, and means nothing outside it), plus whether the customer agreed to keep the card on file.
For Venmo, BakeryOS shows a QR code that opens Venmo with the amount filled in. BakeryOS sends nothing to Venmo.
Photos and the camera
- Receipt photos. The owner can photograph a supplier's receipt, or pick one from the photo library, to fill in an expense. The photo is sent once to be read (see Anthropic, below) and is not kept. The owner checks every line before anything is saved.
- Delivery photos. At a delivery, the owner can photograph the order at the customer's door. The photo is kept on the phone until it uploads to private storage, that customer is emailed a link to it, and it is deleted after 30 days.
Location and Bluetooth
- BakeryOS does not track where the phone is. Stripe's card-reader software asks for the phone's location while it connects the reader and takes card payments, because Stripe needs to know where payments happen to reduce fraud and disputes. That location goes to Stripe. Without it, the card reader can't take payments.
- Bluetooth is used only to connect the card reader.
- To measure mileage and plan the delivery route, the street addresses involved are sent to OpenStreetMap's free map services to work out distances and driving times. No customer's name is sent.
On the device
The device keeps its copy of the business's records, the sign-in, the customer key (see below), settings, and any delivery photos waiting to upload. Signed out, BakeryOS is a demo with made-up data that stays on the device and is never sent anywhere.
Technical details
- A random device ID that BakeryOS makes, so the owner's devices can keep their records in step.
- BakeryOS gets fixes through Expo's update service. Each check sends a random install ID, the platform and the app's version, and, if the app hit an error while starting, a short technical error message.
- Like any web server, BakeryOS's server sees the network (IP) address each request comes from. When a customer asks the bakery's website for a sign-in code, that address is kept with the code to stop abuse.
- BakeryOS uses no analytics, advertising or crash-reporting services, and does not track anyone across other apps or websites.
Who helps run it
Each of these companies gets only what its job needs, and does that job for the bakery or for BakeryOS's publisher:
- Supabase: the database, the sign-in, and private photo storage.
- Vercel: runs BakeryOS's server and its web version.
- Stripe: card payments and the card reader.
- Resend: sends the sign-in code and the bakery's emails to customers (order updates, receipts, the delivery photo), and keeps the bakery's email list.
- Anthropic: its Claude AI reads receipt photos, and checks the allergy words a customer types against the bakery's recipes. Only those words and the flavors ordered are sent for that check: no name or contact details.
- OpenStreetMap services (Nominatim and OSRM): street addresses, to find them on a map and measure driving distance and time.
- Expo: delivers app updates.
- GitHub: holds a private nightly backup of the business's records, with customers' details still encrypted.
- Twilio and Retell: the bakery's phone line and its voice assistant. When someone calls, BakeryOS's server may look up the caller's number among the bakery's customers and pass only their first name to the assistant. The assistant's summary of a call, with the caller's name and number, is emailed to the owner.
- Telegram: alerts to the owner's phone. A new website order shows a first name and what was ordered, never an address or a card; an urgent call shows the caller's name, number and what it's about.
- Apple: the App Store. When the owner taps to call, text, email or get directions, BakeryOS hands that to the phone's own apps.
BakeryOS uses these services only to do the jobs above, and each is expected to protect the information it handles at least as well as this policy does. The information in BakeryOS is never sold or rented, and never shared for anyone's advertising.
How it's protected
- Everything travels over encrypted connections (HTTPS).
- Customers' details are encrypted (AES-256) inside the business's records with a key that only the owner's devices hold. BakeryOS's server and database can't read them. When the bakery's website records an order, the server locks the customer's details with a key that can lock but not unlock.
- To send order emails and recognize callers, the server keeps its own copy of each customer's name, contact details, delivery addresses, and the brand and last four digits of a card kept on file. That copy is encrypted with a separate server key, and a customer is found by a coded fingerprint of their email or phone number, never the plain value.
- A few things are readable on the server because a job needs them: the email list (address and first name), a log of which emails went to which address, and a delivery order's address until the order is done, so its emails can say where.
- Only the owner's account can read or add to the business's records, and the database enforces it. Nothing in the records is ever rewritten: a mistake is fixed by adding a correction.
How long it's kept
- The business's records: for as long as the bakery uses BakeryOS, and at least as long as tax and food-licence rules require sales records to be kept.
- Delivery photos: 30 days.
- A delivery's readable address on the server: deleted when the order is done.
- Sign-in codes: work for one hour.
- Receipt photos: not kept.
Your choices
- The owner can sign out of any device from Account. To close the account or have its information removed, write to dev@anglworks.com.
- The bakery's customers can ask the bakery to see, correct or delete what it holds about them, except the sales records the law requires it to keep. Every newsletter email has an unsubscribe link.
- Permissions: the camera, photos, Bluetooth and location can each be turned off in the iPhone's Settings, under BakeryOS. The feature that needs it then stops working; without Bluetooth or location, the card reader can't take payments.
- Do Not Track: BakeryOS doesn't track anyone across websites, so a browser's Do Not Track setting changes nothing here.
Children
BakeryOS is a tool for running a business. It is not meant for children, and it does not knowingly collect information from children under 13.
Changes
If this policy changes, the date at the top changes with it, and any change to what BakeryOS keeps or who helps run it is described here.
Contact
ANGL WORKS, LLC
dev@anglworks.com