This page explains what Hala Law (hala-law.com) handles, why, for how long, and how to exercise your rights under the Saudi Personal Data Protection Law (PDPL).

Who is the data controller?

Hala Law is operated by Faisal Abdulaziz, based in Riyadh, Saudi Arabia, who is the data controller for the personal data described here. The dedicated privacy channel is privacy@hala-law.com.

The controller's legal name and contact details are published above, as Article 4 of the PDPL Implementing Regulations requires at collection. Google sign-in and the five public-source legal AI tools are available; newsletter/lawyer-contact forms, deadline reminders, and both optional Waratha hosted routes remain disabled pending their separate release steps. Manual calculators and reviewed public legal-information pages remain available without signing in or using a hosted model.

What is processed

  • Manual calculator inputs — including salary, dates, estate value, and heir counts — stay in your browser unless you deliberately choose an optional hosted step described below. Public share links contain no input, result, query string, or fragment. A result image leaves the device only when you explicitly choose to share that image.
  • Newsletter or lawyer-contact request (currently disabled): email address, request type, page/tool of origin, interface language, consent record, confirmation status, and creation time. No name, phone number, free text, calculator input, or result is accepted by that endpoint. Newsletter and lawyer-contact consent are separate and unticked.
  • Deadline reminder (currently disabled): email address, objection type, deadline date, chosen reminder date, interface language, delivery/confirmation status, and creation/sent times. No party name, document, or case narrative is collected. The reminder has its own unticked consent and privacy link.
  • Optional Waratha hosted steps (currently disabled): if separately approved and re-enabled, the text parser would send a description only after server-validated, versioned consent. The server masks IDs, phones, emails, Saudi IBANs, and recognizable numeric currency or estate amounts before a DeepSeek call; automated masking cannot guarantee detection of names or amounts written in words, so users are instructed not to enter either. A separate explanation choice would send only the deceased's sex plus heir types and counts to Hala Law for deterministic recomputation, then only heir enums and exact fractions to DeepSeek for row ordering. Manual calculation and deterministic explanation remain local.
  • Waratha operational metadata: tool, interface language, and success/block/error outcome; never the description, heir composition, or model output. A separate aggregate Riyadh-day counter stores the date, reserved-call count, configured ceiling, and update time, with no input or user identifier.
  • Account (Google sign-in): Supabase in Frankfurt stores the Google-returned account profile and session tokens for authentication. The profile can include the account identifier, email address, display name, and avatar supplied by Google.
  • Legal AI tool usage: after sign-in, five tools send only selected public-source unit identifiers and their reviewed public text to DeepSeek for ordering. Hala Law records only the tool, language, route outcome, account identifier, and time, with durable per-user limits; it does not send the account profile or identifier to DeepSeek.
  • Temporary abuse prevention: public AI and email-write routes use request timestamps keyed by client IP in volatile server memory for a ten-minute window. The application does not write that IP to lead, reminder, AI-audit, or quota tables. Hosting/network security logs are controlled separately by those providers under their own retention terms.
  • Direct email: if you write to a Hala Law address, the sender address and message content are processed to answer that correspondence. Do not send case documents or sensitive facts unless a secure, appropriate channel has been agreed.

Analytics

Hala Law uses Google Analytics 4 from Google LLC to measure and improve how the site is used, on an explicit-consent, default-denied basis: no tag loads and no cookie is set before you agree through the consent bar, and a decline loads nothing and is remembered so you are not asked again.

  • What is sent after consent? Page views and generic event names only, such as "calculator started", with IP anonymization. Calculator inputs, results, and any category derived from them are never sent in any case.
  • Identifiers: only after consent, Google Analytics sets cookies carrying a random measurement identifier that does not include your name or email.
  • Purpose: aggregated usage statistics to improve content and tools, with no advertising profiles.
  • Retention: Google retains user-level event data for two months and then deletes it automatically; aggregated statistics remain without individual identifiers.
  • Transfer outside Saudi Arabia: Google processes analytics data outside the Kingdom under its policy linked in the sources list; this transfer does not occur before your explicit consent.
  • Withdrawing consent: the "Analytics settings" link at the bottom of any page lets you change your choice at any time, and a decline stops any further collection from your device.

Processors and transfers outside Saudi Arabia

When the optional email features are legally released, lead and reminder records will be stored with Supabase in Frankfurt, Germany, and the configured email-delivery provider will receive the email address and message needed for delivery. Those are transfers outside Saudi Arabia. They will not be re-enabled until the applicable Article 29 transfer basis, safeguards, processor details, and this policy have been reviewed; consent alone is not presented here as a complete transfer assessment.

Account data is stored with Supabase in Frankfurt, Germany — a transfer outside Saudi Arabia — for authentication only. Google provides sign-in and acts as the identity provider under its own privacy policy. The five legal AI tools send only reviewed public-source units—not account data—to DeepSeek outside Saudi Arabia for ordering.

If the optional Waratha routes are later re-enabled, a scrubbed parser description or the explainer's heir enums and exact fractions will be processed by DeepSeek outside Saudi Arabia. DeepSeek's handling — including its statements about service improvement and storage location — is governed by its linked privacy policy. Hala Law does not use descriptions to train its own model and does not promise that a third party will never use submitted data. Manual entry and local explanation avoid that transfer.

Retention and destruction

  • Unconfirmed newsletter, lawyer-contact, and reminder rows are deleted after 7 days.
  • A confirmed newsletter row is retained until unsubscribe, consent withdrawal, or a valid deletion request.
  • Lawyer-contact rows are deleted no later than 90 days after creation, or earlier on cancellation/deletion.
  • Reminder rows are deleted when cancelled, after the reminder is marked sent, or when the deadline expires. A sent marker prevents duplicate delivery if immediate deletion temporarily fails; the next retention run removes it.
  • Hala Law does not retain the Waratha description or model response in its database. The provider's retention is governed by its policy.
  • Your account profile and legal AI usage rows are retained until you request account deletion at privacy@hala-law.com; deleting your account also removes the account identifier from any retained usage rows.
  • The in-memory IP rate-limit key is used only for the ten-minute window and is swept after expiry on subsequent limiter activity or disappears when the server instance ends.
  • Direct correspondence is retained only while needed to answer and document the request, then deleted unless a legal obligation requires longer retention.

The daily retention job and the write endpoints fail closed if the required deletion rules cannot run. Newsletter/lawyer collection also remains code-disabled pending an opaque, revocable confirmation-token migration; the legacy reversible email token is not accepted as a production release state.

Your rights under the PDPL

RightWhat it meansHow to exercise it
Information/accessKnow what we process and access itprivacy@hala-law.com
CopyReceive an intelligible copy where applicableprivacy@hala-law.com
CorrectionCorrect inaccurate or incomplete dataprivacy@hala-law.com
DestructionRequest destruction where the purpose has endedprivacy@hala-law.com
Consent withdrawalStop any processing based on your consentUnsubscribe link or email

Under Article 3 of the Implementing Regulations, rights requests are handled without delay and within 30 days. An extension of up to 30 additional days is available only for the stated exceptional workload circumstances, with advance notice and reasons.

Every newsletter email will include an unsubscribe link. Unsubscribing deletes that lead row, stops future newsletter messages, and does not affect the rest of the site. Lawyer-contact cancellation deletes that request; reminder cancellation deletes the reminder row. The email features remain disabled until the privacy gates described above are complete.

Governing language and updates

In the event of any conflict between the Arabic and English versions of this policy, the Arabic version prevails. Any change to this policy is announced on this page with the date of the change in the visible change log, and prior versions remain documented there.