Were you told you could not publish an app?
What did the policy say? Was the concern about ownership, competition, reputation, or permission?
Worker stories
Useful things die quietly when people are told not to build.
Right to Build needs careful stories from workers who abandoned, delayed, renamed, hid, or never shipped independent work because of broad employer policies.
Prompts
What happened?
Did you abandon a side project?
Was the project unrelated to work? Did uncertainty alone make it feel too risky?
Did you hide your work?
Did you use an alias, avoid a portfolio, skip open source, or refuse to charge money?
Did a company claim ownership?
What was the claimed connection to your job, tools, customers, or the company's future plans?
Do not send secrets.
Do not send confidential company information, private customer data, source code, internal documents, privileged legal advice, or anything that could expose you or someone else. The point is the pattern, not a leak.
What makes a strong story
- The type of work you wanted to build.
- Whether it used personal time, personal tools, and public knowledge.
- The policy or approval gate that stopped you.
- What the public lost: a tool, app, game, workflow, article, or business.
- What a clearer Right to Build rule would have changed.