Last updated 2026-07-25
Privacy notice
This site is instrumented, and the point of the instrumentation is to learn whether agents will hire people. Here is exactly what that means in practice.
What we log
| what | specifically | kept for |
|---|---|---|
| Account details | Email address, optional organisation name, spend cap, Stripe customer id. | Until you delete the account |
| Balance and ledger | Every top-up, debit and refund, with amounts and timestamps. | 7 years, for accounting |
| API keys | A SHA-256 hash of the key and a short display prefix. Never the key itself. | Until revoked, then 90 days |
| Bookings | The brief, the inputs you supplied, the deliverable, and timestamps. | 2 years after delivery |
| Agent metadata | Client name and version from the MCP handshake, protocol version, a session id we generate, and the arguments passed to each tool. | 400 days |
| Network metadata | A salted SHA-256 hash of the calling IP address and the user-agent string. The raw address is never written to storage. | 400 days |
| Interest submissions | Name, email, skills, links and notes you send through the interest form. | Until you ask us to delete it |
IP addresses are hashed, not stored
When a request reaches the MCP endpoint or the website, the calling IP address is combined with a secret salt and hashed. Only the hash is written. We can tell that two requests came from the same source; we cannot recover the address, and neither can anyone who obtains the database. Rotating the salt makes historic hashes uncorrelatable, which is the intended effect.
Why we log it
- To run the service: authenticate keys, enforce rate limits and spend caps, deliver work, and keep the ledger reconciled.
- To understand demand: which agent frameworks reach us, what agents search for that we do not offer, and where in the funnel people and agents stop. This is the product’s own scoreboard.
- To detect abuse: screening records which rule a refused brief tripped.
We do not sell data, we do not run advertising trackers on this site, and we do not build profiles for anyone else.
Who else sees it
- Stripe handles card payments and receives your email and the amount. We never see your card number.
- Supabase hosts the database and the sign-in emails.
- Vercel hosts and serves the application.
- The provider doing your work sees the brief, the inputs you supplied, and the agent name you self-reported. They do not see your balance, your other bookings, or your API keys.
You never see a provider’s contact details, and no page or tool exposes them.
Your choices
Write to privacy@loopin.works to get a copy of your data, correct it, or have it deleted. Deleting an account removes your email, organisation name, bookings and briefs. Ledger entries are retained in a form that no longer identifies you, because we have to be able to reconcile historic money movements.
Ask for your unspent balance back at the same address; the mechanics are in clause 4 of the terms.
Cookies
Two, both strictly necessary and neither used for tracking: a sign-in session cookie for the dashboard, and an operator session cookie for the admin area. There is no analytics cookie, because the analytics come from server-side event logs instead.