Privacy Policy
Last updated: 4 October 2026
This policy explains what data Sened for Restaurants handles, where it is kept, and who can reach it. It covers the desktop application and the pages of this website. It is written plainly, because anyone buying a system to run their restaurant deserves to know exactly where their data goes before they pay for it.
In short: your restaurant's data lives on your own device. There is no server of ours it passes through, no account with us to create, and no subscription your service depends on. The only outward connection is a backup to your own Google Drive — optional, switched on by you, and stopped whenever you want.
On this page
Who is responsible for this policy
Sened for Restaurants is a product of Sened Digital Solutions, Nouakchott, Mauritania. Privacy enquiries go to contact@sened.group.
Two roles matter here. The restaurant owner decides what data goes into the system and why, and answers for it to their customers and under the rules that apply to them. We are the software provider: we deliver the application and fix its faults, and we do not operate a service that your restaurant's data passes through. Because the application runs on the restaurant's device, in normal use we see none of that data at all.
Restaurant data: what is recorded, and where
Sened keeps the following in a single database on the restaurant's device:
- Operations: orders with their items, times and statuses; tables and floors; invoices, payments and the day's closing.
- Menu and stock: the menu and its prices; ingredients, quantities and low-stock thresholds; purchases, suppliers and expenses.
- Staff: account name, internal email, role and permissions, with the password stored as a hash that cannot be read back.
- Customers — only if you choose to record them: what you or your staff enter, such as a name and phone number for delivery orders or a loyalty scheme. Sened does not ask for this data and does not need it to work.
- Settings: store details, currency, tax, printers and local network configuration.
Waiter and kitchen devices reach this data over the local network the owner sets up, not over the internet. Control of the device and of every member of staff's permissions stays with the owner alone.
What we never do with your data
- We do not collect it: Sened does not send your restaurant's operating data to a server of ours — there is no such server.
- We do not sell or rent it to anyone, and do not share it with data brokers or advertisers.
- We do not use it for advertising or to build profiles of you or your customers.
- We do not use it to train AI models, neither ours nor anyone else's.
- We do not track your usage: this edition of Sened sends no telemetry and no analytics to anyone.
Google Drive: the scope and Limited Use
Backing up to Google Drive is an optional feature. It is neither requested nor active until the owner presses the connect button. Sened then asks for exactly one scope:
https://www.googleapis.com/auth/drive.file
This is the narrowest scope that does the job: it grants access only to files Sened itself created in your account. The application uses it for three things and nothing more — upload the backup file, list the backups it created, and download one you selected in order to restore it. The rest of your Drive is not visible to Sened and cannot be, because the scope itself does not allow it.
When signing in with a Google account, Sened also receives openid, email and profile, and uses them solely to show which account is currently linked inside the application.
A backup file holds your restaurant's data in full, and travels from your device to your own Google account directly, without passing through us. Once there it is also governed by Google's terms and privacy policy.
Limited Use disclosure: Sened's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Retention and deletion
- On your device: data stays as long as the database is on the device. We impose no retention period and delete nothing — the file is yours.
- In Drive: backups remain in your account until you delete them. Disconnecting inside the application stops future access, but does not delete backups already uploaded; you delete those in Drive.
- The connection token: kept on your device in the protected storage the operating system provides, and erased when you disconnect.
- With us: we retain nothing, because we receive nothing. The only exception is what you yourself send to our contact address, which we keep for as long as it takes to answer you.
Your control and your customers' rights
Because the data is in your hands, control over it is practical rather than procedural:
- Access and export: export the full database to a file from the backup settings, at any time and without anyone's permission.
- Correction and deletion: edit or delete customer records, staff records and the rest from inside the application.
- Withdrawing consent: disconnect Google Drive in the application's settings, or revoke its access from the Google account permissions page.
- Portability: the database file is yours; move it to another device and restore it there.
If your restaurant falls under a data-protection regime that gives your customers rights — access, correction, erasure — you are the one who answers those requests, using the tools above, because you are the controller of that data. We will help you technically on request.
How the data is protected
The measures are set out on the Security page. The main ones: local storage that never crosses an external network, a separate account with defined permissions for each member of staff, passwords stored as hashes, and the Google token held in the system's protected storage. Because the device is yours, part of the protection stays your responsibility: a password on the operating system, a closed local network, and backups whose restore you test from time to time.
No one can promise absolute security. What we can promise is the smallest possible exposure — by keeping inside your restaurant everything that has no reason to leave it.
This website
These pages exist to describe the product and publish its policies: no forms that collect data, no cookies of ours, no analytics, and no JavaScript written by us — apart from one script Cloudflare injects to hide email addresses from harvesting bots, described on the Security page. They are hosted on GitHub Pages behind Cloudflare, and both may process technical connection data such as an IP address in order to serve and protect the page, under the GitHub Privacy Statement and the Cloudflare Privacy Policy. Fonts are loaded from Google Fonts, the only external connection the page makes. The screenshots shown come from a demo store with invented names and figures, not from any real restaurant's data.
Changes and contact
If the way Sened handles data changes, we update this page and change the date at the top. Any material change — collecting data we did not collect before — is stated here plainly, not slipped through quietly.
For questions, privacy requests, or anything you want settled before buying, write to contact@sened.group. To report a security vulnerability, put the word "security" in the subject; the details are on the Security page.