Kickstarter ‘Bug’ Exposed Projects
A security lapse at the popular crowd-funding website Kickstarter.com exposed more than 70,000 project ideas that weren't ready to be viewed. — The information that could be seen didn't include credit-card numbers or other sensitive personal details …
Context & Ripple Effects
Kickstarter entered 2012 with unusually rapid growth, record-breaking campaigns and growing mainstream attention; its role as a funding channel made creator confidence part of the platform’s operating foundation.
The lapse exposes a weakness in the boundary between draft and public project pages. Although the disclosed material excluded payment and sensitive personal data, unpublished ideas are the asset creators expect Kickstarter to protect before launch.
First-order effects
- More than 70,000 creators’ unpublished project ideas became visible, compromising the confidentiality of projects that were not ready for public scrutiny.
- Kickstarter faces immediate pressure to restore the access controls that distinguish private project preparation from public fundraising.
Second-order effects
- Creators planning launches may reassess what they upload before publication, making confidence in Kickstarter’s privacy controls a practical condition of using the platform.
- Because payment details were not exposed, Kickstarter’s immediate response is centered on project confidentiality and permission design rather than card-data remediation.
Third-order effects
- As crowdfunding becomes a mainstream financing venue, platforms’ treatment of pre-launch material becomes a competitive trust issue alongside their ability to attract backers.
- The incident points to a broader shift toward treating publication status as a security-sensitive permission boundary, not merely a product-interface setting.
The trend: Crowdfunding platforms are becoming custodians of commercially sensitive pre-launch information, making granular access control part of platform trust.