Privacy Policy

What we receive

The account: email address, your name if you gave one, interface language, and the time you last signed in. The password is kept as a scrypt hash, not as a password — it cannot be turned back, which is why we can replace it but never remind you of it.

Invoices: the photo of the document and everything printed on it — supplier, date, number, line items, quantities, units, prices and totals. The photo is scaled down to 1800 pixels on its long edge and stored beside the invoice so you can check the reading against the paper.

Access to your accounting system: server address, login and password. The password is encrypted with AES-256-GCM and decrypted on our server only at the moment a document is sent. It is never stored in the app or in the browser.

Devices and sessions: device name and identifier, a hash of the refresh token, and when it was issued and expires. The token itself exists only on your phone.

Technical logs: request path, response code, timing, and the text of an error when one happens.

What we do not collect

Location, address book, advertising identifiers, browsing history. The app carries no ad networks, no behavioural analytics and no tracking of you across other companies’ apps and websites — which is why it never asks permission to track.

Why we need it

To read an invoice and match its lines to your catalogue. To post the delivery into your accounting system. To show how supplier prices moved. To sign you in and tell your restaurant apart from another. To answer you when you write to support.

We do not use your data for advertising and we do not sell it. Your invoices do not become training data for anyone else’s models.

Who else sees it

Reading the photo — Google (Gemini). Reasoning about the lines — Anthropic (Claude). Short text parsing and voice transcription — OpenAI. Catalogue search — Voyage AI and Cohere, which receive product names and no prices. Sign-in emails — Resend. Hosting — Vercel. Database — Neon, Singapore region (ap-southeast-1).

Your accounting system (Syrve and the like) receives documents on your instruction, onto your own server.

Each of them processes the data on our instruction and only for its own task. Nobody else receives it, except where the law requires.

How long we keep it

As long as the restaurant exists in the service. Invoices and price history are the restaurant’s books: they are needed for years and are deleted at its request.

Sign-in codes live for minutes, sessions for weeks, and a spent token never works again.

Deletion

In the app: Profile → Delete account. What goes is everything that can sign in — the account record, every session on every device, unused sign-in codes and links.

The restaurant’s data stays: invoices, catalogue, price history and accounting credentials belong to the restaurant, not to whoever held the login. The same invoices are worked on by people with no account in the app, and we will not erase somebody else’s books because one person left.

To delete the restaurant’s data as well, write from the account address to devragrouphk@gmail.com — we erase it and confirm by reply.

How it is protected

TLS only. Account passwords as scrypt hashes. Accounting-system passwords under AES-256-GCM. Session tokens stored as hashes. One restaurant’s data is separated from another’s at the query level: the server takes the organization from your session, never from what the client sent.

Your rights

You can obtain a copy of your data, correct it, delete it, or object to the processing. Write to devragrouphk@gmail.com from the address the account is registered to.

Children

The service is for restaurants and their staff. It is not intended for children.

Changes

If this policy changes we update the date at the top of the page, and we email the account about anything material.