Stellar Kiosk is the app behind the self-ordering screens that some restaurants have on their own premises: you choose from the menu, pay by card on the reader and take a ticket with your order number. It is used by restaurants that subscribe to Stellar Store. Three different parties are involved:
If you link your account with the kiosk's QR code (section 2), your account and your stamps are also governed by the privacy policy of that same restaurant's online shop, which is also their controller.
About Stellar, the developer of the app:
Stellar Digital S.L. (trading as Stellar Technology)
Tax ID (CIF): B-93774057
Address: Avd. Juan Gómez Juanito 16, 29640 Fuengirola, Málaga (Spain)
Email: hello@stellartech.app ·
Website: stellartech.app
You do not need to give any personal data to order at the kiosk. It does not ask for your phone number, email, address or a user account. If you do not scan the restaurant app's QR code (below), the order is anonymous: it is not linked to any customer record, loyalty scheme, stamps or coupon.
| Data | Purpose |
|---|---|
| Order content: products, chosen options, quantities, amount, eat in or take away, language, date and time, order number and order code | Preparing and handing over your order, charging for it, printing your ticket and keeping the restaurant's till and accounts |
| A name to call you (only if the restaurant asks for it, and then it is needed to order; up to 40 characters; it does not have to be your real name. If it does not ask, you are called by the turn number on your ticket) | Letting you know when your order is ready. It appears on your ticket, on the kitchen ticket and on the restaurant's point-of-sale terminal |
| Notes for the kitchen that you add to a product (optional, for example "no onion") | Preparing the dish the way you asked |
| Payment details returned by Stripe: card brand, its last 4 digits, how the card was read and the technical receipt data required by the card schemes (for example, the authorisation code) | Printing them on your ticket. Stellar's servers only keep the Stripe payment reference and its amount, not the card brand or digits |
Please do not write health data or other personal data in the notes. If you have an allergy or intolerance, check the allergens on the menu and tell the staff before ordering.
At restaurants that have it switched on, the kiosk's start screen shows a QR code. If you choose to scan it with the restaurant's customer app (at Lettus, the "Lettus" app), signed in to your account, the kiosk is linked to your account in that restaurant's online shop while you place the order:
| Data (only if you scan the QR code) | Purpose |
|---|---|
| The internal identifier of your account, stored with the order | Adding your stamp and, if you choose it, applying your free order |
| Link record: kiosk and restaurant, the internal identifier of your account, the start time, the time of the link and the end time, how it ended and which order came from it | Knowing which account goes with which order, making sure nobody else can use the link and being able to check any issue with a stamp or a free order later |
| Failed scans: the IP address of your connection and the identifier of your account, only when you scan a code that is not valid | Stopping anyone who tries codes blindly |
If you do not scan the QR code, none of this is processed and the order is anonymous.
For the kiosk to work, data about the device itself, which belongs to the restaurant, is also processed: the name the restaurant gives it, its manufacturer and model, the app version, its connection IP address and the time of its last connection, and an access credential (Stellar's servers only keep its cryptographic hash and its last 4 characters so it can be recognised, never the full credential). The device itself also stores the serial number of the connected card reader and the PIN of the staff technical screen, the latter hashed irreversibly.
When the restaurant installs the app as a dedicated device (kiosk mode), the app grants itself these permissions and turns on the device's location, so that payments work without anyone having to do it by hand. The app does not access contacts, photos, camera or microphone (the QR code in section 2 is read by your phone, not by the kiosk), and contains no advertising, analytics or tracking tools. The Stripe Terminal component built into it does send Stripe the technical data it needs for the reader and the payment to work (for example, the device model and operating system, the reader's serial number, connection and payment events, and the location), under Stripe's privacy policy.
Payment is taken on a Stripe card reader (for example, the WisePad 3) connected to the kiosk. The card data is read and encrypted by the reader itself and goes straight to Stripe: neither the app nor Stellar's servers see the full card number, its expiry date or its security code. The money goes to the restaurant's Stripe account.
The amount is first authorised and is only charged once the order has been recorded correctly; if anything fails before that, the authorisation is cancelled and you are not charged. If the failure happened just after charging, the full amount is refunded to the same card.
The payment is processed by Stripe Payments Europe, Ltd. (Ireland) in two roles: as a processor, charging on behalf of the restaurant under Stripe's data processing agreement (stripe.com/legal/dpa), and as an independent controller for its own purposes, such as fraud prevention and its legal obligations, under its privacy policy (stripe.com/privacy).
No automated decisions are made about you, no profiles are built, and the data is not used to send you advertising.
Kiosk orders are not sent to delivery platforms or to third parties for marketing purposes. The data is hosted in the European Union. Outside the European Economic Area:
When something goes wrong (an order that does not reach the kitchen, a payment that is not completed), the system alerts Stellar's technical team through a messaging service (Telegram, outside the EEA). That alert is purely operational: the type of incident and the restaurant, with no customer data at all (no names, order codes, amounts or identifiers). The details stay in the server's internal logs, in the European Union.
You can ask for more information about these safeguards at hello@stellartech.app.
The app is downloaded and updated through Google Play, which processes its own data as a controller under its privacy policy.
All communications are encrypted (HTTPS). Each device is identified by its own credential, stored encrypted on the device, which can be revoked at any time at the restaurant's request. Each restaurant can only see its own data, and each kiosk only the orders it placed itself. The kiosk runs in dedicated mode, with no way out to other apps, and its technical screen is PIN-protected. The kiosk's QR code changes every 10 seconds, each code expires after 30 seconds and each link only admits one person.
You can exercise your rights of access, rectification, erasure, objection, restriction of processing and portability. As the restaurant is the controller, please contact it first (its details are on your ticket). If you cannot, write to hello@stellartech.app: we will pass your request on to the restaurant and help it respond. If you did not scan the QR code, the order is anonymous: to find it we will need the restaurant, the date and time and the order number or code printed on your ticket. If you scanned it, we can also find it from your account.
You can also lodge a complaint with the Spanish Data Protection Agency (www.aepd.es) or with the data protection authority of your country of residence.
The app is not specifically aimed at children and does not ask them for any data: you can order without giving any.
If this policy changes, the new version will be published at this same address with a new update date. This is a translation of the Spanish version, which prevails in case of discrepancy. It is also available in Swedish.