Privacy policy

1. Who runs Lamha

Lamha is run by one person, its owner, from Saudi Arabia. He is responsible for the data described here, and he is who you write to about it at info@lamha.co.business.

The service is still in beta, and there is no payment system in it yet.

2. What we collect, and why

This table is everything Lamha's database holds about you and about your viewers. What is kept outside the database — cookies, rate-limit counters and the servers' technical logs — is described in sections 6 and 11.

Your own views of your own recordings are not counted. And opening the same page more than once within six hours counts as one view, not several.

And what gets written outside the database

• Server logs. The website's hosting and the delivery network write a technical access log that normally contains an IP address, the time and the page requested, as every web server does. Those are short-lived operational logs kept by the hosting and delivery providers; we do not use them to track anyone, do not join them to an account, and they are not what feeds the view statistics you see.
• The mail log. When a message is sent or fails, a line goes into the server log with the recipient's address and the subject — never the body and never the link inside it.
• The rate-limit counters, small temporary files whose keys are hashed (see section 11) and which are swept away after a day.

3. What the extension does, and does not do

The Chrome extension is what actually records. Its permissions are declared in its manifest.json; here is what they mean:

• It records only what you pick: the current tab, your screen, or an area of it — after you choose it yourself in Chrome's own picker.
• The microphone and camera are off by default. They work only when you turn their switch on in the popup, and the camera appears as a bubble on the page so you can see it running.
• "Keep a copy on this computer" saves the file to your own downloads folder. That copy goes nowhere else.
• Its manifest grants it two addresses and no others: lamha.co.business and cdn.lamha.co.business. That is the whole list, and it cannot be widened at runtime. (The popup's advanced settings do hold two fields that point it at a different Lamha installation; leave them alone unless that installation is yours.)
• It reads the open tab's address for one reason: to see whether the page can be recorded at all (Chrome's own pages cannot be). The address is not stored and never leaves your computer.
• The title and address of the page you record are never used and never sent. A recording's name is what you type, or a date and time if you type nothing.
• The only code the extension injects into another page is the recording interface you can see: the countdown, the toolbar, the area selector and the camera bubble — injected into the tab you are recording, when you start recording. The script that runs automatically runs on lamha.co.business pages alone, and its job is to hand your sign-in to the extension.
• Your session token is kept in the extension's own storage inside your browser, and is never written to a log.

4. Where your data is kept

• Accounts, titles, statistics and comments: a MySQL database on shared cPanel hosting the owner of Lamha rents from a commercial provider. If you need to know which provider, and which country that server stands in today, ask at info@lamha.co.business and we will tell you.
• The recording files and their posters: an ASUSTOR network drive that the owner of Lamha keeps at his home in Jeddah, Saudi Arabia.
• Delivery: Cloudflare's network carries the address cdn.lamha.co.business through a tunnel to that drive, so your browser can reach it without the drive being exposed on the internet. Like any delivery network, the requests pass through its servers, so it sees them and keeps its own logs. The recording files themselves are served with a private, no-store header, so they are not held in its cache and no copy of them stays there.

The split between the two machines is deliberate: the storage machine has no user table. It knows file keys, not people. And nothing on it opens without a signature: a video's playback URL is signed for six hours and the page mints a fresh one every time it is opened, while a poster image's URL (and a screenshot's own file, when a link preview asks for it) is signed for thirty days, because chat apps keep a preview far longer than six hours and an expired signature would leave a broken card behind.

Because the recordings sit on a machine at a home, playback can occasionally be unavailable if that home loses power or internet. Nothing is lost when that happens, but playback stops until the machine is back.

5. Who can see a recording

Every recording has one of three settings, which you choose and can change at any time:

• Private: you alone. Anyone else opening the link sees a "not found" page.
• Link: anyone holding the link can watch, with no account. This is the default.
• Password: the link alone is not enough; a password you set is asked for, and stays unlocked for whoever enters it for twelve hours.

• When the link is pasted into a chat app or a social network, that app usually fetches the page to draw a preview: the recording's title and poster image can appear there, and that image's URL stays valid for thirty days. A password-protected recording's preview is deliberately blank: the card carries Lamha's own logo and the owner's name, never the title and never a frame of the recording.
• You can set an expiry date, after which the page answers that the recording has expired.
• You can turn the download button off for a particular recording, so it can be watched without being saved in one click.
• A private link and a link that never existed answer identically, so nobody can probe to learn that something is there.
• Comments are visible to everyone who can open the page, including people with no account.

6. Cookies

All of them are needed for the site to work. There is no advertising or tracking cookie, and nothing from another company is loaded on these pages.

• lamha_sid — keeps you signed in. 30 days.
• lamha_lang — remembers whether you chose Arabic or English. One year.
• lv_… — one per recording you watch, so a page refresh is not counted as a new view. Six hours.
• lamha_pw_… — remembers that you entered the right password for a protected recording. Twelve hours.
• lamha_x — protects the dashboard's forms from forgery. lamha_cmt spaces out consecutive comments. lamha_flash carries one confirmation message across a redirect and is erased immediately after.

7. The email we send

Two messages exist, and no others:

• A password reset link, when you ask for one from the sign-in page. The link is good for one hour.
• A message with a temporary password and your sign-in details, sent when the owner creates the account for you, and again if he issues you fresh login details later. If you sign up yourself, no email is sent at all.

There is no newsletter and no marketing email, and your address is not given to anyone else.

8. Who inside Lamha can see your data

The owner alone, through an admin panel. What it shows him, plainly, so that you know:

• The list of accounts: email address, name, plan, storage used, and account status.
• Every recording in the service: its title, size, owner and view count — which is how he sees what is filling the disk.
• He can suspend or delete an account, move it between plans, delete a recording, and restore a deleted one while its file is still on the disk.
• He can open the share page of any recording that is shared by link, exactly as anyone holding the link can. A private recording answers him with the same "not found" it gives everyone else, and a password-protected one asks him for the password like any other viewer. The admin panel itself does not play recordings or show what is in them.

Deleting a recording from the admin panel is the same delete you perform yourself: the link dies at once, and the file is wiped from the disk thirty days later. Deleting a whole account works differently, and section 10 describes it.

9. How long things are kept

• Recordings: until you delete them. Deleting kills the link at once; the file stays on the disk for thirty days — the window in which a delete by mistake can still be undone — and is wiped after that, leaving nothing of it.
• View records, comments and buttons: deleted along with the recording they belong to.
• Sign-in sessions: thirty days. An expired session stops working the moment it expires, and a maintenance job deletes its row from the database.
• Your account: until you ask for it to be deleted — section 10 sets out exactly what goes and what remains.

10. What you can do about your data

• Change your name, language and password from the Account page, and sign out your other devices with one click.
• Delete any recording whenever you like, or make it private, put a password on it, give it an expiry date, or turn its download off.
• Delete any comment written on your own recordings.
• Delete your whole account: there is no button for this on the site yet, so write to us from the address on the account at info@lamha.co.business. Your account row goes (email, name, password hash), and with it your sessions, your recordings' records, their statistics and their comments; every share link dies at once.
• Ask for a copy of what is held about you, or for it to be corrected: write to the same address.

One more thing worth saying plainly: comments you wrote on other people's recordings are not deleted with your account — your name is detached from them and they are left anonymous. If you want the text of those gone too, say so in the same message.

11. How it is protected

• The site is served over HTTPS, and your session cookie is marked Secure, so your browser never sends it over an unencrypted connection. Passwords are stored only as hashes.
• Every database query is a prepared statement, the standard protection against injection.
• Video URLs are signed and short-lived, and will not open without a valid signature.
• The dashboard checks an anti-forgery token on every write, and the admin panel opens only for an admin account.
• Sign-in, registration and comments are rate-limited, and the keys of those counters are hashed, so no email address or IP is written into those files in the clear (the servers' own logs are a separate thing, described in section 2).

No system is perfect, and Lamha is a young service run by one person. If you find a flaw that touches anyone's privacy, tell us at info@lamha.co.business and it will be dealt with.

12. Children

Lamha is a tool for work, and is not aimed at children. Do not create an account for a child. If we learn of an account made for one without a guardian's permission, we delete it.

13. Changes to this page

Lamha changes, and this page changes with it. The date at the top is when it last changed. If something material changes in what we collect or where it is kept, we will say so here plainly, not in a footnote.