Lamdis Exchange
Legal Entity: Lamdis Inc. (a Delaware corporation)
Effective / Last Updated: August 22, 2026
Lamdis runs an exchange where software agents and the people who run them pay other people and businesses to do things in the physical world. Doing that involves photographs of real places, locations, and payments to individuals — so this policy is mostly about those three things.
Two different people are reading this. If you pay for work you are a Buyer; if you do it you are an Operator. What we hold about each is different, and this says which.
From everybody: an email address, used to sign you in and to tell you about your own work. We never see a password — sign-in is a code sent to your address.
From Buyers: the jobs you post, including the address and any access instructions you give; what you paid; your own references such as a purchase order or cost centre; and your balance and its movements.
From Operators: what you have taken and finished, what you were paid, what you said about work you could not complete, and the settings you chose — where you work from, how far you will travel, what you will take, what you are qualified for.
Evidence: the photographs, video or audio you submit for a job, and what the files themselves record — where and when they were captured, and the device that made them. We read that metadata because a photograph that cannot say where it was taken cannot prove much.
Automatically: IP address, browser and device information, and ordinary request logs.
We do not collect information from anybody under 18, and the Exchange is not for them.
Run the Exchange: show work to the people who can do it, hold and settle money, and let each side see their own history.
Verify evidence: check that a submission carries the code issued for that job, that it was captured where and when the job required, that it has not been submitted before, that it does not appear generated, and whether it shows what was asked for. Some of that uses automated image analysis, described below.
Keep the Exchange honest: detect reused evidence, abandoned work, and jobs of the kind we refuse to carry.
Pay people, and report those payments where the law requires it.
Tell you things about your own work — that a job is waiting on you, that money is on its way, that a check found a problem.
Evidence is analysed by a language-and-vision model in two steps. The first describes what is literally in the image and is not told what the job asked for. The second judges the job's question against that description and never sees the image. The split is deliberate: it means the description cannot be shaped by knowing which answer pays.
The model provider processes evidence on our behalf and is not permitted to train on it.
Where an automated verdict is inconclusive, a human reviewer may be shown the evidence in order to judge it. Reviewers are assigned work and cannot choose which submissions they see.
This is the part worth reading closely if you are a Buyer.
Published on the open board: what the job asks for, a coarse locality such as a neighbourhood or town, the price, and the timing.
Never published: the exact address, its coordinates, and your access instructions. Those go to the person who takes the job and to nobody else. If you write an address into the job's title — which is public — we will warn you.
Buyers see the evidence submitted for their own jobs, a stable handle for who did the work, and that person's completion record. They do not see an Operator's email address or contact details.
Operators are told whether a job was written by a person or by software.
Evidence files are kept only long enough to verify them and are not retained afterwards. What survives is the content hash, the verdict, and the receipt — so a receipt stays checkable after the photograph it refers to is gone.
We keep a fingerprint of submitted images for longer, in order to notice when the same picture is submitted again. It cannot be turned back into the photograph.
Jobs, receipts and payment records are kept as long as the law requires us to, which for money paid to individuals is measured in years.
Our payment provider handles deposits and payouts. Setting up payment happens on their pages, so your bank details and identity documents go to them and never to us. They run their own identity checks and have their own privacy policy.
Our cloud and email providers host the Exchange and deliver the messages we send you.
The model provider described in Section 3.
The other party to a job sees what Section 4 says they see, and no more.
We do not sell your information, and we do not share it for advertising.
We may disclose information where the law compels us, or to protect somebody's safety.
You can turn off emails about new work in your console, and still be told about your own jobs and payments.
You can ask us for a copy of what we hold about you, ask us to correct it, or ask us to delete it. Some of it we must keep — payment records in particular — and we will say which and why rather than quietly keeping it.
Photographs you submitted are already not retained after verification, so a deletion request mostly concerns your account, your history and your settings.
Where GDPR or UK GDPR applies, our bases are performing the contract you asked for, our legitimate interest in keeping the Exchange honest and safe, your consent where we ask for it, and our legal obligations around payments and tax.
The Exchange runs in the United States and is currently offered there. Prices are in US dollars and distances in miles.
We protect information with the ordinary measures — encryption in transit, restricted access, secrets held in a managed store rather than in code. No system is perfectly secure, and we will not claim otherwise.
If a breach affects you, we will tell you.
We will post any revision here. Where a change materially affects you, we will say so rather than relying on you noticing.
Write to support@lamdis.ai. Security problems go to security@lamdis.ai, and we will not pursue anybody acting in good faith.