We use essential cookies to run DALAA. With your permission, we use analytics and an approved Meta Pixel pilot to measure business-page visits and booking creation; Meta also receives network information when contacted. Optional choices are off by default and can be withdrawn anytime. See our Cookie Policy and Privacy Policy .
DALAA

For customers, business partners, staff, and visitors

Privacy Policy

Last updated: 23 October 2026 — version 2.1 (contact number only)

Legal operator
Mehwar Al-Riyadah for Software and Digital Solutions Company, a limited liability company (trading as MEHWAR TECH); Companies Control Department, Jordan, registration no. 85032; national establishment no. 200216890; 49 Al-Furat St., Amman 11118, Jordan; +962 79 3232 111
Legal notice address
49 Al-Furat St., Amman 11118, Jordan
Privacy and legal notices
privacy@dalaa.app

DALAA is a platform owned and operated by Mehwar Al-Riyadah for Software and Digital Solutions Company, a limited liability company (trading as MEHWAR TECH) (the "Company"). The Company, not the brand, is the legal contracting party. Mehwar Al-Riyadah for Software and Digital Solutions Company, a limited liability company (trading as MEHWAR TECH), registered with the Companies Control Department, Jordan, registration no. 85032, national establishment no. 200216890. Registered office: Amman. Address: 49 Al-Furat St., Amman 11118, Jordan. Phone: +962 79 3232 111. Website: https://mehwartech.com. This policy explains processing under Jordan's Personal Data Protection Law No. 24 of 2023.

1. Who controls your data

Mehwar Al-Riyadah for Software and Digital Solutions Company, a limited liability company (trading as MEHWAR TECH), registered with the Companies Control Department, Jordan, registration no. 85032, national establishment no. 200216890. Registered office: Amman. Address: 49 Al-Furat St., Amman 11118, Jordan. Phone: +962 79 3232 111. Website: https://mehwartech.com. The Company is the controller for accounts, the marketplace, Platform security, support, subscriptions, and its own analytics and communications. Processing is subject to Jordan's Personal Data Protection Law No. 24 of 2023, without removing mandatory protections under other applicable law.

Partners are independent controllers of the customer, staff, payroll, consultation, treatment and clinical records they use for their own operations. They must comply with Jordan's Personal Data Protection Law No. 24 of 2023, obtain the consents required for those purposes and obtain separate explicit consent for health or clinical data.

For partner-controlled records, the Company acts as a processor on the Partner's documented lawful instructions, for the agreed purposes and duration only. It requires confidentiality, applies appropriate technical and organisational security, and uses sub-processors under corresponding data-protection obligations.

The Company will notify the Partner of a personal-data breach affecting its records without undue delay, assist with lawful rights and notification requests, and return or delete partner-controlled data when the service ends, subject to mandatory retention and legal holds. The Partner remains responsible for its controller obligations; this clause does not authorise collection of health data without consent.

2. Information we process

Account and identity data: name, email, phone number, profile image, language, account role, authentication identifiers, sign-in events, security settings, and optional birthday or gender information when provided for supported features.

Customer and booking data: selected business, branch, service, professional, beneficiary details, appointment times, status, waitlists, cancellations, no-shows, notes, reviews, favorites, loyalty activity, memberships, packages, gift cards, and customer-service history.

Business and staff data: business and branch profiles, addresses, services, prices, availability, rooms and resources, photos, staff identities, roles, permissions, schedules, leave, time entries, commissions, payroll calculations, contracts, expenses, inventory, suppliers, invoices, and operational reports.

Payment and subscription records: cash or manual bank-transfer status, transfer references and uploaded proof, deposits, receipts, invoices, refunds, tills, settlement and reconciliation records, plan tier, trial status, and Assisted Setup orders. DALAA does not currently process live card payments and does not ask for card numbers or security codes.

Messages, translations, and communications: booking messages, customer and partner support correspondence, WhatsApp or other enabled channel messages, delivery status, language variants, translations, notification preferences, and human-handoff history.

Uploads and documents: business images, payment proofs, contracts, forms, consultation documents, consent evidence, clinical media where enabled, and files sent to support. Do not upload information that is unnecessary for the stated purpose.

Calendar data: if an authorized user connects Google Calendar, DALAA receives OAuth identifiers and the minimum calendar event and availability data needed to create supported booking events, detect busy times, maintain sync, and troubleshoot failures.

Location and technical data: selected city, approximate or precise location when permission is granted, IP address, device and browser details, app version, language, time zone, identifiers, security events, logs, and feature usage.

3. Clinical and health-related information

Some specialized-care partners may enable optional clinical tools for consultations, consent, treatment notes, media, allergies, contraindications, or related records. This information may be sensitive or legally protected. It is collected by or for the relevant partner and is visible only to authorized roles under the partner’s configured access rules.

Partners must obtain required consent, limit access to qualified personnel, maintain accurate records, and satisfy applicable professional, retention, and health-data obligations. DALAA provides software tools and does not make medical decisions, diagnose conditions, prescribe treatment, or guarantee outcomes.

DALAA does not use clinical notes or clinical media for advertising. We do not use them to train general-purpose AI models unless a separate, lawful and explicit arrangement says otherwise.

Health and clinical data require separate explicit consent for the specified purpose. Account assent or international-transfer consent is not consent to health-data processing.

4. Why we use information

We process information to create and secure accounts; provide search, profiles, booking, waitlists and calendars; run partner operations; support loyalty and memberships; record manual payments; deliver notifications and messages; provide support; prevent fraud and abuse; enforce agreements; maintain reliability; meet legal obligations; and establish, exercise, or defend legal claims.

Prior explicit, documented consent is our main basis for processing. We process without it only where Jordanian law permits, such as a legal obligation, court order or protection of vital interests where allowed. We do not treat legitimate interests or a request for a service as a general independent exception to Jordanian consent requirements.

We use data needed to provide the service you request under consent or another basis permitted by law. Marketing, cookies, device and location permissions, calendar access, clinical data and international transfers remain separate choices; terms acceptance or privacy acknowledgement does not replace any of them.

Withdraw consent using available account controls or privacy@dalaa.app. Withdrawal does not invalidate earlier lawful processing; subsequent processing requires a valid legal basis and retention limits. Exercising your rights does not impose financial or contractual consequences prohibited by law.

We may use aggregated or de-identified information to understand product performance, capacity, and market activity. We do not present de-identified information as an identifiable person’s record.

5. AI-assisted features and translation

DALAA may use AI-assisted tools for structured business insights, message suggestions, receptionist workflows, rebooking support, categorization, summaries, and translation. These features can be incomplete or incorrect and should be reviewed by an authorized person before important action is taken.

We limit data sent to AI services to what is reasonably needed for the feature and apply access controls and provider terms. Partners must not use AI features to make unlawful employment, medical, credit, or other high-impact decisions. AI output is not medical, legal, financial, employment, or professional advice.

Ask DALAA may interpret your search or booking request and suggest server-verified choices. A suggestion is not a confirmed booking or account change: supported customer actions require your explicit confirmation. Owner insights use aggregate operational information; they are not authority to execute business changes or access clinical records.

Automated messaging may hand a conversation to human staff. Translations may not preserve every nuance, so users should confirm critical booking, safety, consent, payment, and clinical details directly.

6. Sharing and service providers

We share relevant booking and account information with the business, branch, and authorized staff involved in your booking or request. Businesses may share internal operational data with their authorized owners, managers, accountants, practitioners, and staff according to role permissions.

Providers receive data needed for their enabled function: Clerk receives identity and authentication data for sign-in; Replit and cloud infrastructure providers host application data; PostgreSQL/Neon infrastructure stores records; Google Cloud-backed object storage stores uploaded files; Resend receives email addresses and email content; Twilio receives phone numbers and SMS content where SMS is enabled; Expo and device push services receive push tokens and notification content; Google Maps receives map and location queries; Google Calendar receives authorized calendar and booking-event data; Meta/WhatsApp Business receives recipient details and messages where enabled; managed OpenAI-compatible services receive the limited inputs needed for AI or translation; and Cloudflare processes request and technical data for routing, delivery, and security. Providers may change as the Platform evolves.

We may disclose information to professional advisers, auditors, insurers, regulators, courts, law enforcement, or a buyer or successor in a corporate transaction where lawful and necessary. We do not sell personal data or disclose it for third-party targeted advertising.

7. Google Calendar connection

Calendar connection is optional and tied to the authorizing user. DALAA uses authorized access to create or update supported booking events and treat Google busy times as availability blocks. DALAA remains the source of truth for bookings.

DALAA stores OAuth access and refresh credentials for the authorized connection, with encryption and restricted access, to maintain that connection. Calendar access is used for the disclosed calendar functionality, not advertising or general-purpose AI training. DALAA’s use and transfer of information received from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements.

You can disconnect Google Calendar from DALAA or revoke access in your Google account. Disconnection stops future sync but may not remove events already copied to your calendar. Google processes information under its own terms and privacy policy.

8. Cookies and analytics

Cookie consent, messaging consent, device permissions, and clinical consent are separate choices.

We use essential cookies and local storage for sign-in, security, language, preferences, and session continuity. We may use first-party or service analytics to measure visits, page performance, conversions, feature use, and errors.

Optional web analytics and marketing storage are controlled through Cookie Settings; you may accept, reject, or later change those choices. Cookie consent does not grant marketing-message consent, device permissions, calendar access, or clinical consent; these are separate choices. An approved business-specific Meta Pixel pilot may measure business-page visits and successful booking creation only after you approve both analytics and marketing cookies. Meta receives a minimized event, a booking event identifier where applicable, and network information inherent to contacting its servers, such as your IP address and browser headers. The browser integration does not share names, contact details, services, prices, or private page URLs, and automatic event collection and advanced matching are disabled. Meta processes information under its own privacy policy. Rejecting or withdrawing either cookie category stops future browser measurement; it does not delete information previously received by Meta. DALAA first-party reporting remains authoritative.

9. Security

We use measures designed to protect information, including encrypted transport, managed authentication, access controls, role permissions, audit records, private file access, environment-managed credentials, backups, and monitoring. Sensitive clinical and payment-proof access is restricted by purpose and role.

No system is completely secure. Keep credentials confidential, use current devices, grant staff only the access they need, and contact support promptly if you suspect unauthorized access. Do not send passwords, authentication tokens, or full financial credentials by email or chat.

Where a data breach could cause serious harm, we notify affected people within 24 hours of discovery and notify the competent authority within the period and in the manner required by law. We notify the Partner controlling affected records without undue delay.

10. Retention

We retain information for as long as needed to operate the Platform, maintain accounts and entitlements, complete subscriptions and support, preserve business and booking history, meet tax, accounting, employment, health-record and legal obligations, resolve disputes, and protect the Platform.

Retention depends on the record type, relationship, market, partner instructions, legal holds, and applicable limitation periods. Signed clinical records, consent evidence, payroll records, invoices, and audit trails may need to be retained after an account closes. When retention is no longer required, information is deleted, anonymized, or securely isolated.

11. Access, correction, export, and deletion

You may request awareness of and access to your data, correction, deletion or concealment, restriction, objection, withdrawal of consent, and a copy or transfer of your data as the law provides. Use account controls or privacy@dalaa.app; proportionate identity verification may be needed.

You may complain to Jordan's Personal Data Protection Council through the Ministry of Digital Economy and Entrepreneurship's official channels. We encourage contacting our DPO first, without making that a condition on your right to complain.

Account deletion does not automatically erase records that a partner independently controls or information DALAA or a partner must retain by law, for financial integrity, safety, fraud prevention, consent evidence, disputes, or legal holds. Where appropriate, identifying information may be anonymized while transaction or booking records are retained.

For payment proofs, invoices, subscription charges, or refunds, contact payments@dalaa.app. For records held by a specific business, contact that business as well.

12. Cross-border processing

Data is processed outside Jordan for authentication, hosting, storage, email, notifications, maps, calendar and enabled optional features. Laws and government access may differ, and some recipients may not provide protection equivalent to Jordan's. We assess recipient protection and apply required safeguards; consent does not waive other legal obligations.

Providers' published disclosures include United States processing for Clerk, Replit, Resend, Expo and OpenAI-compatible services; US, European and other cloud regions depending on Neon, Google Cloud, storage, Google Maps and Google Calendar configuration; US, Ireland and Australia where Twilio regions are enabled; US and international processing centres for Meta/WhatsApp; and Cloudflare's global network, including the US, Europe and Asia-Pacific. These are provider-declared processing scopes, not a promise that all data resides in one country; actual destinations depend on the service, configuration and sub-processors.

These disclosures cover the providers in the sharing section and only their enabled functions. Request current destination and sub-processor details from privacy@dalaa.app. We request and record separate explicit consent, tied to this privacy version, at customer or partner registration completion and staff invitation acceptance. Transfers use that consent or another basis permitted by law; contact the DPO to withdraw it.

13. Children

Accounts for under-18s are not allowed. A minor's data is processed for a booking or service only through a parent or legal guardian with their consent and only as necessary. Additional health or service consent remains separate.

14. Changes and contact

We may update this policy as the Platform or law changes, communicate material changes, and request renewed acknowledgement or consent where needed. Earlier versions remain available for records; signing in alone is not assent to a new version.

Data protection officer: Salman Al Assaf (General Manager), privacy@dalaa.app. Mehwar Al-Riyadah for Software and Digital Solutions Company, a limited liability company (trading as MEHWAR TECH), registered with the Companies Control Department, Jordan, registration no. 85032, national establishment no. 200216890. Registered office: Amman. Address: 49 Al-Furat St., Amman 11118, Jordan. Phone: +962 79 3232 111. Website: https://mehwartech.com.

These terms are between the Company identified in the legal notice and you. They are governed by the laws of the Hashemite Kingdom of Jordan. The competent courts of Amman, Jordan have jurisdiction, subject to any non-waivable consumer right or mandatory rule requiring otherwise.

The Arabic version prevails if these Arabic and English texts conflict. The registered Arabic legal name prevails over its English translation.

Electronic acceptance and records

Electronic acceptance of the Company's terms is given through an affirmative checkbox and click when completing account registration, booking or the relevant action. Electronic records and messages are valid and binding under the Jordanian Electronic Transactions Law to the extent permitted by law. A visit, sign-in or preselected checkbox is not recorded as acceptance.

Acknowledging the privacy policy is not blanket consent to processing. International-transfer consent and other consent-based purposes are recorded separately.

Data protection officer

Data protection officer: Salman Al Assaf (General Manager). For privacy, data-protection and rights requests, contact privacy@dalaa.app.