Platform brief 02
Blind
Blind tries to solve the hardest professional-network problem: letting workers speak about employers while proving they are actually workers.
Architecture
Anonymity is a workflow, not a mood.
Blind's central promise is separation: verify a work affiliation, then let the user post under a handle rather than a real name. That design is meaningfully different from a public resume network. It reduces the direct identity link that makes many workplace discussions impossible elsewhere.
The remaining risk sits in content and operations. Posts, comments, and direct messages still exist on servers. A person can also reveal themselves through details that no cryptographic design can hide.
Separation model
Work email proves affiliation.
Handle is meant to stand apart from the email identity.
Posts gather around company, industry, and compensation topics.
Platform still stores and reviews content for safety and policy.
An anonymous workplace forum does not remove identity risk. It moves the risk from account fields into language, timing, and detail.
What the graph contains
| Data type | Risk level | What to watch |
|---|---|---|
| Company affiliation | Medium | The employer domain is the ticket into the room. It is also the strongest contextual clue. |
| Posts and comments | High | Unique events, office locations, dates, and writing style can identify a person. |
| Direct messages | Medium | Private does not necessarily mean end-to-end encrypted or invisible to operations. |
| Device and session data | Medium | Security logs and abuse controls may preserve technical identifiers. |
| Real-name profile | Low | The product does not depend on a public legal-name resume. |
Risk pressure
Use pattern
Good for compensation truth. Bad for confessions.
Blind is strongest when users share salary ranges, promotion norms, interview loops, or broad workplace sentiment. It is weakest when posts describe rare incidents, small teams, legal disputes, or anything an employer could triangulate from timing.
- Use a handle that does not appear anywhere else.
- Remove dates, team names, project labels, and office-specific details.
- Treat direct messages as stored platform content.
- Do not post from a work network when the topic is sensitive.
Verdict
Blind earns credit for designing around anonymity rather than pretending a real-name profile can become private later. The tradeoff is that the most sensitive data is the user's own writing. The product can separate identity fields; it cannot neutralize identifying detail.