Privacy Policy
Dingly helps cafés and restaurants call orders, run stamp cards and keep in touch with their guests. This policy explains what personal data that involves, why we hold it, who else handles it, and what you can do about it. We have tried to keep it plain and specific.
- 1. Who we are
- 2. Our role: shops and guests
- 3. Data about shop owners and staff
- 4. Data about guests
- 5. The Dingly app and App Clip
- 6. Server logs and security data
- 7. Why we use data, and our legal bases
- 8. Service providers we use
- 9. Cookies and on-device storage
- 10. How long we keep data
- 11. Your choices and rights
- 12. International transfers
- 13. Security
- 14. Children
- 15. Changes to this policy
- 16. Contact us
1. Who we are
Dingly (“Dingly”, “we”, “us”) is a service for small cafés and restaurants, based in Cairo, Egypt. It runs at dingly.win, in the Dingly app for iPhone and Android, and in the Dingly App Clip on iPhone.
For any privacy question or request, email hello@dingly.win.
We do not sell personal data, we do not show ads, and we do not use third-party analytics or tracking tools on the website, the guest pages or the apps.
2. Our role: shops and guests
Dingly has two kinds of users, and our role is different for each:
- Shop owners and their staff. When you create a Dingly account for your business, we decide how your account data is used. For this data we are the controller.
- Guests of a shop. When you track an order, join a stamp card, leave feedback or share your email at a café that uses Dingly, we collect that data on behalf of that shop. The shop is the controller and decides how it uses its guest list (for example, which offers to email). Dingly is the shop’s processor: we store and process the data to run the service for the shop and do not use it for our own marketing. Each shop’s guest list is kept separate and is not shared with other shops.
If you are a guest and want to know what a shop does with your data, ask that shop first. You can also contact us and we will help or pass your request on.
3. Data about shop owners and staff
Account and sign-in
- Email address, password (stored only as a one-way hash, never in readable form) and role (owner, manager or cashier).
- Team invitations: the email address you invite.
- Counter-tablet cashier logins: a label you choose (such as “Front counter”) and a 6-digit code, stored only as a hash. These logins have no email address.
- One-time links for password reset (valid 30 minutes) and email change (valid 24 hours). We store only a hash of each link.
Your shop
- Shop and branch names, branch addresses, and the map coordinates we look up from those addresses with Google Maps.
- Menus, prices, allergen and diet tags, photos, logo, cover image, colours, social links, your Google review link, the guest Wi‑Fi name and password (the password is stored encrypted), loyalty settings and message texts for automations and campaigns.
- If you use AI menu import, the menu photo or text you submit is sent to our AI provider to turn it into menu items (see section 8).
Activity in the desk
- Orders created from your desk or your Odoo Point of Sale: the order number shown to guests, its status and times. The Odoo module sends only the order’s ID, number, counter and status, not customer details.
- Which staff account added or removed a stamp or redeemed a reward, so the shop has a history of changes.
Subscription and payment
- Your plan, its dates and status, and payment records (amount, status and the Paymob transaction reference).
- Payments are made on Paymob’s checkout page. We send Paymob your shop name and account email. You enter your card details with Paymob directly; we never see or store your card number.
4. Data about guests
Guests can use most of Dingly without giving any personal details. Here is what is collected, and only when you use that feature:
Tracking an order
- To follow an order you type the number on your receipt. We hold the order number, its status and times as sent by the shop. We do not need your name for this.
- If you allow browser notifications for your order, your browser gives us a push address from its push service (for example Apple, Google, Mozilla or Microsoft). We store it only until the alert for that order has been delivered, then delete it. The push itself carries no content; your browser asks us what is ready.
- In the Dingly app, if you tap “Notify me when it’s ready”, your phone gives us a push token from Apple (APNs) or Google (Firebase Cloud Messaging), plus your app language so the alert is in your language. We link the token only to that order, store it only until the alert has been delivered, then delete it (a token for an order that never finishes is deleted after 24 hours). The alert shows the shop name, your order number and the branch, and opens the order when tapped.
Stamp card
- Your mobile phone number, which is how the shop recognises your card.
- Your stamps, visits, last visit date, stamp history, rewards and reward codes, and a random card code shown as the QR code on your card.
- Whether you ticked the box to receive offers from that shop. If you did, the shop may send offers as notifications on your wallet card. To stop them, use the unsubscribe link in any offer email, ask the shop, or remove the card from your wallet.
Apple Wallet and Google Wallet
- The card in your wallet shows the shop’s name and design, your stamp count, any reward ready to collect, your current order number and the card’s QR code. It does not show your name or phone number.
- If you add the card to Apple Wallet, your device registers with our server so the card can update itself. We store a device identifier and push token issued by Apple for that card, and use them only to update it.
- If you add the card to Google Wallet, Google stores the card content listed above and we keep the card’s ID so we can update it.
- Some shops add a “nearby” message. Your phone’s wallet app shows it when you are close to one of the shop’s branches, using the branch locations stored in the card. This happens on your phone; Dingly does not receive your location.
Profile and email offers (optional)
- You can add your name, email address and birthday to your card.
- A shop only emails you offers (welcome, birthday, “we miss you”, review requests and campaigns) after you tick the box and confirm through the link we email you. We keep a record of each request, confirmation and unsubscribe, with the time, IP address and browser type, as proof of consent.
- Every offer email has an unsubscribe link. Unsubscribing takes effect at once.
Feedback and ratings
- Feedback: your star rating and comment. Your name, phone or email are kept only if you give a low rating and ask the shop to contact you, at shops that offer this.
- Dish ratings: your stars and optional comment, linked to a random code stored in your browser so you can change your own rating.
Wi‑Fi
- Some shops ask for your name, email or phone before showing the Wi‑Fi password. These details are kept only if you tick the box agreeing to share them with the shop. Joining the Wi‑Fi never signs you up for email offers.
5. The Dingly app and App Clip
- Staff use the app to run the desk and manage the shop. It handles the same data as the website (section 3) and keeps you signed in with the same session cookie.
- Guests use the app or the App Clip to follow orders and keep stamp cards. They handle the same data as the guest pages (section 4). Card codes are saved on your device so your cards open with one tap.
- Camera: used only to scan QR codes (shop tags and guest cards). Scanning happens on your device; we do not store or receive camera images.
- Photos: used only when you choose a picture for a menu item, logo or cover. Only the picture you pick is uploaded.
- Notifications: the app asks permission only when you tap “Notify me when it’s ready” or turn on an alert in Account → Notifications, never at launch. Guest order alerts are described in section 4. Shop owners and managers can opt in to alerts for low ratings or contact requests and for orders waiting too long. For these we store the phone’s push token (from Apple APNs or Google Firebase Cloud Messaging), the app language and your choices, linked to your account and shop, until you turn the alerts off, sign out, or delete your account (or until Apple or Google tells us the token no longer works). Staff alerts never include the guest’s comment or contact details. Push tokens are used only to deliver these alerts, never for advertising or tracking.
- Live Activities (iPhone Lock Screen order tracking) run on your device. The App Clip checks your order’s status with our server; no Live Activity push token is sent to us.
- The app and App Clip do not ask for your location, contain no advertising, no third-party analytics and no tracking across other companies’ apps or websites.
6. Server logs and security data
Like any website, our servers record technical details of each request: IP address, time, the address requested and the browser or app type. We use them to keep the service secure (for example, limiting repeated sign-in attempts) and to fix problems. Logs are rotated automatically and are not used to profile anyone.
7. Why we use data, and our legal bases
We use personal data only for the purposes below. Where data protection law asks for a legal basis, including Egypt’s Personal Data Protection Law (Law No. 151 of 2020) and, for visitors from the European Union, the GDPR, these are the bases we rely on:
| Purpose | Legal basis |
|---|---|
| Running shop accounts, the desk, guest pages, order alerts, stamp cards and wallet cards | Performance of our contract with the shop. For guest data, the shop’s instructions as controller. |
| Account emails: sign-in links, password and email changes, team invitations | Performance of contract; our legitimate interest in keeping accounts secure. |
| Marketing emails and wallet offers from a shop to its guests | The guest’s consent, which can be withdrawn at any time. |
| Collecting subscription payments and keeping payment records | Performance of contract; legal obligations such as accounting and tax rules. |
| Security, abuse prevention, backups and fixing problems | Our legitimate interest in a safe, working service. |
| Answering support requests | Our legitimate interest in helping you, or performance of contract. |
We do not use automated decision-making that has legal or similarly significant effects on anyone.
8. Service providers we use
We run Dingly on our own server and share data only with the providers needed to deliver the features below. Each receives only what it needs for its task.
| Provider | What it does | Data involved |
|---|---|---|
| Our hosting provider | Rents us the virtual private server (VPS) where Dingly, its database and its backups run | All data described in this policy, stored on that server |
| Cloudflare | Delivers our emails (Cloudflare Email Sending) and provides our domain’s DNS | Recipient email address and the email’s content |
| Apple | Apple Wallet card updates and Dingly app notifications on iPhone (via Apple Push Notification service), the App Clip, the App Store, Safari web push | Wallet and app push tokens, card content, an empty “something changed” signal, the text of app alerts (shop name, order number, branch) |
| Google Wallet cards, map coordinates for shop addresses (Google Maps), Chrome web push, Dingly app notifications on Android (Firebase Cloud Messaging) | Wallet card content, shop branch addresses, an empty push signal, app push tokens and the text of app alerts (shop name, order number, branch) | |
| Paymob | Subscription payments on dingly.win | Shop name, account email, amount; card details you enter on Paymob’s page |
| Anthropic | AI menu import, only when a shop uses it | The menu photo or text the shop submits |
| Mozilla, Microsoft | Web push in Firefox and Edge, only if a guest uses those browsers and allows alerts | An empty push signal |
Each provider handles data under its own terms and privacy policy. We may also disclose data if the law requires it, to protect people’s safety or our rights, or as part of a sale or reorganisation of the business (in which case this policy would continue to apply to your data).
9. Cookies and on-device storage
We use only the cookies and storage needed for Dingly to work. There are no advertising or analytics cookies, so we do not show a cookie banner.
| Name | Purpose | Lasts |
|---|---|---|
pager_session (cookie) | Keeps shop staff signed in. Signed by our server and not readable by page scripts. | 30 days, or until you sign out |
pager_wifi_… (cookie) | Remembers that you already filled in a shop’s Wi‑Fi form | 30 days |
| Browser / device storage | Your language choice, your saved stamp card codes, a random code for your dish ratings, puzzle progress, and the order you are tracking | Until you clear it |
10. How long we keep data
- Shop accounts are kept while the account is open. When you delete your account, your sign-in is removed at once (see section 11). A shop you own is closed at once and its data, including its guest list, is erased within 30 days.
- Guest data is kept for the shop while it uses Dingly, until the shop deletes that guest, or until the shop’s account is deleted. When a guest is deleted, their name, phone, email, birthday and wallet links are erased and their card stops working. Stamp and order counts are kept without anything that identifies the person, so the shop’s totals stay correct.
- Order alert push addresses (browser) and app push tokens for orders are deleted as soon as the “ready” alert is delivered, or after 24 hours for an app token whose order never finishes.
- Staff app push tokens are kept until you turn the alerts off, sign out of the app or delete your account, or until Apple or Google reports the token is no longer valid.
- Consent records are kept as proof of consent while the guest record exists. When a guest is deleted, the IP address and browser type in those records are erased.
- Payment records are kept for as long as accounting and tax law requires.
- Backups are taken nightly and kept for 14 days, then deleted. Erased data disappears from backups within that time.
- Server logs are rotated automatically and kept only for a short period.
11. Your choices and rights
Depending on where you live, you may have the right to access, correct, delete or receive a copy of your personal data, to object to or restrict some uses, and to withdraw consent at any time. Here is how to do that in practice.
Shop owners and staff
- Delete your account in the app: Account → Delete account, then confirm with your password. Your email, password and every session are removed immediately and you are signed out everywhere. If you own a shop, it is closed straight away and its data is erased within 30 days. Some activity records (such as “this staff account added a stamp”) stay attached to an anonymous placeholder rather than to you.
- You can also ask us to delete your account by emailing hello@dingly.win from the account’s email address.
- Change your email or password any time under Account. For a copy of your account data, email us.
- Owners can export the full guest list as a CSV file from Customers before closing a shop.
Guests
- Stop offer emails: use the unsubscribe link in any email. It works immediately.
- Copy or delete your data: ask the shop. Shops can export everything held about a guest (profile, orders, stamps, rewards and consent history) and delete a guest from their Customers screen.
- If you cannot reach the shop, or prefer not to, email hello@dingly.win with the shop’s name and the phone number on your card. We will pass the request to the shop or, where appropriate, act on it ourselves.
- Removing a card from your wallet stops updates to that card. Clearing your browser or app data removes the card codes saved on your device.
We will answer requests within 30 days and may ask you to confirm your identity first. If you are unhappy with how we handle your data, you can complain to the data protection authority where you live; in Egypt this is the Personal Data Protection Center.
12. International transfers
Our server and some of our providers (such as Cloudflare, Apple, Google and Anthropic) may store or process data outside Egypt or outside the country you live in, including in the European Union and the United States. Where we transfer data across borders, we rely on the safeguards these providers offer and on the protections required by applicable law.
13. Security
We protect data with measures suited to a small service, including:
- HTTPS for all connections to dingly.win.
- Passwords and cashier codes stored only as one-way hashes; emailed links stored only as hashes and short-lived.
- Guest Wi‑Fi passwords stored encrypted.
- Every request checked against the signed-in account and its shop, so one shop cannot see another shop’s data.
- A firewalled server, key-only administrator access, automatic security updates and rate limits on sign-in and forms.
No system is completely secure. If a breach affects your personal data, we will notify you and the relevant authorities as the law requires.
14. Children
Dingly is not directed to children under 13, and we do not knowingly collect personal data from them. Shops should not enrol children under 13 in stamp cards or marketing. If you believe a child under 13 has given us personal data, email us and we will delete it.
15. Changes to this policy
We will update this policy when Dingly or the law changes. The date at the top shows the latest version. If we make significant changes, we will tell shop owners by email or in the app before they take effect.
16. Contact us
Email hello@dingly.win for any question about this policy or your data. See also our Terms of Service and Support page.