Legal

Privacy Notice for Business Users

Last updated 25 October 2026For restaurant owners and managers
Draft — pending legal review.This text describes how HalallO works today but has not been reviewed by a lawyer. Details in [brackets] are still to be filled in.

What we collect when you claim and manage a restaurant, why, who sees it and for how long. Restaurants handle different data from diners, so they get their own notice.

1.Who is responsible

[COMPANY LEGAL NAME], [REGISTERED ADDRESS], company number [COMPANY NUMBER] (“HalallO”, “we”) is the controller of the personal data described here. Privacy contact (data protection officer where one is required): [DPO / PRIVACY CONTACT].

This notice covers people who use HalallO for Business: owners and managers who claim or manage a restaurant at business.halallo.com or in the business features of the HalallO app, and people who contact our business team. How we handle diners’ data is in the HalallO Privacy Policy.

2.What we collect

CategoryWhat it includesWhere it comes from
AccountEmail address, password (stored only as a secure hash by our authentication provider), account creation date, when you accepted the terms, and that you signed up from the business panel.You
Claim detailsThe restaurant, the role you claim (owner or manager), the verification method, your full name and contact phone number, the business email you verify, your declaration and its time, the one-time claim code we issue, status, stage, reviewer notes and dates.You, and our review team
Claim filesBusiness documents (licence, registration, hygiene certificate, utility bill or lease) and photo proofs. These may show names, addresses, signatures or faces if you include them.You
Verification codes6-digit email codes, stored only as salted hashes, valid for 15 minutes, with attempt and send counters.Generated by us
Security signalsYour IP address is used to compute a salted one-way hash for rate limits and abuse checks; we store the hash, not the IP address, with claim and upload records. Counts of claims, uploads and code requests. A bot-protection token when the security check is on.Your device, our systems, Cloudflare Turnstile
Restaurant contentHours, phone, website, description, menu, prices, photos (with location metadata removed), reservation settings and change requests. This is business information and becomes public on the listing.You
Membership and planWhich restaurants you manage and your role; plan and reservation settings.Our systems
CommunicationsEmails you send to business@ or support@ and our replies; service emails we send you.You, us
Technical logsIP address, browser and device type, pages requested and timestamps, kept briefly by our hosting providers for security and troubleshooting.Your device
Billing (planned)When billing launches: a Stripe customer ID, plan, invoices, billing name and address, tax ID if you give one, and the card brand and last four digits. Full card numbers go to Stripe and never reach HalallO.You, Stripe
Usage analytics (planned)If we turn on product analytics: pages and features used, with pseudonymous IDs. You will be able to opt out.Your device

We do not ask for government photo ID and we do not use your data to make decisions with legal effects based solely on automated processing: every claim is decided by a person.

3.Why we use it, and our legal bases

Where the GDPR or UK GDPR applies, we rely on these legal bases:

PurposeDataLegal basis
Create and secure your account, sign you in, reset passwordsAccount, security signals, logsContract; legitimate interests in security
Verify that you own or manage the restaurant and decide claimsClaim details, claim files, codesContract; legitimate interests in protecting restaurants and diners from takeovers
Publish and maintain your listingRestaurant content, membershipContract
Prevent fraud, spam and abuse (rate limits, duplicate and repeat claims)Security signals, claim detailsLegitimate interests; legal obligations where applicable
Run Paid Plans: billing, invoices, tax (when launched)Billing, accountContract; legal obligations (tax and accounting)
Send service messages (claim updates, security notices, changes to terms)Account, claim detailsContract; legitimate interests
Answer your questions and handle complaintsCommunicationsLegitimate interests; contract
Improve the product with aggregated usage (if enabled)Usage analyticsLegitimate interests, or consent where the law requires it
Comply with law and enforce our termsAny relevant dataLegal obligations; legitimate interests

We don’t send marketing emails without your permission, and every marketing email will have an unsubscribe link. We do not sell your personal data.

4.Notice for California and other US states

In the last 12 months we have collected the categories above, which under the CCPA/CPRA correspond to identifiers (name, email, phone, IP-derived hash), customer records, commercial information (plans and purchases, when billing launches), internet activity (logs), professional information (your role at the restaurant), and sensitive personal information limited to account login credentials. We use them for the business purposes in section 3.

We do not sell personal information and we do not share it for cross-context behavioural advertising. We do not use sensitive personal information to infer characteristics about you. Retention is described in section 7. You can exercise your rights as described in section 8, including through an authorised agent, and we will not discriminate against you for doing so.

5.Who can see it

  • The public: your restaurant content and the “Managed by owner” caption on the listing. Your name, email and phone number are not shown on the listing.
  • Other members of the same restaurant: that you manage it, and your role.
  • Our review team: claim details and claim files, through private links that expire after 5 minutes. Reviewers do not see whether a restaurant pays.
  • Service providers who process data for us under contract, listed in section 6 and on the Subprocessors page.
  • Authorities or others when the law requires it, or when needed to protect someone’s safety, prevent fraud or enforce our terms.
  • A buyer or successor if HalallO is merged, acquired or sold, under this notice’s protections.

6.Service providers we use

ProviderWhat forStatus
SupabaseDatabase, authentication, file storage and server functions, on Amazon Web Services in the United States (us-east-1)Used
VercelHosting and delivery of business.halallo.comUsed
ResendSending email (verification codes and service emails)Used
Cloudflare TurnstileBot protection on sign-in, sign-up and password resetUsed when the security check is switched on
StripePayments, invoices and tax calculationPlanned, with billing
PostHog (EU Cloud)Product analytics, with an opt-outPlanned

More detail, including where each provider processes data, is on the Subprocessors page. We will update it before a planned provider starts processing your data.

7.How long we keep it

DataHow long
AccountWhile your account exists. Deleted when you delete your account (here: Account → Delete account, or in the app: Settings → Delete account).
Claim files (documents and photo proofs)Deleted automatically within 90 days after the final decision on the claim (a daily job), or when you delete your account if that is sooner.
Claim records (who claimed what, when, method, decision)For as long as the membership lasts and up to 3 years after the claim is decided, to handle disputes and repeat abuse. After that, the name, phone and email on the record are erased automatically.
Verification codesValid for 15 minutes; the hash is overwritten when used, expired or replaced.
IP hashes and rate-limit recordsUp to 12 months, then the IP hash and any email in them are erased automatically.
Restaurant contentWhile it is on the listing. Facts diners rely on (such as hours) may stay after you stop managing the listing; photos you uploaded are removed on request.
Billing records (when launched)As long as tax and accounting law requires, typically 6 to 10 years depending on the country.
Server logsA short period, typically up to 30 days, set by our hosting providers.
BackupsDeleted data disappears from encrypted backups as they expire.

8.International transfers

Our database and files are hosted in the United States, and some providers process data in other countries. If you are in the European Economic Area, the United Kingdom or Switzerland, your data is transferred outside those areas. Where required, we rely on the EU–US Data Privacy Framework (and its UK extension and Swiss framework) where the provider is certified, or on the European Commission’s Standard Contractual Clauses and the UK addendum, together with the provider’s security measures.

EU representative: [EU REPRESENTATIVE, IF REQUIRED]. UK representative: [UK REPRESENTATIVE, IF REQUIRED].

9.Your rights

Depending on where you live, you can ask to access, correct, delete or receive a copy of your personal data, to restrict or object to how we use it, and to withdraw consent where we rely on it. California and other US state residents can ask to know, delete and correct their personal information and to opt out of its sale or sharing (we do neither).

  • Edit your restaurant content in the dashboard, and delete your account on the Account page or in the HalallO app (Settings → Delete account). Deleting your account also deletes your claim files.
  • For anything else, email [DPO / PRIVACY CONTACT] from the address on your account. We confirm requests from that address and answer within the time the law sets (normally one month, or 45 days in California).
  • You can complain to your data protection authority, for example in the EU the authority where you live, or the ICO in the UK.

If we can’t delete some data because the law requires us to keep it (for example invoices) or because we need it to handle a dispute, we tell you and keep it only for that purpose.

10.How we protect it

  • Encryption in transit (HTTPS with HSTS) and at rest by our hosting provider.
  • Row-level security in the database: you can read only your own claims and the restaurants you manage.
  • Claim files sit in a private storage area. Uploads go through a server function that checks permission, size, the real file type, image dimensions and PDF content, and removes location data from restaurant photos.
  • Verification codes are stored as salted hashes with attempt limits; IP addresses are stored only as salted hashes.
  • Sign-in uses PKCE; you can sign out on every device from the Account page. Staff access to the review console is limited to approved accounts.

No system is perfectly secure. If a breach affects your personal data, we will tell you and the authorities as the law requires.

11.Age

HalallO for Business is for adults acting for a business. Business accounts must belong to people aged 18 or over.

12.Changes to this notice

We update this notice when our practices change, for example before billing or analytics launch. If a change materially affects you, we tell you by email or in the panel before it takes effect. The date at the top shows the last update.

13.Contact

Privacy requests: [DPO / PRIVACY CONTACT]. Business questions: business@halallo.com. Account help: support@halallo.com. Post: [COMPANY LEGAL NAME], [REGISTERED ADDRESS].