Reporting a Security Hole
Found a security hole in Hyper Sheets? Tell us first, privately, so we can close it before anyone misuses it. This page explains how, where the limits are, and what we give as thanks.
In effect since 10 October 2026
The short version
- Report by email. Write to [email protected]. Your report is read by the person who runs Hyper Sheets.
- Use your own accounts. Test with accounts you own. Never open, change or delete anyone else's data.
- We will not come after you. If you follow the rules on this page in good faith, we consider your testing authorized.
- No money, but a badge and coins. We cannot pay yet. A valid report earns the secret Ethical Hacker badge, coins and a place on the thanks list.
1. What you may test
- learnhypersheets.com, including the web app (PWA) and the Android app on Google Play.
- Its API at api-prod.learnhypersheets.com.
- belajarweb.dev.
Anything else, including the third-party services we use (such as Cloudflare, Google, Google Play, payment providers and Roblox), is not ours to authorize. Report holes in those services to their owners.
2. Rules while testing
- Test only with accounts you own. To test access between accounts, make a second account of your own.
- Do not open, change, download or delete anyone else's data. Many people on Hyper Sheets are students, children among them.
- If you see someone else's data by accident, stop there, do not keep or share it, and tell us in your report what you saw.
- Prove the hole exists and stop. Do not use it further, and do not keep access.
- Do not load the service: no load testing, no denial of service, no high-volume automated scanning.
- No spam, no phishing, no tricking learners or staff (social engineering).
- Keep the hole private until we fix it, or until 90 days after your report, whichever comes first. If a fix needs longer, we will talk it through with you.
3. How to report
Email [email protected], in English or Bahasa Indonesia. Include:
- where the hole is (the page address or endpoint) and what kind it is;
- the steps to reproduce it, with proof such as screenshots or requests;
- its impact: what someone with bad intent could do with it;
- your Hyper Sheets username, if you would like the badge and coins;
- the name or handle for the thanks list, or that you would rather stay anonymous.
Hyper Sheets is run by one person, so please be patient. We aim to reply within 7 days, to tell you when the hole is closed, and to explain if we think the report is not a security issue.
4. We will not come after you
If you test and report in good faith and follow the rules on this page, we consider your testing authorized. We will not take legal action or report you to the authorities over it. If someone else raises it, we will state that you acted with our permission.
This covers only the systems listed under What you may test. We cannot give permission on anyone else's behalf.
5. Our thanks
We are a small project with no funding, so we do not pay money for reports. For a valid report of something not reported before, we give:
- the secret Ethical Hacker badge on your Hyper Sheets profile, which cannot be earned any other way;
- coins, more for a hole with more impact. They are bound to your account and cannot be gifted to another;
- a place on the thanks list below, if you want one.
Rewards are at our discretion. Each hole is rewarded once, to the first reporter. Like all coins and badges they are virtual and cannot be exchanged for money (see the Terms of Service).
6. What we do not count as a hole
These usually earn nothing unless you show real impact:
- missing or loose email records (SPF, DKIM, DMARC);
- missing security headers or cookie flags, without a working attack;
- clickjacking on pages with no sensitive action;
- CSRF on sign in or sign out;
- visible software versions or error messages, and usernames that are public anyway;
- self-XSS, which can only reach yourself;
- rate limits on endpoints where they have no impact;
- automated scanner output without proof the hole can be used;
- holes that need a victim's already compromised or rooted device, or a very old browser;
- denial of service, social engineering and physical access.
7. Thanks list
People who reported a hole responsibly and agreed to be named. Thank you for keeping this place to learn safe.
No names here yet. Yours could be the first.
What changed
- 10 October 2026: This page was published, along with security.txt.