Stringer — Terms of Service
Version 2026-10-23. In force from 23 October 2026.
*Changed from version 2026-08-30: the operator's legal identity is corrected to Researchmatic Limited, trading as Bureau of Machine Affairs, with its company number and registered office. No other term has changed, and an acceptance of version 2026-08-30 stands as an acceptance of this version.*
This document is published at https://stringer.run/v0/terms, and as plain markdown at https://stringer.run/v0/terms.md. When you accept these terms, the version identifier above and the date you accepted are what we record — nothing else about the acceptance, and never a copy of this document as it stood on some other day.
Operator and licensor: Researchmatic Limited, trading as Bureau of Machine Affairs ("BMA", "we", "us"), a company incorporated in England and Wales (company number 05121736), whose registered office is at 212 St. Margarets Road, Twickenham, TW1 1NP, and which operates the Stringer platform.
Some terms below are not settled, and say so. Where that is the case there is a [TO BE COMPLETED: …] note in place of the term, rather than wording written as though the question had been answered. We would rather you could see the gap than infer a position we have not taken.
Structure. Part A binds everyone. Part B is for developers. Part C is for providers. Part D is for everyone again. They are separated because the two relationships are genuinely different — a developer buys, a provider earns — and merging them is how a platform ends up with one document that fits neither.
Part A — Terms that bind everyone
A1. What Stringer is, and what we are not
Stringer connects an AI agent (acting for a developer, who pays) with a body (a device, today a phone carried by a person, who earns) so the agent can obtain information about a physical place.
We are an intermediary.
- The contract for the sensing itself is between the developer and the provider. BMA is not a party to it.
- Our service is matching, escrow and settlement — bringing the two sides together and moving credit between them. We do not supply, perform, resell, or warrant the sensing. We do not take title to it.
- Our fee is consideration for that brokerage only, never for the underlying sensing.
- Consequently the provider, not BMA, is responsible for how a mission is performed, and a developer's recourse for the sensing itself is against the provider, with BMA facilitating settlement and disputes.
This mirrors how the money actually moves: the provider earns the mission value less our commission, and we never take the mission value as revenue. It is also the basis on which we treat our taxable supply as the commission and not the mission value.
A2. Current scope — read this before anything else
These terms govern a system that is very small, and we would rather say so than have you infer a maturity that does not exist.
- Coverage is prescriptive, not a list of places we serve. Anywhere with no rule against it is permitted, and the prohibitions do the work: sanctioned or hostile jurisdictions, recorded exclusion zones such as hospitals, schools and prisons, and places whose local law requires all-party consent to a recording. A refusal deliberately never names the place.
- Not every capability is reachable everywhere. Structured observations and sound are permitted by default. Raw video is prohibited inside the older city fences, and a mission that would open a microphone is refused where all-party recording consent is required — including a text mission that would be fulfilled by transcribing.
- Everything settles in platform credit. No money has ever moved through the system, and no withdrawal mechanism has ever operated.
- Availability is best-effort. There is no uptime commitment, no support commitment, and no service level.
A3. Accounts and credentials
- You are responsible for your access tokens. Rotate or revoke them at any time. Do not share them. Activity under your token is treated as yours.
- Sign-in is by emailed link. Keep your email account secure.
- An account may hold up to 50 active agents, and limits apply to how fast an account may call us. We may change them.
A4. Prohibited uses
You must not use Stringer, and must not instruct an agent to use Stringer:
- To target, follow, identify, photograph, wait for, or build a picture of a specific individual. This is the single most important prohibition in these terms. It applies whether the person is named, described, or picked out by what they are wearing or carrying.
- To capture inside a private space — a home, a workplace you are not entitled to be in, a medical or care setting, a school, a lavatory or a changing room — or anywhere a reasonable person would expect not to be filmed.
- To harass, intimidate, stalk, or place anyone under surveillance, including a provider.
- To circumvent the on-device privacy protections, to modify the app, or to present modified data as having come from a genuine device.
- To induce a provider into anything unlawful, dangerous, or dishonest — including trespass, a traffic offence, or misrepresenting who they are working for.
- To capture material relating to a person's health, ethnicity, religion, sexuality, political affiliation or trade-union membership, or to deliberately position a device where such material is what there is to see.
- To gather evidence for, or in furtherance of, a criminal offence.
- To resell, sublicense, or route third-party demand through your account without our written agreement.
- To scrape, probe, or infer the platform's coverage, supply density, or any provider's location beyond what an API deliberately returns.
Our screening is not a permission. We refuse missions our filters classify as person-targeting, and we re-screen every instruction sent to a provider mid-mission. Those filters are heuristics and they can be evaded. Passing them is not our approval, and does not shift responsibility from you to us.
A5. Reporting a problem
Today the only address we publish is beta@stringer.run.
[TO BE COMPLETED: a dedicated route for reporting abuse, reporting a safety incident, or serving a legal notice. There is not one today. This is a gap in the product, not in the drafting.]
Part B — Developer terms
B1. Missions and screening
Each mission you submit is screened before it is quoted. It may be refused because it targets an individual, because the location is outside our coverage, because your consent tier is not permitted there, or because the capability is not available. A refusal is not a judgement about you.
B2. You are responsible for what your agent does
An autonomous agent's actions are yours.
- You are responsible for every mission your agent submits, every prompt it writes, and every instruction it sends to a provider mid-mission — whether or not you saw it before it was sent, and whether or not you would have approved it.
- "The model decided to" is not a defence under these terms.
- If you configure your embodiment to accept missions with reduced screening, or none, you remain responsible for the outcome.
B3. What you receive, and what you must not claim about it
- You receive structured written observations, and on a media mission, a clip delivered to a storage location you control.
- Encrypted delivery means nobody but you can read the content. It does not mean the content provably came from a particular device. Nothing in this system signs anything. You must not represent our output as attested, device-proven, or tamper-proof to any third party.
- Redaction is performed on the device and we cannot verify it. We record the device's declaration. We do not certify it.
- Observation text is influenceable by whatever is in front of the camera. Anyone can write anything on a sign. Treat it as untrusted input to your systems.
B4. Your obligations for media you receive
If you request video or audio:
- You become a controller of that footage in your own right. It arrives at your storage, under your control, and our controls end at that point.
- You must have, and must be able to evidence, a lawful basis. The platform asks you to declare one from a short list. Declaring is not having, and we do not currently retain your declaration.
- You must not attempt to identify any individual appearing in it, nor undo the redaction.
B5. Credits, fees and money
- Credits are not money. In the current release they have no cash value and cannot be redeemed.
- Fulfilling a mission mints credit under per-account daily caps set by us. Minting rates are set by the platform and never by an account holder.
- We charge a commission on each settled mission and may charge a subscription.
- We may adjust caps, rates and the credit model. Credits may be forfeited on termination for abuse.
[TO BE COMPLETED: this section is drafted for a credit-only system. Enabling real money changes it fundamentally — whether a credit top-up is a multi-purpose voucher, whether we are handling client money, whether the float needs safeguarding, and whether the earning side sits inside the e-money perimeter. It must be re-drafted, not amended, before any cash flows.]
B6. The software licence
The Stringer platform software is proprietary and licensed under the terms in the LICENCE file. The MCP server component, which runs on your own machine and holds your private key, is licensed permissively under ISC — deliberately, so that a security claim you are asked to trust is one you can read and verify.
Part C — Provider terms
C1. What you are agreeing to
You install our app on your own device and carry it. When a mission is offered you decide whether to take it. You are never obliged to accept anything, and declining is free.
C2. Your status
You provide services as an independent contractor. You are responsible for your own tax and national insurance on anything you earn. Nothing in these terms creates an employment relationship, a partnership, or an agency.
[TO BE COMPLETED: whether a provider is a self-employed contractor, a worker or an employee under UK law — and whether that answer changes once credits become withdrawable — is not settled, and we are not going to paper over it. The statement above is what applies until it is. The facts that make it a real question are, on one side, that you supply your own device, that every mission is offered and never assigned, that declining is free and by design affects nothing, that there is no shift, rota, minimum or schedule, that you set the area you are willing to work in, that a mission can be abandoned part-way with pro-rata settlement, that you publish your own prices on the marketplace and are hired at the number you set, that you may answer any offer with a counter at your own figure, and that the owner of a device sets a price floor for it which no offer can go under — and, on the other, that the platform sets minting rates and caps and may change them, which prices only the credit you earn on your own missions and cannot touch paid work for a stranger, because that is escrowed at a price the requesting agent offers and you accept or counter, that a reputation score gates access to paid work automatically, that there is no right of substitution, that a requester issues instructions during a live mission, and that the platform mediates disputes and controls settlement.]
C3. Consent, and what you are told
Before you accept any mission you are shown what the requester will receive, what they will not, and anything that changes what they can do while you are out — including whether they can send you instructions and operate your camera. We record which version of that wording you agreed to.
You can stop any mission at any time, and you are paid for the part you completed.
C4. Your responsibilities while working
- Obey the law of the place you are in — traffic law, trespass, privacy, recording law, and any local restriction on filming.
- Do not enter private property you are not entitled to be in.
- Do not point the camera at an individual, do not follow anyone, and do not respond to an instruction that asks you to. If a requester asks you to target a person, refuse and report it. You will not be penalised for refusing.
- Do not put yourself in danger. No mission is worth an injury. Stopping is always allowed.
- Do not attempt to defeat the on-device privacy protections, run a modified app, or submit observations the device did not produce.
C5. Safety and risk
You perform physical activity in the real world at your own risk.
One fact worth stating plainly. A live-interactive mission lets a person you have never met direct where you walk and what you look at, in near-real time, in a city. That is materially different from being asked to go and photograph a shop front, and you should decide whether to accept one on that basis.
[TO BE COMPLETED: what duty of care, if any, we owe a provider walking to a location we sent them to; whether that changes when the requester is a stranger rather than the provider's own agent, and again when the requester is an autonomous agent with no human in the loop; whether insurance is required, and of whom; and what these terms must say about lone working, working after dark, or working in an area a provider does not know.]
C6. Ratings, reputation and exclusion
Requesters may rate you and leave a written note. Outcomes feed a reputation score which affects the work you are offered. A low score can exclude you from paid work from strangers, automatically.
A complaint and appeal process exists.
[TO BE COMPLETED: whether an automated exclusion of this kind is lawful without a human-review route, and what these terms must say about it. Note also that upholding a complaint currently has no financial consequence — the safety loop and the money loop are not connected.]
C7. Payment
- You earn platform credit on settlement, less our commission.
- No withdrawal mechanism has ever operated.
[TO BE COMPLETED: everything about withdrawal — timing, minimums, currency, fees, tax reporting, and the status of the balance before it is withdrawn. It must be drafted before the first withdrawal, not after.]
Part D — Terms that bind everyone again
D1. No warranty
The service is provided "as is" and "as available". We do not warrant that it will be uninterrupted, that a mission will find a provider, that an observation will be accurate, or that redaction or screening will catch everything.
D2. Liability
[TO BE COMPLETED: no limitation or exclusion of liability has been settled for these terms, and none is asserted here. The LICENCE file caps BMA's liability at one hundred pounds for the platform SOFTWARE; whether any cap, and what cap, is appropriate for a service involving physical activity by human beings is a separate question and is not answered here. The exposures the clause has to be drawn against are: physical harm to a provider performing a mission; harm to a bystander who is filmed, identified, or made the subject of a mission they never knew about; misuse of media by a developer after it has left our systems; a false claim about our security properties made by a developer to a third party; loss of a credit balance through a defect or a security failure; and regulatory action arising from a mission we screened and passed.]
D3. Suspension and termination
We may suspend or terminate an account for breach, abuse, or unlawful use, and may revoke its tokens.
[TO BE COMPLETED: notice, appeal, and what happens to a credit balance on termination.]
D4. Changes
We may change these terms. Every version carries the identifier and the date at the top of this document, and the version you accepted is what is recorded against your record. A later version does not retrospectively alter a consent you gave under an earlier one.
[TO BE COMPLETED: notice period and mechanism for a change.]
D5. Governing law
These terms and any dispute arising out of them (including non-contractual disputes) are governed by the law of England and Wales, and the courts of England and Wales have exclusive jurisdiction.
[TO BE COMPLETED: consumer-jurisdiction rules may override this for providers, and possibly for individual developers.]
Versions
- 2026-10-23 — in force from 23 October 2026. Corrects the operator's legal identity. Version 2026-08-30 described Bureau of Machine Affairs as a company in its own right; the operator is, and always was, Researchmatic Limited (company number 05121736), trading as Bureau of Machine Affairs, and its registered office is now stated. No other term changed. An acceptance of version 2026-08-30 stands as an acceptance of this version, and nobody who accepted it is asked to accept again.
- 2026-08-30 — in force from 30 August 2026. C2's analysis of what makes a provider's employment status a real question said, on the platform's side of the ledger, that you cannot set your own price. That stopped being true: providers publish their own prices on the marketplace and are hired at them, may counter any offer with their own figure, and a device owner sets a floor no offer can go under. The minting sentence was narrowed with it — minting prices own-mission credit only and cannot touch paid stranger work, which is escrowed at the price the agent offers and the provider accepts or counters. Owner ruling, 2026-08-30. No other term changed, and the question C2 raises is still open.
- 2026-08-29 — in force from 29 August 2026. The first version in force.
Before this version there was no published document. draft-2026-08-03 was an internal draft that never took effect and was never served. A record already filed against that identifier records what was actually put in front of that person at the time, and stays as it is.
The same document as plain text: /v0/terms.md