Privacy Policy

This Privacy Policy explains what personal data Dawr App collects, why, where it is stored, how long it is kept, who it is shared with, and what rights you have under Egypt's Personal Data Protection Law 151/2020 — whether you hold an account or are a client of an organization using the service. This notice is given under that Law at the point of collection.

1. Who this policy covers, and who is responsible for your data. Dawr App ("we") provides appointment scheduling and queue-management software used by clinics and service businesses ("Organizations") for their own customers ("Clients"). Two roles apply:

   You are…	Controller of your data
   Organization staff with a login (owner, receptionist, staff)	We are controller of your account data (login, sessions, audit logs).
   A Client of an Organization (e.g. a patient with an appointment)	The Organization is controller — it decided to put your name and phone number in the system. We act as processor on its instructions.

   Clients: contact your Organization first about your data — it is responsible for why it was collected. If you cannot reach it, contact dawr@example.com and we will assist.

   Your track link shows your appointment details to anyone holding it — share it carefully. Each link is protected by a long, randomly generated token that cannot be guessed. A link stops working 7 days after your appointment ends.

2. Data we collect. We collect only what is necessary.

   2.1 Clients (booked into an Organization's queue):

   Data	Why	Required?
   Name	Identify you in the queue and records	Yes
   Phone number	Appointment and status notifications	Yes
   Email address	Extra contact channel	No
   Preferred language	Notifications in your language	No
   Appointment details (date, time, status, branch, department, queue position)	The scheduling service itself	Yes
   Telegram user ID	Updates via Telegram	No — opt-in only
   Browser push subscription (your browser vendor relays each message's title and text when notifying you)	Notify you if you close the track tab	No — opt-in only
   Messages sent to you (e.g. "your turn is starting")	Your in-page inbox history	Automatic with the above

   We do not collect payment details, national ID numbers, or health records. Organizations must not enter health or other sensitive data (see Terms §7).

   2.2 Organization staff (logins):

   Data	Why
   Name, email, phone, password credential (never stored recoverably)	Account login
   Session records (login times, IP, device/browser info)	Security, suspicious-login detection, session management
   Audit entries (actions taken, time, IP, device)	Security, accountability, dispute resolution
   Payment records for paid plans (bill amount, payer name, payment reference and method — InstaPay, cash, or bank transfer — plus receipt image; card numbers are never collected)	Verify plan purchases (paid plans only)

3. Purposes and lawful basis. Account administration and login; running queues, appointments, track links, and notifications; email verification and security (fraud prevention, session integrity, troubleshooting). Lawful basis: your explicit consent and, for clinic operations, performance of the service contract with your Organization (Law 151/2020 Art. 6).
4. Use limits.Data is used strictly for the purposes above. Transactional messages only (verification, queue/appointment updates) — no direct marketing without separate explicit consent. No sale of personal data. No solely automated decisions with legal or similarly significant effects. Medical-type Organizations are responsible for obtaining proper client consent for their clients' presence in the system.
5. Recipients. Your Organization (its own Client data, managed directly); database/hosting infrastructure; email delivery; messaging providers (only data needed for a message you triggered, only where enabled); authorities where required by law. Never sold; never shared across Organizations. Details next.
6. Cookies and local data.Staff login uses strictly necessary HttpOnly session cookies plus a forgery-protection token — no consent banner applies to these, as they are not trackers. The public track page needs no login and sets no advertising or analytics cookies; an opted-in push subscription lives locally in the visitor's browser. Interface preferences (language, theme) are stored locally. No third-party ad trackers anywhere.
7. Where data lives (cross-border).Database in London, UK (Neon/AWS); application servers in Frankfurt, EU (Render); verification emails sent from the US (Resend); traffic secured and distributed via Cloudflare's global network. The UK and EU maintain data-protection regimes we rely on for adequate protection. By accepting this policy you explicitly consent to these transfers. We will seek the Center's transfer permit and record its reference here once issued.
8. Retention. Account and Organization data while active, deleted on verified request (organizations enter a 30-day reversible hold, then are permanently erased); inbox messages and push subscriptions auto-deleted after 90 days of inactivity (sooner if invalid); server logs, delivery records, and audit rows auto-deleted after 90 days; payment receipts purged 90 days after a request is rejected or the linked subscription ends; backups age out on their cycle. After purpose ends, retained data is anonymized.
9. Your rights (Law 151/2020). Access or obtain your data; correct, complete, or erase it; restrict processing to a stated purpose; withdraw consent; object to processing; be told of any breach affecting you. Write to dawr@example.com — we reply within 6 working days. Withdrawal stops future processing but may end account use. Complain to the Personal Data Protection Center and the courts. For Client data, contact your Organization first (see §1).
10. Security. Appropriate technical and organizational measures: encrypted connections and storage, protected credentials, least-privilege internal access, role limits on who inside an Organization sees Client data, security-event logging, and vetted sub-processors. No system is perfectly secure; we work to prevent breach, destruction, alteration, or unlawful access.
11. Children.Not directed at children. Organizations must hold a guardian's consent before entering any minor's data, and enter no more than necessary.
12. Breach notification. On learning of a personal-data breach we notify the Center within 72 hours and affected subjects within 3 working days at the account email, describing what happened, the data concerned, and remedial steps.
13. Changes and questions. Updates post here with a new version and date; material changes get reasonable advance notice. dawr@example.com.