Privacy
What LaqtaRoom stores about you, why it is stored, how long it is kept, and how to have it removed.
Last updated 2026-09-14
Who is responsible
LaqtaRoom is operated by LaqtaRoom, Beirut, Lebanon. For anything in this policy — including a request to see or delete your data — write to support@laqtaroom.com.
There are two kinds of people in this service, and the distinction decides much of what follows. A photographer holds an account and uploads work. A client opens a room link, usually with no account at all. For a photographer’s account we are the data controller. For the photographs and video inside a room, and for notes a client leaves on them, the photographer decides what is collected and why; we hold and process it on their behalf.
What is stored
The categories below cover everything the service holds about you. They are grouped rather than listed column by column, so read each row as describing a kind of record and not an exhaustive field list.
The right-hand column distinguishes two different things that both get called deletion: a record being erased, and a record being made unusable but kept. Where we mean the second, it says so.
| What | Why | Kept for |
|---|---|---|
| Account — name, email, hashed password (if you set one), username, when the username last changed, any usernames you used before, and — if you use “Continue with Google” — the identifier Google gives your Google account | To have an account and sign in. Old usernames are kept so nobody else can take one and be mistaken for you | Until the account is erased |
| Account settings — your branding, display preferences stored against the account, and saved layouts | So the app looks and behaves the way you set it up | Until the account is erased |
| Sessions — a session identifier, the IP address and browser user-agent it was created from, and when it was last active | To keep you signed in, and — in the service’s own administrative and operational views — to tell one signed-in browser from another | Signing out erases the row. An expired session stops working at once, but there is no periodic sweep: an abandoned row is erased the next time that same cookie is presented, and otherwise when the account is |
| Uploaded work — photographs, video, the smaller versions and thumbnails generated from them, and any watermark settings | To store and deliver the room | Until deleted, then 10 days in the trash — where it can still be restored — before erasure. Configurable per deployment |
| Rooms — room name, the client name and welcome message you set, access settings, folders, who has been added as a member or invited, and any links you make to a single shot, a set of shots or a folder — with who each is for, its settings, and when it was last opened | To make the room work and to control who gets in | For the life of the room, then the trash window above |
| Review activity — comments, timecoded notes, drawings on frames, reactions, picks, approvals and sign-offs, and the name a guest typed when asked for one | To make review work: a note has to be attributable to someone | For the life of the room |
| Room access log — for each visit to and download from a room: the time, whether it succeeded, the name given, the IP address and the browser user-agent | So a photographer can see their work arrived, and so a password being guessed at is visible rather than silent | For the life of the room |
| Notifications — in-app messages telling you what happened in your rooms, who did it, and whether you have read them, plus any announcements sent to you and whether you opened them | To tell you about activity without emailing you | Until the account is erased |
| Presence — periods during which you were signed in with an active tab | To total how long an account has been active, for our own operational and administrative views. Who is in a room right now is worked out live and not stored | Until the account is erased |
| Activity log — an internal record of actions taken in the app: who, what, which room, when | Support, and investigating something that went wrong | Erased automatically after 120 days |
| Operational metrics — counts and totals about the service as a whole, not tied to a person | To know whether the service is healthy | Per-minute figures 48 hours, hourly 90 days, daily kept indefinitely |
| Support messages — anything you send through the feedback screen, and our replies | To answer you | Until the account is erased |
| Email codes — single-use codes for verifying an address or resetting a password | To confirm it is really you | Marked used, or expired, as soon as they are spent — they stop working immediately. The record itself is erased with the account |
What is not stored
There is no advertising network, no third-party analytics, no tracking pixel and no behavioural profiling anywhere in this service. Nothing you do here is sold, and nothing is shared with anyone for their own purposes. We do not hold payment card details: if paid plans are introduced, a payment provider will handle the card, and this page will name them before that happens.
Cookies and similar storage
Four kinds of thing are stored in your browser:
- Authentication. A session cookie, so you stay signed in from one page to the next; and a room grant cookie, so a client who has entered a room password is not asked again on every photograph. The grant lasts twelve hours and stops working the moment the photographer changes the code or the password. On a link the photographer has locked to devices, a device cookie holds a random key, for a year, so your device stays one of the ones allowed in until the photographer releases it. And while you sign in with Google, a cookie lasting ten minutes ties Google’s answer to the sign-in you started.
- Who you said you were, in one room. When a client types a name on entering a room, that name and a random identifier are kept in a separate cookie for that room, for a year. It is what makes “Sara picked these eleven frames” still say Sara when she comes back on Thursday, rather than showing the photographer four different strangers. It is issued per room and never follows you between rooms, and on its own it opens nothing — a browser holding it and no grant gets exactly as far as one holding neither.
- Security. Whatever Cloudflare Turnstile, our bot check, needs in order to tell a person from a script on the sign-in, sign-up and room-entry forms.
- Preferences you set. Roughly twenty small values kept in your own browser’s local storage, recording choices you made in the interface: light or dark, background style and accent colour, how wide the notes panel is, which sidebars and sections are collapsed, thumbnail size and sort order, your last pen colour, which notes you have read, and which one-off banners you have dismissed. There is also a single marker, discarded when you close the tab, that stops the page reloading twice in a row after an update. These never leave your device and are never sent to us.
The first three are necessary to provide something you asked for: to stay signed in, to get into a room, to have your notes signed with the name you gave, and to keep scripts off the forms. The fourth is not necessary in the technical sense — the app works without it — but every value in it records a choice you made yourself, is readable only by your own browser, and is discarded when you clear your browsing data. There is no analytics or advertising storage here at all.
On that basis no consent banner is shown. If anything is added that tracks you or reports on you, this page changes first, and consent is asked for before it is set. This assessment is one we intend to have reviewed against the rules of each place the service is offered.
Who else touches your data
- Cloudflare — R2 object storage for the photographs and video, and Turnstile to keep bots off the public forms.
- Resend — sends the only two emails this service sends: your email verification code and your password reset code. Everything else the app tells you appears inside the app, not in your inbox.
- Google — only if you choose “Continue with Google”. Google tells us your name, your email address, that the address is verified, and an identifier for your Google account. We ask for nothing else, and get no access to your Google account itself.
- Our hosting provider — runs the application and its database.
Each is used to run the service and for nothing else. Where one of them holds data outside the UK or EEA, that transfer relies on the standard contractual protections that provider offers.
Rooms, links and search engines
A room link is unguessable, and for a room set to link access the link is the whole secret: anyone holding it can open the room. A room can also require a password, or admission by the photographer one person at a time.
We ask search engines not to crawl room links or invitations at all, and the responses carry an instruction not to index, cache or store images from them. Both are requests: a crawler that ignores them is not prevented from anything, and a room address that has been posted somewhere public can still show up as a bare link even when its contents are never read. Neither measure is what keeps a room private — the access check does that. Treat a room link the way you would treat the work inside it.
Your rights
You can ask for a copy of what we hold about you, ask for it to be corrected, ask for it to be deleted, or object to our holding it. Write to support@laqtaroom.com and we will respond within one month.
If a request concerns photographs or notes inside a photographer’s room, we will normally pass it to that photographer, since it is their material and theirs to decide. If you are in the UK and unhappy with how we have handled a request, you can complain to the Information Commissioner’s Office at ico.org.uk.
Deleting an account
There is no self-service delete button yet. Write to support@laqtaroom.com and we will disable the account and then erase it, along with your sessions, rooms, uploaded work and support history.
Some things outlive that moment, and we would rather list them than imply a clean sweep:
- What you contributed to other people’s rooms. A note or a pick you left in a room belonging to someone else stays in their room — it is part of their record of the job, not only yours. It is no longer linked to your account, but the name that was shown against it remains shown, because a conversation with the attributions stripped out is no longer a usable record for the person who owns it.
- Access and audit records. Entries in a room’s visit and download log keep the name given at the time, for the life of that room. The internal activity log keeps its entry, with whatever name was recorded, for 120 days from when it was written.
- Notifications already delivered to other people. A message in someone else’s notification list saying what you did keeps the name it was written with, and is erased when their account is.
- Files already in the trash, which are erased on their normal 10-day schedule.
- Database backups, kept for 14 days by default and overwritten on that rotation, so a copy persists until the last backup taken before the deletion ages out.
If any of these matters to you, say so when you write to us and we will tell you exactly what would remain and what can be done about it.
Changes
If this policy changes in a way that matters, the date at the top changes and account holders are told before it takes effect.