Privacy policy

Last updated: October 23, 2026

Who we are

Cloud M SARL ("we") runs SYNQ, the internal system our staff use for ordering and purchasing: branches order from the central kitchen, purchasing buys from suppliers, deliveries travel between branches, and branch managers ask for new products. Cloud M SARL is responsible for the personal data in SYNQ.

SYNQ is for our staff only. There is no public sign-up: an administrator creates every account.

This policy covers SYNQ on the web at https://delimanagement.cloudm.tech and the SYNQ app for iPhone, iPad and Android.

What we collect

We collect only what SYNQ needs to work. Here is all of it, and how it reaches us.

Your account

An administrator enters these details when creating your account. You can change your name, email address and preferences yourself.

your name and work email address;
your role, your branch and, if you work in the central kitchen, the categories you prepare;
your language (English, French or Arabic) and, in Arabic, whether numbers use Arabic-Indic or Latin digits;
whether your account is active, when it was created and last updated, and when its email address was verified;
your password, stored only as a bcrypt hash, from which the password can't be recovered;
if you use two-factor authentication: its secret key and your 8 recovery codes, encrypted;
if you add a passkey on the web: its public key and a name you can change, such as "Safari on Mac". We receive no biometric data, such as your fingerprint or face.

Your work in SYNQ

As you work, SYNQ records what you do, with your name and the time:

the orders, deliveries, purchase orders, product requests and day closures you take part in: who created, sent, reviewed, approved, declined, prepared, dispatched or received each one, and when;
the notes and reasons people type, such as why something was declined, returned, cancelled or removed;
the history of each of them: every change of status, who made it, when, and any note;
an activity log of who did what and when, with the old and new value of each changed detail. When an email address is changed, for example, the old address stays in the log. The log holds no IP address or device details;
in the central kitchen, who opened each order first, and when.

Photos

Administrators add product photos, and branch managers can add photos to product requests: JPG, PNG or WebP files of up to 2 MB.
When a photo is uploaded, the server removes its location and other camera information (Exif, XMP and IPTC data), keeping only its orientation.
Photos are stored on the server under random 40-character file names.

Signing in from the app

Your email address and password, sent once over an encrypted (HTTPS) connection.
Your device's model name, such as "iPhone 16 Pro" or "Samsung SM-X200", which the app reads automatically. It isn't the name you gave your phone. It labels the sign-in in your own list of signed-in devices.
For each sign-in, the server keeps that model name, when you signed in, when the sign-in was last used and when it expires. The sign-in key itself is stored only as a hash.
With two-factor authentication, the server holds your sign-in for 5 minutes while you enter your code.

Web sessions

When you use SYNQ on the web, or open its sign-in page or these pages, even without signing in, the server stores your session with your IP address and your browser's identification (its user agent).

Protection against password guessing

To slow down password guessing, the server counts failed sign-ins by email address and IP address, and requests by IP address. The counts last about a minute.

Push notifications

Push notifications stay off until we switch them on. Once they are on, and you allow them on your phone:

the server stores your phone's notification token and its platform (iOS or Android), linked to your account and to that sign-in, with the last time the phone checked in;
notifications carry as little as possible: order or document references and branch names, never people's names or items. For example, "New order" followed by the order's reference and the branch it comes from, or "Delivery … is on its way";

What we don't collect

your location: photos lose theirs on upload;
your contacts;
your phone's advertising identifier;
anything through your microphone, which the app doesn't use.

We don't track you across other apps or websites, and we use no analytics, crash-reporting or advertising services. We don't sell your data.

Why we use it

To run SYNQ: to sign you in, show you what your role and branch need, and pass orders, deliveries, purchase orders and product requests between the people who handle them.
To keep the company's records: who did what and when, so that orders, stock, deliveries and purchases can be checked later.
To keep accounts safe: to slow down password guessing, refuse passwords known from data leaks, and let you see and end your own sign-ins.
To tell you what needs your attention: in the notification bell and, once they are on, by push notification.
To show SYNQ the way you chose: in your language, with your digits and theme.

Who can see your data

Your colleagues see your name on the orders and documents they are allowed to open, with the notes and reasons on them. Central kitchen staff don't see the notes written for other categories.
Administrators see every account (name, email address, role, branch, categories, whether it is active), the full history of every order and document, and a daily activity report of each person's actions, which they can export as a CSV file.
Administrators and the central kitchen's chef see which kitchen staff haven't opened an order yet.
Only administrators see other people's email addresses, language or two-factor status.
Suppliers see, on a printed purchase order, the name of the person who issued it and the address of the branch it is delivered to.
Photos: a photo opens only for someone signed in to SYNQ. Everyone signed in sees the product photos. A product-request photo is shown only to administrators and to the managers of the branch that made the request; once the request is approved, its photo becomes the new product's photo.

Service providers

We use these providers to run SYNQ. Each receives only what its task needs.

Cloudflare: all traffic between your browser or phone and the server that runs SYNQ passes through Cloudflare's network, including your IP address.
Google Firebase Cloud Messaging, which passes notifications on to Apple Push Notification service on iPhone and iPad, only once push notifications are on. They receive your phone's notification token and the text of each notification. Once push notifications are on, Google's Firebase software also starts when the app opens, before you sign in. Google declares that this software collects a device identifier, diagnostic data and other technical data, not linked to your identity and not used for tracking. Firebase keeps an app installation's identifier until it is deleted, then erases it within 180 days.
Have I Been Pwned (its Pwned Passwords service): when a password is set, SYNQ checks that it hasn't appeared in a data leak by sending only the first 5 characters of the password's SHA-1 hash. The password itself never leaves the server.

These providers may process data outside Lebanon.

How long we keep it

Your account, the business records, their history, the activity log and product-request photos: as long as Cloud M SARL keeps its business records. Today, none of these is deleted automatically.
Product photos: when a photo is replaced or removed, the old file is deleted.
App sign-ins: a sign-in stops working after 12 hours without use (30 days at most), when you log out, when your account is deactivated, or when your password changes. Its record is deleted when you log out, or otherwise within about a month.
Notification tokens: deleted with their sign-in, when you log out of the app, when Firebase reports that they no longer work, or after a month without use.
Web sessions: end after 2 hours without activity, when you log out, or when they are ended for you, for example when your password changes. Remember me keeps a browser signed in for up to 400 days, unless you log out or your password changes.
Password-guessing counts: about a minute. A sign-in waiting for its two-factor code: 5 minutes.
Error logs and backups: the server's error log can include the ID of the account involved in an error, and we copy the database before each update. We use them only to fix problems and to restore the service if an update goes wrong.
After your account is deactivated: see "Deleting your account" below.

Cookies and browser storage

SYNQ on the web uses only its own cookies, all needed for it to work: no advertising, analytics or third-party cookies. It loads no scripts or fonts from anywhere else.

the session cookie, which keeps you signed in. It is encrypted and ends after 2 hours without activity;
XSRF-TOKEN, which protects your forms against forged requests;
a cookie whose name starts with remember_web, only if you tick Remember me, for 400 days;
appearance, your light or dark theme, for 1 year;
sidebar_state, whether the side menu is open, for 7 days.

Your browser's local storage also holds your theme and, for at most 24 hours, any draft you haven't sent yet. Drafts are cleared when you log out.

On your phone

The app keeps its sign-in key in the phone's secure storage (the iOS Keychain or the Android Keystore), on that phone only. It is never synced, and it is wiped if you reinstall the app.
A draft you haven't sent yet, such as an order you're putting together, is kept for at most 24 hours and removed when you log out.
The app also stores the interface's translations, your theme and its registration for push notifications.
A report you export (CSV or XLSX, which can include staff names) is saved in the app's temporary folder so that you can share it; the phone clears that folder.
The app is left out of Android backups.
Permissions: the app asks for the camera and photo library only when you add a photo of a product, and for notifications only once push notifications are on. It never asks for your location or contacts, or for permission to track you.

How we protect it

Every connection uses HTTPS; the app refuses any other.
Passwords are stored only as hashes, and a password that has appeared in a data leak is refused.
You can add two-factor authentication, with an authenticator app and recovery codes, and passkeys on the web.
The server checks your role on every request, so you reach only what your role allows.
Sign-in keys are stored as hashes on the server, and in your phone's secure storage.
Failed sign-ins are slowed down, and unused sign-ins expire.

If you think someone else has used your account, change your password and tell an administrator straight away.

Your choices and rights

See and correct your details: your name and email address are in Settings → Profile.
Manage your security: in Settings → Security, change your password, set up two-factor authentication and, on the web, passkeys. In the app, the same page lists your Signed-in devices, and you can log any of them out.
Choose how SYNQ looks: pick your language in the menu, and your theme and digits in Settings → Appearance.
Withdraw a permission: you can turn off the app's access to the camera, photos or notifications at any time in your phone's settings.
Ask us: you can ask us for a copy of your personal data, or to correct or delete it, where the law allows. Data we need as business records may be kept. See "Contact" below.

Deleting your account

Your account is created and managed by Cloud M SARL's administrators, so you don't delete it yourself. To have it deleted, ask your manager or an administrator. An administrator deactivates it: you can no longer sign in, on the web or in the app, and every sign-in it held stops working. Your name and email address stay on the account, and the records you took part in keep showing your name, because they are Cloud M SARL's business records. You can also ask us to delete your other personal data, where the law allows (see "Your choices and rights" above).

You can also write to us at [email protected].

Children

SYNQ is only for our staff and is not meant for children. We don't knowingly collect children's data.

Changes to this policy

We update this policy when SYNQ or the way we use data changes; the date at the top shows the current version. We'll let you know about important changes.

Contact

Cloud M SARL is responsible for your data in SYNQ. For a question about this policy, or a request about your data:

Email: [email protected]
At work: your manager or an administrator