Effective 19 November 2026.
What we collect and why
Your sign-in. You sign in through Auth0. The app asks Auth0 for your basic profile, your email address and a sign-in pass that keeps you signed in. Our database stores your Auth0 user identifier and your email address, so we know which bakery you belong to.
Your bakery. When you create a bakery we store its name, when it was created and, if it is closed, when it was closed.
Your role. We store whether you are an owner or staff in a bakery, whether that membership is active, and when you joined.
Invitations. When an owner invites someone we store the invited email address, the role (always staff), whether the invitation is pending, accepted, revoked or expired, who sent it, who accepted it, when it was created and when it expires (7 days after it is created). We store only a scrambled form of the invitation link's secret, not the secret itself.
Products. For each product a bakery adds we store its barcode number, its name, any catalog details, its counting unit and the user identifier of the person who added it.
Stock changes. Each stock change is a permanent record: the product, the quantity, the unit, how it was captured (reviewed, rapid, manual or correction), an optional note of up to 500 characters, the time on the phone, the time the server accepted it, and the user identifier of the person who recorded it. Stock changes cannot be edited or deleted by anyone using the app. A mistake is fixed by recording a new correction. The one exception is account deletion, which removes the recorder's identifier and note from their changes (see Deleting your data).
Owner ordering settings. Owners can set targets, minimums, how often to review a product, an ordering note of up to 500 characters, and how far back to look at movement. We store these with the user identifier of the owner who last changed them.
Barcode lookups. When someone looks up a barcode, our server asks Open Food Facts for a product name, brand and image address for that barcode number. The request comes from our server, not your phone, and carries the barcode number and the app's name, not who you are. We keep the answer for the bakery so the same barcode is not looked up again for 7 days (or 1 hour if nothing was found).
On your iPhone
- The camera is used to scan product barcodes. Barcodes are read on the phone. Camera frames stay on the iPhone.
- You can also pick a photo of a barcode from your photo library. The barcode is read from the photo on the phone.
- Counts waiting to be sent, for example while you are offline, are saved in a file inside the app until the server accepts them.
- Your sign-in pass is kept in the iPhone's secure storage (the Keychain), for this device only. Signing out removes it.
- During account deletion the app saves a small file that lets it finish the deletion if the connection drops. It holds a random number, not your name, email or account identifier.
Who processes your data
- Auth0 runs sign-in. Auth0 keeps its own record of sign-in events for each user.
- Neon hosts the database where we keep everything listed under "What we collect".
- Vercel hosts the web app and the server the iPhone app talks to.
- Apple delivers the iPhone app and provides the camera and barcode reading on the phone.
- Open Food Facts receives barcode numbers for product name suggestions, as described above.
Each handles data under its own terms and privacy policy.
What people in your bakery can see
- Everyone in a bakery, owners and staff, can see the bakery's products, current stock and stock history, including any note written with a change. For each change, the history shows other members only a label for who recorded it: "You", "Owner", "Team member" or "Deleted account". The recorder's user identifier is not sent to other members. A correction also stores which earlier entry it corrects; that reference holds no personal data.
- Only owners can see the list of members, with each member's email address, role and join date.
- Only owners can see invitations and the email addresses they were sent to.
- Only owners can see and change the ordering settings and the order board.
- The app is built so that people in one bakery see only their own bakery's data.
Server logs
When a request fails with a server error, our server writes one line to the hosting provider's logs. It holds the route name (such as "/api/v1/products", never the full address), the status code, the type of error and a database error code. As written in the code today, it does not hold error messages, your email, your user identifier, sign-in passes or request contents. When an account is deleted, the server logs whether the sign-in was deleted or kept and why, without your identifier or email. A failed health check is also logged, without personal data. To limit how fast one person can call the service, the server keeps a count per person and kind of request under a one-way code. It does not hold your identifier, and each count is removed within two days.
Vercel and Auth0 keep their own request and sign-in records under their own policies.
Cookies and browser storage
The web app uses cookies from our sign-in provider, Auth0, to keep you signed in. When you open an invitation link, the browser holds the link's secret in the browser's temporary storage for that tab, including while you sign in, until the invitation is accepted or fails, then removes it. Closing the tab also clears it. We use no advertising or analytics cookies.
Deleting your data
Deleting your account. In the iPhone app, open Account and tap Delete Account. On the web, open Account and choose Delete my account. Either way, here is what that does:
- Your account record, including your email address, is deleted, along with all your bakery memberships.
- Invitations sent to your email address, or accepted by you, are deleted. On invitations you sent, the link to you is removed.
- Your user identifier on products, stock changes and ordering settings is replaced with a placeholder that does not identify you. Notes you wrote on stock changes are erased, and so is the ordering note on any product whose settings you changed last.
- Counts still waiting on your phone are discarded, and your sign-in pass is removed from the phone.
- If you are the only active member of your bakery (people an owner has removed do not count), the bakery is closed and its pending invitations are deleted. Accounts of people who were removed earlier are not deleted by your deletion. Removed members' account records are kept until the owner asks for deletion.
- If you are the last owner of a bakery that still has other active members, nothing is deleted. Remove the other members first, then delete your account.
What is kept. The bakery's name, products, quantities, times and capture types in the stock history stay, including after a bakery is closed. Notes written by other people stay. Invitations you sent stay, with the invited email address, except pending invitations of a bakery that closes, which are deleted. These records are shared with the rest of the bakery, which is why deleting one person's account does not remove them.
Your Auth0 sign-in. Your sign-in may be shared with other Leaf Automation products. We delete your sign-in only if it was created for Bakery Stock Pilot, is not shared with another Leaf Automation product, and is not a Leaf Automation staff address. Otherwise we keep it, and the app tells you so. If your bakery data was deleted but removing the sign-in did not finish, the app asks you to try again.
Deleting the rest. There is no button today to delete a whole bakery's data. To ask us to delete a closed bakery's records, anything kept after an account deletion, or your Auth0 sign-in, write to contact@leafautomation.ai. We answer within 30 days. We delete a closed bakery's records only on email from the owner's sign-in address.
How long we keep data
We keep account, bakery, invitation and stock records until they are deleted as described above. The code has no automatic expiry for them. Invitations stop working after 7 days but the record stays. A barcode lookup answer is reused for up to 7 days. After that it is replaced, or removed the next time the bakery looks up a barcode. Backups are held by the database provider; we promise no separate retention period.
Children
Bakery Stock Pilot is a work tool and is not meant for children under 13. We delete information we learn came from a child on email request to contact@leafautomation.ai.
Changes
If this page changes we will change the effective date above.
Contact
For privacy questions, email contact@leafautomation.ai.