Halaal

Trust Center/Halaal Inc LTD

Cookie Policy

We use strictly necessary cookies to keep your workspace secure, plus a few first-party functional cookies that are written only when you take an action (such as signing in or submitting a form). We do not use advertising or analytics cookies on public profiles, forms, or signage displays.

Version 1.5 · Last updated 13 October 2026Effective 13 October 2026
01

Overview

This policy applies to the entire Workspace ecosystem, including but not limited to:

account.halaalos.comworkspace.halaalos.comforms.halaalos.comlink.halaalos.comhalaal.linkurl.halaalos.comhala.alslides.halaalos.com

Everything we store falls into two buckets: strictly necessary cookies (for authentication, security, and keeping a signage screen working offline), and a few first-party functional cookies that are written only in direct response to an action you take — for example remembering your last-used workspace after you sign in, or noting that you have already submitted a form. These exist solely to make the feature you asked for work; none of them track you across sites, and we run no advertising or analytics cookies — our usage statistics are cookieless by design: we count visits to a page, never the people making them. When you open a link someone shared with you, which share it was travels in the link itself and is read by that page only — nothing about it is stored on your device, and closing the tab forgets it. Because we set no advertising, analytics, or cross-site tracking cookies, we do not show a cookie-consent banner. If we ever introduce genuinely optional or tracking cookies, we will ask for your opt-in consent first and make refusing them as easy as accepting. You can review or clear any of the above at any time via your browser (see Managing Cookies). For how we handle personal data more broadly, see our Privacy Policy.

02

What are Cookies?

Cookies are small text files that a website stores on your device to remember information between visits. In this policy, we use the term “cookies” to refer to both traditional cookies and modern browser storage (like LocalStorage). We use them strictly for utility (like keeping you logged into your dashboard), not for surveillance.

03

Cookie Categories

We use the minimum amount of storage required to run our platform securely.

🔐
Strictly Necessary

Authentication & Session

Essential for keeping you signed in. Without these, you would be logged out on every page refresh.

🛡️
Strictly Necessary

Security & Anti-Abuse

Used to detect bots (via Cloudflare Turnstile), prevent spam on forms, and enforce rate limits to protect our servers.

⚙️
Functional

Preferences

Stores local choices like 'Dark Mode' or your last active workspace. These do not track you across the web.

🚫
We do NOT use

Zero Tracking

We do not use third-party advertising cookies, behavioral profiling, or cross-site analytics pixels.

Cookie / tokenProviderPurposeRetention
sb-<ref>-auth-token
(First-party cookie · strictly necessary)
SupabaseKeeps you signed in. Set via @supabase/ssr — scoped to .halaalos.com (.halaal.app on our former addresses), SameSite=Lax, Secure.Session / until sign-out
__cf_bm
(Third-party cookie · strictly necessary)
CloudflareBot-management token that distinguishes automated traffic from real visitors.~30 minutes
cf_clearance / Turnstile
(Third-party cookie · strictly necessary)
CloudflareRecords that an anti-bot / security challenge (including Turnstile) was passed.Up to ~1 year
last_used_tenant_<userId>
(First-party cookie · functional)
HalaalWritten after you sign in, to route you back to your last-used workspace.30 days
form_submitted_<id>_<version>
(First-party cookie · functional)
HalaalWritten only after you submit a public form, to prevent duplicate submissions. Not used for tracking.1 year
halaal_buyer
(First-party cookie · functional)
HalaalWritten only after you confirm a shop order from the email we send, so your next order from this device does not need confirming again. It holds that one address, signed, and nothing else.6 months
theme / preferences
(Local Storage · functional)
HalaalRemembers local choices such as dark mode. Stored on your device; not used to track you.Persistent (local)
shop basket & recently viewed
(Local Storage · functional)
HalaalOn a shop, keeps your basket and the last few products you looked at on your device, so they are there when you come back. Never sent to us or to the shop.Until cleared / replaced
where this visit came from
(Session Storage · functional)
HalaalOn a public page (a shop, a form, an event, a bio), notes where the link you followed came from, such as “Instagram” or “a poster”, so an order, answer or sign-up made in the same tab can tell the organisation which of its links is working. It holds nothing that identifies you, and is never sent anywhere by itself.Until the tab is closed
signage offline cache
(Local Storage + service worker · strictly necessary)
HalaalOn digital-signage displays, keeps the last content so the screen keeps working if the network drops.Until cleared / replaced

Cookie names are indicative; exact identifiers set by Supabase and Cloudflare may vary by version. The functional cookies above appear only after the related action (signing in, submitting a form, or confirming an order).

Payments & checkout

When you upgrade or pay, we hand you off to our Merchant of Record, Lemon Squeezy (United States). Their checkout pages set their own cookies under Lemon Squeezy's own cookie and privacy policies, which we do not control.

When you pay a shop by card, you go to Stripe Checkout, the seller's payment page run by Stripe. Stripe sets its own cookies there, under its own cookie and privacy policies, which we do not control. We do not load Stripe's scripts on our own pages.

04

Public Pages & Displays

4.1 Profiles & Link Routing

Our public-facing services (Link in Bio profiles and Short Links) are designed for absolute privacy. When someone visits your profile or clicks a link:

  • ✓We count the visit on our server: when, the kind of device, the country, and the site that linked to it. No address, no identifier.
  • ✓Viewing a profile or an event, following a short link, or opening a link someone shared sets no cookies at all on the visitor's device.

One exception applies to public forms: if you fill in and submit a form, we store a single first-party cookie (form_submitted_<id>_<version>) on your device for one year so the same form is not submitted twice. It records only that a submission happened and is never used to track or profile you.

4.2 Digital Signage Displays

Public display pages — the screens shown in your premises (for example a foyer, prayer hall, or classroom) — are built to run unattended on a screen and do not set advertising or tracking cookies on the display device. To keep working when the network drops, a display does keep a local copy of its current content on the device (via LocalStorage and a service-worker cache). As explained in section 02, we treat this device storage as in scope here; it is strictly necessary for the signage feature and is never used to identify or track anyone.

  • ✓The display periodically requests its content from our servers; we process those requests (including the device's IP address) only to deliver content and keep the service secure.
  • ✓We do not profile, identify, or track the people who walk past or view the screen.
05

Managing Cookies

You can clear or block cookies via your browser settings (Chrome, Safari, Edge, etc.).

Warning: If you block strictly necessary cookies, you will not be able to log in to the Workspace dashboard, as we won't be able to verify your identity securely.

Questions?

If you have concerns about a specific cookie or our data practices, please reach out.

Contact privacy@halaal.app

Data controller: Halaal Inc LTD, registered in England & Wales (company no. 16055333), 167–169 Great Portland Street, London, W1W 5PF. Cookie and privacy queries: privacy@halaal.app.