Privacy

What we store about customers

An email address, a name if you give us one, a six-digit code, and the record of which shops you collect at and when you were stamped. That's the lot. We never ask for and never hold payment card details.

What shops can see

A shop sees your first name, your progress on their card, and when you last visited. They cannot see your email address, and they cannot see anything about the other shops you collect at. There is no export of customer emails in the product.

What we store about shops

Shop name, web address, contact details, opening hours, location and the reward setup, all of which the shop chooses to publish. Billing is handled by Stripe; we keep only the Stripe customer and subscription identifiers so we know whether an account is active.

Where it lives

Data is stored in the EU on Railway's infrastructure. Transactional email goes through Resend. Map tiles come from OpenStreetMap, and geocoding an address uses Nominatim. If you accept analytics cookies, those events go to Firebase Analytics (Google) and, for advert measurement only, the Meta pixel (Facebook).

Email we send you

As a customer you get a receipt when you collect honey, a note when a comb fills up, a Sunday summary of your week, and the occasional reminder that a reward is going unclaimed. Every one of those can be switched off individually from the footer of any email, no sign-in needed, and sign-in links are the only thing that always sends, because turning those off would lock you out of your own card.

Shops cannot email you. They never see your address, and there is no button anywhere in the dashboard that sends you anything. Reminders are sent by BeeLoyalty on a schedule, capped at one a fortnight, and only ever to people who are close to a reward.

Cookies

• Necessary. One cookie per signed-in session, so you stay signed in. It isn't used for tracking.
• Live chat. The chat bubble is run by Crisp, a French company that stores its data in the EU. It sets its own cookies so a conversation survives you reloading the page, and it loads whether or not you accept analytics. If you never open the chat, all it holds is that cookie. Anything you type into it is read by us.
• Google Wallet, only if you add a pass. If you tap “Add to Google Wallet”, we send Google the card's reference, your first name if you gave one, your stamp count and the shop's name, so the pass can show them and update itself. Never your email address, and never anything about the other shops you collect at. Delete the pass from Google Wallet and that copy goes with it.
• Analytics and advertising, only if you say yes. Two things, and both only after you accept. Firebase Analytics (Google) counts page visits and taps, so we can see which parts of BeeLoyalty get used. The Meta pixel (Facebook) reports back when someone who saw one of our adverts goes on to start a trial. The pixel is advertising technology, and Meta may use what it receives for its own advertising — that is the trade, and it is exactly why it sits behind a yes rather than loading by default. We send it the name of the event and nothing else: no email, no shop name, no identifier of ours. Choose “Necessary only” and neither is ever downloaded. Nothing is sold on. .

Deleting your data

• Customers: Profile → Delete my account. It removes your account, your code and every honeycomb you hold, immediately. Shops keep their stamp totals, but with nothing linking any of it to you.
• Shops: cancel from the billing portal, then email us to have the shop and its data removed.

Getting in touch

Questions, or want a copy of what we hold? Email [email protected] or call +44 1270 917447.

Who the data controller is

BeeLoyalty is a service of Marangoni Junior Limited, registered in England and Wales, company number 16641108, at 29 Pickering Croft Place, Crewe CW1 4GR, United Kingdom. That company is the data controller for everything described on this page.