Lammat privacy notice (V2)
Effective date: 9 November 2026
1. Who we are
Lammat (https://lammat.ae) is an app for organizing gatherings in the UAE: inviting guests, checking them in, sharing costs or setting a price, letting guests pay the organizer directly through the organizer's own payment account or link, and sharing photos. Lammat is software: it never receives or holds anyone's money (section 8).
Lammat is run by Core Hub For Computer Systems & Communication Equipment Software Design (كور هاب لتصميم نظم الحاسب الآلي وأجهزة الإتصال), Dubai, United Arab Emirates, trade licence 1662573, issued in Dubai. "Lammat", "we" and "us" mean that business.
This notice follows UAE Federal Decree-Law No. 45 of 2021 on the Protection of Personal Data.
Questions, requests and complaints about your data: support@lammat.ae.
2. Who this notice is for
- Organizers. People who create a Lammat account to run gatherings. An organizer works in a Space, the organizer's home in Lammat. Each Space has one Owner and can have Admins whom the Owner invites.
- Guests. People an organizer invites to a gathering. Guests do not need an account.
- Visitors. Anyone who opens the Lammat website or app.
3. Who is responsible for what
- For a gathering's guest list, the organizer decides why and how it is used: whom to invite, what to charge and what to show. The organizer is responsible for that use. Lammat processes the guest details for the organizer, to run the gathering, under our terms with the organizer.
- For everything else we are responsible ourselves: accounts, security, analytics, error reports, our own billing and our legal duties.
If you are a guest, you can ask the organizer or us about your details. Either of us will help.
4. What we collect, and why
4.1 From organizers
| What | Why |
|---|---|
| Your email address | To create your account, sign you in, confirm your address and send you service emails. |
| Your password | To sign you in. We never store the password itself, only a scrambled version (a "hash") that cannot be turned back into it. |
| If you sign in with Google: an account number from Google and the email address Google confirms | To sign you in and contact you about your account. We do not ask Google for your files when you sign in. |
| Your Space: its name, who is Owner and Admin, who invited or removed whom, and when | To run your Space and keep a history of changes to your team. |
| What you enter for a gathering: title, date, welcome message, meal, matches, activities, location, check-in times, a 6-digit PIN, and cover and meal pictures | To show the gathering to your guests. We store the PIN only in scrambled form. |
| Menu and activities files you upload (a PDF or photos of a printed page) | To show them to your guests. Lammat stores them, with your cover and meal pictures. |
| Billing settings and records: amounts, prices, fees, bills, payments, refunds and notes you add | To work out what each guest owes, track payments and keep an accurate financial history. |
| Your connections: for Ziina, your Ziina account number, its status, a masked label and an encrypted access key; for Google Drive, an encrypted access key and a masked label | So guests can pay you through your own Ziina account, and to save your guests' photos in your Drive. Section 8 explains more. |
| If you share your own payment link: the link, and which payments you mark as received | To show the link to your guests and keep track of the payments you confirm. Lammat does not see those payments (section 8). |
| If you add bank transfer details: the bank name, account holder, the account number and IBAN, and the currency | To show them to guests of gatherings you bill with them, so a guest can pay you by transfer. Lammat does not see or verify the transfer (section 8). A corrected detail is saved as a new version and the earlier one is kept as a record. |
| Once card payments for memberships open, and only if you add a card: a reference to your Stripe subscription, its status and its dates | To run your membership. Stripe keeps your billing details. We never see or store your card details. |
| Your free months or membership code: when they started and end, and which code you used (never the code itself) | To give you the offer once and stop it being used twice. |
| Feedback you choose to send us: an optional rating from 1 to 5, an optional message and, only if you tick "You can reply to me about this", your account's email address | To improve Lammat and, if you asked, to reply to you. A copy is emailed to our support mailbox (support@lammat.ae). |
4.2 From guests
| What | Why |
|---|---|
| Your name and mobile number, typed at check-in | So the organizer knows who came and can reach you about the gathering, and to match your bill to you. We do not use your mobile number to identify you or sign you in. |
| Your agreement at check-in: that you ticked the box, when, and which version of this notice was in force | To show that you agreed (section 5). |
| How many people came with you (a number only, no names or ages) | To share the costs fairly. |
| When you checked in, and if you cancel, that you cancelled and when | To keep the guest list and bills accurate. A cancellation is recorded, not erased. |
| Your bills and payments | To track who has paid. |
| Photos you upload, their original file name and the time | To share them with the other guests of the gathering. |
Your phone may add hidden information to a photo, such as where and when it was taken. We remove location and other hidden data from photos. Before a photo is stored, its GPS position and its other hidden metadata (camera details, timestamps, edit history) are removed, and the picture itself is unchanged. A photo larger than 5 MB is also made smaller on your phone before it is uploaded.
بالعربية: «تزيل منصة لمّات بيانات الموقع من الصور قبل حفظها: يُحذف موقع التصوير والبيانات المخفية الأخرى في الصورة (مثل تفاصيل الكاميرا ووقت التصوير وسجل التعديل)، وتبقى الصورة نفسها كما هي. وتُصغَّر الصورة التي تتجاوز 5 ميغابايت على هاتفك قبل رفعها.»
4.3 From everyone who uses the app
| What | Why |
|---|---|
| Your IP address (your network's internet address) | To deliver the app to you and to protect sign-in, check-in and other forms from attacks. For this protection we store only a scrambled form of the address. Our hosting provider also sees the address and may keep it in its technical logs. |
| A random value your browser makes for itself, and a per-gathering value it derives from it, sent only with PIN requests | To count wrong PIN attempts per phone, so phones on one Wi-Fi do not lock each other out. See section 13. |
| If several wrong PINs are entered for a gathering, or several sign-ups use email addresses that already have an account: signals from your browser and device that Cloudflare Turnstile checks to tell a person from an automated program | To stop people guessing a gathering's PIN, and to limit how many times someone can check whether an email address already has an account. Your IP address is also sent to Cloudflare for this check; Lammat receives only a pass or fail answer. |
| Usage information (analytics): which steps are used, such as "checked in" or "payment started", with your language, whether your screen is a phone, tablet or computer, and random reference numbers for the gathering and the Space | To understand how Lammat is used and where people get stuck. See section 6. |
| Your approximate location (country and city), worked out from your IP address by our analytics provider | To understand where Lammat is used. |
| Error reports: what went wrong, on which kind of screen, your browser and device type, and the app version | To find and fix problems. |
We do not record your screen or your taps. Lammat has no advertising and no advertising trackers.
5. Why we are allowed to use it
UAE law lets us use personal data with your consent, and without it in the cases the law lists. We rely on these:
| Purpose | Why we may do it |
|---|---|
| Running your account, Space and gatherings, and your membership | It is needed to carry out our agreement with you. |
| A guest's name and mobile number, shared with the organizer | Your consent. Before you check in, you tick a box next to one message: "I share my name and mobile with the organizer. See the privacy notice." Check-in needs the tick. Lammat records when you ticked it and which version of this notice was in force. |
| Showing a guest's name and payment status to the other guests on the payment status board | The board is described in this notice (section 7.1). Its legal basis is an open point for the lawyer. The check-in message does not mention the board. |
| Check-in, bills and payments for a gathering | It is needed to carry out the arrangement between the organizer and the guest (a share of costs or a price), which Lammat runs for the organizer. |
| Photos guests upload, shown to the gathering's other guests with the uploader's name | The uploader chooses to share the photo, and must only share photos the people in them are happy to share. Anyone shown in a photo can ask us to remove it (section 12). |
| Security: stopping password guessing, PIN guessing and abuse | It protects you and your data, and the law expects us to keep data safe. |
| Service emails (confirm your address, reset your password, security and billing notices) | They are needed to run your account. |
| Keeping financial records | The law requires accounting records to be kept. |
| Error reports | They are needed to keep the service working. |
| Analytics | It helps us improve Lammat and does not identify you. You can stop it (section 6). |
Taking back your consent. You can take back your consent at any time: write to support@lammat.ae. The organizer then turns the payment status board off or removes you from it, and we anonymise your name and mobile number (section 12), except where they are needed for a bill that is still open or for financial records we must keep (section 10). Taking back consent does not affect what was done before.
We send only service emails. We do not send newsletters or marketing emails, and we do not sell personal data.
6. Analytics: what it can and cannot tell us
- Our analytics tool, PostHog, gives your browser a random ID. It is not your name, email or phone number.
- We never tell PostHog who you are. Guests are never identified in analytics, whether or not they have an account.
- For organizers, a few account events (such as "account created" or "Space created") are recorded with a random account reference, not your name or email.
- If you use Lammat as an organizer and as a guest on the same phone, analytics can tell that one device did both. It still cannot tell who you are.
- Analytics events carry a random reference for the organizer's Space and say whether the visitor has checked in. This applies from the first screen, before a visitor enters a PIN.
- Analytics is never used to decide what you owe or whether you have paid.
- To stop it: block PostHog (
eu.i.posthog.com) with your browser or a content blocker, or clear the site data of lammat.ae. Lammat works the same without it. We cannot yet switch it off from inside the app.
7. Who we share data with
7.1 Inside a gathering
- The organizer (the Space's Owner and Admins) sees each guest's name, mobile number, number of companions, check-in time, bill and payment status.
- Other guests of the same gathering see the name of whoever uploaded each photo.
- Payment status board. If the organizer turns it on (it is off unless they do), the gathering's guests can see each other's names and one of four statuses: settled, marked received by the organizer, pending or unpaid. They never see amounts or payment details. This notice describes the board, and the message you tick at check-in does not mention it (section 5).
- Before you check in, after entering the PIN, you see only what the organizer chose to show (for example the meal, the activities or the location). You see no guest names.
- Inside a Space, the Owner sees the sign-in email address of each team member.
7.2 Lammat's own people
Day to day, Lammat's operator sees counts and technical health, not guests' names or photos. We look at a specific Space's data only when needed to fix a problem you asked us to look at, to keep Lammat safe, or to follow the law. Feedback you send is read only by Lammat's own team, in our owner console, and each time it is opened we keep a record of who opened it.
7.3 Companies that help us run Lammat
They process data for us and may use it only to provide their service.
| Company | What they do for us | Where the data is processed |
|---|---|---|
| Cloudflare | Hosting, database, file storage for gathering pictures, menus and activities files, technical logs, sending service emails (Cloudflare Email Service), and the security check on the guest PIN page after repeated wrong PINs (your IP address is sent to Cloudflare for a bot check) | Cloudflare's global network, which can be outside the UAE |
| PostHog | Analytics (section 6) | European Union |
| Sentry | Error reports | Germany (European Union) |
| Ziina | Payments from guests to organizers (section 8) | Ziina is a UAE company; its systems may be outside the UAE |
| Stripe | Membership payments from organizers to Lammat, once card payments for memberships open (section 8) | Stripe's global network, which can be outside the UAE |
| Sign-in with Google, if you choose it, and Google Drive (section 7.4) | Google's global network, which can be outside the UAE |
Our emails contain no tracking images and we do not track links, so our email provider does not see when you open an email or click a link.
7.4 The organizer's own Google Drive
Each Space keeps the photos its guests upload in the organizer's own Google Drive. When a guest uploads a photo, Lammat saves it into the organizer's Drive. Google then holds it under the organizer's account and agreement with Google.
- Lammat asks for the smallest access it can: only the files Lammat itself creates.
- Guests never get access to the organizer's Drive. They see photos only through Lammat.
- If the organizer disconnects the Drive, Lammat deletes its access key. It never deletes the organizer's files.
- Google user data. We use information from Google only to sign you in and to store and show your guests' photos. We do not sell it, do not use it for advertising, and do not let people read it except to keep Lammat safe, to follow the law, or with your consent. Our use follows Google's API Services User Data Policy, including its Limited Use rules.
7.5 When the law requires it
We may share information when the law requires it, when a court or authority in the UAE orders it, or to protect people from harm. We share only what is needed.
8. Payments
- Lammat is software and never holds your money. Lammat is not a bank or a payment service. It never receives, holds or sends anyone's money, and it is not a party to payments between guests and organizers. Guests pay the organizer directly, through Ziina or through a payment link the organizer shares. If the organizer charges a price, the guest buys from the organizer, not from Lammat.
- Paying through Ziina. Ziina is a UAE payment company that says it is licensed by the Central Bank of the UAE. Money goes from the guest to the organizer's own Ziina account. It does not pass through Lammat.
- Guests paying through Ziina: you type your card details on Ziina's own page, never in Lammat. Lammat tells Ziina only the amount, the currency, the gathering's name as the payment label (or, until the name is verified with Ziina, the fixed label "Lammat event share"), and where to send you back. We do not send Ziina your name or mobile number. Ziina tells Lammat whether the payment went through and the fee, so we can mark your bill paid. Ziina's own privacy notice applies to what Ziina holds.
- Paying through the organizer's own payment link or bank transfer. If the organizer shares a payment link instead, you pay on that service's own page, outside Lammat, and the money goes from you to the organizer. Lammat only shows you the link. If the organizer adds bank transfer details as well as, or instead of, a payment link, Lammat shows you the bank name, account holder, the account number and IBAN, the currency and a suggested reference (the gathering's title), and you make the transfer at your own bank. In both cases Lammat does not see, process or check that payment, and it shows your bill as "Marked received by the organizer" only when the organizer confirms the payment. That service's or your bank's own terms and privacy notice apply.
- Organizers: each Space connects its own Ziina account. You may use the same Ziina account for more than one of your own Spaces, never in another person's Space. Lammat asks Ziina only for permission to read basic account details and to create payment requests. It does not ask for permission to move money out of your account. As far as we know, Ziina does not let you remove Lammat's access from its side, so you disconnect in Lammat, which deletes our keys.
- Memberships: when card payments for memberships open, organizers who add a card pay Lammat through Stripe, on Stripe's own page. Stripe sends receipts and payment emails to the billing email on the membership. We never see your card details.
During your free months, and until you choose to add a card, we share nothing with Stripe. Stripe receives your email and card only if you add a card.
9. Sending data outside the UAE
Some of the companies in section 7.3 process data outside the UAE. The UAE has not yet named any country as giving adequate protection, so we transfer data only in the cases the UAE data protection law allows when no such list exists (Article 23 of Federal Decree-Law No. 45 of 2021):
- the transfer is needed to provide what you asked for: your account, your gathering, a payment or your membership; and
- each company is bound by a written agreement (its data processing terms) that requires it to use the data only for us, keep it secure, and tell us about any breach.
We use European Union regions where we can (PostHog and Sentry), send each company only what its job needs, and keep a record of these transfers. You can ask us for a copy of the safeguards for any company (section 12).
10. How long we keep data
We keep personal data only as long as we need it for the purposes in section 4, or as long as a law requires. The table gives each period. When a period ends, we delete the data or anonymise it (section 12 says what anonymise means).
| What | How long |
|---|---|
| A sign-in session on a device | Stops working after 30 days, or after 14 days without use. You can end all your sessions at any time. |
| Links in account emails | Confirm-your-email links stop working after 24 hours and password-reset links after 30 minutes. Each works once. |
| Invitation links for new Space Admins | Stop working after 7 days. Each works once. |
| A guest's check-in on a device | Stops working after 180 days. The guest's recovery link stops working after 730 days (2 years). |
| PIN entry on a device | Stops working after 7 days. |
| Sessions, check-ins, PIN entries and links that have stopped working | Deleted 90 days after they stop working. |
| Counters that limit repeated attempts (wrong PINs, sign-in tries, emails sent) | Deleted once they expire: after 30 minutes, or after 2 days for the daily email limit. They are removed the next time the same feature is used. They hold no name, email address or IP address, only one-way coded values. |
| Your organizer account | While your account is open. When you close it, we anonymise your details within 30 days, except financial records. |
| Guests' names and mobile numbers, and the record of their agreement at check-in | Until 2 years after the gathering's date, then anonymised. Sooner if the guest asks (section 12), unless they are needed for a bill that is still open. |
| Bills, payments and financial records of a gathering | 5 years after the end of the year in which the gathering took place, so that organizers who run a business can meet UAE record-keeping rules. After that, the names and mobile numbers in them are anonymised. Until then we do not edit or delete them in Lammat: corrections are added as new records, so the history stays accurate. |
| Lammat's own membership and billing records | 5 years after the end of the tax period they belong to, or longer if a tax law requires it. |
| Photo records in Lammat (file name, uploader, time) | 2 years after the gathering's date, then deleted. When a photo is removed from the gathering, Lammat stops showing it, and its record stays until then. The photos themselves are in the organizer's Drive, and the organizer decides how long to keep them. |
| Meal pictures, menus and activities files an organizer adds | While the gathering is in Lammat. A removed or replaced one is deleted once no version of the gathering uses it; a deleted draft's are deleted with it. |
| Feedback you send | Kept until your account is deleted, or sooner if you ask us to delete it. |
| Analytics, error reports, technical logs and sent emails | Kept by PostHog, Sentry and Cloudflare for the periods of our plans with them. For each email we send, Cloudflare keeps the address it went to, its subject and whether it was delivered for about 30 days. We are confirming the other periods and will list them here. |
Until it is deleted, the record of a session or link never contains the secret itself, only a scrambled form of it.
11. How we protect data
- The app works only over encrypted connections (HTTPS).
- Passwords are stored only as a "hash" made with a slow, modern method. Passwords must be at least 8 characters, and very common passwords are refused.
- Sign-in sessions, email links, guest links and invitation links are long random codes. We store only a scrambled form of each one. Gathering PINs are stored only in scrambled form.
- Card details never reach Lammat.
- Our secret keys are kept in our hosting provider's encrypted secret storage, never in our code. Access keys to an organizer's Ziina or Drive are stored encrypted.
- We limit how often anyone can try to sign in, enter a PIN or request an email.
- Each Space's data is kept separate from every other Space's, and we test this automatically.
- Our analytics and error tools are set up not to receive names, email addresses, phone numbers, passwords, cookies or what you type into forms.
No system is perfectly secure. If personal data is exposed in a way that could harm you, we will tell the UAE authority for the data protection law (section 12) as the law requires, tell the affected organizers so they can tell their guests, and tell the people affected without undue delay.
12. Your rights
You can ask us to:
- tell you what data we hold about you, and give you a copy in a usable form;
- correct data that is wrong;
- delete your data, or anonymise it;
- limit or stop some uses of your data;
- take back a consent you gave (section 5);
- review a decision that was made only by automated means. Lammat does not profile people. Some account limits follow your membership status automatically, and you can ask us to look at them.
How to ask: email support@lammat.ae. Organizers: write from the email address of your account. Guests: tell us the gathering and the name you used. We may ask for information to confirm the request is yours. We answer within 30 days. If a request is complicated, we tell you why and when you will have an answer.
What "anonymise" means. We remove or replace every detail that could identify you, such as your email address, or a guest's name and mobile number, so the record can no longer be linked to you.
When you ask us to delete your data. We anonymise it, on request and at the end of the periods in section 10. Financial records stay for the period in section 10. A note an organizer typed into a financial record cannot be changed, and it may contain a name. Photos in an organizer's Drive belong to the organizer.
Things you can do yourself:
- Organizers can reset their password and sign out of every device at once.
- Guests can remove a gathering from their own device ("Remove from this device"). This clears the device only, and the organizer's records stay. It is not available while a payment is in progress.
- Guests can change the number of companions while the organizer allows it, and can cancel their check-in until the gathering starts and before bills are made.
If you are not happy with our answer, you can complain to the UAE authority for the data protection law. That was the UAE Data Office; in June 2026 its work moved to the new Artificial Intelligence and Data Authority. About a consumer matter, you can also contact the Ministry of Economy's consumer line, 800 1222, or, in Dubai, the Department of Economy and Tourism.
13. Cookies and storage on your device
| Name | What it does | How long |
|---|---|---|
__Host-lammat_session | Keeps an organizer signed in | Up to 30 days |
lammat_signed_in | Remembers only that this browser is signed in, so "Sign in" opens your Spaces instead of the sign-in form. It holds no name, email or sign-in token. | Up to 30 days |
__Host-jamaatna_guest_... (one per gathering) | Remembers that you checked in to that gathering | Up to 180 days |
__Host-jamaatna_pin_... (one per gathering) | Remembers that you entered the gathering's PIN | Up to 7 days |
| A short sign-in cookie | Protects sign-in with Google and connecting your Drive or Ziina | About 10 minutes |
ph_..._posthog (a cookie and browser storage) | Holds the random analytics ID (section 6) | Up to one year |
lammat.guest-device.v1 (browser storage) | A random value the browser makes for itself. It is used only to count wrong PIN attempts per phone, so phones on one Wi-Fi do not lock each other out. Lammat keeps only a one-way coded value made from the per-gathering value below, deleted like the other attempt counters (section 10), never linked to a name or a check-in. A per-gathering value derived from it is sent with PIN requests and may appear in Cloudflare's technical request logs for up to 7 days. | Stays on your phone until you clear site data; "Remove from this device" does not clear it |
| App storage (offline cache) | Keeps the app's own files (layout, icons, code) so it opens quickly. It never holds your personal data, bills or photos. | Until the app updates |
The session, guest and PIN cookies and the short sign-in cookie are needed for Lammat to work; the browser's device value is needed to protect the gathering's PIN, so phones on one Wi-Fi do not lock each other out; lammat_signed_in only saves you a step. The names starting jamaatna come from Lammat's earlier name. If you used Lammat's first version, your browser may still hold its guest and PIN cookies (the same names without the __Host- prefix). This version starts with none of the first version's data, so those cookies match nothing in it, and your browser removes them when they expire.
14. Children
Lammat is for adults. Organizers must be at least 18. Guests under 18 should be checked in by a parent or guardian. Lammat asks no one's age, and it records companions only as a number, never as names or ages. We have no advertising and do not profile anyone. If we learn that we hold data from a child who should not have given it, we delete it.
15. Changes to this notice
We update this notice when Lammat changes. The date at the top shows the latest version. If a change matters to you, we tell organizers by email or in the app at least 30 days before it takes effect. Guests can always read the latest version at https://lammat.ae/privacy. Before a new use of your data begins, we tell you.
Language. This notice is available in Arabic and English. If the two differ, the Arabic version prevails.
16. Contact
Core Hub For Computer Systems & Communication Equipment Software Design, Dubai, United Arab Emirates
Email: support@lammat.ae