Who sees what
Choose a perspective. You see what that party can see, what it cannot, and where the honest limits are.
This describes the design, not a running service. ‘Concept — to confirm’ depends on open decisions.
Platform
Sees: that it gave every worker a code
Does not see: who uses the channel
Worker
Sees: own rooms and the pseudonyms in them
Does not see: who talks to which representative
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
Representative
Sees: who made contact, under a pseudonym
Does not see: workers' own rooms
State
Sees: nothing by default
Does not see: message content: we do not have it, except what was said in a consultation
Consultation (concept — to confirm): 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
Worker (and fellow workers in the same room)
Can see
- Own messages and rooms.
- The pseudonyms of people in rooms they joined.
- The public registry of recognised bodies.
- Own case files with a body.
Cannot see (by design)
- Real names of others (unless someone chooses to show it).
- Members of rooms they are not in.
- Who contacts which representative.
Honest limits
- A fellow member can take a screenshot and pass it on, also to the platform. No technology stops that.
- In small rooms people can guess who is who. That is why a hub or city room opens only from a minimum number of participants (20, concept — to confirm).
We do not give data to immigration or labour authorities unless a court or the law orders us to. We publish how often that happens.
In a consultation with a polder.tech consultant (concept — to confirm)
Only when the worker opens a consultation, alone or with the group. The consultant does nothing in the worker's name.
| Who | Sees in a consultation |
|---|---|
| Consultant (polder.tech) | The content of the consultation. In a consultation polder.tech reads along, because the consultant works for polder.tech. |
| Platform | Nothing. Designed so that the platform sees nothing of consultations: not that a worker asked, not how often, not about what. |
| Representative body | Only what the worker hands over, with the worker's consent. |
| polder.tech after the end | Only role, date and route category (concept — to confirm). |
Honest limits
- In a group consultation a colleague can pass on what was said.
- With a lawful order the state can demand what polder.tech keeps from a consultation.