Last updated: 17 November 2026Draft — awaiting legal review

Privacy

The Abla’s xbloom app and this website are run by Abla Roastery. This page explains what is kept on your device, what reaches our servers or anyone else’s, and when.

No account

You use the app without registering or signing in. We don’t ask for your name, email or phone number, and we don’t create an account for you.

What stays on your device only

Your favourites, your personal recipes (the ones you write and the ones you import) and your settings are stored only on your device. They are not sent to Abla and are never published.

They go when you delete them or the app. They may be included in your device’s own backup (iCloud or a computer), depending on your Apple settings; Abla has no access to it.

What the app asks Abla’s server for

The app loads Abla’s published recipes, the coffees and feature settings. These requests carry no name and no identifier of you or your device. Like any server on the internet, ours sees the network (IP) address a request comes from (see “Server logs”).

Importing from an xBloom link

Pasting an xBloom share link sends nothing. Only when you tap Fetch recipe does your device send the share id in the link, and nothing else, directly to xBloom’s public endpoint (client-api.xbloom.com), the one xBloom’s own share page uses. No account or key is used.

xBloom’s server sees that request and your network address, and xBloom’s privacy policy applies to it. The request does not pass through Abla’s servers, and the imported recipe is stored on your device only when you choose to save it.

Bluetooth and your machine

The app uses Bluetooth only after you tap Find my machine, and iOS asks for your permission first. It is used to find your xBloom nearby, connect to it and read its identification, and then to send it the recipe you select.

Information about your machine stays on your device and is not sent to Abla. The app does not use your location.

For Abla staff only: machine diagnostics run from approved staff devices when the staff member taps Scan, and their log leaves the device only if that person exports it.

The Coffees tab and the store

The Coffees tab shows abla.sa, the Abla store, which runs on Salla. Your store account, cart, orders and payment happen in the store itself, under the store’s and Salla’s privacy policy.

The app does not read the store’s pages, its cookies or your session there, and draws no conclusion about an order or a payment.

For Abla staff: device access

A staff member activates team access on their phone with a code the owner gives them. The app creates a key on the device: the private key stays in the iOS Keychain on this device only and is never sent.

The server stores the public key, the staff member’s name as the owner entered it, the role, the device label (“iPhone”), its reference (such as ABLA-7K3Q), and when it was activated, last used and revoked. Every administrative action is recorded in the audit log with the staff name and device reference.

Activation codes are stored only as a keyed hash and expire after 15 minutes. Codes, keys and signatures are never logged.

The admin console on this website

The owner signs in to the console with a pre-approved email address and a 6-digit code sent by email through our email delivery provider. The code is stored only as a keyed hash and is valid for 10 minutes.

The console uses one strictly necessary session cookie (httpOnly) that lasts 12 hours. The public pages of this website use no cookies and no analytics.

Every change made in the console is recorded in the audit log with the email that made it.

Accounts from earlier test versions

If you signed in with an earlier test version of the app, that account (your email, your name if you added one, and the recipes and favourites saved in it) stays on the server until you delete it. The app uses it only to bring your recipes onto your device, and it grants no access.

Delete it in Settings → Account from an earlier version → Delete account. That row appears only on a device that still holds such an account.

Notifications

This version of the app does not use push notifications: they are not set up in it, and the app does not ask for permission. If a later version adds them, they will stay off until you turn them on in the app and allow them in iOS, and we will update this page first.

Server logs

For each request our server records the time, the kind of request, the address requested, the result, how long it took, and the network (IP) address it came from. It does not record request contents or headers, or any code, key or signature.

Logs are used only to run and protect the service, and our hosting provider keeps them for a limited time.

No tracking, no advertising

The app does not read the advertising identifier, does not track you across apps or websites, contains no analytics or advertising tools, reads no hardware identifiers and builds no fingerprint of your device. We don’t sell your data or share it for advertising.

How long data is kept

Contact

For any question about your privacy or a request about data we hold, write to {{SUPPORT_EMAIL}}. For help using the app: the support page.

If we change this page, we update its date above.

Back to the home page