1. Our approach
We keep the public website simple, use few outside dependencies, request only needed browser permissions and keep private credentials away from public files.
2. How this portfolio works
The public homepage remains a lightweight site. Visitors do not need an account or payment form. A separate private editor uses Supabase authentication and a portfolio database; editing access is limited through database security policies. The intro, code rain and sounds run inside the visitor's browser.
3. Browser protection
The deployment includes security rules for HTTPS, allowed content, frames, file types, browser permissions and referrer information. These rules reduce common risks, but no website can promise complete protection.
4. Report a security problem
If you find a real security problem on shonkideveloper.com, email the affected page, steps to show the problem and possible impact. Do not view data that is not yours, damage the service, trick people or run destructive tests.
5. Links to project websites
The projects linked from this portfolio may use different hosting and security systems. A problem on a separate project should be reviewed with that project's owner and deployment in mind.