Skip to contentNEARA

Is Nexara safe? Roles, data, and what happens to your orders

A call-center agent needs a customer's delivery address to send dinner to the right door. You need to know who else can open that record, especially after someone changes branches or leaves.

Who can access your restaurant's data?

Nexara, a restaurant order and operations platform built in Amman, Jordan, offers staff roles and branch assignments while keeping customer data restaurant-owned, with CSV export and deletion on request within 30 days. Hosting and recovery details require written confirmation before buying. Start with an access walkthrough to check what each employee can see and do.

Who can access your restaurant's information?

Nexara has a permissions module, user-to-branch assignments and 12 defined roles. These include company owner, area manager, branch manager, cashier, call-center agent, inventory manager, driver and waiter. Those are different responsibilities in a restaurant, and access should follow the work a person actually does.

Waiter, cashier and branch-manager roles are restricted to their assigned branch for dine-in payments. NexaraFlow also assigns task lists by role. For other access boundaries, make the demonstration practical: open the same record as an owner and as the staff member who will use it.

  1. Write down each employee's job and the branch where they work.
  2. Choose the role that matches that job, then review its permissions with Nexara.
  3. Test a routine action and an action that employee should be unable to perform.
  4. Include access review in your process when someone leaves or changes branches.

The restaurant staff roles and permissions guide covers the access decisions to make before handing over a shared restaurant computer. During the demonstration, check the account a cashier will actually use, rather than judging access from the owner's screen.

Where does Nexara use one-time phone codes?

Nexara signup uses a phone number and a one-time SMS code, delivered through JOSMS. Storefront checkout also uses a one-time code to verify the customer's phone.

For the restaurant account, the practical question is whose phone receives that code. If the employee who opened the account leaves with that number, the owner needs a clear way to regain access. Ask Nexara to walk through that situation during setup.

Use a number the business can keep control of when staff change. Protect the associated handset. Employees should enter codes only in the signup or checkout process they started; a message asking them to forward a code deserves a pause, even if it appears to come from a familiar person.

Walk through everyday staff access and account recovery with Nexara too. Record who handles those tasks at the restaurant, rather than leaving that responsibility with whichever employee first opened the account.

Who owns customer records, and can you take them away?

The restaurant owns its customer data. Nexara customer records include addresses and order history, and its published FAQ promises CSV export of orders and customers. Nexara never markets to your customers. Deletion is available on request within 30 days.

CSV is a plain tabular file format that spreadsheet applications can open. Before committing your records, review a sample export and check which fields it contains. If you later move to another system, those columns determine which records you can carry across and what preparation they need.

An exported customer file can contain phone numbers and delivery addresses, so decide who may receive it before downloading. Store the file in a business-controlled location. A copy forwarded to a staff chat puts those details on phones outside the restaurant's account permissions.

If you plan to leave, export and check the records you need before requesting deletion. The customer data ownership guide explains the practical ownership questions, while the Nexara data ownership FAQ states the export policy.

What happens to orders when the internet or printer fails?

Orders keep arriving in Nexara's cloud queue while a branch connection is down; the order board itself needs a connection. Queued tickets catch up when the branch reconnects. A phone hotspot beside the printer PC is a practical backup to include in your opening checks.

A printer failure follows a separate path. The order remains on the board and its ticket waits in a queue. Staff can re-route the affected categories from the dashboard, or Nexara can select a backup printer where one is configured.

Queued tickets print once after reconnection, without duplicating tickets that have printed. Staff can deliberately reprint a ticket when the kitchen needs another copy.

Include a supervised interruption test in setup: follow a test order through a connection loss and recovery, then check the printed ticket against order history. Make sure the person running the shift can identify which printer should receive it. Nexara's order and printing features explain the queue and printer routing.

What should you ask about hosting, payments and AI?

Nexara runs in the cloud. Before buying, obtain written details of the hosting region and encryption arrangements, along with backup schedules and the process for restoring records. If your purchasing policy requires independent security certifications, request the relevant documentation.

AreaWhat Nexara providesQuestion for your review
Online card paymentsNexara supports online card payments through HyperPay, including 3-D Secure verification and refunds.Which parties receive payment information during our checkout flow?
Bloub assistantBloub answers from company data with citations. Its AI providers handle chat requests under a zero-data-retention policy.Which customer fields are sent for the questions our staff will ask?
PrivacyNexara's published privacy policy cites Jordan's Personal Data Protection Law No. 24 of 2023.Which policy provisions apply to customer export or deletion requests?
External accessExternal integrations use access credentials, and Nexara limits how frequently they can make requests.Who will hold our integration credentials and review their use?

For payment review, use a test checkout and ask where the customer enters card details. For Bloub, choose a question your manager would actually ask and request an explanation of the data sent to answer it. Keep the written responses with your purchase agreement so the next manager can find them.

How should you judge Nexara data security before buying?

A restaurant POS security review should identify which system holds each record. Nexara is the order and operations layer beside your till, meaning your cash register. Its access settings govern work and records in Nexara; review the register and payment arrangements with their respective providers.

Make the review a working session with an owner account and a staff account. Use test customer details to follow an order from entry to its saved record. Then compare what each account can access. Inspect an export separately, and keep written answers for requirements that cannot be demonstrated on screen.

Nexara support is available through WhatsApp and email during Amman hours, in Arabic and English. Founder Issa Al-Dalu answers support. Agree internally who will contact Nexara when an access problem occurs, so responsibility stays clear during service.

Use the WhatsApp button below to request a Nexara access walkthrough with the founder at nexaratech.io. Ask to compare an owner account with a staff account and watch a customer CSV export.

What to remember

  • Match staff roles and branch assignments to actual restaurant responsibilities.
  • One-time phone codes verify signup and storefront checkout.
  • The restaurant owns its customer data, with CSV export and deletion on request within 30 days.
  • Orders wait in the cloud during branch interruptions; queued tickets print after reconnection without duplication.

Questions people ask

Is Nexara safe for my restaurant's customer data?

Nexara has defined staff roles, branch assignments and a permissions module. Evaluate these against the records each employee needs to use, then include hosting and recovery requirements in your purchasing review.

Does Nexara use OTP for staff logins?

Nexara uses one-time SMS codes for phone-number signup and customer phone verification at storefront checkout. Ask Nexara to demonstrate the everyday staff login and recovery process.

Can a cashier take dine-in payments for another branch?

Nexara binds cashier, waiter and branch-manager roles to their own branch for dine-in payments.

Can I export my customers and orders from Nexara?

Yes. Nexara's published FAQ promises CSV export of customers and orders, and the restaurant owns its customer data.

Will Nexara advertise to my customers?

Nexara never markets to your customers.

Can I ask Nexara to delete my data?

Yes. Nexara provides deletion on request within 30 days.

Request a Nexara access walkthrough