TechPSC Hall of Fame
We recognize people who help protect TechPSC students by responsibly reporting security issues, privacy risks, and product gaps before they can affect users. Recognition is public, respectful, and focused on safer releases.
We recognize people who help protect TechPSC students by responsibly reporting security issues, privacy risks, and product gaps before they can affect users. Recognition is public, respectful, and focused on safer releases.
We don't offer monetary rewards currently. Valid reports may receive public acknowledgement after the issue is fixed and safe to disclose.
Recognized for coordinated disclosure that helped TechPSC strengthen access control, platform privacy, and student trust.
These reports helped TechPSC make paid content and user information safer across the app and website.
A researcher reported the concerns directly to TechPSC so the team could investigate safely.
TechPSC improved how premium study content is protected for Pass members.
TechPSC improved how user information is protected behind the scenes.
TechPSC will keep reviewing security and privacy as the platform grows.
We keep public summaries simple and do not publish technical details that could be misused.
A responsible report helped TechPSC make premium study content safer for Pass members.
A responsible report helped TechPSC improve safeguards around user information.
Security reports are most helpful when they are clear, reproducible, and give the team time to fix before public sharing. Please avoid accessing, downloading, sharing, or posting real user data.
Send clear steps, affected areas, impact, and minimal proof-of-concept evidence without exposing user data.
We prioritize fixes that protect paid access, personal data, progress, account state, and exam content integrity.
We don't offer monetary rewards currently. Valid reports may be acknowledged on this page after the issue is fixed and disclosure is safe.
Tell us what kind of data or access may be exposed, without including private user records in the message.
Use a test account, screenshots with sensitive values blurred, and enough affected-area context for the team to reproduce safely.
Please allow TechPSC to investigate and deploy a fix before publishing details publicly.
Use a clear subject line such as Responsible Disclosure Report and include affected area, reproducible steps, impact, and your preferred public credit name.
Please do not perform denial-of-service testing, mass scraping, mail bombing, payment abuse, or testing that affects real users.