Help & FAQ
Everything you need to know about GhostClass.
Course Card Explained
Below is a sample course card with all features shown. Hover over the small orange and blue modifiers to see tooltips.
Data Structures & Algorithms
CSE301
32+2+1present8-2absent40+1total
Official 80%Tracking 82.5%
Safe (Official)
Can bunk
3
+ Tracking Data
Can bunk
4
Counts Legend
- 🟢 Green number (e.g. 32) = Official present count from EzyGo
- 🟠 Orange
+Nnext to Present = Correction entries that convert absences to present/DL (does NOT add to total) - 🔵 Blue
+Nnext to Present = Extra present classes you manually added (adds to total) - 🔴 Red number (e.g. 8) = Official absent count from EzyGo
- 🟠 Orange
-Nnext to Absent = Correction entries (cancels those absences) - 🔵 Blue
+Nnext to Absent = Extra absent classes (adds to total) - Total + Blue
+N= Official total + extra sessions added
Progress Bar Legend
- Solid purple bar = Official attendance percentage
- Striped purple overlay (going further right) = Tracking data GAIN (adjusted % is higher than official)
- Striped red overlay (going further right) = Tracking data LOSS (adjusted % is lower than official)
Bunk Calculator (dual panel)
- 🔵 Safe (Official) panel = Based only on data from EzyGo
- 🟣 + Tracking Data panel = Includes your manually tracked sessions
- Shows how many classes you can safely bunk (green) or must attend (amber) to stay at your target %
Correction vs Extra
Correction
- Used when EzyGo marked you absent but you were actually present
- Does NOT add to the total class count — it only adjusts present/absent counts
- Shown in orange on the course card
Example: "You attended class but EzyGo shows Absent. Add a Correction → Present to fix the percentage without affecting the total."
Extra
- Used for classes that EzyGo doesn't know about yet (newly held class not synced)
- ADDS to the total class count AND to present/absent
- Shown in blue on the course card
Example: "Professor held an extra class that hasn't appeared in EzyGo yet. Add an Extra → Present so GhostClass factors it in."
Attendance Chart Explained
The attendance chart gives you a quick visual overview of all your courses. Below is a sample chart showing all four possible combinations.
Target: 75%
CSE30182%
MAT20160%
PHY10178% → 85%
ENG40165% → 58%
Solid Green = Above targetSolid Red = Below targetStriped Green = Tracking gainStriped Red = Tracking lossDashed amber = Target %
Chart Legend
- 🟩 Solid Green = Above target (safe)
- 🟥 Solid Red = Below target (danger)
- 🟩 Striped Green on top = Tracking GAIN (adjusted % higher than official)
- 🟥 Striped Red on top = Tracking LOSS (adjusted % lower than official)
- 🟨 Dashed amber line = Your attendance target (default 75%)
Frequently Asked Questions
GhostClass shows your official data plus any manually tracked corrections or extras. The official (EzyGo) percentage is always shown; adjustments are displayed separately alongside it.
No. GhostClass is a read-only calculator. It cannot modify any records in your institution's system.
The bunk calculator tells you how many classes you can safely skip — or must attend — to stay at or above your target attendance percentage.
Update the target percentage from the header bar or the user profile dialog. The default is 75%.
GhostClass periodically fetches your latest attendance from EzyGo. If data looks stale, visit the dashboard and use the refresh option.
The instructor hasn't updated attendance records yet for that course in EzyGo. However, you can still manually add records.
All EzyGo API calls are queued through a server-side rate limiter (default: 3 concurrent requests) to avoid hitting EzyGo's rate limits. Early users in a burst get sub-2 s loads; later users in the same burst may wait a few extra seconds in the queue.
The original approach exposed the EzyGo bearer token in the browser's Network tab and JavaScript memory — trivially stealable via DevTools or XSS. GhostClass stores the token in an httpOnly cookie (AES-256-GCM encrypted) and proxies all EzyGo requests through the server, so the raw token is never visible in the browser. The trade-off is a small extra network hop (~10–50 ms) per request.
No. Your password is used once to authenticate with EzyGo and is never persisted. Only the resulting bearer token is stored (encrypted) in the database.
Need More Help?
Couldn't find what you were looking for?
Our team is happy to help. Reach out via the contact page and we'll get back to you as soon as possible.
Contact Us →