Three kinds of people appear in this software, and each one is treated differently.

Who this applies to

This policy covers Dearrasa, the restaurant management software, and this website.

Where a restaurant uses Dearrasa, that restaurant decides what guest and staff information is collected and why. In data protection language, the restaurant is the controller of that information and Dearrasa is the processor acting on its instructions. For our own business records, such as who subscribes to Dearrasa and who fills in a form on this site, we are the controller.

That distinction matters in practice. If you ate at a restaurant that uses Dearrasa and you want your details removed, the restaurant is the right place to ask, and we will support them in carrying it out.

What we hold about a restaurant

• Account and billing information. Business name, registered details, the contact people you nominate, their work email and phone, subscription plan and payment records.
• Operational configuration. Outlets, floor plans, stations, menus, prices, tax settings, recipes, suppliers and purchase rates.
• Trading records. Orders, bills, tenders, voids, discounts, ticket timings, stock movements, wastage entries and shift closures.
• Technical records. Device identifiers for your terminals and kitchen screens, sync logs, error reports and access logs.

Recipes, costs and supplier rates are commercially sensitive, and we treat them that way. They are not shared with other customers, aggregated into published benchmarks, or used in our marketing.

What the software holds about your guests

Guest information only exists in Dearrasa where a restaurant chooses to collect it, and it is limited to what a restaurant genuinely needs.

• Contact and identity. Name and phone number, and email where the guest gives one. A guest can decline all of this and still be served and billed normally.
• Visit history. Bills, dishes ordered, spend, outlet and date, which is what makes recognising a regular possible.
• Preferences and notes. Allergies, dietary requirements, seating preference and similar service notes entered by staff.
• Reservations. Party size, time, special occasion notes, and whether the booking was honoured.
• Feedback. Responses and free text a guest submits after a visit, linked to the bill it relates to.
• Consent record. What the guest agreed to be contacted about, when, and through which channel.

A phone number given for billing is not treated as permission to market. Consent for contact is a separate record, and where it is absent the software will not include that guest in a campaign.

We do not build guest profiles across unrelated restaurants. A guest who eats at two restaurants that both use Dearrasa exists as two separate records belonging to two separate businesses.

What the software holds about staff

• Name, role, outlet, login credentials as a salted hash, and the contact detail the restaurant chooses to hold.
• Rostered shifts, attendance, hours worked and leave, and pay rate where the restaurant enters one.
• An audit record of sensitive actions taken under that login, such as discounts, voids, comps, price overrides and stock adjustments.

The audit record exists to protect both the restaurant and the staff member, because an action attributed to a named individual is also an action that cannot be blamed on someone else. Dearrasa does not produce staff performance scores or rankings, and station timing data is reported as kitchen performance rather than as an assessment of a person.

Staff can see their own shifts, hours and leave. Pay rates and cost figures are visible only to manager and owner roles.

Why we process any of it

• To provide the software you subscribed to, which is the reason nearly all of this data exists.
• To meet legal obligations, particularly tax and invoicing rules in India that require sales records to be retained and producible.
• To support you, where a member of your team asks us to look into something.
• To keep the service secure, including detecting misuse of logins and investigating incidents.
• To bill you and keep our own company records.

We do not process your data for advertising, we do not profile your guests for our own purposes, and we do not use your trading records to inform anyone else's business.

Forecasting, and what it does with your data

The forecasting and menu insight features are trained on your own trading history only. A model built for your restaurant group uses your sales, your recipes and your stock movements, together with public information such as the calendar of holidays and festivals and, where relevant to your location, weather signals.

Your data is not pooled with other customers' data to train a shared model. Forecasting does not use guest identity, and it does not use anything about your staff as individuals. The full account of what the model reads and what it does not is on the AI Forecasting module page, written in the same terms as this section.

Where it is stored

• Primary storage and backups are held on managed cloud infrastructure located in India.
• Data in transit is encrypted with TLS. Data at rest is encrypted using the infrastructure key management service.
• Each restaurant group's records are logically separated, with no query path that returns another customer's data.
• Your counter and kitchen devices hold the current shift locally so service continues without connectivity. That local copy is limited to the operating shift and is cleared once it has synced.

Who at Dearrasa can reach your data

Access to production systems is limited to a small number of named engineers, each with an individual account, and it is granted on the basis of what a role requires rather than seniority.

Support staff work within your account only when responding to a request from your team, and that access is logged. Nobody at Dearrasa can read your password, and we will never ask you for it. If someone contacts you claiming to be from Dearrasa and asks for a password or a payment credential, they are not from Dearrasa.

Third parties genuinely involved

We use a small number of service providers because building all of it ourselves would serve you worse. Each one receives only what its function requires.

• Cloud infrastructure, which hosts the software and the database.
• Payment providers, which process card and UPI transactions. They hold the payment credentials, we do not. Dearrasa records only the outcome, amount and reference.
• Messaging providers, which deliver transactional email and messages such as your login details, reward notifications and feedback requests.
• Delivery aggregators, where you connect them. Order and dispatch information passes between you and the platform, on your instruction.
• Our own accountants and auditors, for our company records.

We do not sell data. We do not share it with data brokers, advertising networks or other restaurants. Where a legal authority makes a lawful demand for data, we will comply, and we will tell you unless we are prohibited from doing so.

How long we keep it

• Sales, tax and invoice records are retained for the statutory period applicable in India, because you are required to be able to produce them.
• Guest personal data is retained while it serves the purpose it was collected for, and is removed sooner on request. Where a guest is removed, the underlying bill is retained without identifying detail, since the sale itself must continue to exist.
• Staff records are retained for the period employment records must be kept, after which identifying detail is removed while the audit trail of actions remains.
• Technical and access logs are retained on a short rolling window sufficient to investigate an incident.
• On account closure, you can export everything, and your data is deleted after the retention window stated in the Terms of Service, apart from records we are legally required to keep.

Rights, and how removal actually works

If you are a restaurant using Dearrasa, you can access, correct and export your data from within the product at any time, and ask us for help doing it.

If you are a guest of a restaurant that uses Dearrasa, ask the restaurant. They control the record and they can remove you from it. Where they need us to act on their instruction, we will.

If you are a member of staff at a restaurant using Dearrasa, your employer holds your record. You can see your own shifts, hours and leave in the product, and requests to correct personal detail go to your employer.

Removal is not the same as deletion of history, and we would rather be precise about that. Personal identifying detail can be removed. The commercial and tax record of a transaction cannot be, because law requires it to exist. What we can guarantee is that the retained record no longer identifies the individual.

This website

• This site sets no advertising or tracking cookies, and there is no third party analytics or advertising script embedded in these pages.
• Web fonts are loaded from a font provider, which means your browser makes a request to that provider to fetch them.
• The live order rail and the fire an order demonstration run entirely in your browser. The dishes and tables shown are illustrative, nothing you select is transmitted anywhere, and no record of your interaction is created.
• When you submit the contact or sign up form, the details you enter are sent to us by email so a person can act on them. We use them to reply and to set up your workspace, and for nothing else.

Reaching us about privacy

Questions about this policy, requests relating to your own data, or a report about how data is being handled should be sent through the contact page, marked as a privacy matter. It will reach a person, and you will get a reply.

If you believe you have found a security weakness that puts data at risk, mark it as a security report. Good faith reporting will never be met with a legal threat. Our security practices, including what we do not yet claim, are set out on the Security page.