Skip to content

Prototype: fictional data, not a real service

Demo with made-up data. Do not enter real details: anyone can use this demo.

polder.tech: clickable prototype

A clickable prototype of the three sides of polder.tech, plus an explainer of who sees what. Made to show and discuss the design.

This is not a product and there is no real organisation. All names and data are invented. With the Demo API off, whatever you enter stays in your browser and is gone after a reload. With the Demo API on, the rooms run through a demo server with real end-to-end encryption: that server cannot read the messages.

Tour: the four pillars in 8 steps

For investors and unions. Worker, representative and platform, each with the one fact that matters. Arrow keys to page, Esc to stop.

Demo in 8 storiesStart the tour

Platform

Sees: that it gave every worker a code

Does not see: who uses the channel

a code, once

Worker

Sees: own rooms and the pseudonyms in them

Does not see: who talks to which representative

messages, end-to-end encrypted

polder.tech

Sees: pseudonym accounts, which rooms exist; in the pilot also who is in which room

Does not see: the content of messages, except in a consultation: there polder.tech reads along

only after your yes

Representative

Sees: who made contact, under a pseudonym

Does not see: workers' own rooms

State: only with a legal order

State

Sees: nothing by default

Does not see: message content: we do not have it, except what was said in a consultation

Consultation: only when you open one

  • Consultant (polder.tech): sees the content: polder.tech reads along
  • Platform: sees nothing of it (by design)
  • Representative: only what you hand over, with your yes
  • After the end: polder.tech keeps only role, date and route category
Who sees what, in one picture. The design, not a running service.

The parts

Walkthrough in the order of the demo plan (spec 08)

Walk the scenarios from top to bottom. Each step says what to show.

  1. 1. Onboarding

    1. Inside the platform's app: ‘Get code’
    2. Sign up with e-mail or phone (test phase; code in the demo inbox)
    3. Enter the platform's code (use the sample code)
    4. Choose pseudonym and language; country is separate from language
    5. Consent at A2 level, audio button, separate representative contact
    6. Platform console: nothing changed, there is no counter

  2. 2. Peer rooms

    1. Home: safety alert on top, batched admission, invitation
    2. Bezorgers Utrecht: threads, pins, ‘edited’, post a safety alert
    3. Language room Po polsku — Utrecht, with bridge role
    4. Announcement mode with an open window
    5. Open room: treat as public
    6. 1-to-1 with a colleague

  3. 3. Representative contact

    1. Registry: identical cards, random order, ‘why recognised’, opt-in per body
    2. Chat with Voorbeeldorganisatie A
    3. Body: intake by language
    4. Case with consent ledger, notes and CRM button
    5. Message to workers: opt-in only, equal quota, reach as a band
    6. Badge, role attestations, membership and export
    7. Questions and polls: results as bands, from 10 answers
    8. Statistics by region and sector, also public

  4. 4. Harassment report

    1. Report Zonnige Dakgoot's message (someone else's address); you choose where it goes
    2. Moderation: proposal, a second moderator confirms (four eyes)
    3. Help: talk to a polder.tech consultant
    4. Consultant desk: choose routes, refer on, end
    5. Moderation overview: age, four eyes, appeals

  5. 5. Platform console

    1. Evidence only; why there are no usage figures
    2. Developer portal: API cards, sandbox key, what you never get (mock)

  6. 6. Two evidence packs

    1. Evidence pack for the platform: no reports or moderation figures (placeholders)
    2. Evidence pack for the regulator: moderation in bands, no content or names (mock)
    3. polder.tech operations: recognitions, consultants, health

  7. 7. Worker leaves the platform

    1. Code no longer valid: what stays, objection, find a representative
    2. Leave yourself in two steps, save messages first

  8. 8. Social space

    1. Pinned event from a recognised body
    2. Events under Representatives (the hours statistic is not in this prototype)

  9. 9. What each party can see

    1. Switch perspective
    2. In the app: who sees what, remove a phone everywhere

Worker screens in Polish and Arabic (concept translation)

All screens