Who owns your restaurant's data, and can you take it with you?
Changing restaurant software is risky when your customer list and order history are trapped in a system you cannot inspect. You need to know what you can copy, what must be rebuilt, and which records belong to an aggregator.
Nexara gives restaurants a restaurant order and operations platform built in Amman, Jordan, with CSV export for customer records and orders. You can request deletion within 30 days. Aggregator data remains subject to the aggregator's terms, so export rights differ by channel. The next step is to open and check a CSV export before migration.
What data belongs to your restaurant?
Nexara stores records created through the restaurant's own ordering and operations activity. Customer records can include phone numbers, saved addresses and order history. Orders can include the channel, items, status, customer association and fulfilment details recorded in the platform.
Records from your own website, installable app, call center, table QR channel and branch operations belong to your restaurant. Nexara does not market to your customers.
- Customer records, including saved addresses and order history
- Orders received through your own website and app
- Phone orders entered through the call center
- Table QR orders connected to your branch
- Customer reviews, feedback and complaint cases recorded in Nexara
- Order history searchable by date and other filters
Nexara is the order and operations layer beside the till. It is not a cash register. The cashier can record the day's net sale at close for reconciliation, while Nexara keeps the order records and customer history around that sale.
For a fuller explanation, see who owns your customer data.
Can you export customers and orders?
Yes. Nexara supports self-serve CSV export of customer records and orders. CSV files open in spreadsheet software and can be handed to an accountant, operations team or replacement restaurant platform.
- Open the export area in Nexara.
- Export the customer records and order records as CSV files.
- Check phone numbers, addresses, dates, order statuses and item details.
- Keep the original files in a restricted business folder.
- Give the replacement provider only the fields it needs for migration.
- Request deletion from Nexara when the account is closed.
The how to export orders to CSV guide covers the export process in more detail. Keep a copy of the exported files before asking for deletion, because deletion is a separate action.
What happens when you leave Nexara?
You can export the relevant customer and order records, then request deletion. Deletion is completed within 30 days of a verified request. The request must identify the restaurant account.
| Record or service | Can you export it? | What to check |
|---|---|---|
| Customer records | Yes, CSV export | Phone numbers, addresses and order history |
| Orders | Yes, CSV export | Dates, channels, items and statuses |
| Own-channel customer activity | Yes, CSV export | Website, app, phone and table QR records |
| Nexara account data | Request deletion | Deletion is completed within 30 days |
| Aggregator-held records | Depends on the aggregator | Review that provider's terms and export tools |
Export gives you a copy. Deletion removes the restaurant's data from Nexara after the request is processed. Make sure your new system has received and checked the files before you request deletion.
Nexara's data security and safety information explains the related account and privacy controls.
What about Talabat and Careem orders?
Aggregator orders can arrive in Nexara's order board, but the aggregator remains a separate business relationship. Talabat and Careem keep their own commission on the orders they bring. Their customer data, retention rules and export rights are governed by their agreements and policies.
An order displayed in Nexara does not automatically give the restaurant the same control over every field held by the aggregator. Before leaving an aggregator, ask that provider what customer and order information it will export, in which format and under what conditions.
| Order source | Where the order is handled | Ownership question |
|---|---|---|
| Restaurant website or app | Nexara storefront and order board | Your customer records and orders can be exported from Nexara |
| Call center | Nexara call center screen and order board | Pro-plan call-center records can be exported from Nexara |
| Table QR | Nexara dine-in ordering | Export the order records held by Nexara |
| Talabat | Talabat plus Nexara order intake | Check Talabat's own data terms and export process |
| Careem | Careem plus Nexara order intake | Check Careem's own data terms and export process |
Nexara can bring Talabat and Careem orders into one queue for branch operations. The aggregator still controls its own platform account and records.
What should you check before signing restaurant software?
Data ownership is useful only when the exit process is clear. Ask these questions before connecting your website, phone number and customer records:
- Can I export customers and orders in a readable format?
- Which fields are included in the export?
- Can I export data without paying an exit fee?
- Who owns records from my own website and call center?
Confirm the boundary between your records and an aggregator's records. Ask which records belong to the aggregator, how long deletion takes, and whether you can test an export before moving the whole branch.
Open a sample CSV, search for a known phone number, inspect an order with modifiers, confirm dates and compare the rows with the order history shown in the account. This catches missing columns before a busy service depends on the new system.
Nexara has a free plan plus paid plans per branch in Jordanian dinar. Current rates are available on request. Customer and order CSV exports are available, and deletion can be requested.
What should you rebuild after migration?
Customer and order records can move as CSV files. Menu layout, printer assignments, branch permissions, promotions and workflow settings may need to be rebuilt in another product. Ask the new provider which settings it can import.
A restaurant may move its customer list and order history while recreating its menu, channels and branch setup in the replacement system.
Nexara's features overview shows the operational areas that sit around the till, including orders, customers, menus, printing and reports.
What to remember
- Nexara supports CSV export of customer records and orders.
- Your own-channel customer relationships remain yours.
- Talabat and Careem data is subject to each aggregator's terms.
- Request deletion after checking and securely storing the export.
- Test a sample CSV before moving a branch.
Questions people ask
Can I export customer data from Nexara?
Yes. Nexara supports CSV export of customer records, including customer details, saved addresses and order history held in the platform.
Can I export restaurant orders before leaving?
Yes. Order records can be exported as CSV. Check the file for dates, items, statuses, channels and customer associations before closing the account.
Who owns customer data in Nexara?
The restaurant owns its customer records and order data. Nexara provides the platform that stores and manages those records.
Can Nexara delete my restaurant data?
Yes. You can request deletion. Deletion is completed within 30 days of a verified request.
Do Talabat and Careem customer records belong to my restaurant?
Aggregator records are governed by the aggregator's own terms. Nexara can receive those orders for operations, but Talabat and Careem remain separate providers with their own data policies.
What is Nexara, exactly?
Nexara is the order and operations layer beside the till. It brings channels into one order board, manages customer records and supports operational work around the cashier.