CLCTN · IDEA BACKLOG · ON-DEVICE ML · NOT YET COMMITTED

Little brains we might borrow.

Desert Ant Labs ships small on-device models as drop-in SDKs for iOS, Android and web. Three of the seven are interesting to CLCTN, one of those is interesting enough to plan around, and the rest are noise for a collection app. Nothing on this page is a decision — it is a page of maybes kept in one place so the C2C conversation does not restart from zero.

The reason it is worth a page at all is the commercial shape: on-device means no marginal server cost, no data leaving the phone, and it works offline — which is the same near-zero-infra posture the Technical Blueprint already commits to. A cloud moderation or PII API would break that posture; this does not.

00 · WHY THIS VENDOR IS EVEN ON THE PAGE

Four facts, each of which would individually be enough to disqualify most vendors if it were the other way round.

{{ w.k }}

{{ w.t }}

{{ w.b }}

01 · THE WHOLE CATALOGUE, TRIAGED

Seven products. The skip rows are listed rather than omitted so nobody re-evaluates them in six months — the audio models are for editors and recorders, and CLCTN is neither.

{{ m.name }}

{{ m.does }}

{{ m.forUs }}

{{ m.avail }}

{{ m.verdict }}

02 · REDACT — THE ONLY ONE WORTH PLANNING AROUND

The obvious framing is privacy hygiene. The framing that actually justifies the integration is revenue protection: the day CLCTN takes a cut of a sale, every buyer and seller has an incentive to move the deal off-platform, and the way they do it is by typing a phone number into a chat box. Redact catches that at the keyboard, on the device, in 24 languages.

This is the leak Vinted spends real money fighting. Doing it on-device is strictly better than doing it server-side: it is cheaper, it works before the message is sent rather than after, and it means the PII never reaches our infrastructure — so the GDPR answer stops being "we process it carefully" and becomes "we do not process it."

{{ r.n }}

{{ r.title }}

{{ r.when }}

THE HOOK

{{ r.hook }}

BEHAVIOUR

{{ r.behaviour }}

WHY NOT THE OBVIOUS WAY

{{ r.trap }}

03 · THE WATCH LIST

Both of these are listed as unreleased on every platform. Neither is plannable, both change what we would build if they land — so they get a note rather than a slot.

{{ w.name }}

{{ w.status }}

{{ w.body }}

IF IT SHIPS, IT REPLACES

{{ w.replaces }}

04 · WHAT WOULD HAVE TO BE TRUE

Open questions, in the order they would need answering. Items one and two can be settled in an afternoon with the public SDK and would tell us whether the rest of this page matters.

{{ q.n }}

{{ q.q }}

{{ q.why }}