Frequently asked questions

You can check it without taking our word for it. The PeerJS connection opens a direct WebRTC channel between two browsers: the visitor's phone and the advisor's screen.

No Cloudflare function receives the content of the form. There are two exceptions, deliberate and narrow: verifying an email address and verifying a phone number. Both are messages the advisor triggers. The TURN server, when it is used, only relays encrypted packets. It is technically unable to read their content.

Technical proof on request: architecture diagram and source-code access for audit. The detail is in the technical note.

The service runs on the Cloudflare network. We take on no service level agreement of our own, and our terms say so.

In a partial outage, the WebRTC connection falls back to TURN servers, and your usual procedure still applies.

Every terminal keeps a local cache (localStorage, 30 days): it keeps working even if the API is briefly unreachable.

Two safeguards:

• An escrow clause for the source code is available on request.
• The platform runs on open standards: WebRTC (W3C) and Cloudflare Workers.

A multi-year maintenance contract is available.

Whatever you receive copies in one click into any software (CRM, booking tool, ERP), with no integration needed up front.

For networks and franchises, the quote-based plan includes an API integration and custom development.

They are two different things, and the difference is structural. What a visitor types goes from their phone to the advisor's screen without touching a server. There is nothing to store, so nothing to protect.

What you record about your staff lives in your account: a name, the fingerprint of a code, performance records. Last month's target has to survive a tab being closed. You decide on those records, and you are the one who deletes them.

The rule fits in one sentence: nothing from the visitor, what you enter about your team.

You give them a new one from their profile, in a single field. A code once set can't be read back: the dashboard says it exists, it never shows its value.

And if the staff member leaves, their profile is deleted immediately, with no restore: their records go with it.

Zero server storage: it's the strongest GDPR argument there is, because it's structural.

• Minimisation (Art. 5.1.c): nothing more than what the counter asks for, and none of it remains.
• Right to erasure (Art. 17): nothing to delete on the visitor side. On the team side, a profile is deleted in one gesture, immediately and with no restore.
• Right of access (Art. 15): the visitor reads back what they entered for as long as they're in the queue.
• Rectification (Art. 16): “Review my details” takes them back to their form, already filled in.

Our subprocessors adhere to the EU-US Data Privacy Framework.

The account records what it needs to run, and nothing from the visitor form. It keeps your managers, your branches and their settings. It also keeps your front-desk staff: first name, PIN fingerprint, performance records. Finally it keeps usage measurements, under a fingerprint that changes every day, and the logs security requires.

Three narrow exceptions: the queue tag, and the email and phone verifications. The privacy policy describes them, with retention periods and subprocessors.

They are the figures you enter or import yourself, the ones from your Monday-morning spreadsheet. The platform measures nobody's performance behind their back: no clocking in, no time spent per customer, no keystrokes.

You remain the data controller. Informing the people concerned, consulting staff representatives and judging the proportionality of what you measure are yours. We provide the tool and the processing agreement.

There is nothing to refuse: nothing goes out until they have said yes. The address is entered by the person themselves on the terminal, then confirmed from their inbox. Without that confirmation, it does not exist for sending. A manager cannot sign them up in their place.

Opting out is immediate: one click from the terminal, or from the footer of any message received. Asking for a confirmation to stop receiving would hold on to someone who has already said no.

What you put in: their name, the fingerprint of their code, the records you enter. The note of encouragement you write them is there too.

And what they put in themselves: a nickname and an animation. Possibly their birthday (without the year), and an email address they confirm from their inbox.

No working hours, no clocking in, no location, no time spent per customer.

No: they see that one exists, masked. It is there to send someone their own figures, not to build an address book.

That is the first use of their code. They open their space on the terminal and browse their periods, with their target and their trend. It is not something they have to ask for.

A rank, a nickname and an overall score. No name, no identifier, no metric value leaves for that screen. Published ranks are renumbered. A gap in the sequence would tell the whole team where the colleague who chose no nickname stands.

The leaderboard is switched on or off branch by branch. A staff member with no figure for any of the criteria used is not ranked at all. Giving them a zero would put them last for a reason that has nothing to do with their work.

It depends on your counter: customers per day × minutes of typing avoided per customer.

For example, 40 customers a day and 3 minutes avoided per customer make 2 hours a day. Run the numbers with your own figures on the home page.

No. MobilityOS fits any counter where customers wait before handing over their details. For example: hotels and campsites, travel agencies, phone shops, opticians, garages and dealerships, public offices.

The form fields are fully customisable from the dashboard. Each branch decides what it collects, with no development needed.

You create the account online, customise the fields in the dashboard, then print the QR code. A branch is up and running in minutes.

No dedicated hardware, no software to install: a browser at the counter is all it takes.

Free: €0. Agence: €9 excl. tax per month or €90 excl. tax per year. Réseau: €29 excl. tax per month or €290 excl. tax per year. The free plan has no expiry and needs no credit card. SMS are not included.

The detail of each plan, and what the lower tiers leave out, is on the pricing page.

A reading of your business. You define your metrics, in the words of your own trade. They are entered by hand or imported from a CSV or Excel file. Each staff member finds their own on the terminal, with their target for the period.

As you wish, add a team leaderboard shown in the branch and a results email for whoever asked for it. There is also the list of what to offer today, kept at the counter. And a screen that says whether the tool is being used.

All of them, free included. The staff space, the leaderboard, the results email and the usage statistics do not depend on the plan.

The plans differ in the number of branches and manager seats, automatic form translation and the import assistant. They also differ in email then SMS verification of a visitor's contact details, and in priority support. The detail is on the pricing page.

No. The customer scans the QR code and everything happens in their browser. Nothing to download, no account to create.

The counter works exactly as before: MobilityOS adds to your welcome process, it doesn't replace it. The advisor enters the details the usual way. Only customers with a phone go through the digital queue.

Their own. The language is detected automatically among the 7 available: French, English, Spanish, Italian, Portuguese, German, Dutch.

The address field offers worldwide autocomplete, and formats (phone, postcode) follow the country.

Your labels, the form title and its legal text also translate into the 65 languages offered. Beyond the seven built-in ones, the screens stay in English.

An advisor types their code once when they start their shift, the way they switch on the till. They find their figures there, their position if there's a leaderboard, and the list for the day. None of it is compulsory: the queue works without anyone signing in.

You decide, with a three-position setting. The manager keeps the catalogue: the categories, shared across all your branches. The counter keeps what is available today. Tick a category, type a quantity, log a sale in one click. Nobody ever retypes a label.

Once the day is over, the list is shown greyed out and marked “yesterday's list” rather than vanishing. Yesterday's stock announced as today's would be worse than no list at all. The visitor's screen stops showing it altogether.